Google Just Documented How Search Differs by Country. What Changes for You?

Why does Google's search results page look different in Europe than it does in India?

Because Google runs different result formats in different countries, and it has now written that down. On September 8, 2026, Google added documentation about regional differences in the Search experience, covering aggregator units, supplier units and carousels that appear in some countries and not in others.

I spend most of my week helping founders get found, and the quiet assumption underneath almost every conversation is that Google is one thing. One results page, one set of rules, one screenshot that proves what your listing looks like. That assumption has been wrong for a while. It is now officially wrong, in Google's own documentation.

This matters more than it sounds. If you sell across borders, the page your buyer sees may contain units your own market has never shown you.

What exactly did Google publish on September 8?

Google logged a documentation update titled "Added documentation about regional differences in Search experience" in its Search Central documentation updates feed. The new page describes search experiences available in certain countries, and it names three formats: the aggregator unit, the supplier unit, and the ecosystem carousel.

The page itself opens with a line worth reading twice. Google says it is "evolving the search results page for certain types of queries to provide new opportunities for Vertical Search Services (VSS), Comparison Shopping Services (CSS), direct suppliers, and content providers." That is Google describing a results page built to hand visibility to specific categories of business, in specific places.

It is a documentation change rather than an algorithm announcement, which is exactly why most people will miss it. Nobody writes a breathless post about a docs update. But documentation changes are where platforms tell you what they have already shipped, and this one describes a structural difference in the product, not a ranking tweak.

What is an aggregator unit, and what is a supplier unit?

Google defines an aggregator unit as a unit that provides visibility for ecosystem participants, specifically aggregators, on the search results page. A supplier unit does the same for direct suppliers. The ecosystem carousel is described as a carousel that may appear alongside answers that require data visualisations and interactivity with data.

Strip the vocabulary away and the distinction is the oldest one in commerce. An aggregator is the site that collects many options for you. A supplier is the business that actually provides the thing. In travel, that is the booking platform against the hotel itself. In jobs, it is the job board against the employer. Google is describing result formats that give each of those two roles its own dedicated space.

I read that as Google formalising a fight it has been having for years about who deserves the click. The interesting part is not that Google picked a side. It is that Google built separate real estate for both sides, and only switched it on in some countries.

Which countries and query types does this actually cover?

Google's page names three regions: the European Economic Area, South Africa and Türkiye. For query types it names hotels, flights, ground transportation, products, weather, sports, finance, translation, jobs, local businesses, vacation rentals, car hire and food delivery. If your business sits in one of those verticals and sells into one of those regions, this is your results page.

Look at that list of verticals honestly. It is not a niche. It is most of local commerce, most of travel, most of recruitment, and a good chunk of retail and financial services. The list reads like an index of the industries where a comparison site sits between a buyer and a business.

What the page does not do is tell you that your rankings are about to move. It tells you which features exist where, and it asks you to select where your company is based and the query types most relevant to your business in order to find the features that apply to you. That is a deliberately narrow promise, and I would not stretch it further than Google did.

Why is Google regionalising its own documentation now?

Google's page does not give a reason, so I will not invent one. But this is not an isolated change. The same documentation feed shows Google updating its site reputation policy in late August 2026 to adjust its enforcement approach within the European Economic Area, which is another rule that now reads differently depending on where you are.

Anyone who follows the regulatory side of this will have a theory, and mine is that regulation shapes a good part of it. But Google has not said that on this page, so treat my reading as a reading. What is documented is the pattern: features that exist in some regions, and policies that enforce differently in others.

The practical consequence of that pattern is what I care about. Search is drifting from one global product towards a set of regional products that share a name. Once that is true, a single screenshot of a results page stops being evidence of anything except what one person saw in one country.

Does any of this change what you should build on your site?

Mostly no, and I want to be blunt about that. There is no new markup to add and no setting to flip. What changes is your diagnosis, not your build. The work is figuring out which version of the results page your actual buyers are looking at before you spend a quarter optimising for a layout they never see.

The temptation after news like this is to go build something. Add a schema type, spin up a landing page, chase the new unit. I have watched founders burn real money doing exactly that on the back of a feature announcement that did not apply to their market, and the cost is never just the build. It is the quarter they did not spend on the thing that would have worked.

The exception is if you genuinely are an aggregator or a direct supplier in one of the named verticals, selling into the European Economic Area, South Africa or Türkiye. Then the documentation Google links from that page is your homework, and it is worth reading the specific feature page rather than a summary of it, including mine.

How do you find out which version of Search your buyers are seeing?

Start with your own data rather than a screenshot. Google Search Console splits performance by country, and that report tells you where your impressions genuinely come from. If eighty percent of your impressions are in one market, that is the results page that decides your quarter, whatever a colleague in another country sends you on Slack.

I check three things in that order. Which countries produce impressions, which produce clicks, and whether the gap between the two moves. A market where impressions climb while clicks stay flat is usually a market where the results page changed shape above you, and that is the signal worth chasing rather than a rumour about a new unit.

After that, look at the page yourself from the market that matters, and be honest that you are looking at one sample. This is the same discipline I apply to AI answer engines, where what gets cited in AI Overviews varies by session and by user. One observation is an anecdote. Your Search Console country report is data.

What does this mean if you sell across borders from India?

It means the results page you test against is probably not the one your buyer uses. I work from Bengaluru, and the buyers I help people reach are usually in the United States and Europe. India is not among Google's named regions for these units, so my local results page is a poor proxy for theirs.

This is the unglamorous reality of selling B2B from India to buyers abroad. You are always working one layer removed from the environment your buyer lives in. The fix is not clever. It is refusing to generalise from your own screen, and letting country-segmented data make the call instead.

If you run genuinely different sites or language versions per market, the structural side of this is worth a look too, because hreflang and international targeting decide which version Google even considers for a given country. Regional result formats sit on top of that. Getting the targeting wrong underneath makes every layer above it harder to read.

What should you do next?

Open Google Search Console, filter performance by country, and write down the two or three markets that actually produce your impressions. Then check whether those markets appear in Google's list of named regions. That is a short job, and it tells you whether this documentation is your problem or somebody else's.

If your markets are on the list and your business is an aggregator or a supplier in one of those verticals, read Google's feature pages directly. If your markets are not on the list, file this and move on, and stop treating a screenshot from another country as evidence about your own.

The broader habit is the one I would actually push. Platforms are getting more regional, not less, and the era of one universal results page is ending quietly in documentation updates rather than loudly on stage. Build the habit of checking where your visibility comes from before you decide what to fix. If you want help working out which version of Search your buyers are actually in, reach out. I am always happy to look at a Search Console export and tell you what I see.