Discussion
  • International SEO

Products sold under different model names in different countries: one global page or local pages? How did hreflang cope?

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

    The short answer is: if you sell locally, build local pages that use the local model name, and connect them with hreflang. The model name is often the query itself. A UK shopper searching the UK name and an Australian shopper searching the Australian name are two different demand pools. One global page can only put one name in its title, one price in its offer, and one set of stock and warranty details on the page.

    Hreflang copes with different names better than most people expect, because it never compares names. It maps URLs to URLs. The usual failure is somewhere else: in the product data. Most hreflang generators join pages by slug or SKU. When the model name changes by market, that join breaks without any error, and whole clusters lose their return tags. So before you ask whether Google can handle it, check whether your catalogue knows that the KX-500 and the KX-550 are the same product.

    Why the model name changes the decision

    Regional naming is common. Vauxhall and Opel sell the same cars under different badges. The Honda Jazz is the Fit in other markets. Unilever’s deodorant is Lynx in Australia and the UK, and Axe in most other markets. Electronics brands often add regional suffixes or completely different model numbers for each market. In each case, the name a buyer types depends on where they live and what their local retailers call the product.

    That affects three things a global page struggles with:

    • Query match and click appeal. A result titled with a foreign model name looks like the wrong product, or a grey import, even when it ranks.
    • Commercial detail. Price, currency, stock, delivery, warranty, plug type and regulatory approvals are usually market-specific. Merchant listings also need a real price on every Offer, which is hard to express honestly on one page for six currencies.
    • Specification drift. Renamed models are often not identical. A different chipset, battery, bundle or compliance variant is a common reason for the new name in the first place.

    A global page still has a place. It works when you do not transact locally (a manufacturer that sends buyers to retailers), when the difference is only a suffix nobody searches for, or when a market is too small to maintain. It is also the right shape for support content, as covered below.

    What hreflang actually needs, and why names do not bother it

    An analogy helps here. Think of airline code-shares. One flight can carry QF123 on one airline’s ticket and another airline’s flight number on a partner’s ticket. The departure board does not match those numbers to each other. It links both to the one operating flight record. Hreflang works the same way: each market’s page carries its own “flight number” (the model name), and the cluster only holds together if something underneath links them to one product.

    Technically, Google’s documentation asks you to tell it about “multiple versions of a page for different languages or regions”, and says that “Localized versions of a page are only considered duplicates if the main content of the page remains untranslated”. Nothing there requires identical titles or product names. The same page sets the rules that do matter:

    • Annotations must be reciprocal: “If two pages don’t both point to each other, the tags will be ignored.”
    • Alternates can sit on different domains, so ccTLD setups are fine.
    • You can declare the clusters in an XML sitemap, which is usually easier than page tags for large catalogues.

    Canonicals are where same-language markets get tricky. Google says it prefers URLs in hreflang clusters when it picks canonicals, and asks you to “specify a canonical page in the same language”. Its multi-regional guidance also says that where you have “similar or duplicate content on different URLs in the same language”, you should pick a preferred version. In practice, en-GB, en-US and en-AU pages that differ only in currency are the ones most likely to be folded together.

    Here is the useful twist. Different model names, different specs and different offers make the local pages more distinct, not less. That is a reasonable argument for why renamed products may cluster more cleanly than identical ones. It is not a documented rule, so confirm it with URL Inspection rather than assuming it.

    Where these setups usually break

    Audits of multi-market catalogues tend to find the same handful of problems. None of them are hreflang “failing”. They are the data model failing.

    1. The join key changes by market. If the generator matches on SKU or slug, renamed products drop out of their cluster, or worse, match to the nearest similar slug. Missing return tags mean the whole annotation is ignored for that pair.
    2. One-to-many products. The US sells one model and the UK sells two regional versions of it. Hreflang allows one URL per locale in a cluster. Pick the closest equivalent, or leave the others unmapped. Do not point two UK URLs at one US URL.
    3. “Equivalent” is stretched too far. If a buyer would not accept the local product as the local version of the same thing, it is not an alternate. It is a different product that happens to be related. Link to it visibly instead.
    4. Lifecycle mismatch. A model is discontinued in one market and still sold in another. If the discontinued page now redirects or returns a 404, every page in the cluster is pointing at a non-200 URL.
    5. Canonicals that contradict hreflang. Local pages canonicalised to the US or “global” version stop being eligible as indexed alternates, whatever the hreflang says.

    Watch for this:

    Do not switch model names on one URL by IP address or cookie. Google says Googlebot “usually originates from the USA” and does not vary its crawl location to find page variations. A locale-adaptive global page will usually be indexed with only the US name.

    The cross-name searcher problem

    One scenario is worth planning for. An Australian reads a US review and searches the US model name. If the US page is the one that ranks, hreflang may swap in the Australian URL as the local alternate. The searcher then sees a result carrying a name they did not type. Google does not document exactly when that swap happens for queries that contain another market’s model name, so treat it as a possibility to check, not a certainty.

    The practical fix is cheap: add a short, visible line near the product name on each local page, such as “Sold in the US as the KX-500”. It reassures the visitor, it gives the page a legitimate mention of the other name, and it avoids stuffing every regional name into the title. Schema.org has an alternateName property you can also use. Google does not document using it for product results, so treat it as harmless and unproven.

    Hypothetical example:

    An appliance brand sells 1,400 models across the US, UK, Germany and Australia, and about a third are renamed in at least one market. Its hreflang sitemap is built from SKUs, and SKUs differ by market for renamed models. The validator passes because every tag it finds is well formed. But the renamed products simply have no cluster, so UK searches for UK names still surface US pages that rank on links. The fix is not a hreflang tweak. It is a master product table (GTIN where the item really is identical, otherwise an internal global ID) that every market’s page maps to, with hreflang generated from that table.

    Global page or local pages: a decision table

    Condition Lean towards one global page Lean towards local pages Evidence to inspect
    Do you transact in each market? No, you refer buyers to retailers or distributors Yes, with local price, stock and delivery Where conversions actually happen
    How different is the name? Minor suffix nobody searches for Different name or model number that people search Query data for each name, by country
    Specs and compliance Genuinely identical Different chipset, bundle, approvals or warranty Product data sheets for each market
    Upkeep capacity Small team, many markets, low volume Local merchandising and content owners Current staleness of local pages
    Intent served Support, manuals, parts, spec lookup Shopping and comparison Landing-page intent in Search Console

    Many brands end up with a hybrid: local product pages for commerce, plus one global support or “model finder” page keyed on the master ID that lists every regional name. Support searchers often type whatever name is printed on their box or manual, so a cross-reference page serves them better than forcing them through a market selector.

    How to check whether your current setup is working

    1. Build the cluster table. Crawl each market and export every hreflang pair with status code, indexability and declared canonical. Flag pairs without return tags and any alternate that is not a 200, self-canonical URL.
    2. Check Google’s canonical, not yours. Use URL Inspection on a sample of same-language pairs. Check the Page indexing report for “Duplicate, Google chose different canonical than user” on local product URLs.
    3. Measure correct-market landings. In Search Console, filter by country and by queries that contain each model name. The metric that matters is the share of a country’s product impressions and clicks landing on that country’s URL.
    4. Follow the money. In analytics, look at sessions that land on another market’s page and then bounce or hit a “not available in your region” message. That is the commercial cost of a broken cluster.

    If you are moving from global to local, pilot it. Pick one market and a set of renamed models, keep a comparable set of renamed models on the old setup as a rough control, and compare over 8 to 12 weeks. Watch impressions for local-name queries, correct-market landing share, and conversion rate. If the local pages index but gain little local-name visibility, the constraint is more likely demand or authority than hreflang, and the rollout case weakens. If Google keeps choosing the other market’s URL as canonical, the pages are probably not distinct enough yet.

    The decision rule

    If people search the local name and you sell locally, give that market its own page with its own name, price and specs, and link the markets through a master product ID, not the SKU or slug. Keep one global page for support and cross-reference. Then judge hreflang by one number, the share of each country’s impressions landing on the right URL, not by whether a validator shows green.

    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.