What is AI visibility tracking?

Measuring how often AI engines read, use and send visitors to your pages. HadoSEO counts it from the requests your site receives: crawler reads, answer fetches, pages likely cited, and visits from AI, next to your Google rank from Search Console.

Does this help with ChatGPT SEO?

It shows the ChatGPT side of your SEO: which pages OAI-SearchBot indexed, which pages ChatGPT-User fetched to answer questions, and the visits ChatGPT sent back. It doesn't write content or track prompts; it tells you which pages are working so you know what to improve.

Where does the Google data come from?

Your own Search Console property, connected read-only with Google sign-in: clicks, impressions, CTR and average position per query and per page. Nothing is scraped from live search results.

How fresh is the data?

The Google side syncs daily; Search Console itself reports with roughly a 2–3 day delay, and hides some very-low-volume queries. The AI side is live; it comes from the requests your site receives.

How do you know a page was cited by an AI answer?

A citation is an answer-time fetch we attribute to an answer: the engine retrieved the page live while composing a response. Referral visits from answers are one confirming signal, but not required: cited counts include fetches we attribute to an answer, while visits are confirmed click-throughs. That's why a page can be cited 58 times and receive 19 visits.

Is this prompt tracking?

No. Prompt trackers show what AI says about your brand, and some now read server logs to show which bots visited. Rank & AI Visibility measures what actually happened on your pages from inside the request path: real fetches, real citations, real visitors. The trade-off is honest: it won't show you hypothetical answers you never appeared in.

Which AI engines are covered?

ChatGPT, Claude, Perplexity, Gemini, DuckDuckGo, Mistral and Brave, plus any crawler HadoSEO verifies against its operator's published IPs.

Do I need DNS or the Cloudflare Worker?

For the AI side, yes. The citations and referral data come from your request logs on either path. With Search Console alone you get the Google side.

Can I share this with my team or a client?

Yes. Invite teammates or clients to a domain so they see the same dashboard, and generate PDF reports to send along.

Is my Search Console data shared?

No. The connection is read-only, scoped to your property, used only to show you your own data, and you can disconnect at any time.

[ rank & ai visibility ]

Your visibility in Google and AI answers, side by side.

AI visibility tracking from real requests, not sampled prompts. Connect Google Search Console for clicks, impressions and position. HadoSEO's request logs add the AI side: which engines fetched each page to answer questions, and which answers sent visitors. Counted from real requests.

Connect Search Console Run free scan

app.hadoseo.com/acme-app.com/pages

acme-app.com▾

Pages ›

Visibility by page

Search Console · connectedHadoSEO logs · DNS

pageposclicksfetchedlikely citedvisits

/pricing6.1▲186964112pos 6.1▲ · 186 clicks96 answer fetches · 41 likely cited · 12 visits
/blog/aeo-vs-seo4.3▲4021315819pos 4.3▲ · 402 clicks131 answer fetches · 58 likely cited · 19 visits
/docs/api11.8374892pos 11.8 · 37 clicks48 answer fetches · 9 likely cited · 2 visits
/3.291874227pos 3.2 · 918 clicks74 answer fetches · 22 likely cited · 7 visits
/blog/geo-guide8.4▼121873311pos 8.4▼ · 121 clicks87 answer fetches · 33 likely cited · 11 visits

[ two sources, one view ]

Search Console for Google. Request logs for AI.

Search Console · read-onlyHadoSEO logs · DNS or Cloudflare Worker

[ how the join works ]

1

Google Search Console

read-only · synced daily

clicks
impressions
CTR
position

2

HadoSEO request logs

DNS or Cloudflare Worker · live

answer fetches
likely cited
visits from AI

joined bypage + day

3

app.hadoseo.com/acme-app.com/visibility

Visibility by page

Last 28 days

Example: Search Console and HadoSEO data joined by page
Page	PosPosition	Clicks	Answer fetches	Likely cited	AI visits
	from google		from ai			from ai
/pricing	6.1▲3.2	186	96	41	12
/blog/aeo-vs-seo	4.3▲1.8	402	131	58	19
/docs/api	11.8	37	48	9	2

1Connect Search ConsoleGoogle sign-in, read-only. Clicks, impressions, CTR and position sync daily.
2Connect your domainDNS or Cloudflare Worker: the same request logs that power crawl analytics.
3See both sides, per pageSearch Console history backfills. The AI side records from the first request on.

DNS

no-code · ~5 min

One record at your registrar.

Connect with DNS →

Cloudflare Worker

cloudflare worker · ~10 min

A small Worker on your own zone.

Deploy the Worker →

[ + ]compare the two paths

feature	DNS	Cloudflare Worker
best for	DNSClient-side apps: Lovable, Base44, React, Angular	Cloudflare WorkerServer-rendered sites, or client-side apps you run on Cloudflare
setup	DNSAn A record at your domain provider. No code, no redeploy. About 5 minutes.	Cloudflare WorkerA small Worker on your Cloudflare zone, with your API key. About 10 minutes.
you need	DNSAccess to your domain's DNS settings	Cloudflare WorkerYour domain on Cloudflare
traffic flows	DNSThrough HadoSEO's edge	Cloudflare WorkerThrough your own Cloudflare zone
crawl analytics	DNS✓ every request	Cloudflare Worker✓ every request
prerendering for bots	DNS✓ automatic	Cloudflare WorkerYour choice: prerendered pages, or analytics-only

Search Console only? You get the Google side. Add DNS or the Cloudflare Worker for AI visibility.

[ google search ]

Every query and page Search Console reports, synced daily.

Clicks, impressions, CTR and average position for every query and page Search Console reports. Google's own numbers, about 2–3 days behind, with very-low-volume queries by Google.

