Free tools
Website Search Readiness Check

See what your website
actually provides.

Enter a page to inspect its delivered HTML. Get a short list of findings, source evidence, and a practical next step.

One public HTML page. No account needed. No paid AI queries.

How it works

What is a website search readiness check?

It inspects the HTML returned for one public page. We look for signals that help a person or a search system understand what the page is about: a title, headings, an optional description, a canonical URL when one is needed, indexing directives, and structured data. Each finding includes what the checker actually observed, so you can verify it yourself.

This is a technical starting point. Crawlability and indexing eligibility are foundations; no technical check guarantees inclusion in search results or AI answers.

01

Can the page be indexed?

We inspect any robots or googlebot meta tags and the X-Robots-Tag response header. To inspect robots.txt permissions for specific crawlers, use the AI Crawler Access Checker.

02

What does the response say?

We read the returned title, meta description, and main heading, and show a short excerpt of the delivered text.

03

Are there useful page details?

A canonical tag can identify a preferred URL when duplicate pages exist. JSON-LD may describe content in a machine-readable form.

An example

A service page with an indexing restriction.

Suppose a services page responds with <meta name="robots" content="noindex">. The checker reports that exact directive. The owner can decide whether it was intentional. Removing it allows indexing eligibility to be reassessed; it does not guarantee a ranking.

Methods and limits

One public HTTPS URL, up to three same-site redirects, at most the first 256 KB of an HTML response, a few checks per minute per visitor. We do not run JavaScript, crawl other pages, access a private account, or call any AI service. Blocked requests, non-HTML responses, 404s and partial responses are reported separately.

Questions about the check

Is this a rendered-browser audit?

No. We read the HTML the server delivers and do not run page JavaScript. A page built entirely with JavaScript might show more after rendering.

Does this validate my schema markup?

No. We report whether JSON-LD blocks parse as JSON. A block that parses has not automatically passed search feature requirements, and no special schema markup is required for AI answers.

Why does a result say Not checked?

When the response is incomplete or larger than 256 KB, we say not checked rather than treating an unseen field as missing.

Is there a score?

No. The check lists what it observed with evidence. It does not measure your position in Google, your likelihood of appearing in AI answers, traffic, or revenue.