Start with the relationship, then generate the tag
A multilingual site can have valid-looking hreflang markup and still point to the wrong pages. The difficult decision happens earlier: does this regional page represent the same content as the English page? A similar URL or translated title is a useful clue, but it is a poor substitute for a reviewed relationship.
Our International WordPress case study describes this problem across a multisite network and a separate installation. The engineering work addressed relationship data, auditing and controlled output. It should be read as that implementation story, rather than a claim about current search rankings.
Give each match a reviewable record
A useful audit starts with a table: source page, regional page, language or locale, how the match was proposed, review state and the last relevant change. Keep a proposed match distinct from an approved one. That distinction makes it possible to inspect the system without publishing every suggestion.
Decide what happens when a page is removed, redirected or substantially rewritten. A relationship that was correct at launch can become wrong later. The maintenance process needs an owner and a way to identify affected records; it cannot depend on everyone remembering the original migration.
Check the complete set
Google's guidance calls for fully qualified alternate URLs, self-references and reciprocal relationships between variants. Alternate pages may live on different domains. These requirements make a relationship audit useful beyond a single WordPress installation.
For a release review, sample complete groups rather than isolated tags. Follow each destination, inspect its intended content and compare the emitted relationships with the approved records. An incomplete translation should remain an explicit gap instead of being filled with an unrelated regional homepage.
Make publication a separate decision
The audit interface and public output serve different purposes. Editors need context, warnings and unresolved candidates. Visitors and crawlers need the approved result. Keeping those paths separate gives the team room to review uncertainty without exposing it as a finished relationship.
If you are planning similar work, bring a small sample of real pages, the regional ownership model and an explanation of how translations are published. That is usually more useful for scoping than a promise to install an SEO plugin. The first deliverable should establish how relationships become trustworthy and stay maintained.
Further reading
International WordPress + Hreflang Architecture
Google: localized page versions — checked 18 October 2026.