Content Scanning
How Pages, Posts, builders and fields become translation segments.
The scanner converts WordPress content into stable translatable segments.
Open Instant Languages → Content to scan individual content or scan the complete site.
Supported content types
The core workflow scans:
- Pages
- Posts
- configured Blog / Posts page
- Classic Editor content
- Gutenberg blocks
- Elementor content
- page/post titles
- excerpts and generated excerpts
- selected attributes such as alt/title/placeholder/aria labels
Elementor
The scanner recognizes standard Elementor fields and uses broader human-text detection for third-party/add-on widgets while excluding technical values such as CSS, JSON-like settings, URLs and configuration data.
Repeater/array values are also inspected because many Elementor add-ons store card/tab/list text inside nested arrays.
Technical-data filtering
The scanner deliberately excludes many values that should not be translated, including:
- CSS/JavaScript configuration
- script/style/SVG blocks
- obvious JSON/serialized configuration
- URL-only values
- email-only values
- shortcode-only values where the shortcode itself should be preserved
Rescanning
Rescanning refreshes the source inventory. Stable element/field identities are used where possible so existing translations remain attached. Obsolete scanner-generated segments can be pruned when the underlying source disappears.
Visual-discovery segments created to support runtime content are preserved when appropriate so hard-to-detect third-party text is not lost on the next normal scan.