--- type: Leaf title: Measuring your place in AI Overviews and search features description: Pull the full results page for fixed terms each week. Record the AI Overview, who it cites, and what sits above the organic results. resource: https://nationaldigital.com.au/headless-cms/ai-visibility/ai-overviews-and-serp-features/ tags: - headless-cms - AI Search Visibility - Measurement - Technical SEO - AI Overviews - AI Overview tracking - SERP features measurement - Google AI Overview citations - AI Mode visibility - search results page measurement timestamp: '2026-10-15T06:00:00.000Z' language: en-AU publisher: National Digital author: Cameron Young authorRole: CEO readingTimeMinutes: 6 wordCount: 1047 datePublished: '2026-10-15' dateModified: '2026-10-15' pillar: headless_cms canonical: https://nationaldigital.com.au/headless-cms/ai-visibility/ai-overviews-and-serp-features/ --- _Home — Content & Experience — AI visibility — Measuring your place in AI Overviews and search features_ # Measuring your place in AI Overviews and search features A rank on its own misreads a results page that opens with an AI Overview, a map pack and a question box. A weekly read of the whole page records what actually occupies it. **Quick answer:** A weekly pull of the full Google results page for fixed terms from a fixed location records whether an AI Overview appeared, which domains it cited and which features occupied the page, since Search Console does not separate the feature. ## About this page - Written by Cameron Young, CEO - 6 min read - Updated 15 October 2026 _AI Search Visibility — Measurement — Technical SEO_ ## How do you measure whether your business appears in Google AI Overviews? Pull the full results page for a fixed list of search terms from a fixed location every week, and record whether an AI Overview appeared, which pages it cited, and which other features took the space above the organic results. As a series, that shows how the page is changing. **Additional Context** Search Console counts AI Overview impressions and clicks inside its ordinary totals and does not separate them, so the weekly page read is the only way to see the feature itself. _High confidence · Verified 15 Oct 2026_ *The results page* ## Why a rank alone misreads the page A ranking report says the business is third for a term. On the page, the first thing a customer sees is an AI Overview that answers the question and cites two other sites, then a map pack with three pins, then a box of related questions, and the third organic result sits below the fold on a phone. Another term has the same rank and a plain page, and the result is clicked. The rank is the same number in both cases, which is why the number on its own tells so little. Google's own documentation describes AI Overviews and AI Mode as features that sit within Search and use the same eligibility as ordinary results, with no markup specific to them. That is useful in two ways. It means the measurement has to read the page, because there is no separate report for the feature. And it means the engineering response is the same work that makes any page eligible to be shown and cited. ## What to record for each term Fix the term list. Fix the location, because a results page in Brisbane differs from one in Perth, and a measurement that drifts between them is noise. Then, every week, record whether an AI Overview appeared, which domains it cited, whether a map pack appeared and who was in it, which related questions were shown, which video or shopping units appeared, and the organic positions of the business and its named competitors. Keep the raw page, because a question that arises in three months is answered by the page. Over a month the record shows which terms now open with an AI Overview and which do not, how often the business's pages are cited in one, and which competitors are. It also shows the related questions Google chose to display, which are customer questions in Google's own data and belong in the question set used for the assistant record. ### AI Overviews in Search Console Search Console includes AI Overview impressions and clicks in the Performance report under the ordinary web search type and does not break them out. The report remains the right source for clicks and impressions by page, and [reading Search Console as a weekly record](/headless-cms/ai-visibility/search-console-weekly-record/) describes how to keep it as a series. The feature itself, and who it cites, is visible only on the page. ## The engineering response Because the feature draws on the same index as Search, the response is the ordinary work of being indexable and readable: the page returns its text without script, the canonical is right, the sitemap is current, and the structured data describes the page's facts. That work is described across [crawl health and Core Web Vitals](/headless-cms/ai-visibility/crawl-health-and-core-web-vitals/) and [machine-readable delivery](/headless-cms/omnichannel-content-delivery/machine-readable-delivery/). None of it promises a citation. The record shows whether one followed, and that is the only claim the measurement supports. This page read is one of the sources inside [AI Visibility Management](/services/ai-visibility-management/), where it sits beside the assistant answers and the agent test so that a change in one can be read against the others. *Key Takeaways* ## What a weekly results-page read records A weekly pull of the full results page for fixed terms from a fixed location records AI Overviews, their cited domains and the features that occupy the page. The engineering response is ordinary indexability and readability work, and whether a citation follows is recorded, never promised. - **A rank is one number on a page that has many other things on it** An AI Overview, a map pack and a question box change what a third position means, and only a read of the whole page records that. _Critical_ - **Google documents AI Overviews as ordinary Search with no special markup** The measurement therefore reads the page, and the engineering response is the same work that makes any page eligible and readable. _Important_ - **Fix the terms and the location before the first pull** A results page differs by city, and a measurement that drifts between locations cannot be compared week to week. _Important_ - **Search Console counts the feature without naming it** AI Overview clicks and impressions sit inside the ordinary totals, so the page read is the only source for who the feature cites. _Critical_ ## Questions about measuring AI Overviews ### Is there a report that shows our AI Overview citations? Not from Google. Search Console includes AI Overview clicks and impressions in its ordinary totals without separating them. Seeing which pages an AI Overview cites requires pulling the results page itself for each term. ### Can we opt out of AI Overviews? Google's documentation describes the controls that limit what snippets and previews show from a page, and those apply to AI features as well. Opting out of the feature removes the business from it and leaves competitors in it, so it is a decision to make on the record. ### How many terms should the weekly read cover? Enough to cover the questions customers search for one business line, from a fixed location. The number matters less than keeping the list and the location constant, so that week-to-week differences are real. ### Will structured data get us into an AI Overview? Google says there is no markup specific to AI Overviews and that the same eligibility rules as Search apply. Structured data describes a page's facts in a form machines read without guessing. Whether a citation follows is what the record shows. ## Want to see what the results page looks like for your terms this week? - [Book a scoping call](https://calendly.com/cameron-at-national-digital/discovery) ## Related reading - [Recording what AI assistants say about your business](/headless-cms/ai-visibility/ai-assistant-answers/) - [The sources AI assistants cite when they describe you](/headless-cms/ai-visibility/sources-assistants-cite/) - [Testing whether an AI agent can use your website](/headless-cms/ai-visibility/assistant-task-tests/) - [Reading Search Console as a weekly record](/headless-cms/ai-visibility/search-console-weekly-record/) - [Keeping Business Profile, Bing and your site in agreement](/headless-cms/ai-visibility/business-profile-and-bing-consistency/) - [Crawl health and Core Web Vitals as a standing measurement](/headless-cms/ai-visibility/crawl-health-and-core-web-vitals/) ## Related **Parent:** - [AI visibility](/okf/headless-cms/ai-visibility.md) **Related:** - [Recording what AI assistants say about your business](/okf/headless-cms/ai-visibility/ai-assistant-answers.md) - [The sources AI assistants cite when they describe you](/okf/headless-cms/ai-visibility/sources-assistants-cite.md) - [Testing whether an AI agent can use your website](/okf/headless-cms/ai-visibility/assistant-task-tests.md) - [Reading Search Console as a weekly record](/okf/headless-cms/ai-visibility/search-console-weekly-record.md) - [Keeping Business Profile, Bing and your site in agreement](/okf/headless-cms/ai-visibility/business-profile-and-bing-consistency.md) - [Crawl health and Core Web Vitals as a standing measurement](/okf/headless-cms/ai-visibility/crawl-health-and-core-web-vitals.md) - [Turning visibility findings into engineering tickets](/okf/headless-cms/ai-visibility/findings-to-engineering-tickets.md) # Citations - [Google Search Central - AI features and your website](https://developers.google.com/search/docs/appearance/ai-features) — Google's guidance that AI Overviews and AI Mode use the same eligibility rules as Search and need no special markup. - [Search Console Help - Performance report](https://support.google.com/webmasters/answer/7576553) — How clicks, impressions and position are counted, and the dimensions the report can be grouped by.