Which pages it checks
The checklist covers every page of yours the crawl read, your homepage always among them. Legal pages and files count toward the page checks, though they get no editorial checks. The readiness checks in Website, the standalone Audit, the Snapshot report and Home count the same pages from the same crawl. Website’s Pages heading and pager count the inventory the table lists, including URLs the crawl found and did not read. Filtering the table changes both counts. The site inventory reads your brand’s main language and country, including pages whose URL names no locale. When the crawl leaves mapped URLs out, Website explains how many pages it read out of all the pages listed, including pages that could not be read, and how many mapped URLs it excludes for other languages or countries, non-content URLs, other domains or the page limit. The inventory count comes from the same pages as the table before filters; exclusion counts are recorded by that crawl, so an older crawl with no recorded exclusions shows no explanation. A page engines cited in this run’s answers passes, since the citation shows they read it. A citation from an earlier run doesn’t count: a page cited before that is blocked now fails.What counts as a blocker
Each blocker comes with one line on how to fix it. A page Heralded couldn’t fetch is counted as not read, never as a pass. The list gives counts, such as “2 of 150 pages blocked”, not points.
An HTTP 429 response is a rate limit and stays not measured after bounded retries. A bot challenge is detected before its robots directives, so a challenge page’s noindex is not reported as your page’s own directive.
The checklist in the Snapshot report
The report’s verdict counts the checks below, such as “5 of 9 checks not met”, and reads “Nothing to fix” only when every check is met. The line under it says whether any page is blocked from AI engines and how many pages were checked. Under the verdict, the report groups the checks into page access, homepage content and structure, and speed, and marks each one met, not met or not measured, with what Heralded measured and the target. A blocked page and its fix sit under the page check it fails. The checks are:- the four page checks above, each over every page it read, such as “146/150 pages pass; 4 could not be read”. A page check with no failing page is met, unless most pages could not be read. The page checks read AI crawlers allowed, Page not hidden from AI engines, Page loads for crawlers and Text without JavaScript;
- the five homepage checks behind the report’s technical moves: Citation crawlers allowed, Main text visible without JavaScript, and three about your homepage’s structured data, Company details for AI, Company and website described for AI and Company name, logo and profiles.
/sitemap.xml first. If nothing there reads as a sitemap, it fetches the Sitemap: lines in your robots.txt, up to ten, and reports a missing sitemap only when it fetched every one and none reads as a sitemap. If robots.txt names more than ten and none of the first ten reads as one, the check shows as not measured. The Company and website described for AI check is met once the homepage’s structured data carries Organization and WebSite. A company description that lacks a name, URL, logo or two social profiles (sameAs in the code) shows what it lacks and keeps the points for the parts it has. Only a homepage with no company description reads as having none.
The standalone Audit shows the same checklist under Site readability, after its page checks. Its page table shows each crawled page’s access gates and status. The report links to the Audit under the checklist. Each technical move in the report’s Priority actions links to the check it would fix.
With the WordPress Connector, Heralded can fix robots.txt rules for AI crawlers itself; see Actions.
llms.txt isn’t a check here. Heralded offers it as a kit you can take at any time.