SEO settings before the first job

Use one supported SEO plugin for each page: Rank Math, Yoast SEO, SEOPress or All in One SEO. Enable SEO metadata translation in Translator settings, then confirm the target language is enabled and indexable in the multilingual plugin.

Metadata covered

Translator can localize supported SEO titles, meta descriptions and compatible social fields. The exact fields depend on the active SEO plugin. Schema IDs, technical settings and generated canonical/hreflang relationships remain under WordPress, the SEO plugin and the multilingual plugin.

URL slugs

1. Enable Translate URL slugs.
2. Keep the source slug unchanged.
3. Let the multilingual plugin add the configured language directory, subdomain or domain.
4. Preview the target URL.
5. After a structural slug change, save Permalinks if WordPress requires rewrite refresh.
6. Verify internal links, canonical and hreflang.

Do not manually add a second language prefix inside the translated slug. Avoid changing a published slug without a redirect plan.

Media and ALT text

Translate ALT text only when it communicates image meaning. Decorative images should have empty ALT text. Product/gallery images may be shared across languages or linked through language-specific attachments depending on the multilingual plugin. Verify the target image ID, filename strategy, caption, title and ALT text.

Menus and homepage assignment

Translating a page does not automatically create every multilingual menu configuration. In Polylang/WPML, create or assign the target-language menu to the same theme location and link target-language menu items. Assign the correct translated front page if the system uses separate posts. TranslatePress normally translates rendered menu strings through its dictionary.

Dynamic and global content

Headers, footers, popups, forms, cookie notices and theme option strings may live outside the current page. Translate them through their own public post type, builder template, string registry or TranslatePress rendered-string workflow. Do not duplicate global templates unless the active multilingual system requires it.

Pre-publication page review

• Correct target language, status, author and publication date.
• Correct title, headings, body text and calls to action.
• All internal links point to the appropriate language where available.
• Forms send, validation messages display and thank-you routes work.
• Desktop, tablet and mobile layouts match the source.
• SEO title/description, canonical, hreflang and social preview are correct.
• Images load and meaningful ALT text is localized.

WooCommerce publication review

• Product relationship is native to the multilingual commerce stack.
• Price, stock, SKU, tax and variations remain synchronized.
• Product title, descriptions, attributes and tabs are localized.
• Cart, checkout, account and email language behavior is correct.

After publishing

1. Open the public target URL in a signed-out browser.
2. Test the language switcher in both directions.
3. Purge page, object and CDN caches.
4. Recheck source and target after cache regeneration.
5. Submit or refresh the sitemap only after the target is final.