New — Every scan now includes an AI Visibility report. It checks the four things that decide whether an answer engine can cite you: whether AI crawlers are allowed to fetch the page, how much of your content exists without JavaScript (crawlers don't run it), whether your content is shaped so an answer can be lifted from it, and whether the markup says who you are.

New — A no-JavaScript check that catches the most expensive AI-search mistake there is. If your page renders in the browser, GPTBot and ClaudeBot see a blank page — the report shows exactly what share of your words reach them.

New — Answerability scoring: which of your headings ask a question, whether a direct 20-to-120-word answer follows each one, and whether the page opens with the answer instead of a warm-up.

New — Ask the AI directly. Enter the questions your buyers ask, and WebScore puts them to Claude with live web search, then records whether you were mentioned, whether you were cited with a link, where you ranked in any list of recommendations, and which competitors showed up instead.

New — Prompt suggestions are free: WebScore reads your site and drafts ten buyer-style questions that never name your brand, which you can edit before running a check.

Improved — PDF reports now include an AI Visibility section: crawler access, how much of the page survives without JavaScript, how many question headings get a direct answer, and a score for each of the four areas, followed by every finding with its fix. It appears on the cover, in the executive summary and as its own section, and does not move the overall score — same as in the app.

Improved — The before/after proof card in the homepage hero now shows AI Visibility too: whether AI crawlers are allowed, how much of the page survives without JavaScript, and where the site stands on answerability, entity schema and trust. It reads as a current-state score rather than a gain, because the module is newer than these sites' first scans and there is no honest before to compare against yet.

New — A proper pricing page at /pricing. Every difference between scanning free, unlocking a $3 report and paying once for Lifetime, laid out line by line across scanning, the report itself, staying fixed and the AI tools, plus what a scan checks and the questions people actually ask before paying.

New — Clicking the URL field on the homepage now opens a full-screen scan panel: one oversized input, nothing else on the page competing with it, and the three things people want to know before typing a domain, that the account is free and previews every module score, what Lifetime costs, and the 14-day money-back guarantee. Submit from there and the reachability checks run in the panel rather than dropping you back to the page.

Improved — The scan panel can be left at any point: a close button in the corner, the Escape key, a click on the backdrop, or the link under the form. Whatever you typed is still in the field when you come back, and the page behind never scrolls while it is open.

Improved — On phones the before/after proof card shows just the categories now: Accessibility, SEO, Performance, AI Visibility and their scores. The per-check detail underneath each one was turning the card into a wall of small text at that width, so it waits for a screen wide enough to read it. Nothing changed on desktop.

Fixed — The Uneed and Product Hunt badges wrapped onto two rows on phones. They now stay on one row and scale down together, sized by height so they keep the same height as each other and their proportions, down to a 320px screen.

Improved — The homepage headline is now just "Website health audit", with the promise underneath it in one line: find what is holding back your traffic, conversions and rankings, and exactly how to fix it. The module list and the MCP mention that used to crowd the subheading moved out, since the MCP section is now the very next thing on the page.

Improved — Every em dash is gone from the landing page copy. Thirty-four of them, rewritten as real sentences rather than swapped for another punctuation mark.

New — The MCP server gained five tools and now runs as a loop rather than a set of one-off lookups. get_fix_plan ranks every open issue by how many score points fixing it recovers, so your AI picks what to work on instead of guessing. compare_scans diffs two scans and reports what was resolved, what is new and what is still open, so it can check its own work after deploying a change.

New — AI Visibility is now available over MCP. get_ai_visibility returns crawler access, how much content survives without JavaScript, answerability, entity schema and trust signals, and get_ai_visibility_brief hands your coding agent a brief written for the job: the failing checks, the change to make, what must not regress, and how to verify it. get_scan_history rounds it out with recent scans and their ids.

Improved — Scan results now lead with a short summary before the JSON: the score table, the issue counts and the five fixes worth doing first. An assistant that reads only the top of the response still gets the part that matters.

Improved — The fix rankings use the same deduction tables the analyzers score with, so a "+25 SEO" is the real delta. Performance and Best Practices are scored by Lighthouse rather than from an issue list, so their findings are marked unpriced and ranked by severity instead of being given an invented number.

New — Every blog article now ends with a real, visible FAQ section. All 37 have at least five questions, each answered in a single paragraph short enough to be lifted as a snippet, and the questions carry their own anchor links so an answer engine can cite the exact one.

Fixed — Eighteen articles were publishing FAQPage structured data whose answers appeared nowhere on the page. Google requires that text to be visible, and an answer engine reading the rendered page saw nothing at all. The FAQ frontmatter is now the one source for both the visible section and the schema, so the two cannot drift apart.

Improved — Nineteen articles had no FAQ at all, five had only three questions, and four opened without answering the question in their own title. All of that is fixed. Across the blog the number of question headings with a direct answer underneath went from 52 to 243.

Improved — The MCP server now sits directly under the hero, rebuilt as a single panel: what it does on the left, the paste-ready config on the right with a copy button and syntax colouring, and the tools it works in underneath. It replaces three stacked centred blocks that took twice the height to say the same thing. The hero subtitle now names both halves of the AI story too: AI visibility runs on every scan, and MCP is how an agent applies the fixes.

Improved — On the pricing page, Lifetime sits in the middle where the plan you should pick belongs, and each card now ends where its own content ends instead of being stretched to match the tallest one. The Creem payment badge moved below all three cards, since it covers every purchase and not just Lifetime.

Improved — The pricing block on the homepage is now just the decision: what you get free, what $3 unlocks, what Lifetime costs. The full feature lists moved to the pricing page rather than crowding the page you were still deciding on.

Improved — The homepage now leads with what each part of WebScore gets you rather than what it checks. Every section, from the three-step flow to the audit checklist, states the outcome first and keeps the technical detail underneath it.

New — The live demo now includes AI Visibility. It is a real report from a real scan, with crawler access, the no-JavaScript reading, answerability, entity schema and trust signals, plus the per-section "Copy fix for LLM" briefs.

Fixed — The AI Visibility issue list was titled "SEO Issues" and told you to improve your rankings, because it reuses the SEO component. It now says what it is, on both the dashboard and the demo.

Improved — The hero is lighter: the embedded demo frame is gone, replaced by a "Try the interactive demo" button that opens the full annotated report at /demo. Same thing to look at, without a second app booting behind the fold.

Improved — Landing page design pass: the hero is down to one headline, one input and two buttons, on a plain band with a single brand glow that now renders in light mode too. The announcement badge, the inline score line and the spinning gradient around the URL field are gone, and the "Try the interactive demo" button now has a real fill in light mode instead of reading as bare text. Alongside it, one heading scale that steps down on phones instead of six different sizes, shorter paragraphs, consistent icons on every card, and hover states that lift the card and nudge its arrow.

New — AI Visibility now knows what kind of page it is looking at. A landing page is no longer marked down for having no byline, no TL;DR and no citations — those are article conventions. Product pages are checked for Product schema with price and availability, listing pages for ItemList, and articles keep the full provenance checks. The detected page type is shown next to the score, with the reason on hover.

New — Every AI Visibility section has a "Copy fix for LLM" button. It writes a brief for your AI coding agent: the exact checks failing, why each one costs you citations, the change to make, what must not regress, and how to tell it worked. There's a whole-report version too, ordered by how much score each section is losing.

Improved — Checkout now takes the buyer from your signed-in session rather than the link, so a purchase can only ever credit your own account.

v2.1.72 — released September 10, 2026