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.
- International SEO
Marketplaces with different inventory per country: how do you handle hreflang when equivalent pages don’t exist in every market?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
adminAdmin
Use hreflang only between pages that are genuinely equivalent, and leave it out where an equivalent does not exist. For a marketplace with different inventory in each country, that usually means category and informational pages carry hreflang across the markets where they exist, because they serve the same intent even if the listings differ, while individual listings and products available in only one market carry no hreflang at all. Do not point hreflang at a category page or homepage in a market that lacks the product; that is not an equivalent page, and it confuses both the annotation and the user. Generate annotations from an explicit equivalence mapping, rather than assuming every URL has a counterpart in every market.
What counts as equivalent
Page type Equivalent across markets? hreflang Homepage Yes Yes Category pages that exist in several markets Yes, same intent, even with different inventory Yes, among markets where the category exists Product available in several markets Yes Yes, among those markets only Product available in one market only No counterpart No Individual listings from local sellers No No Help and policy pages Usually yes, if the topic applies Yes, where the page exists Building an equivalence mapping
- Assign stable identifiers to categories, products and content that can exist in several markets.
- Record which markets each identifier exists in, and its URL in each.
- Generate hreflang from the mapping, listing only markets where the page exists, including a self-reference.
- Update the mapping when availability changes, removing a market’s annotation when the page there is removed.
- Use XML sitemaps for hreflang at scale, which is easier to manage than annotations in page HTML for large sites.
x-default
An
x-defaultannotation tells Google which version to show users whose language or region does not match any listed version. For marketplaces, it is typically the international or main market version, or a market selector. Apply it to pages that have a sensible default; for a product available only in some markets, x-default may not be useful, and it should never point to an unrelated page.Hypothetical example:
A marketplace operating in the UK, Germany and France generates hreflang for every product by assuming all three markets have it. Many products exist only in one market, so annotations point to 404s or redirect to category pages, and Search Console’s international reporting and crawl analysis show widespread errors. The marketplace builds a mapping by product identifier, generates hreflang in sitemaps only for products present in more than one market, keeps category hreflang for categories that exist across markets, and drops annotations for single-market products and listings. Errors fall, and the right market’s version appears more consistently in each country’s results.
Watch for this:
Annotations that point to URLs returning 404s or redirects are ignored and waste crawling. Validate hreflang targets regularly, especially after products are removed from a market, and remove annotations when a counterpart disappears.
Category pages with different inventory are still equivalent
A common worry is whether a category page with 2,000 products in one market and 200 in another counts as equivalent. For hreflang purposes it generally does: the page serves the same intent, a shopper looking for that category, in each market. What matters is that the page exists and is meaningful in each market. If a category is almost empty in one market, consider whether it should be indexable there at all; a near-empty category page is a weak page regardless of hreflang, and removing it from that market’s cluster is better than pointing searchers to it.
Monitoring hreflang at scale
Large marketplaces should monitor hreflang continuously rather than auditing occasionally. Useful checks include the share of annotations pointing to non-200 URLs, missing return links, and pages where Google shows a different market’s version in a country’s results, which Search Console’s country filter can reveal. Automate the checks against the equivalence mapping so errors are caught when availability changes, not months later.
Helping users when no equivalent exists
When a user in one market lands on a product that is not available there, hreflang cannot help, because there is no equivalent. Handle it on the page: show that the product is not available in their market, suggest similar products that are, and offer a link to the local site. Avoid automatic redirects based on location, which can stop crawlers reaching pages and frustrate users.
Annotate only equivalent pages, drive hreflang from an explicit mapping of which pages exist in which markets, manage it through sitemaps at scale, validate targets regularly, and handle unavailable products with helpful on-page alternatives rather than misleading annotations.
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.
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.