AI Website Source & Indexability Check
This page does not run a simulated crawler and does not claim to reproduce Googlebot or Search Console. Until VibeToRank deploys a hardened public fetch service, use these manual checks to inspect what a public AI-built website exposes.
Five checks you can run now
1. Final status and redirects
Use your browser network panel or an HTTP-status tool. Record the submitted URL, every redirect, the final URL, and the final status.
2. Canonical and robots
View page source and find rel="canonical" and robots directives. Also check response headers for X-Robots-Tag.
3. Initial HTML
In View Source—not only Inspect Element—confirm the title, description, H1, meaningful text, and ordinary same-origin links appear.
4. Sitemap and robots files
Check /robots.txt, its Sitemap declarations, /sitemap.xml, and /sitemap_index.xml. A sitemap helps discovery but does not guarantee indexation.
5. Structured data
Identify JSON-LD types and validate syntax. Markup must match visible content and cannot guarantee a rich result or AI citation.
Interpret carefully
A missing item suggests a line of investigation, not a diagnosis by itself. Indexed, ranking, mentioned, and cited are separate outcomes.
Record the evidence
| Check | Observed fact | What it does not prove |
|---|---|---|
| Status/redirect | Final status and URL | That Google indexed it |
| Initial HTML | Text and links in response | How every crawler renders it |
| Canonical/robots | Declared preference and permission | That engines will obey/index |
| Schema | Types and validity | Rich results or citations |
Follow the full AI-built website audit methodology or read the Bolt.new diagnostic.
Need the source and rendered output compared?
Request free triage for an ambiguous finding or a paid audit for manual route, rendering, and indexation investigation.
Request free triageView the audit