Homepage HTML is nearly empty before JavaScript runs
Client-rendered builds can send a mount node and a script tag. Visitors see your product; a crawler that reads the raw HTML sees almost nothing.
For AI builders / The launch

AgencyProof inspects the public pages of your AI-built site: what search engines, AI assistants and first visitors actually receive. You get a scored report, a prioritized fix list, and a fix prompt your coding assistant can act on.
Run a free, two-page automated preview. Public-page inspection; authenticated areas are out of scope.
What the inspection finds
The builder got the product on screen. These are the things it rarely checks, and the ones a launch day exposes first.
Client-rendered builds can send a mount node and a script tag. Visitors see your product; a crawler that reads the raw HTML sees almost nothing.
A template or platform default can block GPTBot, ClaudeBot or PerplexityBot. The report names the crawler and quotes the rule.
Missing Open Graph title, description or image, so the post that announces your launch has no card.
“Get started” pointing at #, or a pricing link to a page that was never built. Link-pattern checks catch the shapes that dead-end.
Run a free, two-page automated preview. Public-page inspection; authenticated areas are out of scope.
agencyproof scan marlow-dental.example in agency mode: crawled the reachable public pages in scope, ran 54 checks across links, metadata, claims, and copy, generated client report with 21 findings. 3 launch blockers found. Launch Readiness: 71 out of 100 — fixes required before launch.
Before JavaScript runs
Many AI builders render pages in the browser. Visitors see your product. A crawler that reads the raw HTML, as many AI assistants’ fetchers and link previews do, receives a mount node and a script tag.
What a visitor sees
What a crawler receives
The free scan reads your homepage as served, the way these crawlers do. What the Launch Audit adds:
Illustrative example. yourapp.example is a placeholder, not a scanned site.
From finding to fix
Every full report includes a fix prompt written for the stack the inspection detected, so the instructions point at the right file. Paste it into the tool you build with, then review the change.
Copy the audit’s fix prompt into your implementation assistant. The prompt is copied or exported from the workspace. It is not an integration and not automatic remediation.
This site was built with Lovable (React + Vite). Finding: the homepage HTML is nearly empty before JavaScript runs. The response for / carries about 40 characters of readable text and an empty <div id="root">. Fix: put the page title, meta description and Open Graph tags in index.html. Pre-render the public marketing routes so the first HTML response already contains the headline, copy and links. Keep client rendering for the signed-in app. Do not change routes, copy or styling. List the files you changed.
Copy and claims
AI products make bold claims, and investors, enterprise buyers and journalists ask for the evidence. The inspection flags the lines they will ask about, so you can back them up or soften them before launch.

<p class="hero-sub">
99% accurate on any document, guaranteed.
</p>Evidence shows an observation at scan time. It does not establish cause.AgencyProof identifies wording that may need evidence or specialist review. It does not provide legal advice or determine regulatory compliance.
Example claim written for this page, not taken from a real site.

The report
AgencyProof Launch Readiness Score and a rules-based Hold, Conditionally ready, or Ready verdict. A cofounder can read the decision; an engineer can start on the list.
Which plan fits
The question is how your pages reach a crawler, not how big your company is.
If your site is server-rendered
Framer, Webflow, Next.js, Astro and similar
Snapshot inspects up to 10 reachable public pages, static HTML only. The report records actual coverage.
If it renders in the browser, or the launch matters most
Lovable, Bolt, Vite and React single-page apps; a Product Hunt day or funding news
Launch Audit reviews up to 35 reachable public pages and inspects up to 12 of them in a real rendered browser. The report records actual coverage.
Not sure how your homepage renders? Run the free scan and read the result first.
Before launch
Run the free scan to see how your homepage reaches a crawler, then the audit that fits your stack.
Work the prioritized list. Paste each fix prompt into your coding assistant and review what it changes.
Launch Audit includes one re-scan after the initial completed scan, with no expiry deadline. With a Snapshot Audit, a second look is a second audit.
Want the full list to work through yourself? Read the pre-launch checklist.
Illustrative post-fix state.
Methodology boundaries
Not performed on any tier
Not performed on some tiers
Audit scope
AgencyProof inspects a bounded sample of reachable public pages. The report records the pages and methods used, plus important checks that were not performed.
Accessibility
Automated accessibility checks do not establish WCAG or legal conformance and do not replace manual testing with assistive technologies.
Performance
Static performance signals and Lighthouse lab measurements, when present, are point-in-time diagnostics. They are not field data or a guarantee of user experience.
Claims and compliance
AgencyProof identifies wording that may need evidence or specialist review. It does not provide legal advice or determine regulatory compliance.
AI search
Entity and crawler signals can reduce ambiguity. They do not guarantee rankings, citations or recommendations by an AI system.
Readiness
“Ready” is the result of the AgencyProof scoring model for the site as observed at scan time, not a guarantee of business, legal, security or launch outcomes.

Launching soon
Say what you're shipping and when, and we'll suggest the inspection that fits. A human reads and answers every message.