v1.8.0Duplicate and hidden meta descriptions, unsized images, and check descriptions that match the scan
- The meta tags check now flags a page with more than one meta description tag. Google doesn't say which one it shows, and the second tag is often left behind by a theme or an SEO app. A duplicate counts the same as a missing tag.
- It also flags a description Google can't read. Google stops reading the page head at the first element that doesn't belong there, such as an image or an iframe, and ignores the tags after it. The search preview lists every description tag the page has and names the element that hides the description, and description tags are recognised whatever the letter case of their name attribute.
- The page speed check now also flags pages where several images have no width and height set, which makes the layout jump as they load. It only ever warns, because a stylesheet can size images in ways the HTML doesn't show. The by-the-numbers strip shows how many images lack a size.
- The methodology page and the report's check explanations now describe exactly what each check measures. Several described tests the scan doesn't run, such as skipped heading levels, touch targets, render-blocking resources and schema validation, and the score was described as weighted when every check counts equally.
- A check that warns or fails now shows how to fix it right under the check, without opening it. Opening a check still explains why it matters and what passing looks like. This changes how reports display, not their scores, so older reports show it too.
- Scores can change: a page with a duplicate or hidden description now gets a meta tags warning where it used to pass, or a fail if meta tags already had another problem, such as a missing canonical link, and several unsized images turn a passing page speed check into a warning. Existing reports keep the scores they were given, so a since-last-scan comparison can show these checks changing for this reason alone.
v1.7.0An embeddable badge for pages that read as human-written
- Reports whose verdict is "Mostly human-written", scored with enough confidence, now include an "Add this badge to the page" box with a copy-paste HTML snippet. Other reports don't get a badge at all.
- The badge names the page that was scanned and shows that report's AI score and scan date. It links back to the report, so anyone who sees it can check the evidence behind it.
- A report covers a single page, so the badge is meant for that page, not a sitewide footer. It stays tied to the report it came from: a later scan of the page gets its own badge, and an older report already points visitors to the latest scan of the same page.
- Scores, verdicts and the scan rubric are unchanged. Past reports are not re-scored, and older reports with a qualifying verdict show the box too.
v1.6.0The full governance breakdown for everyone
- On the single-page report, the full governance breakdown is now shown to everyone: every risk's explanation, frameworks, guidance links and fix snippets. The paid plan that gated it was retired before launch.
- This applies to past reports too. The breakdown was always worked out on every scan and only hidden, so older reports now show it in full.
- Scores, verdicts and the scan rubric are unchanged. Past reports are not re-scored.
v1.5.0Current-generation scoring, and reports that show their age and what changed
- Both scoring passes, the fast first pass and the stronger second pass, now run on the current generation of the underlying model, and escalation also acts as a safety net: when the first pass cannot evaluate a page, the stronger pass runs instead of the scan failing. The rubric, the four signal categories, the findings with evidence and the fields on the report are unchanged.
- Scores and confidence are not strictly comparable across this boundary: a fresh scan of the same page may differ from one scored under an earlier version, so compare reports scanned under the same version.
- Every report shows how long ago the page was scanned, with the exact time on hover; previously the header read "Scanned just now" whatever the report's age. A recent scan of the same page is reused only briefly and is labelled when it is, and every report has a "Re-scan this page" button, so you can check a fix without going back to the homepage.
- When a page was scanned before, its report opens with what changed since that scan: the SEO and AI scores before and after, the SEO checks that improved or got worse, and the change in the number of AI findings. Older reports point to the latest scan of the same page.
- That comparison only lists checks that come out the same on an unchanged page. Page speed and the broken-link check are measured live and can vary between runs, AI findings are written fresh on every scan, and governance risks can shift for reasons other than changes to the page, so none of these are compared item by item. When the two scans were scored by different generations of the scoring model, the comparison says so.
- Past reports are not re-scored; the next fresh scan of a page runs under this version.
v1.4.1Stricter content-domain detection
- Fixes a misclassification where local-business and blog pages built on a popular CMS were labelled as news sites and shown news-publisher risks such as defamation exposure. The platform a site is built on is no longer treated as evidence of what the site is about.
- Domain keywords now match whole words only, so a newsletter signup no longer reads as a news signal and a site's own terms-of-service page no longer reads as legal-sector content.
- The page's own structured-data declarations, the schema.org types it says it is, now count as a signal of what kind of page it is.
- A page is only placed in a specialised sector when independent signals agree. Weaker evidence falls back to general, so sector-specific governance risks no longer attach to a page on thin evidence. The trade-off is deliberate: a page we can't place confidently gets the general checks rather than another sector's.
- AI and SEO scores and verdicts are unchanged. Past reports are not re-scored; the next fresh scan of a page runs under this version.
v1.4.0Sentence rhythm, search/social previews, and indexability
- Reports now show a sentence-rhythm chart: one bar per sentence of the crawled text, in reading order, with average sentence length, rhythm variation, and vocabulary diversity alongside. Even cadence is one of the strongest machine-writing tells; this makes it visible instead of only describing it. The chart is a heuristic lens computed from the crawl — it is not an input to the AI score.
- A new search & social preview section rebuilds how the page presents in a Google result and as a shared link, from the tags we crawled — and flags missing or truncation-prone titles and descriptions, and a missing share image.
- Indexability is now surfaced: the page identity card lists the robots directive and canonical URL, and a page that opts out of search indexing gets a prominent alert at the top of the report, since that overrides everything else ranking-wise.
- LLM-marker phrase counts are now contextualised as a density per 1,000 words with a plain-language density band, and a page with zero matches now says so instead of hiding the section — absence of stock AI vocabulary is itself a signal.
- The by-the-numbers strip gains a text-to-HTML content ratio.
- Backwards-compatible: everything above is computed at render time from the crawl snapshot already stored with each scan, so existing reports gain the new sections without being re-scored. Scores and verdicts are unchanged.
v1.3.2Reasoning summary moved up; report previews use it
- The model's one-paragraph reasoning summary now renders directly beneath the verdict, so the plain-English explanation of the score is the first thing a reader sees.
- Link previews and search snippets for a report now use that same per-scan summary instead of a generic score string, so a shared report describes the page it analysed rather than just the numbers.
- Scoring is unchanged, and no report content was added or removed — only the section order and the preview text moved.
v1.3.1Pro plan required for the full governance breakdown
- The governance section now gates on plan. Free viewers see the alert summary, the score band, and the first risk as a teaser; a Pro CTA stands in for the remaining risks.
- The top-of-report alert card stays visible to everyone — the count and severity badges still answer how many risks were found and how severe they are on a free scan.
- Pro and Business viewers see every risk's plain-English explanation, regulatory framework, official guidance links, and copy-paste fix snippets.
- Scoring is unchanged. Only the rendering branches on the viewer's plan; a cached scan reads the same numbers as before, what changes is what the page chooses to show.
v1.3.0Content-domain detection and governance scoring
- Reports now classify the page's content domain — what kind of site it is, in plain-English sector labels — and use that classification as one input to the new governance score below.
- A new governance score sits alongside the SEO and AI scores. It summarises how the page's content domain and its AI-automation signal combine into regulatory and trust exposure for that kind of site.
- Findings now include a governance risk section: each risk renders as its own card with a severity, a plain-English explanation of the exposure, and a pointer to the relevant regulatory framework when one applies.
- Mitigations the page is already doing — visible AI disclosures, expert-author bylines, regulatory boilerplate — are listed alongside the risks rather than silently folded into the score, so readers can see what is working.
- Backwards-compatible: scans cached under earlier versions render without the new section. Past reports are not re-scored.
v1.2.0Evidence, recommendations, and a richer page snapshot
- Findings now ship with verbatim evidence quotes pulled from the page, tagged by where they appeared, so readers can see exactly what triggered the call.
- Findings now carry a one-sentence recommendation: the single most actionable next step for that issue.
- Reports now name what the page is doing well alongside the findings, not only what to fix.
- Reports surface a page identity card (title, meta description, final URL, language, OG card), by-the-numbers stats (words, images, alt coverage, link counts, schema blocks, HTML size), the full H1–H3 outline, and a sample of internal links checked for broken paths.
- Backwards-compatible: scans cached under earlier versions render without the new fields. Past reports are not re-scored.
v1.1.0Public release
- Initial public methodology: 7 SEO checks, 4 AI signal categories (content / structure / imagery / tone), 3 verdict bands.
- Two-model pipeline: a fast first pass, with escalation to a stronger model when the first pass returns low confidence.
- Findings capped at 3 per scan to keep reports scannable.
- Single-page scans only. Multi-page passes deferred to a later release.