One scorer, two surfaces
The free check on our homepage and the AEO Content Score inside the dashboard share the same code path. We made that a hard rule: if the public report says a page scores 61, the dashboard says 61 too. The dashboard just runs it against more of your pages — your own site, and anything you've published through a connected HubSpot account — and sorts worst-first so you know where to start.
How a page is read
We fetch the page, strip scripts, styles, and markup, collapse whitespace, and keep the first few thousand characters of visible text. That's roughly what an answer engine has to work with when it decides whether a page contains a quotable, standalone answer. If the page can't be fetched, the score is null and the interface says so — it is never silently zero.
Freshness
Signs that the content is current and dated: visible update dates, changelogs, the current year in prices and comparisons. Answer engines weight recency heavily for anything that changes over time, and a page with no temporal signals at all reads as potentially stale.
Structure
Clear headings, lists, an FAQ, and factual statements that can be lifted out of context. An engine reads a chunk of your page, not the whole thing — the question is whether that chunk contains an extractable answer, or whether the answer is scattered across three paragraphs of narrative.
Readability
Concise, plain, quotable sentences. Comparison tables with real numbers score better than prose describing the same comparison, because a table row is already the shape of an answer.
Overall, and what each axis maps to
Overall is the plain average of whichever axes could be scored. Each axis also maps to a specific fix — freshness to schema and dated-content updates, structure to an FAQ block, readability to a comparison table — and each of those is a one-click template in Agent Studio, grounded in the page that was just graded.
See this on your own brand
Run the free check — same scoring the dashboard uses, no account needed.
Run free check