The checkup reports what its fetch can verify—not whether a website will rank or be cited.
One submitted public URL coordinates Search visibility, Agent readiness, and Website performance checks. Every result includes an observed value and status. Optional or contextual practices stay in Review and do not reduce the Search or Agent score.
Three evidence sections inside one report.
Search visibility checks
Page metadata, HTML, crawl and index signals, links, structured data, trust evidence, and other observable page signals.
Agent readiness checks
Public HTML, crawler-policy evidence, discovery resources, and optional agent-friendly conventions.
Mobile Lighthouse items
Four Lighthouse categories and five mobile lab metrics when Google PageSpeed Insights completes the Performance stage.
Performance is independent. A missing API key, quota limit, timeout, or upstream PageSpeed failure makes only that stage unavailable; Search and Agent evidence still returns.
A bounded fetch, not a full-site crawl.
Submitted page
The final public HTML response, status, headers, metadata, visible initial text, headings, links, images, directives, and structured data for one URL.
Supporting public files
Bounded requests for robots.txt, a discovered or likely sitemap, llms.txt, llms-full.txt, and an optional Markdown response for the submitted page.
Provider-specific access
Root-policy evidence for selected search and agent crawlers. A named crawler group is optional; wildcard rules may govern access instead.
Mobile performance
Google PageSpeed Insights mobile Lighthouse categories and metrics, kept separate from exact-URL and origin-level Chrome UX Report field data.
Only objective Search and Agent issues lower their scores.
Each Search and Agent stage starts at 100. Critical findings deduct 10 points and Needs work findings deduct 2 points. The score never falls below zero. Lighthouse uses Google's returned category and metric scores instead of this deduction model.
An objective issue that can materially block or undermine the checked evidence.
An objective weakness that the single-page fetch can verify.
An optional, intent-dependent, contextual, or manually verified item.
The checked public evidence met the defined condition at the recorded time.
It means the objective checks in that stage found no score-impacting failure at that time. Review items, private data, site-wide evidence, rankings, indexing, citations, and business outcomes remain outside that claim.
llms.txt, Markdown, and crawler declarations are context—not Google requirements.
The checkup can inspect llms.txt, llms-full.txt, Markdown delivery, structured discovery links, and named crawler policies because some publishers or providers may use them. Missing optional conventions stay in Review and do not reduce the score.
For Google's AI experiences in Search, conventional SEO remains foundational. Google says no new machine-readable files, AI text files, special markup, or additional technical requirements are needed for AI Overviews or AI Mode. Read the current Google Search Central guidance.
Eligibility and observable evidence are not outcomes.
- It does not crawl every page or verify complete internal-link, duplicate-content, backlink, or broken-link coverage.
- It does not read private Search Console, analytics, CMS, conversion, server-log, or business data.
- It cannot prove current indexing, rankings, AI mentions, citations, recommendation, referral traffic, leads, or revenue.
- Lighthouse is controlled mobile lab evidence. It is not a complete accessibility audit or a substitute for real-user field data.
- Fetched page text is untrusted evidence. A recommendation still needs context and verification before implementation.
Read the consolidated Overhyped evidence limitations or inspect the representative Website Checkup report.
Use one page for each important public claim.
The automated checkup, human-reviewed audit, focused tools, ongoing managed service, and coming-soon AI CMO in one comparison.
Checkup methodologyHow the One Website Checkup worksWhat is fetched, how 33 Search and 16 Agent items are scored, when 9 Lighthouse items are available, and what remains a Review item.
Managed-service methodologyHow managed SEO and AEO evidence is measuredHow prompts are selected, what each sample records, how visibility terms are defined, and where attribution stops.
LimitationsWhat Overhyped evidence cannot provePublic-data, sampling, platform, attribution, performance, and outcome boundaries across every offer.
Product statusCurrent status of the AI CMOThe product direction is coming soon; no public account, finished dashboard, pricing plan, or launch date exists today.
Representative reportRepresentative Website Checkup reportA dated self-check of Overhyped's live homepage with observed evidence, Review items, and an independently measured Performance stage.
Commercial processHow managed-service scope and pricing are decidedA customized written proposal confirms ownership, quantities, access, approvals, fees, and engagement terms before onboarding.
About OverhypedWhy Overhyped exists and who is responsibleThe AI CMO direction, why real service work came first, the first-person origin story, operating principles, design-engineer and advisor identities, and public responsibility boundaries.