Create the protected source package

Export Translation Content

Select published source pages, target languages, file layout, and the exact content families allowed into a translation round, then download a protected package that can return safely through StagLingo Import.

Export source content

Add the exact pages and target languages for this batch.

Open Tools → StagLingo → Export. The main panel keeps page and language selection visible while less common controls remain inside Advanced export settings.

  1. 01

    Enter one same-site default-language URL or published content ID per line.

  2. 02

    Keep the request within the maximum of 100 page entries.

  3. 03

    Select at least one target language detected from TranslatePress.

  4. 04

    Check each locale's Published or Unpublished status before assuming its public URL is ready.

  5. 05

    Order languages by configured order, language name, or locale shortcode when that helps divide later work.

  6. 06

    Use Select all or Deselect all to reset the language group quickly.

StagLingo Export page for entering source URLs and selecting TranslatePress target languages
Use the default-language source URL—not a manually constructed translated URL. Download a current inventory from Page URLs and Content Discovery when preparing a larger batch.
Advanced export settings

Choose what StagLingo reads and how the files are grouped.

Export mode controls whether current translations are read. Delivery controls whether the output includes the protected AI handoff files. Layout changes package organization without removing protected CSV identity columns.

Recommended mode

Fast blank export

Performs one default-language page request and one DOM extraction regardless of how many language columns are selected. It does not delete or alter existing translations; only later non-empty reviewed cells can be written.

Audit mode

Include existing translations

Reads the selected locale dictionaries, Translation Blocks, Gettext, and translated URL slugs. Use it when current translations must appear in the files for review or correction.

Recommended delivery

AI Work Package ZIP

Adds the batch manifest and workflow instructions required for a protected Skill handoff while honoring the selected CSV layout.

File-only delivery

Standard CSV export

Returns the selected CSV organization without the self-describing AI Work Package wrapper. Use it only when your process already handles the protected file contract.

Default

Per language

One ZIP, one CSV per locale, all selected URLs in each language file.

Page packages

Per page

One transport ZIP contains one upload-ready page ZIP with all selected languages per URL.

Parallel page work

Page folders

One outer ZIP, one folder per source URL, separate language CSVs inside each folder.

Single table

Combined CSV

Every selected page and language column is kept in one CSV.

StagLingo advanced Export settings for export mode, delivery type, and CSV file layout
Content scope · Part 1

Include the article and the page interface around it.

The Recommended complete-page preset covers main content and the surrounding WordPress, theme, and builder fields most likely to appear to a visitor. Every family is classified separately to avoid overlapping writes.

Article fields

Main page content

  • Headings, paragraphs, and lists
  • Tables and captions
  • Links and emphasized text
  • WordPress title and manual excerpt
Navigation context

Page orientation

  • Header and primary navigation
  • Breadcrumb labels and current title
  • Table of contents
  • Previous and next article navigation
Generated metadata

Author and date text

  • Author and byline widgets
  • Publication dates
  • Updated-date wording
  • Locale-formatted metadata identities
Interactive regions

Forms and notices

  • Contact and subscription form text
  • Search controls
  • Banners and notices
  • Server-rendered popups and dialogs
Shared regions

Footer and templates

  • Footer menus and copyright text
  • Sidebars
  • Remaining reusable UI
  • Custom builder-widget safety net
Fallback

Unmatched visible text

If no standard main-content wrapper exists, unmatched rendered text safely falls back to the Main page/body content family.

First part of StagLingo Export content scope covering article, WordPress, theme, builder, and page interface text
Keep WordPress title selected for dynamic H1 and title mirrors. Keep Table of contents selected whenever later heading revisions must also update generated TOC records.
Second part of StagLingo Export content scope covering image, accessibility, form, SEO, social, and URL fields
Content scope · Part 2

Add attributes, search metadata, social fields, and URL slugs deliberately.

These values may not appear as ordinary visible paragraphs, but they affect accessibility, search presentation, sharing, forms, and language-specific URLs.

  1. 01

    Keep Current-page image ALT text selected for featured and article/body images owned by the current page.

  2. 02

    Select Related/listing card image ALT only when cross-post and rotating-card ownership should enter this package.

  3. 03

    Include image title, aria-label, other element title attributes, and form placeholders or button values as needed.

  4. 04

    Keep rendered SEO title, meta description, Open Graph, and X/Twitter metadata in a complete-page review.

  5. 05

    Select translated page URL slug only when the TranslatePress SEO Pack slug API is detected.

Related or listing-card image ALT is intentionally excluded from the recommended presets because the image can belong to another post and the card may rotate between requests. Current-page body images remain part of the safe default.
When current translations are included

Choose the audit scope by what reviewers must still be allowed to change.

Existing-translation scope affects only Include existing translations. Fast blank export always includes every selected source because it deliberately avoids reading current target-language storage.

Reduced scope

Missing or suspicious

Omits complete rows that pass mechanical checks and includes missing, unreviewed, or mechanically suspicious language cells.

Reduced scope

Missing only

Includes rows with no usable translation in at least one selected language. It is not a semantic quality audit.

The two reduced scopes write mechanically accepted cells as /. Those cells are protected from change during Import even when their meaning is wrong. Use All selected strings when semantic review is the goal.

Optional page exclusions

Leave the field blank to scan the full rendered body. To exclude a site-specific region that should never enter the CSV, use comma-separated simple selectors: a tag, .class, #id, tag.class, or tag#id. Test exclusions on a small page before applying them broadly.

Do not break row identity

Translate target cells while preserving the five protected columns.

Every exported CSV begins with the same identity contract. The chosen layout may divide pages and languages differently, but it never changes what Import uses to prove the source, owner, and row are still valid.

post_id

Resolved WordPress content owner.

source_url

Same-site default-language page.

content_type

Semantic and storage-owner class.

exact_english_source

Immutable source value for this row.

source_hash

Integrity guard for the exact source.

01

Upload the complete ZIP

Use the AI Work Package with the translatepress-ai-work-batch Skill. Do not upload an arbitrary subset or move rows between source files.

02

Preserve protected HTML

Inline-parent rows can control complete sentence order around links. Keep their HTML and adjacent anchor relationship intact.

03

Return one reviewed package

Download the import-ready reviewed ZIP and pass it through StagLingo Import for validation, backup, transactional writing, and read-back.