Does your website actually need hreflang?

Plan hreflang when you have alternate language or regional versions of the same content. A hreflang tag is a code annotation connecting those versions. Google can sometimes discover alternatives without it, but recommends identifying them explicitly. When annotations are useful.

Separate language from market

A multilingual website offers more than one language. A multiregional website targets different countries; it can also be multilingual. These are separate decisions in Google’s international website guidance.

Hypothetical example: a small furniture shop publishes English and French product descriptions. Ask whether both pages serve the same delivery area or whether each supports a different market. Write down the answer before choosing language and region labels.

Do not begin by commissioning a separate version for every possible country. My recommendation is to start with audiences you can serve and content your team can maintain. Ask the business owner to approve that scope in plain language.

Which pages should be connected?

Connect equivalents at page level. Make a spreadsheet with the page purpose, each language address, a content reviewer, and an approval column. Treat this sheet as your implementation brief, rather than asking a developer to guess relationships from page names.

Google recommends separate URLs, meaning web addresses, for different language versions. Changing the language at one address through browser settings can leave some versions undiscovered. Google’s URL recommendation.

Build a small mapping sheet

The following is a hypothetical planning example. Replace the descriptions with your real addresses. Ask someone who knows the products to review the pairings before marking a row ready.

For each pair, compare the actual offer. Check the product, service scope, booking action, and delivery information. Regional differences may be intentional; record them so the reviewer can distinguish a deliberate variation from an unfinished translation.

If addresses are still being designed, work through the URL structure guide first. Keep address changes in a separate task list. Approving a language map should not silently approve a website migration.

How should your developer add the annotations?

Choose one implementation method your team can maintain. Google treats HTML tags, HTTP response headers, and XML sitemaps as equivalent methods, with no search benefit from using all three. HTML is page code; response headers accompany a server response; a sitemap lists website addresses. Supported implementation methods.

A minimal HTML pattern

For HTML, place the annotations in the page’s <head> section. Use the same set on both versions. Replace the placeholders below with complete page addresses before using this pattern. HTML placement rules.

<link rel="alternate" hreflang="en" href="[FULL_ENGLISH_URL]">
<link rel="alternate" hreflang="fr" href="[FULL_FRENCH_URL]">

The placeholders are not working addresses. Ask your developer to show the completed example from your own website, alongside the approved mapping row. Review the English and French pages together before extending the implementation.

Make the technical handoff specific

• Identify where the language relationships will be maintained.
• Ask for a completed example using an approved page pair.
• Request a list of pages awaiting content decisions.
• Assign responsibility for updating the mapping when pages change.

If the team chooses a sitemap, use the XML sitemap guide to organise the related work. Do not request an additional HTML implementation simply because you cannot see tags in the page. First ask which method was agreed and where its output can be inspected.

How do hreflang and canonical tags work together?

Hreflang connects language or regional alternatives. A canonical tag identifies a preferred address among similar or duplicate pages. Google discusses using both for duplicate regional content in the same language. Regional duplicate content guidance.

Ask two separate questions during review: which alternatives belong to this page, and which address is being identified as preferred? Require an explanation for each answer. Do not accept a blanket instruction to point every translated page at the original language.

Translated main content is not treated as duplicate content merely because it is another language version. Google’s distinction for translations. For the separate decision about preferred addresses, read the canonical tag guide.

Hypothetical review: your shop has a complete French product description, but its canonical setting names the English page. Flag that choice for investigation. Ask the developer to explain the intended indexing arrangement before approving the rollout.

How can you check the setup without becoming an SEO specialist?

Review the mapping and the delivered output side by side. Each version should include itself and its alternatives using complete addresses. Missing reciprocal links can cause Google to ignore the annotations. Implementation and troubleshooting rules.

Follow one customer journey

1. Open the English page. Confirm the product or service matches your approved row.
2. Open its alternative. Read enough to confirm it fulfils the equivalent purpose.
3. Inspect both directions. Ask the developer to show each page’s actual annotations.
4. Review the canonical decision. Record any unexplained mismatch.
5. Save the result. Note the addresses, reviewer, unresolved issue, and next action.

Test more than the homepage. I would include a product, a service, and a page without a translation. For the untranslated page, inspect what the implementation outputs instead of assuming every page must have the same number of alternatives.

When an address opens an error page, create a separate repair task using the 404 troubleshooting guide. If the page has deliberately moved, review the work with the 301 redirect guide. Then update your mapping sheet to reflect the decision.

Write actionable issue reports. Replace “French SEO is broken” with “The English chair page lists the French homepage; the approved counterpart is the French chair page.” Include the expected destination and ask the reviewer to repeat that exact check after the fix.

What should your team deliver this week?

Agree on a small acceptance checklist before implementation. My suggested first delivery is an approved mapping sheet, a completed page pair, and a repeatable review process. These are project deliverables, not promises about search traffic.

• Business owner: approve the languages and markets being served.
• Content reviewer: confirm equivalent pages and flag unfinished work.
• Developer: document the chosen method and demonstrate its output.
• Marketing lead: record the checks and assign unresolved issues.

Before closing the task, rehearse a future change. Ask what happens when someone adds a translation, removes a product, or renames a page. Write the responsible person and the required review beside each scenario.

A useful handoff should let another employee continue the work without rebuilding the page map. Keep the implementation note beside your content planning sheet. When the team publishes a new language version, make reviewing that row part of the publishing checklist.