===BODY===In short: We have launched Page Analytics, a page-by-page breakdown that shows AI-bot activity, citations, ranking and content score for every URL on your site. You browse the table, sort by the metric you care about and open any page for engine-by-engine detail; WriteWorks joins your sitemap, crawl logs and citation data behind the scenes. It's aimed at growth and search-marketing leaders who need to know which pages AI engines can read - and which they can't.
Site-level AI-search reporting tells you that visibility is up or down. It rarely tells you which URL caused it, which means content fixes get prioritised on instinct rather than evidence.
What is Page Analytics?
Page Analytics is a per-URL reporting view inside WriteWorks Analytics that scores how each page on your site performs in AI search. Instead of looking at one aggregate visibility figure for the whole domain, you see a row for every URL with its bot activity, citations, ranking and content score side by side.
That shift matters because AI-search performance is uneven at page level. A single well-structured page can earn citations across several engines while neighbouring pages on the same topic are never crawled at all.
How Page Analytics works
Page Analytics joins three sources of data: the URLs in your sitemap, crawl logs showing AI-bot activity against those URLs, and citation data from AI engines. Each page is then scored, and results can be compared across engines.
The four metrics on each row answer different questions:
- Bot activity - whether AI crawlers are reaching the URL at all, which is the first prerequisite for being cited.
- Citations - where the page has been referenced in AI answers.
- Ranking - how the page sits relative to other content for the queries it's associated with.
- Content score - a page-level score reflecting how readable and usable the content is for AI engines.
Because the data is joined to your sitemap, coverage gaps become visible too: pages you expect to be working hard that show no bot activity are as informative as the pages earning citations.
Who Page Analytics is for
Page Analytics is especially useful if you:
- Own a large content library and need to decide which URLs to refresh first, rather than auditing everything.
- Have invested in AI-search visibility but can't yet attribute results to specific pages.
- Suspect technical or structural issues are stopping AI crawlers reaching parts of your site.
- Manage content and SEO across several teams and need a shared, page-level source of truth.
- Report to leadership on AI search and need evidence tied to specific assets, not just a trend line.
Advanced users benefit too. If you already run detailed log analysis or citation tracking separately, having crawl and citation data joined per URL in one table removes a manual reconciliation step.
What Page Analytics changes
The practical shift is that AI-search work becomes a prioritisation exercise instead of a guessing game. When you can sort by content score or filter for pages with no bot activity, the next ten tasks in your content backlog choose themselves.
It also changes how you diagnose problems. A page with strong bot activity but no citations points to a content issue; a page with strong content but no bot activity points to a crawl or discovery issue. Those are two very different fixes, and Page Analytics separates them.
How to use Page Analytics
1. Open Analytics → Page Analytics.
2. Browse the per-page table and sort by the metric you care about - bot activity, citations, ranking or content score.
3. Click a page to open its engine-by-engine detail and see how that URL performs across ChatGPT, Claude, Perplexity, Gemini and Google AI Overviews.
Tips for a better result
- Start with your commercially important pages rather than the top of the table, so effort lands where it converts.
- Sort by content score ascending to surface pages AI engines are likely struggling to parse.
- Look for pages with citations on one engine but not others - engine-by-engine detail often reveals a formatting or structure fix rather than a whole rewrite.
- Check that your sitemap is current before you draw conclusions; missing URLs won't appear in the table.
- Re-check the same pages after a content update to see whether bot activity and citations follow.
Frequently asked questions
What does Page Analytics show for each URL?
Page Analytics shows four things per URL: AI-bot activity, citations, ranking and content score. Together they indicate whether AI crawlers are reaching the page, whether AI engines are citing it, how it ranks relative to other content, and how readable the page is for AI engines.
Which AI engines does Page Analytics cover?
Page Analytics compares performance across the AI engines WriteWorks tracks, including ChatGPT, Claude, Perplexity, Gemini and Google AI Overviews. Click any page in the table to open engine-by-engine detail, so you can see whether a URL performs consistently or is only being picked up by some engines.
How does Page Analytics know which pages to include?
It uses your sitemap URLs as the basis for coverage, then joins crawl logs and citation data against them. That means pages missing from your sitemap won't appear, so it's worth confirming your sitemap is complete and current before interpreting the results.
Does a low content score mean the page needs rewriting?
Not necessarily. A low content score highlights that AI engines may struggle to read or use the page, which is often a structure, formatting or clarity issue rather than a subject-matter one. Compare it against bot activity and citations for the same URL to work out which fix is needed.
The bottom line
Page Analytics turns AI-search visibility from a single site-level number into a per-URL worklist, so you can see exactly which pages AI engines can read, which they cite, and where content fixes will earn the most.
If you'd like to know which of your pages are doing the heavy lifting in AI search - and which are invisible - open Analytics → Page Analytics and sort the table by content score.
