Bot View Checker

Use the Bot View Checker to inspect what crawler-style requests receive from one public page.

Open the Bot View Checker

When to use it

Start here when a page looks complete in a browser but you are unsure whether search crawlers, AI crawlers, or preview bots receive readable content.

It is useful for checking:

• a homepage or important landing page
• a React, Vite, Vue, or AI-built website
• a page before connecting Prerender Buddy
• a page after DNS or middleware setup
• differences between crawler families

How to run the check

1. Enter the complete public URL, including HTTPS.
2. Run the check.
3. Review the response status and readable text.
4. Check whether the title, description, headings, and links are present.
5. Review app-shell warnings and crawler-specific results.

Use the final public hostname. Root and www are different request paths, so test both when both are accessible.

How to interpret the result

A healthy result normally exposes meaningful page copy, headings, metadata, and links in the crawler-style response.

A thin result may expose only:

• a root application element
• script and stylesheet references
• loading text
• a generic title
• very little readable content

That may indicate a crawler-readability issue, especially when the browser displays substantially more content.

Important limitations

The checker sends controlled crawler-style requests. It does not prove that a crawler operator visited the page, accepted the response, indexed it, or used it in search or AI results.

Readable HTML removes a technical blocker. It does not guarantee rankings, citations, traffic, or recommendations.

Recommended next step

If the response looks thin, use Raw HTML vs Rendered HTML to confirm whether JavaScript adds the missing content. If several templates may be affected, use the Bulk Crawler Readability Checker.