Website AEO
Website AEO (/visibility/pages) lists every page of your website with what AI answers do with it: how often it is cited, where it ranks among every page any answer cited, whether AI crawlers can read it, and the next step open on it. Pages are grouped into your site's own sections (Sections), named and ordered by your home page's navigation, with Legal and other last, or shown as one List.
The pages come from your sitemap (or, without one, the links on your home page), from a connected CMS, from the pieces you published through Viewfield and from the pages AI answers cited in the last 120 days. Only your site's English pages are listed; locale copies are left out.
Which site
One site is listed: the Website AEO site. It starts as your website, read from the public pages ("Your website · read only", with Connect your CMS to edit). A CMS connection that serves your website becomes the Website AEO site by itself; connecting any other site asks whether to make it the one. A manager changes it under Website AEO site in the AI Search Visibility settings (Settings on the Visibility board).
The numbers
| Column | What it is |
|---|---|
| Readability | Can the AI crawlers fetch and read it: the latest audit, scored 0 to 100 |
| Citation share | Of every citation the tracked answers made in the range, the share that named this page, per engine (ChatGPT, Claude, Gemini and Perplexity) and averaged with equal weight |
| Change | The citation share's change against the range before |
| Cited rank | This page's place among every page any tracked answer cited in the range, yours and everyone else's: "Cited rank #4 of 212". Not a search ranking |
| Actions | The open next steps on the page: a change to prepare, to review, to publish, each for named questions; Prepare starts one |
Ranges of 7, 30 (the default) or 90 days; views of All, Cited, Needs work (an open action, or readability under Good) and Not cited; sorted by any column; and the export downloads the list as CSV.
The readability audit
Viewfield fetches each page as its own reader, ViewfieldBot, with no model call: the pages AI answers cite, the pages a question should be won with and the pages with open work every day, the rest every week.
| Check | What passes |
|---|---|
| Reachable | The page answers 200 to a plain request: not an error, not a redirect chain, not another host |
| AI crawlers allowed | robots.txt lets every answer engine's crawler read this path |
| Indexable | No noindex in the meta robots or the X-Robots-Tag header; nosnippet is a warning |
| No bot wall | No bot challenge or captcha |
| Words in the HTML | The words are in the HTML a crawler receives, not only after JavaScript runs |
| Canonical link | The canonical link names this page, or none is set |
| Headings | One H1 and sections under H2s a crawler can split on |
| Structured data | JSON-LD a crawler can read |
| Title and description | A title and a meta description |
| Freshness | A visible updated date or a sitemap lastmod inside the last 12 months |
| Response time | Answered inside 3 seconds |
Each check says what was found, with its numbers ("robots.txt blocks PerplexityBot and Claude-SearchBot on /blog"), and what to do about it. A page that cannot be reached scores 0; a page your robots.txt keeps Viewfield's reader out of is not scored at all, because Viewfield honors that. Each AI crawler's verdict is robots.txt read for it, as text; Viewfield never sends a request under another crawler's name. Blocking a training crawler (GPTBot, ClaudeBot, Google-Extended) is shown as your choice and never costs readability: it keeps a page out of future models, not out of today's answers.
A page's own view
Open a page for three tabs:
- Analytics: its section (the pages before and after it there), its numbers with their change, its citation share over time with every change applied and every piece published marked on the line, how many answers cited it, and the questions AI answers cite it on and the ones it should win.
- Content: the readability audit in full, each AI agent's verdict from robots.txt, and the content factors that help an answer quote it (answer first, question headings, an FAQ, lists or tables, depth, a date).
- Optimize: its open next steps, and Prepare changes to propose a change to it for a question; see Page changes.
A manager can Check again to read the page now (twenty a day per workspace, one a minute per page).
Over MCP and in chat
list_aeo_pages, get_aeo_page, and in chat a page can be checked again now (managers). See MCP overview.