What a crawler sees before your JavaScript runs.

Enter a URL and see what a non-JavaScript crawler receives: the title and description actually served, whether the canonical is self-referencing, what structured data parses, and how many words of real content exist in the initial HTML response.

What it checks

• Server-rendered title, description, and canonical, per URL.
• Whether the canonical points at the host that is actually served.
• Structured data that parses, and references to nodes that do not exist.
• Visible word count in the raw response, before hydration.

The failure this catches most

Single-page applications where every route returns the same homepage HTML. Google records the URL, sees identical content, and files it under discovered but not indexed. It is invisible in a browser and it silently caps a site's indexed page count at one.

The second most common finding

Canonical host mismatch. A site served on www with canonicals pointing at the apex — or the reverse — splits authority between two hosts and hands search engines a redirect for every URL in the sitemap. Cheap to fix, and worth checking before anything else on this list.