Choose title, content, excerpt, and meta by post type
Each enabled post type has four independent source-part controls. Use them to keep the translation editor focused on text that the type actually renders.
Field behavior
| Control | Source value | Collection rule |
|---|---|---|
| Title | WordPress post title | Added when enabled and non-empty |
| Content | Main post content | Parsed into translatable segments when enabled |
| Excerpt | WordPress excerpt | Added when enabled and non-empty |
| Meta | Registered post-meta keys | Added only for approved, non-empty values |
All four controls default to enabled for a newly encountered post type. They are displayed only while the type itself is enabled, except that Pages are permanently enabled and therefore always expose their field choices.
Configure a lean policy
- Go to Settings → POM Translate → Content types.
- Expand the decision for the relevant post type by enabling the type if necessary.
- Leave Title on when the name appears in cards, archives, navigation, headings, or SEO output.
- Turn Content off only if the main editor is unused or contains no language-dependent output.
- Keep Excerpt on when summaries are displayed; otherwise remove it from the translation workload.
- Enable Meta only after confirming which custom keys are registered.
- Save the settings and reload the page to verify the values persisted.
- Save one source object and inspect its rows in Translate contents.
Effects of changing a part
On the next eligible save, POM Translate rebuilds the stored representation for that object using the active parts. A disabled title or excerpt is no longer collected. Content parsing and its structural skeleton stop when Content is off. Meta stops registered custom-field values from participating.
This reconciliation is object-specific: changing the setting does not immediately revisit every existing post of the type. Plan source saves before judging the result on older content.
Avoid accidental gaps
A post type may use information outside the four familiar WordPress fields. A builder can store structured data in the main content, in metadata, or through an integration-specific parser. Determine where the source actually lives before switching a part off.
Test an archive card, a single object, search results, and SEO output in both source and target languages. A page that looks correct in its main body can still expose an untranslated title or excerpt elsewhere.