Prism
Start free
Site crawling

Find the pages quietly telling Google to stay away.

Prism fetches, checks and Lighthouse-scores every page — and reads everything each page tells Google, not just what it shows people.

Prism's Site Health issues report: seven issue types ranked by severity, each with the share of pages affected: critical client errors 96, serious slow-loading pages 182, warnings for missing meta descriptions and canonicals 468 each, thin content 214, and notices for 1,240 images missing alt text and 320 missing Open Graph tags.
The crawl · every page

The same checks, every time.

Every page the crawler touches gets the same treatment, not a sample.

Can Google have it
The status it returned, where its redirects end up, what its canonical points at, and whether the page is telling Google to index it in one place and to stay away in another
Is it worth having
Length and substance, near-duplicates of other pages on the site, and titles and meta descriptions that are missing, cut off or reused
Can anything reach it
What links to it from inside the site, what it links out to and whether those still resolve, and whether anything links to it at all
How fast is it
Lighthouse runs against the page and returns performance, accessibility, best-practices and SEO scores, so a slow template comes back as a list of URLs
How does it present
Open Graph and Twitter card tags for when somebody shares it, and structured data checked for the errors that stop it being used

A page can look indexable and quietly not be.

One stray rule can pull a healthy-looking page out of Google, and nothing in the browser shows it. Prism reads the response headers as well as the markup, so the contradiction arrives as a finding with a URL list attached.

  • Caught, with the URLs

    Every page saying index in one place and noindex in another, listed — usually a CDN rule or stray middleware.

  • See what a release changed

    Crawl Comparison sets two runs side by side — pages, health score and every issue type, diffed.

  • Lighthouse in a real browser

    Each page is scored on what it renders; the crawl checks read the HTML your server returned.

Prism's Crawl Comparison report: two crawls set side by side with the movement in pages crawled, health score and each issue type between them.

Frequently asked questions

What does the crawler check?

Every page gets the same treatment: the status it returned and where its redirects end up, what its canonical points at, whether the robots meta tag and the X-Robots-Tag response header agree, how substantial the content is and whether another page duplicates it, what links to it and what it links out to, whether its images carry alt text, whether it has the tags that make it shareable, and how it scores when Lighthouse runs against it.

Why do pages silently drop out of Google?

Often because of an instruction nobody can see. A page can return 200, say "index, follow" in its markup, and still carry "noindex" in its X-Robots-Tag response header, which never shows up in view-source. Prism records both, so the contradiction is a finding with a URL list rather than a mystery.

Can I compare two crawls?

Yes. Because every run does the same work on every page, Crawl Comparison can set two runs side by side and show the movement in page count, health score and every issue type between them.

Does it render JavaScript?

Lighthouse runs against each page in a real browser and scores what it renders. The crawl checks themselves read the HTML your server returns, headers included, so those findings describe exactly what the server served. Content drawn only by a client-side fetch shows up in the Lighthouse scores rather than the parsed crawl record.

Run the first crawl and read the findings.

Point Prism at a site: every page crawled and Lighthouse-scored, and every finding classified by what it does to your traffic, on the free plan, for ten properties.