clicks3,751impr86.4kavg pos4.9▲4.7

last 30 days · Search Console

[ queries · 28d ]

queryclicksimprctrposΔ

aeo vs seo/blog/aeo-vs-seo2876,8404.2%4.6▲1.8287 clicks · 6,840 impr · 4.2% CTR · pos 4.6 ▲1.8
ai crawler analytics/product/crawl-analytics1423,4804.1%5.2▲2.7142 clicks · 3,480 impr · 4.1% CTR · pos 5.2 ▲2.7
generative engine optimization guide/blog/geo-guide893,6102.5%8.9▼0.689 clicks · 3,610 impr · 2.5% CTR · pos 8.9 ▼0.6
prerender for ai crawlers/product/prerendering611,8703.3%7.6▲1.461 clicks · 1,870 impr · 3.3% CTR · pos 7.6 ▲1.4
crawl log analysis tool/product/crawl-analytics261,5401.7%12.4—26 clicks · 1,540 impr · 1.7% CTR · pos 12.4 —

[ movers · 28d ]

rising

ai crawler analytics▲2.7

aeo vs seo▲1.8

prerender for ai crawlers▲1.4

falling

generative engine optimization guide▼0.6

lovable seo checklist▼0.4

see all queries →

[ coverage vs avg position · 90d ]

pages crawled + served rendered · logsavg position · Search Console · lower is better

HadoSEO connected

pages crawled + served rendered · logs14 → 412

avg position · Search Console · axis inverted (lower is better)18.2 → 4.9

41219

90d agotoday

[ ai answers ]

Which AI engines read you, use you to answer, and send you visitors.

Measured from the requests your site receives: which engines fetched each page live, which pages were likely cited, and which answers sent visitors.

answer fetches5,906likely cited824AI visits189

last 30 days · request logs

[ per engine · 30d ]

search index answer fetches likely cited (% of answer fetches)

ChatGPT16%

Perplexity15%

Claude12%

Gemini8%

DuckDuckGo12%

Brave11%

Mistral10%

+ 3 more engines in the dashboard

answer fetch = live retrieval while composing an answer · likely cited = an answer fetch we attribute to an answer (can exceed visits) · visit = confirmed click-through

[ ai referral visits · 30d ]

189 visits from AI answers · 30d

chat.openai.comperplexity.aiclaude.aigemini.google.com

[ most likely cited · 30d ]

/blog/aeo-vs-seoChatGPT · Perplexity · Claude58· 19 visits

/pricingChatGPT · Perplexity41· 12 visits

/blog/geo-guidePerplexity · Gemini33· 11 visits

/ChatGPT22· 7 visits

[ per page ]

One page. Its Google rank, its likely AI citations, and the crawls behind both.

/pricing/blog/aeo-vs-seo/docs/api

app.hadoseo.com/acme-app.com/pages/pricing

acme-app.com▾

Pages ›

/pricing

Last 30 days

Google · Search Console

impressions

4,210 ▲38%

clicks

186

ctr

4.4%

avg position

6.1 ▲3.2

AI · request logs

answer fetches

96

likely cited

41

likely-cited rate

43%

AI visits

12

likely cited by engine: ChatGPT 18 · Perplexity 14 · Claude 9

● avg position 9.3 → 6.1 (inverted, up is better)● likely cited 18 → 41 · 30d

Merged timeline

Sep 22 · logs

Googlebot crawled · snapshot v12
Sep 23 · snapshot

title changed (v13)
Sep 24 · logs

ChatGPT-User fetched · likely cited
Sep 26 · Search Console

Google avg pos 9.3 → 6.1
Sep 27 · logs

Perplexity-User fetched · likely cited
Sep 30 · logs

AI visit from chat.openai.com

Read it like this: Google clicks went up a little; AI started answering questions with this page; a few people clicked through from those answers.

Joined by page and day. No spreadsheets, no exports.

[ the shift ]

How much of your discovery comes from AI?

AI referral traffic is small next to Google. And it's growing. Knowing your own split is the difference between reacting to headlines and reacting to your data.

4.8%

of discovery visits from AI answers ▲2.1 pts · 90d

34.5%

fewer clicks for the #1 result when an AI Overview appears

Ahrefs · Apr 2025 →

68%

of US Google searches end without a click

SparkToro · 2026 →

8%

of people click a link when an AI summary shows vs. 15% without

Pew Research · Jul 2025 →

[ ai share of discovery visits · 90d · weekly ]

6%4%2%

2.7%4.8%

AI share of visits Google clicks (volume, own scale)90d ago → today · illustrative sample

Think of AI reads as the new "impressions": an early sign your work is landing, before a click (or even without one).

[ + ] prompt trackers vs hadoseo

what it measuresprompt trackers: answers to prompts you choose · hadoseo: requests your pages actually receive

shows answers you're absent fromprompt trackers: yes · hadoseo: no

ties to Google rank and visitsprompt trackers: no · hadoseo: yes

[ prompt trackers ][ hadoseo ]

what it measuresanswers to prompts you chooserequests your pages actually receiveprompt trackers: answers to prompts you choose · hadoseo: requests your pages actually receive

shows answers you're absent fromyesnoprompt trackers: yes · hadoseo: no

ties to Google rank and visitsnoyesprompt trackers: no · hadoseo: yes

Prompt trackers show answers you might appear in (and some read your logs). HadoSEO shows what actually happened on your site. Many teams use both.

[ questions ]

Rank & AI visibility, answered.

[ see both sides ]

Your Google rank and your AI answer traffic, in one view.

Connect Search Console Run free scan