Discussion
  • International SEO

Global templates force English navigation and footers onto localised pages. Has localising them changed rankings in non-English markets?

Published 1 reply

Discussion starter: an international SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    Localising the navigation and footer is worth doing, but mostly for reasons other than language detection. On pages with substantial localised main content, Google will generally work out the page’s language from that content, so English boilerplate rarely causes a page to be treated as English. Where localising shared templates can plausibly move rankings is internal anchor text, how your pages look in results (breadcrumbs and sitelinks), and thin pages where the boilerplate makes up a large share of the text. No controlled public test that isolates this change exists that I can point to, so expect evidence from your own rollout rather than from the industry.

    What Google says about language on a page

    Google’s documentation on multilingual sites says it uses the visible content of a page to determine its language, not the lang attribute, and it recommends one language per page rather than side-by-side translations. It also warns about the reverse of your situation: translating only the boilerplate while leaving the main content in one language, which is common on user-generated content and can produce the same content appearing several times in results with different boilerplate. Your case, localised main content inside English chrome, is not directly addressed. The reasonable reading is that the main content dominates the language decision, and that the boilerplate matters more for users than for classification, with exceptions below.

    Four ways English templates can cost you

    Anchor text

    Main navigation links are internal links to your category pages. On a German site, a link labelled “Men’s running shoes” to the page targeting “Herren Laufschuhe” gives Google an English description of a German page, repeated on every URL.

    Result presentation

    Breadcrumbs shown in results and sitelinks can be drawn from navigation labels. English labels in a Japanese result look like a foreign site.

    Thin pages

    On product pages with short descriptions, a mega menu and footer can outweigh the main content. That is where language signals get mixed and hreflang clusters can misbehave.

    Users

    Visitors in non-English markets notice English menus immediately. Bounce, lower add-to-basket rates and weaker trust are commercial costs whether or not rankings move.

    The first card is the one with the clearest mechanism. Anchor text is a documented input to how Google understands linked pages, and navigation anchors are the most repeated anchors on a site. If your category pages in a market struggle for head terms while product pages do fine, English navigation anchors are a plausible contributor, alongside the usual suspects of thin category copy and weak local links.

    What results to expect

    Be careful about the size of the expected effect. On strong pages with plenty of localised content and good external links, I would not expect localising the footer to move rankings noticeably. The candidates for measurable change are:

    • Category and hub pages whose main internal links come from the navigation.
    • Markets where local-language head terms differ a lot from literal translations of your English labels, so the English anchors carry almost no relevant terms.
    • Thin templates (store locator pages, short product pages, tag pages) where the boilerplate is most of the text.
    • Click-through rate on queries where breadcrumbs or sitelinks are visible in results.

    Watch for this:

    A literal translation of English navigation labels is not localisation. If the German category is known locally by a different term than the English label implies, translate to the term people actually search, which usually means the category page’s own target keyword. Otherwise you swap English anchors for German anchors that still do not match the page.

    How I would test it

    This is a change you can stage by market, which makes a reasonable natural experiment.

    1. Pick a treatment market and a comparison market with similar template, seasonality and link profile. If the platform cannot localise per market, stage by template instead (navigation first, footer later).
    2. Choose the primary metric by page type: non-brand clicks and impressions to category pages in the treatment market, from Search Console filtered by country and page. Track CTR on queries where breadcrumbs show.
    3. Record the baseline for at least several weeks, long enough to cover weekly cycles and any promotions.
    4. Deploy and wait for recrawl. Navigation changes appear on every URL, so the change is effectively sitewide once the high-traffic pages are recrawled. Use URL Inspection on a sample to confirm Google has seen the new labels.
    5. Compare the treatment market with the comparison market over the same period, and annotate core updates. If both move together, the change probably did not cause it.

    Hypothetical example:

    A retailer localises navigation in its French and Italian stores but not yet in Spain. Over the following two months French and Italian category pages gain non-brand impressions for head terms such as the local equivalents of “trail shoes”, while Spanish category pages stay flat and product pages in all three markets move similarly. That pattern points to the anchor change. If all three markets had risen together, the more likely explanation would be seasonality or an update.

    Checks worth doing before you spend engineering time

    You can gather evidence about whether the English chrome is confusing anything without changing a line of code.

    • Look for a translation offer. Search in the local market with a local-language browser and see whether Google offers to translate your localised pages, or shows a translated title. If it does, Google may be reading the page as a different language from the searcher’s, which is worth investigating on that template.
    • Check result breadcrumbs and sitelinks for brand and category queries in each market. English labels there are a visible, easy-to-explain cost.
    • Measure the text ratio on thin templates. Crawl a sample of short product and store pages and compare the word count of the main content with the navigation and footer. Where boilerplate is the majority, prioritise those templates.
    • Check hreflang reporting. Crawl the hreflang clusters and look for pages where the localised version is not being returned for local searches while the English version is. Several causes produce that, but mixed-language thin pages are one of them.
    • Read the internal search logs in each market. If local users search your site with terms your navigation does not use, you have both an anchor-text problem and a findability problem.

    If none of these show anything, the SEO case rests mainly on anchors, and the user case carries the rest.

    Where to start if engineering time is limited

    1. Main navigation labels, translated to local target terms. Highest leverage for anchors and user trust.
    2. Breadcrumbs, including their structured data, so result breadcrumbs appear in the local language.
    3. Buttons and interface text near the main content (add to basket, size guide, delivery information), mostly for conversion.
    4. Footer last. Legal and company links matter for trust, but the footer’s search contribution is smaller, and localised legal pages often need to exist anyway for compliance.

    If the platform forces a global template, the argument for fixing it is easier to win on conversion and compliance than on SEO alone. Localised navigation almost always helps users; ranking gains are plausible on category pages and thin templates, but they need your own before-and-after data to prove. I would lead with the user case, run the market-staged rollout, and let the category page numbers make the SEO case.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.