Google is expanding AI Overviews. Ranking is no longer a click

#What Google actually changed

Chris Long posted the first public example on 27 August 2026: the AI Mode prompt box appearing by default inside Search. Barry Schwartz replicated it and asked Google. The spokesperson’s line, reported by Search Engine Roundtable and Search Engine Land on 28 August, is the only official text:

For some queries, AI Overviews may dynamically expand for topics where our systems determine it’s most useful for people. Our research has shown that with this dynamic experience, users find Search more helpful and engage deeper in follow-up exploration.

Robby Stein from Google added one operational detail on X: if you have already started scrolling, the expansion stops so you do not lose your place.

Until this change, an AI Overview loaded a short block. You had to click Show more to get the long answer. The ten blue links were still on the first screen for most queries. The new behaviour is the long answer first. Schwartz’s write-up is explicit that this pushes the default results further down.

That is the whole mechanism. Everything below is what it does to a site that already ranks.

#What Google said, and what it did not

Name the gaps, or you will invent a rollout plan Google never published.

Google did not give a percentage of queries. Google did not give a date when this becomes the default for all searches. Google did not link to updated documentation. Google did not say the ten blue links are going away. The source is a spokesperson quote plus a product tweet, not a developer doc.

Glenn Gabe posted two YMYL examples of the expanded overview. In his screenshots the answer is so long you cannot see the end of it, and the classic results are not on screen. He flagged the problem for sites that live in those ten links. We are one of those sites on commercial queries.

The 31 August Search Forum Recap collected the same stories: expanded overviews, the spam team still resourced, shopping ads inside AI Mode. The overview change is the one that hits an agency’s offer pages. The ads in AI Mode are a separate tax on the same screen.

#Ranking is not a click

A position of 2 to 4 used to mean a few percent CTR on a commercial query, often more. Expected CTR tables from the last decade assumed a blue-link layout. They are the wrong instrument now.

On 31 August 2026 we inspected the live URLs that carry the offer. Google Search Console URL Inspection returned Submitted and indexed, last crawled inside the last four days of August, robots allowed, Google-chosen canonical matching the page. Indexing is not the missing piece.

The missing piece is the click. The query is answered on the results page. The title tag never gets a chance.

#Our measurement: offer URLs at positions 2 to 4

Property https://wppoland.com/ and the locale properties, web search, 28 days ending 31 August 2026. These are Search Console rows, not estimates.

Read the table in two layers.

The German WooCommerce developer query is the cleanest. Position 2.9, 214 impressions, zero clicks. The page itself has 926 impressions across all queries and still zero clicks. URL Inspection on 31 August: indexed, crawled 30 August, review snippets detected. Google has the page. People are not leaving the results.

