AI visibility · AI overview tracking
AI overview tracking: AI search summaries per query and market
An AI search summary sits above the links on the results page, and whether it appears, what it says and which sources it cites changes by query and by market. Run your query set on the search engine itself from an exit in each market, logged out, and record the summary as a page element: present or not, its citations and how it moves.
Pay per GB · No subscription · Prices in EUR, excl. VAT
- €2.00
- per GB on ARC Fast, excl. VAT
- −44%
- at 1 TB (€1.12 / GB)
- 185+
- countries, city targeting
- Never
- expires — no subscription
Written for
- SEO and GEO teams
- Content strategists
- Search agencies reporting to clients
- Publishers measuring search traffic
The short answer
- This is search-page tracking, not chatbot tracking: the summary is a block on the results page, with its own presence rate, citations and interaction with the organic links below it.
- Google's AI Overviews were available in more than 200 countries and territories and more than 40 languages as of May 2025, so the market you query from decides the language and sources of the summary.
- Pew Research found an AI summary on 18% of Google searches in its March 2025 US panel, and far more often on long, question-style queries.
- Summaries are generated and vary between runs; sample each query more than once per period before calling a change.
The problem
What goes wrong without the right IPs
Rank tracking ignores the block above rank one
A page can hold position one while a summary above it answers the query and cites a competitor. A tracker that stores only organic positions reports no change while clicks drop.
Summaries are not deterministic
The same query can show a summary on one run and not the next, or cite different sources. A single check per week turns that noise into false trends.
Summaries load after the results
Depending on the page, the summary block can be assembled by scripts after the initial HTML arrives. A plain HTML fetch may then miss it and record a false absence.
One market reported as everyone's
Availability, language and cited sources differ between countries. A summary checked from one country tells you nothing about the others.
Personalised runs
Signed-in sessions and carried cookies shape the page. A logged-out run on a fresh session is the only comparable baseline.
What to collect
What you can collect
- Summary present
- Yes or no, per query, market and run. The presence rate across runs is the headline metric.
- Cited sources
- Each linked source in the summary, its domain and its order. Whether you are cited is the main outcome.
- Summary text
- Stored for diffing and for checking how your brand or product is described.
- Brand mentions
- Whether your brand and competitors are named in the text, regardless of citation.
- Organic results below
- Positions and URLs, to see whether the cited sources are also the top-ranked pages.
- Pixel offset of first organic result
- How far the summary pushes the links down the page, at a fixed viewport.
- Market, exit IP and viewport
- Country, language, exit and device profile, so every run can be reproduced.
- Run number within period
- Lets you report presence and citation as rates over repeated samples, not single observations.
How it runs
How a collection run works
- 01
Pick queries that can trigger a summary
Summaries appear far more often on long, question-style queries than on one- or two-word ones. Build a query set per market from your informational and comparison keywords, translated for each language.
- 02
Render the page, logged out, in the market
Load each query in a headless browser from an exit in the market, with a fresh context and the market's locale. Hold one sticky session for the page load and any "show more" expansion, then discard it.
Playwright: one fresh context per query, market in the username21 linesimport { chromium } from "playwright"const [host, port] = "proxy.arcproxies.io:8000".split(":")async function check(country: string, locale: string, url: string) { const sid = Math.random().toString(36).slice(2, 10) const browser = await chromium.launch({ proxy: { server: `http://${host}:${port}`, username: `USERNAME_pool-arcfast_country-${country}_session-${sid}_sesstime-5`, password: "PASSWORD", }, }) const ctx = await browser.newContext({ locale, viewport: { width: 1366, height: 900 } }) await ctx.route("**/*.{png,jpg,jpeg,webp,gif,woff,woff2,mp4}", (r) => r.abort()) const page = await ctx.newPage() await page.goto(url, { waitUntil: "networkidle" }) const html = await page.content() await browser.close() return html} - 03
Parse the summary as a block
Extract presence, text, cited links in order, and the position of the first organic result. Parse the organic results from the same page so citation and rank come from one observation.
- 04
Sample, then aggregate
Run each query several times per period, on fresh sessions. Report presence and citation as rates, for example "cited in 4 of 6 runs", and treat changes smaller than your sampling noise as no change.
- 05
Diff summaries over time
Compare the stored text and citations week on week. A new source cited, a competitor added, or a factual statement about your product changing are the events worth a person's attention.
Setup
Recommended setup
Summaries are a consumer-facing page element, rendered in a browser, so residential is the default; the ISP pool is a saving only where you have checked that it shows the same block.
| Plan | Role | Session | Targeting | Price |
|---|---|---|---|---|
ARC Fast Rotating residential | Default for summary checks Residential exits in each market, held for one rendered page and its expansion. City targeting is there for queries with local intent. | Sticky, 5 minutes per query | Country + city | €2.00 / GB €1.12 at 1 TB (−44%) |
ARC Ultra Premium residential | For markets with gaps in the grid Premium residential for the markets where ARC Fast leaves failed runs you cannot explain. Route only those. | Sticky per query | Country + city | €3.50 / GB €2.17 at 1 TB (−38%) |
ARC Mobile Mobile 4G/5G | For the mobile results page Carrier IPs with a mobile device profile, when the summary on a phone is the deliverable. Country only, four markets. | Sticky, 5–60 minutes | Country (DE, GB, US, JP) | €3.50 / GB €3.15 at 1 TB (−10%) |
Prices are list prices in EUR, excl. VAT. Volume discounts apply automatically at checkout — full ladder on the pricing page.
Connect
One connection string per market
The country, city and sticky session are tokens in the username. Change the token, change the market; keep the session handle, keep the IP.
http://USERNAME_pool-arcfast_country-de_session-k3f9a1x2_sesstime-10:PASSWORD@proxy.arcproxies.io:8000Swap _country-de for any market you quote. The full grammar is on the residential proxies page.
Illustration
What 500 queries in 6 markets, 3 samples a week costs
An illustration with round numbers — your pages, payloads and retry rate will differ. The arithmetic is the real price ladder.
Assumptions
- Queries per market
- 500
- Markets
- 6
- Samples per query per week
- 3
- Rendered page, images and fonts blocked
- 1.2 MB
- Weeks per month
- 4.3
- Bandwidth per month
- ≈ 47 GB
On ARC Fast
€82.72per month, excl. VAT
47 GB bought in one purchase at €1.76 / GB (−12% volume rung, applied automatically).
The same 47 GB on ARC Ultra: €146.41 at €3.12 / GB. Route only the jobs that need it through the pricier pool.
Rendered results pages are much heavier than plain HTML; blocking images, fonts and media is the largest saving. Bandwidth does not expire, so a quarterly purchase covers a quarter of runs.
Bandwidth never expires, so a bigger single purchase is only ever cheaper per GB. See the ladder.
In depth
AI overview tracking, in depth
AI search summaries are not the same as AI assistants
The parent AI visibility page covers answer engines in general. This page is about one surface: the generated summary a search engine places on its own results page. It differs in ways that change how you measure it.
| Search-page AI summary | Standalone AI assistant | |
|---|---|---|
| Trigger | A search query; appears on some queries only | A prompt; always answers |
| Context on the page | Organic results, ads and other blocks around it | The conversation only |
| Key metrics | Presence rate, citation share, links pushed down | Mentions, sentiment, cited sources |
| Collection | Rendered results page per query and market | Prompt and follow-ups per run |
| Comparison point | Your organic rank on the same page | Other assistants |
How AI Overviews choose and show sources
Google's documentation on AI features says a page must be indexed and eligible to be shown in Search with a snippet to appear as a supporting link in AI Overviews or AI Mode, and that there are no additional requirements or special optimisations needed beyond normal SEO practice. It also notes that these features may use query fan-out, issuing multiple related searches across subtopics, which is why cited sources are not always the pages ranking for the query you typed.
Traffic from AI features is included in Search Console's Performance report under the Web search type, not separated out. That is a reason to measure the page itself: presence and citation per query come from collection, not from your analytics. Site owners can limit what appears from their pages with nosnippet, data-nosnippet, max-snippet or noindex.
What the research says about clicks
Pew Research Center analysed the browsing of 900 US adults in March 2025, covering 68,879 Google searches. An AI summary appeared on 18% of them. Users who saw a summary clicked a traditional result on 8% of visits, against 15% when no summary appeared, and clicked a link inside the summary on about 1% of visits.
Query shape mattered. Searches of one or two words produced a summary 8% of the time; searches of ten words or more, 53%. Searches starting with a question word produced one 60% of the time. That is the practical case for tracking presence by query type, not just by keyword.
Google reported in May 2025 that AI Overviews had reached more than 200 countries and territories and more than 40 languages. Wider availability makes the per-market view the default rather than an extra.
Sampling: how many runs make a measurement
A generated summary is not a fixed ranking. Presence and citations vary between runs of the same query from the same market, so a single observation per week is an anecdote. Run each query several times per period on fresh, logged-out sessions and report rates.
- Three samples a week per query and market is a sensible floor for trend reporting.
- Keep the configuration fixed — exit country, locale, viewport and device profile — so variance comes from the engine, not from you.
- Report ranges, such as cited in 4 to 6 of 9 runs this month, rather than a single yes or no.
- Store the exit with every run — the guide to testing proxy location shows how to check it.
For the classic ranking side of the same pages, see SERP monitoring; for running the browser itself, the Playwright integration has the proxy setup in detail.
Works with anything that takes a proxy URL
Playwright
- Puppeteer
- Python requests / httpx
- Node.js
- n8n
- Docker
FAQ
Questions
Something not covered? Write to contact@arcproxies.io.
How do I track whether my site is cited in AI Overviews?
Render the search results page for each query from an exit in the market, logged out, and parse the summary block: whether it is present, its text and the sources it links. Repeat each query several times per period and report how often your domain is cited.
Why does the AI summary appear on some runs and not others?
Because it is generated per request and the engine decides per query whether to show it. Presence and citations vary between runs even from the same market. Sample each query several times and treat the result as a rate.
Can I see AI summaries with a plain HTTP request?
Not reliably. The summary block can be assembled by scripts after the first HTML arrives, so a plain fetch may record a false absence. Render the page in a headless browser and block images, fonts and media to keep the weight down.
Does Search Console show AI Overview traffic separately?
No. Google says traffic from AI features is included in the Performance report under the Web search type, without a separate breakdown. Measuring presence and citations per query therefore needs collection from the results page itself.
Which countries can I track AI summaries in?
ARC Fast and ARC Ultra take a country token for every market in the targeting list and a city token for a published list of metros. ARC Mobile adds carrier IPs in Germany, the UK, the US and Japan for the mobile results page.
How much bandwidth does AI overview tracking use?
Rendered results pages are heavier than plain HTML. At about 1.2 MB per page with images and fonts blocked, 500 queries in six markets sampled three times a week is roughly 46 GB a month.
Sources & review
Last reviewed by the ARC Proxies team. Prices are read from the live catalog at build time.
- [1]Google Search Central: AI features and your website
- [2]Google: AI Overviews are now available in over 200 countries and territories, and more than 40 languages (May 2025)
- [3]Pew Research Center: Google users are less likely to click on links when an AI summary appears in the results (22 July 2025)
Get started
Buy a gigabyte and try it on your own targets.
No subscription, no sales call. Code WELCOME15 takes 15% off your first purchase, and whatever you do not use is still there next quarter.