Page-level AI citation rate: how to track one URL from crawl to citation
Site-wide numbers hide what a single page is doing. Here is how to follow one URL through crawls, citations, and content changes, using the sitemap page tabs.
You rewrote a pricing explainer three weeks ago. Your overall AI visibility is flat. Did the rewrite do anything? The dashboard cannot say, because it averages hundreds of pages together and the one you care about is a rounding error.
To judge one page, you need numbers for that page alone: when it is crawled, whether it is cited, how its position moves, and what changed on it. That used to mean stitching three tools together. On November 4, 2026, Promptwatch added page tabs to the sitemap view that bring those together for one URL.
The three tabs
Open a page from the sitemap and you get three views.
AI Visibility. One URL's citation rate and position over time, plus the prompts and responses that cite it. This is the number most people want first. It answers "is this page being cited, and is that going up or down?"
Content. The page as it was crawled, shown as a preview or as markdown, with content stats. It also shows how much changed between the last two audits, with title edits highlighted. That is your record of what the crawler actually saw, which is not always what you think you published.
Agent Analytics. Citation visits, crawler visits, and the crawler logs for that URL. These are the IP-verified AI crawler requests, so the page's access story is separated from everything else on the site.
Why a page needs all three
Each tab answers a different question, and the answer to the main question is usually a combination.
| Question | Where to look |
|---|---|
| Is the page cited, and where does it land? | AI Visibility |
| Did the change reach the crawler? | Content |
| Is the page being fetched at all? | Agent Analytics |
Take the pricing explainer. If the AI Visibility tab shows a flat citation rate, check Content next. Does the markdown view show your rewrite, or the old version? The audit comparison shows how much changed between the last two audits, so you can tell whether the edit was big or cosmetic. If the crawled version is stale, the page was not re-read yet, and judging the rewrite now would be premature.
Then check Agent Analytics. If crawler visits are present and citation visits are near zero, the page is collected but not pulled into answers. If crawler visits are absent, the problem is access, and no amount of rewriting will fix it.
Reading the citation rate carefully
A page-level citation rate is a ratio over the prompts you track, not a property of the page in isolation. If you add or remove prompts, it moves. If the model set changes, it moves. Before you read a change as the effect of an edit, check whether the tracked set changed in the same period.
Keep your reading modest. A rise after an edit is consistent with the edit helping, but it is not proof. Other pages, other sources, and the engines themselves all change. What you can say with confidence is what the page's data did and when.
Position matters alongside rate. The AI Visibility tab shows position over time, and a page that is cited but late in the source list is in a different spot from one cited first. The prompts and responses listed under the tab let you read the actual answers, which often explains a number faster than a chart does.
Page Tracker for pages outside your control
The sitemap tabs cover pages on your own site. Page Tracker is the companion for specific URLs, yours or a competitor's. If a competitor's comparison page keeps appearing in answers to your prompts, track it and watch how its citations behave. Citation Trends adds per-page figures for first cited, ramp-up days, peak rate, and decay half-life, which show whether a page's citations are steady or fade.
A routine for one page
- Record the date and the current citation rate and position from AI Visibility.
- Open Content and note the crawled version and the title.
- Make your edit and publish.
- Watch Agent Analytics for the next crawler visit on that URL.
- When Content shows the new version, start your comparison window from that date, not from the publish date.
- Read the AI Visibility tab after enough days have passed to include several runs of your daily monitor.
Step 5 is the one people skip. Counting from the publish date charges the old version's days to the new page.
If the page is published through Promptwatch's CMS connections, the publish status tracking follows each document from draft to live URL and then through crawls, citations, and AI traffic. That gives the same page-level story from the other direction, starting at the moment of publishing.
Why we rank it first for this job
Most trackers in our directory report brand-level visibility and stop there. The page-level view needs three data sources to agree: citations, the crawled content, and crawler logs. Promptwatch is the platform we would evaluate first for it because those three live in one place, and pages that underperform come back as Action Board items and Content Refresh suggestions instead of sitting in a report.
Next step
Start the 7-day free trial, connect your sitemap, and pick the one page you rewrote most recently. If you want a quick outside-in check first, run the free AI Visibility Report at promptwatch.com/ai-visibility-report.