The Polish pricing page is the volume case. 3367 impressions, 18 clicks. The average position of 19.9 is a mix of tail queries. The money queries sit at 1.7 to 6.3 with CTR between 0 and 0.88 percent. Hash sitelinks of the same page (#ile-kosztuje-strona-wordpress and siblings) also collect impressions at position ~6 with zero clicks. Those are the questions an expanded overview can answer without opening us.

The Spanish developer landing has thousands of impressions at position 25. That is still a ranking problem, not only an overview problem. The German price page at position 53.8 is the same class: we had numbers on the Polish sibling and buried them on the German one. We moved the 2026 ranges to the top of /de/wordpress-preisliste/ the same day. That is a title and H1 job, not an overview job.

The rest of the site still clicks. Brand queries (wppoland) convert. Informational English posts (jQuery, AMP, WordPress 7.1) still produce double-digit clicks. Poland as a country row: 170 clicks from 19555 impressions (0.87 percent). The United States: 56 clicks from 51951 impressions (0.11 percent). The commercial head terms are the ones the expanded overview can finish without us.

#YMYL queries get the long answer

Gabe’s examples were health and money. Pricing a WordPress site and hiring a WooCommerce developer sit in the same family: the searcher wants a number, a definition, a next step. Those are the queries Google’s systems are most likely to call useful for a long answer.

We cannot prove from Search Console alone that an expanded overview fired on woocommerce entwickler. Console does not expose that layout. We can prove the CTR is incompatible with a visible blue link at position 3. A 0 percent CTR at position 2.9 is not a bad title. It is a result that was not the thing on screen.

If you only have average position and CTR, treat “position better than 5, CTR under 1 percent, commercial intent” as the working definition of this layout until Google ships a report.

Sitelinks and ads can also crush CTR. We still see them. The Polish pricing page collects impressions on hash fragments at position 6 with zero clicks. That is a sitelink, not an overview. The difference is visible in Search Console: the page URL has a # in the page dimension. Expanded overviews do not create a hash URL. If the row is a clean canonical with position 3 and CTR 0, do not blame sitelinks.

Shopping ads inside AI Mode, also in the 31 August recap, are another tax. They sit in the same expanded module. We do not run Google Ads on those queries, so an ad row is not us competing with ourselves. It is Google monetising the answer. You cannot title-tag your way past that. You can only be the source the module cites.

#What we changed on the offer pages

On 31 August 2026 we shipped a GEO pass on the landings in that table, then the locale siblings.

Each page now leads with a short answer block that names WPPoland and states the fact the query is asking. Pricing pages keep market ranges labelled as market context, with the binding quote after written scope. Service pages do not publish a SKU list.

FAQ questions were rewritten to the query string, not a paraphrase. Jaki jest cennik WordPress 2026? rather than a generic “how much does a website cost”. Was macht ein WooCommerce Entwickler? rather than “what does an online shop cost”. The overview extracts questions. If your question is not the query, you are not a candidate.

We added a comparison table where the query is a choice (freelancer, agency, senior with a written SLA). Tables survive extraction better than a paragraph that buries the contrast in adjectives.

We did not add more city URLs. The offer URLs were already in the sitemap and already indexed.

The live check after deploy, cache-busted: HTTP 200, index, follow, and the new first heading present on /pl/wordpress-cennik/, /de/woocommerce-entwickler/, /pl/wordpress-developer/, /es/desarrollador-wordpress/, /de/wordpress-preisliste/. IndexNow accepted 41 of those canonicals.

This is not a claim that CTR will recover next week. It is a claim that the page now contains a citeable sentence. Without that sentence the overview has to invent one or pick a competitor.

#What will not fix this

Indexing more programmatic city pages. We spent August promoting city landings into the sitemap. That work is about coverage. It does not move a query that already ranks at position 3.

Padding word count. We banned the batch expanders after they shipped numbered filler into production. Thin posts stay noindex unless Search Console shows clicks. An extra 800 words of repeated H2s will not be cited.

Tweaking the title from 60 characters to 55. The title is not on the first screen if the overview is expanded.

Buying more impressions at position 15. The German price page at 53.8 still needs to rank. That is the exception in the table. Everything else in the top five is a citation problem.

#How to check your own queries in Search Console

Export 28 days, dimensions query and page, web search.

Keep rows with impressions of at least 50 so you are not reading noise. Split them:

1. Position worse than 10. Ranking work, links, intent match.
2. Position 5 to 10, CTR under 2 percent. Mixed. Could be ads, could be a short overview, could be a weak title.
3. Position better than 5, CTR under 1 percent, commercial or YMYL intent. This is the expanded-overview bucket until proven otherwise.

Inspect the URL. If it is indexed and recently crawled, stop debugging robots.txt. Read the first 80 words of the live HTML. If the query is not answered there with a number or a named definition, that is the edit.

Do this per locale property, not only on the domain property. Our Polish pricing queries do not show in the English property. Averaging six languages hides the commercial row.

On WordPress, the first 80 words are often not the first 80 words of the_content(). A page-builder hero, an auto excerpt, or a “skip to content” block can push the actual answer below what a crawler stores as the opening. View source on the live URL, not the editor. Search for the query string. If it first appears after two screens of testimonials, the overview has nothing to lift.

We build this site in Astro. The answer block is HTML in the Markdown, immediately after the AEO who/what/where cards. There is no widget area that can shuffle it. If you are on WordPress, put the answer in a real paragraph at the top of the post content, not in a custom field the theme forgets to print.

#What belongs in the first 80 words

The overview is a summariser. It needs a sentence it can lift.

Name the organisation. “WPPoland (Mariusz Szatkowski)” in sentence one or two. First-person without a name is a weak entity.

Answer the query in the same words the searcher used. If they typed wordpress cennik, the heading and the first sentence should contain those words and a range, labelled as market context.

Put the range in a table as well as in prose. Extractors like tables. Our Polish pricing page already had the table. The German sibling had the contracting essay first. We put the 2026 ranges above that essay.

FAQ questions must be the query, including the year if the query has a year. “What does a WooCommerce developer do?” is better than “How can a specialist help your store grow?”.

Do not promise a click. The reader of the overview may never hit the page. The job is to be the source of the number they just read.

#What we do not know, and what to do anyway

We do not know what share of our impressions now render the expanded layout. Search Console does not say.

We do not know whether citing us inside the overview will ever show up as a click, a branded search, or a direct visit. We will keep the same 28-day window and compare October to August on the rows in the table. If CTR stays at 0 on woocommerce entwickler while position stays at 3, the overview still owns the query. If branded searches for wppoland rise while that CTR stays flat, the citation is working without a blue-link click.

We do not know if Google will widen this to every commercial query. The spokesperson left that door open. Treat the current rows as the leading indicator, not as a one-off test.

What to do anyway: put a citeable fact in the first paragraph of every URL that already ranks in the top five for a commercial query. Measure those rows monthly. Do not spend the next sprint adding thin URLs to the sitemap.

Last updated 31 August 2026. Sources: Search Engine Roundtable, Search Engine Land, Google spokesperson quote of 28 August 2026, Robby Stein on X, Chris Long’s first public example, Glenn Gabe’s YMYL screenshots, and our Search Console export for the 28 days ending 31 August 2026.