Website Auditor AI Review | Improve Your GEO & AI Search Visibility with Website Audits 📈 EP #531
Summary
A video walkthrough from Everyday AI runs a third party tool, Website Auditor, against several websites and shows what it reports back: technical faults, security checks, and a read on how discoverable the pages are to large language models. The framing is generative engine optimisation, so the audit output is treated as a worklist for making a site easier for assistants such as ChatGPT, Claude and Gemini to find and reference.
The tool behind the review is a live product with a public homepage, API documentation and a changelog, and it ships a companion MCP server published as open source on GitHub, which means the same audit can be called from inside an agent rather than only from a browser. The walkthrough was not run again by AIOTruth, so what appears on screen stands as the publisher's own demonstration of the product.
Demonstration by Everyday AI, embedded from YouTube. AIOTruth did not reproduce the test.
Why it matters
Most site audits still grade the classic search layer and stop there, but the things that decide whether an assistant can quote you sit slightly to the side of that: whether the crawler reaches the page without executing scripts, whether the main text extracts cleanly, whether entities and claims are stated in a form a retrieval system can lift. A tool that turns those checks into a named list gives an owner something concrete to fix, and the MCP server matters more than the dashboard does, because it lets the check run inside the assistant workflow that is doing the optimising. The caution is the same one that applies to every vendor in this category: a supplier's visibility score is a proxy the supplier defined, not a measurement of whether ChatGPT or Gemini actually cited you, and only tracked answers over time settle that.
Source
- website-auditor.io/ the item itself, published by Everyday AI, created by Everyday AI
- github.com/SpikeyCoder/website-auditor-mcp/releases Public source code or repository
- github.com/SpikeyCoder/website-auditor-mcp Public source code or repository
- website-auditor.io/changelog Reproducible first-party demonstration, first party
- website-auditor.io/api Named expert analysis, or a first-party claim about itself, first party
- youtube.com/watch?v=AYGmc-1Kk4kwhere AIOTruth found it
What was checked
- canonical URL taken from the page itself
- read the item page (200)
- https://github.com/SpikeyCoder/website-auditor-mcp/releases: supports the item, tier 6 (Public source code or repository)
- https://github.com/SpikeyCoder/website-auditor-mcp: supports the item, tier 6 (Public source code or repository)
- https://website-auditor.io/api: supports the item, tier 8 (Named expert analysis, or a first-party claim about itself)
- https://website-auditor.io/changelog: supports the item, tier 2 (Reproducible first-party demonstration)
- https://website-auditor.io/: supports the item, tier 8 (Named expert analysis, or a first-party claim about itself)
- https://jayjohnson.co.uk/perfecting-prompts: does not mention the item, tier 9 (Reputable reporting)
Limitations
- The demonstration was not independently reproduced by AIOTruth.
AIOTruth judgment
Relevance scored 10 because the subject is AI visibility itself rather than a general marketing topic that touches it. Evidence scored 9 and the status is Confirmed because the tool's own homepage, API documentation and changelog were fetched, alongside a public GitHub repository for its MCP server, so the product exists and behaves roughly as described rather than being a claim resting only on a video. Usefulness scored 6, the weakest of the four, because the walkthrough demonstrates the interface and its findings without establishing that acting on those recommendations changes what assistants retrieve or cite. Originality scored 7: the packaging of security checks, technical faults and GEO reporting into one audit is a reasonable combination, but the audit tool category is already crowded. Confirmed evidence carrying a proxy metric and an unproven outcome is what produces 8.1.
How this score was calculated
| Dimension | Weight | Score | What produced it |
|---|---|---|---|
| AIO relevance | 30% | 10 | ai search, geo, ai visibility; 3 scope question(s) matched |
| Usefulness | 30% | 6 | 1 artifact(s), 4 actionable marker(s), 0 measured figure(s) |
| Evidence | 25% | 9 | Reproducible first-party demonstration; 5 verified source(s) across 2 domain(s) |
| Originality | 15% | 7 | no original testing found; closest archive match 0.083 |
aioRelevance x 0.30 + usefulness x 0.30 + evidence x 0.25 + originality x 0.15. The rubric is published in full on the Editorial Method page. Scoring is deterministic: the same item scores the same on every run.
Watch the demonstration Open the source
Found something wrong here? AIOTruth corrects material errors openly. Have something we should review? Submit a find.