PlatformPages
See which of your own pages the engines ignore.
Sources starts from the domains the engines cite. Pages starts from your site: every URL you publish, and what each one earns. Citations, AI crawls, and Google Search Console sit on the same row, so a page that already ranks in classic search can still show as invisible to the models.
Three signals on every row.
Citations come from collected answers. Crawls come from LLM Analytics. Search figures come from Google Search Console. Each is independent of the others, so a page can rank in Google and still never appear in an AI answer.
Every page, and what it earns
| Page | Status | Citations | Cited by | Clicks | Position |
|---|---|---|---|---|---|
| /compare/notion-vs-confluence | Search only | 0 | None | 842 | 4.2 |
| /guides/knowledge-management | Crawled, never cited | 0 | None | 96 | 11.4 |
| /pricing | Cited | 18 | 1,204 | 3.1 | |
| /guides/remote-teams | Earning nothing | 0 | None | 0 | None |
The useful list is the pages that earn nothing.
The filters above the table are the point of the screen. Each one names a gap and carries its own count, so you can see the size of the problem before opening it.
- 01
Not cited
In the inventory, but no engine pointed at the page in this window.
- 02
Earning nothing
No citation, no crawl, and no search clicks. The hardest version of the question.
- 03
Crawled, never cited
An assistant fetched the page and still did not cite it. Usually the most useful list on the screen.
- 04
Not in sitemap
Cited or crawled, but absent from what you declare. The models found something you never listed.
Google Search Console beside the citations.
Connect Search Console and the table gains clicks, impressions, and average position. That is how you see a page classic search already rewards that the models still ignore.
Google Search Console
What it adds
Clicks, impressions, and average position on the same row as the citations.
- Clicks
- 2,142
- Impressions
- 48,610
- Average position
- 8.4
How you connect
Add one address as a Restricted user on your Search Console property. Answyn stores no password or token. Removing that user in Search Console revokes access immediately.
- Stored on our side
- Nothing
- The question it answers
- Ranks in Google, missing from AI
- Your inventory, plus what they found
- The list is your sitemap, plus any page the engines cited or an AI crawler fetched. A cited page missing from the sitemap is kept and labelled.
- Citations from collected answers
- How often the engines pointed at that page in the selected window, and which engines did.
- AI crawls when LLM Analytics is on
- Which bots fetched the page, and how many of those were live fetches: an assistant reading it to answer someone now.
- Search Console when connected
- Clicks, impressions, and average position beside the citation columns. Google finalises those figures a couple of days late.
- Filters that count the gaps first
- Not cited, earning nothing, crawled but never cited, and not in the sitemap. Each filter carries its own count.
- A grant you can revoke
- Search Console access is one Restricted user on your property. Removing that user there ends the connection immediately.
More of the Answyn platform.
Nine screens, one record. Open the next surface when you want the next kind of evidence.
AEO Hub
What is measured, and how each number is earned.
Customer Journey
Where buyers hear you, and the shape of that walk.
LLM Analytics
Whether engines read you, and who clicks through.
Wyn
Answyn's AI search analyst, in plain English.
The Answyn MCP
Claude and ChatGPT, reading the same figures Wyn uses.
The Answyn API
Scheduled jobs that read every brand on one key.
Briefs
Writing and technical packs from the gaps you already ranked.
Reports
Board-ready documents from the same evidence.
Start with the questions your customers already ask.
Build the evidence now, then use every new answer to make the next marketing decision clearer.