> ## Documentation Index
> Fetch the complete documentation index at: https://docs.heralded.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Website

> See what holds your site back, choose what to work on and explore your pages.

**Website** opens on **Overview**, with a headline about your site, its Website score and the findings to address first. **Pages** holds the page list and map. The date beside the title names the report you are reading.

## Overview

The figure band shows your **Website score**, **Reach**, **Message** and **Experience**. Choose a figure to open its findings. Each info button explains the figure. The score's info button also opens its full history and [method](https://docs.heralded.ai/methodology/website-score.md).

**How it’s worked out** opens the score panel: the score, **Reach**, **Message** and **Experience**, each with its weekly trend, then **Fix first** with the points each finding takes off. Its properties give the checks measured and the last read's page coverage. **Open as a page** adds each area's score and the full weekly trend. [Website audit](https://docs.heralded.ai/concepts/website-audit.md#how-your-website-score-is-worked-out) explains the calculation.

### Findings

**Fix first** lists up to five findings in [priority order](https://docs.heralded.ai/methodology/website-score.md#fix-first), with their severity, affected page count and area. Open a finding for its evidence and affected pages. **All findings** opens the full list, issues before what could be better, then information and checks that could not be measured. **Back to overview** returns to the overview. Choose **Group** to narrow it to Reach, Message or Experience.

Existing work opens from its stage, such as **Needs you**, **Heralded is on it** or **Live**. Work waiting for your review or approval says **Needs you**. **Work on this** offers the kinds of work that fit a finding and their cost. **Add to Work** files your choice for approval. You can select several available findings and add their work together. A reader without permission to start work sees the findings without filing controls.

A finding’s panel shows what Heralded found, its affected pages, the points it takes off your Website score and what it costs its area, as in "Costs 3.3 points in Conversion". Its pages follow, five at a time. Opening a page replaces the panel, with Back to the finding. **How to fix it** keeps the steps you can follow yourself, before the pages. The header gives the severity and area; **Open as a page** adds when it was measured.

**Your key pages** shows three first screens at a time. Each card has the page's title, address and four checks: what you sell, who it is for, why to choose you and the next step. Changed pages lead, marked **Improved**, **Worse** or **Changed**. Open a card for the page panel. **History** on the page's full page lists each stored read's date and page changes.

**What changed on your site** opens the new and changed pages, fixed findings and new findings. A page count opens Pages under that filter. A finding opens its panel. When the findings rules changed, the list says so instead of claiming a finding was fixed or appeared.

## Pages on your site

Pages counts the addresses on your site's report map, across its languages and hosts. An address that redirects to another page does not count separately. Numbered listing pages and unread generated archives do not count as pages either. [Site readability](https://docs.heralded.ai/concepts/site-readability.md) describes coverage and selection.

## Pages

Choose **List** or **Map** on Pages. The list groups the current page of results by URL section, past a language prefix. For example, `/de/blog/guide` belongs to **Blog**. A top-level address such as `/pricing` belongs to **Site**. These are URL sections, not buyer audiences.

The three figures above the list follow its filters and count all matching pages, before pagination:

* **Pages AI can reach** counts pages whose access checks say AI can read them.
* **With findings** counts pages with an issue or improvement. It shows a dash when any matching page was not measured.
* **Cited in AI answers** counts pages with at least one citation. It shows a dash when the citation measurement is unavailable.

Each row shows the page's address and how many of your claims it states under its title, then citations, **What to fix**, findings, readability and Search Console clicks. **What to fix** names the measured findings for that page. **No findings** means the page was measured and has none. **Not measured** means no verdict was recorded.

**Filters** holds Category, Findings, Readable, Since last read and Language where more than one language is present. Search by title or address. Sort from a column heading and turn pages with the pager. **Site makeup** opens the category breakdown under those filters.

A page outside the main language carries its language while all languages are shown. **New** and **Changed** mark pages found or changed since the previous report. Open a row for the page's panel, with its citations, checks, findings and available work.

## Map

The map shows your pages as a tree, with the links between them. Open a grouped section to see its pages; **All sections** returns to the tree. Filter by **Pages with findings**, **Pages cited by AI**, section or language, or use **Find a page**. **Everything** shows pages with and without findings or citations. On a phone, **Filters** opens these choices. **Show as AI sees it** marks pages AI crawlers cannot read and links that need JavaScript.

The map starts with **Pages with findings** and **Pages cited by AI** selected. If neither set has pages, it shows **Everything**.

Select a page to open its shared panel with its first screen, findings and citations. A finding with fitting work offers **Work on this** or the stage of existing work. **Website** returns to the page list for the same report.

## Before a result is available

Before your Website score, **AI access** can show how many pages were checked and how many AI cannot read. Pending and unavailable results say so. Unmeasured figures use a dash. A partial read keeps its recorded results and its status beside the date.

## A page's panel

Open a row to see its page pane. The link beside its title opens the page in a new tab.

* Its header shows the page's type, last read, topics and, on a key page, its first-screen checks. The link icon opens the original page.
* Three [figures](#page-stats) lead to **AI answers**, **AI crawlers** and **Search clicks**, each with its weekly trend. **Page check**, the page's **Findings**, **Work on this** and **Cited on** follow, five rows at a time. Each finding keeps this page's note and severity.
* **Rewrite** offers **The first screen · free** and **The whole page · 1 credit** to members who can start work, on pages Heralded has read. An existing page rewrite opens from its stage.
* **Open as a page** adds the citation trend, **Engines**, the passages AI lifted, crawler visits, search visits, the comparison with competitor pages, delivery details, every page property and the link to all answers. A key page also has **History**, with each stored read's date and page changes.
* **Correct page type** is in the header's **⋯** menu. **Copy link** shares the open panel with its filters. The site-map link stays with the page's properties.
* **AI answers** opens the passages AI lifted. **Cited on** lists the questions whose answers cite the page; each opens its engines and passages.

## Page stats

A page's panel shows three figures under its header:

* **AI answers** counts citations of the page in your tracked questions' answers over the period. Open it for the passages answers lifted from the page and the times AI assistants fetched it live for their users.
* **AI crawlers** counts requests from AI training and AI search bots. Open it for each bot by kind, search-engine bots included.
* **Search clicks** counts clicks from Google Search. Open it for Search Console's impressions, position and queries, and the visits Google Analytics credits to AI assistants. The full page's properties give the word count, images, links in and clicks from your homepage.

On a key page, the properties also give **Load time**: the seconds until the page's main content shows on a simulated mobile load, PageSpeed's Largest Contentful Paint. Weekly reports measure it on key pages. A lab figure moves by up to a fifth from one run to the next, so compare it against other pages rather than week on week. The row is absent where PageSpeed did not answer.

Live fetches, crawler requests, search clicks and visits cover one 28-day window ending two days before the latest pinned weekly report started. A measured zero shows 0. A figure whose source is not connected reads **Not connected**, and its info button names the connection that fills it: Search Console fills **Search clicks**, Cloudflare or the WordPress Connector fill **AI crawlers** and live fetches, and Google Analytics fills visits from AI.

Crawler and live-fetch counts exclude requests known to be unverified. WordPress requests with unknown verification count. Visits from AI are a floor because visits without a referrer count as direct. WordPress crawl counts are a floor because caches can answer before WordPress sees a request.

The **AI crawlers** screen groups the bots into training, AI search, live fetch and search-engine bots. These counts include served requests with verified or unknown verification and exclude known-unverified requests.

When [Cloudflare](https://docs.heralded.ai/concepts/connections.md#cloudflare) verified that an AI crawler was refused on a page, or got not found from a page that is live, Heralded raises a site fix naming the crawlers and their counts, with where to find the rule in Cloudflare's Security Events and AI Crawl Control. You change that rule yourself; no connection applies it. With only the WordPress Connector, refusals stay unmeasured, because the plugin never sees a request your CDN or firewall answered. Search engine bots and unverified requests never count as refused.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.