website in GET /v1/brands/{brand_id}/audit, as Figures in the API describes.
Your weekly report arrives while website work continues in the background. The site read has no time limit. It stops at its page allowance or your brand’s usage allowance and marks that coverage as truncated. One-time audits keep their time limits.
Findings
A finding is one thing a page or the whole site can get wrong, such as a missing title or a homepage that never says what you sell. Full audits and weekly reads check every finding below. Quick audits leave out seven findings, and Base audits leave out six. Each checked finding ends in one of three states:- Measured. Heralded read what the finding needs. Its share, from 0 to 1, is how much of what it reads holds the finding, such as the share of read pages without a title.
- Not measured. Heralded could not read what the finding needs. The finding’s
reasongives the class and itsdetailsays why in words, such as “Lighthouse returned no font-size audit for the homepage.” The classes arenot_readwhen the pages or checks it needs were not read,truncatedwhen the run ran out of time before the finding was judged,pendingwhen a page speed result had not arrived,provider_unavailablewhen a service Heralded relies on failed,no_briefwhen the finding needs a brief that the read has none of, andnot_in_quickwhen it is a check a Quick audit leaves to the Base audit. - Not applicable. The finding cannot apply to your site, such as a language-alternate check on a site in one language.
llms_txt, ai_training_blocked and thin_pages.
Copy and positioning checks
Heralded checks whether your pages make specific claims, sound generic, show proof, state your brand’s claims, address your buyer and name a problem you solve. Each answer has a short reason based on the page. If the check fails to return a valid answer, those findings stay unmeasured. Proof is not checked on About pages. Tone is checked separately against your brief. An uncertain tone answer stays unmeasured. Quick audits check copy and proof without a brief.Areas and groups
The findings sit in eight areas, and the areas in three groups.How the score is worked out
- Area. An area’s score is 100 × (1 − the sum of weight × share ÷ the sum of weights), over its measured findings. It has no score when none of its findings was measured. Positioning also needs a finding read from a page’s first screen, and Design one read from a first screen or from Lighthouse.
- Group. A group’s score is the mean of its areas that have a score.
- Website score. The score is the mean of the groups that have a score.
versions.bands gives the cut-offs.
A finding’s points off its area are 100 × its weight × its share ÷ the sum of the area’s weights. Its points off the Website score are those points divided by the number of scored areas in its group and by the number of scored groups, which is how the score averages them. Rounding happens at each step, so the points can add up to a point more or less than the score lost.
Fix first
Fix first orders the findings that hold something back by their points off the Website score, most first. A finding in an area with no score takes no points and comes last. Findings with equal points go issues before improvements, then the larger stake, which is the weight times how much of the site the finding touches, then the finding whose nearest page is fewest clicks from your homepage.Rules versions and trends
The findings, their weights and their thresholds are versioned together as the findings rules, andversions.findings_policy names the version a read used. Two scores compare only when they were measured under the same rules version and the same kind of read. Where the version changes, the trend breaks, break_before marks the first point of the new line, and the changes since the last read name no fixed or new findings.
A brand’s first website score is marked as measured more deeply when a Base or Full audit of the same site came before it. The weekly report reads more of the site than the audit did, so a score that differs from the audit’s is not a change in your site.
Changes since the last read
Each weekly report lists what changed since the previous one:- the new pages it judged;
- the pages whose content changed;
- the findings fixed, measured with a share before and none now;
- the new findings, measured with none before and a share now.