Google AI Overviews Can Expand Before You Scroll: Measure the Lost Viewport
Some Google AI Overviews can expand automatically before a user scrolls. Measure the pixel displacement and first-organic visibility instead of relying on rank position alone.
Direct answer: Google says some AI Overviews can expand automatically while a searcher remains at the top of the page. Once the person starts scrolling, the expansion stops so the page does not continue moving beneath them.
For publishers, this creates a measurement problem. A result can keep the same reported position while moving farther below the initial viewport. Measure the pixels and interface state before estimating any visibility effect.
What Google said about the expansion
On August 28, 2026, Search Engine Roundtable reported Google’s explanation of the behavior. Google said AI Overviews may dynamically expand for some queries when its systems find the additional detail useful. If the user starts scrolling, Google stops the expansion to preserve that person’s place.
Observed versions can reveal more answer text and an “Ask anything” prompt without requiring a manual “Show more” click. This is query-dependent interface behavior, not a documented ranking-system change.
Google has not published the eligible query classes, expansion timing, rollout percentage, or click-through effect. A screenshot can verify one interface state; it cannot establish a traffic result.
Position does not measure the viewport
Average position describes where a result sits within Google’s reporting rules. It does not describe how many pixels of AI answer, shopping modules, images, prompts, or other features appear above the link. Two observations can report the same position and give the result very different visual exposure.
| Field | What to capture | Why it matters |
|---|---|---|
| Viewport | Width, height, zoom, device scale | Defines the visible area |
| AI Overview height | Pixels before and after expansion | Measures the added displacement |
| First organic result | Top-edge vertical coordinate | Shows whether it remains above the fold |
| Expansion state | Collapsed, expanding, expanded, stopped by scroll | Prevents unlike screenshots from being compared |
| Source links | Count, presentation, and vertical position | Separates answer growth from publisher-link exposure |
Run a repeatable viewport test
- Choose a fixed query list and record whether each query produced an AI Overview in the baseline.
- Use one viewport, browser version, locale, device class, and signed-in state per test cell.
- Capture the page immediately after load, during any expansion, and after the interface settles.
- Do not scroll until the expansion window has been recorded. Then repeat with an immediate scroll to test the stop behavior.
- Measure the AI Overview container and the first organic result’s vertical coordinate.
- Repeat across logged-out or fresh state, normal account state, mobile, and desktop where available.
Save video or timestamped screenshots only when they come from the stated environment. Do not recreate a Google interface as evidence. The output should be a table of measured interface states, not a chart with estimated CTR.
What Search Console can and cannot show
Google’s generative-AI reporting can help compare impressions and clicks over time, but it does not identify whether a particular impression used the dynamic expansion state. It also does not report the height of the AI Overview or the pixel position of the first organic link.
Use the Generative AI report guide for the documented metric boundaries, then reconcile it with analytics using the AI impressions versus traffic workflow. Treat the viewport test as a separate interface dataset.
If clicks fall while measured pixel displacement increases, the two observations are consistent with a visibility explanation. They still do not prove causation without a suitable comparison period and control for query demand, ranking, snippet changes, and other SERP features.
The publisher decision
Do not rewrite pages merely because one AI Overview became taller. Keep answering the query clearly, support consequential claims, and make the source useful when a searcher chooses to click. The immediate operational change is measurement: add viewport state to any SERP-observation protocol.
Google’s confirmation supports the existence of dynamic expansion and its scroll-stop behavior. It does not support a universal rollout claim, a ranking conclusion, or a percentage loss in organic traffic.
Sources, method, and limits
Source: Search Engine Roundtable’s August 28 report containing Google’s explanation of the dynamic expansion and scroll-stop behavior.
Method: We translated the interface claim into a pixel-displacement protocol that keeps ranking, viewport exposure, source links, and clicks separate.
Limits: No cross-query sample or CTR study has been run for this article. Google has not published eligibility, rollout, or traffic data for the feature.
Ask a question or join the discussion