Skip to content
OlaCheap

SEO and discovery · Practical guide

Audit hreflang, canonical and sitemap URLs on a multilingual website

Correct international SEO starts with genuinely translated page content and consistent URL metadata, not an arbitrary language count.

First published · OlaCheap technical reference · Check current provider instructions before changing production services

Map which content is genuinely available per language

Create an inventory of the canonical English routes and the languages that have reviewed versions of the main content. A translated navigation bar does not make an English article a Japanese or Vietnamese article. Record pages that are still drafts, redirect to a fallback, or are intentionally blocked from indexing.

Request each listed URL without being signed in and note the final HTTP status, destination and content language. Do not include a redirecting or unavailable translation in the sitemap just because a locale switcher can construct that path. Only published canonical pages should contribute to the counted language variants.

Check the full hreflang return-link set

For each published language edition, inspect the canonical link and the alternate language links. A valid hreflang relationship should be reciprocal: each version links to itself and the other versions using fully qualified URLs. Incorrect return links are a common reason that a seemingly complete language map fails a technical audit.

If one page has only an English version, do not fabricate Japanese or Vietnamese URLs. Use an appropriate default for unmatched languages without pointing it at an unreviewed translation. Avoid combining alternate language markup with misleading canonical URLs that all point to one language regardless of actual translated content.

Reconcile the sitemap with what production serves

Compare every sitemap URL to the page's final response, canonical URL and robots directives. A page with a noindex override or a redirect should usually be absent from the set of URLs you actively request search engines to index. Be aware that a dynamic sitemap may differ from a source-code count because of real publishing rules.

Follow internal links from the homepage, categories, mobile menus and related articles. A valid XML list does not compensate for content hidden behind JavaScript-only controls or paths users cannot discover. Search engines may find pages through links outside the sitemap, so coherent navigation remains an important part of SEO.

Measure indexed pages independently from XML counts

After a code change passes tests and is deployed, check the live XML again and verify some URLs in each language. Record the date and commit to distinguish a successful source merge from production actually running that version. If a newly published page is missing, inspect deployment, cache, sitemap generator and noindex state first.

Submitting a sitemap helps discovery but does not guarantee crawling or ranking. Track the Google Search Console Page Indexing report, URL Inspection evidence and real impressions over time. Avoid claiming that a 200 response from IndexNow means Google indexed the sitemap: it is a separate notification protocol.

Next practical step

This article is an educational checklist, not a claim of live product availability or a substitute for current documentation from your provider.

Use OlaCheap SEO tools →

References and official documentation

These materials help verify procedures. Provider requirements may change, and this guide does not claim first-hand security certification or independent testing of third-party products.

Related technical guides