Verify hreflang and alternate-language links
POM Translate writes alternate links in the public document head for the current route. Each link points to the localized version of the same base object.
Generated language codes
For every available locale, POM Translate emits its normalized regional code, such as en-GB or es-ES.
When only one configured locale uses a language, it also emits the short language code, such as en or es. If multiple regional locales share that language, the ambiguous short code is omitted.
An x-default alternate points to the configured base locale.
Context and exclusions
Alternates are generated for the same contexts used by canonical resolution: front page, singular content, terms, archives, authors, search, and pagination.
Locales excluded from the current post or term context are removed before links are built. A feed, embed, administration screen, or route without a resolvable canonical does not receive these head links.
Review the cluster
- Open one localized page.
- Inspect every
rel="alternate"link. - Confirm each URL resolves with status 200.
- Check that every indexable language page lists the same cluster.
- Confirm each regional code uses a hyphen and correct casing.
- Verify
x-defaultpoints to the intended base route. - Repeat for a term archive and a paginated route.
The <html lang> value is also normalized for the active locale, and dir follows WordPress RTL detection.
Translation completeness
Available languages are eligible for alternates even when some fields fall back to the source. POM Translate does not infer SEO readiness from translation status.
Exclude the locale from that object or finish the translation before exposing a misleading alternate. If the route must remain accessible but not searchable, manage its robots directive through the SEO plugin and review whether it should stay in the alternate cluster.
Rank Math sitemap alternates reuse the same localized URL map. Head alternates remain the primary behavior for both supported SEO integrations.