Pages
Audit your own pages for citability, authority and readability — the three things that decide whether an engine quotes you.
Pages is the audit surface for your own site. Add the URLs that matter, and each is scored on the three properties that determine whether an AI engine can use it as a source.
Everything else measures the outside world. This screen measures the part you control.
Preview. The page audit crawler is not yet running, so this screen renders a sample dataset rather than your own pages. The scoring model below is what it will report. See Product status.
The three scores
| Score | Question | Driven by |
|---|---|---|
| Citability | Can an engine lift a quotable passage from this page? | Direct answers near the top, structured data, clean heading hierarchy, self-contained paragraphs, FAQ markup |
| Authority | Should it trust this page? | External references, author and organization signals, freshness, depth relative to competing pages |
| Readability | Can it parse the page cleanly? | Machine-readable structure, sensible markup, content not buried behind scripts, sane page weight |
Plus an Issues count: concrete defects found in the last audit, which flow into Pages Optimization as a work queue.
The scores are deliberately separate because the fixes are unrelated. A page can be beautifully structured and completely untrusted, or authoritative and impossible to extract a passage from. Averaging them into a single number would hide which lever to pull.
The page table
Each tracked page shows its title, URL, type (Marketing, Feature, Blog, Comparison, Tool), the three scores, its issue count and when it was last audited. Search filters the list.
Open a page for its full audit: score breakdown, the specific issues found, and what to change.
Managing tracked pages
- Add page — paste a URL to audit and track it. Start with the pages that already earn AI traffic (see AI Tracker → Top landing pages) and the pages you want cited: pricing, comparisons, category guides, docs.
- Re-analyze — re-run the audit after shipping a fix, rather than waiting for the next scheduled pass.
- Delete — stop tracking a page. Scores and issues go with it.
Track pages with a job to do. Fifteen well-chosen pages produce a better work queue than a hundred that nobody will ever edit.
Reading the scores
Compare across your own pages before comparing against any absolute standard. The useful questions are relative:
- Which of my pages scores worst on citability and receives AI traffic? Fix that first — it is already being read.
- Do my comparison pages score below my blog posts? Comparison pages are disproportionately cited for high-intent prompts; a gap there costs more than the number suggests.
- Did the score move after the last deploy? Re-analyze after each change so you learn which fixes actually pay.
From score to fix
Pages tells you what is weak. Pages Optimization tells you what to change, issue by issue, with severity, category, what the engine found, and a specific fix.
The loop is: audit a page here → work its issues there → re-analyze → watch the citation index for that page in Sources.