Rebuild an outdated content skeleton

A skeleton preserves the markup and placeholder positions used to reconstruct translated structured content. Suspect it when layout changes appear in the base language but the translated page keeps an older component order or structure.

Confirm the symptom

1. Compare the current base editor content with both public language variants.
2. Separate stale page-cache HTML from stored structural output.
3. Check whether the content was updated through a normal WordPress save.
4. Confirm the post type and content part remain enabled.
5. Review recent builder, shortcode, or parser integration changes.

Re-extract safely

Create a backup, then save the current base-language object through its supported editor or programmatic save path. This allows POM Translate to parse the current structure and source values.

Review the Translation Manager afterward. New or changed source blocks may need fresh translations; do not assume old translations can be mapped safely after major layout changes.

If only custom builder fields are stale, verify their metadata or shortcode registration loads before the save. Do not edit the skeleton table manually or remove placeholder tokens from translations.

Clear the affected rendered-content and page caches, then test nested formatting, links, repeated modules, and shortcodes. Use Reset translation storage only for an intentional complete rebuild, never for one stale object.