Free · No account

Can Google index this page?

Paste a URL you just put live and get the specific mechanical reason it cannot be indexed — the blocking header, tag, rule or redirect, quoted back to you. Not a score.

We fetch that exact URL, unmodified — we do not silently add https or strip www, because those may be the thing you are asking about.

What it checks

  • The X-Robots-Tag response header. The most common cause on a fresh deploy and the hardest to find, because it is a header — it does not appear in "view source".
  • The meta robots tag, and whether it says noindex.
  • robots.txt, resolved for Googlebot against your exact path — including the case where it returns a server error, which Google treats as "do not crawl this site at all".
  • The redirect chain, every hop shown.
  • The canonical tag — missing, self-referential, pointing elsewhere on your site, or pointing at another domain entirely (the classic site-builder template leftover).
  • Whether there is real content in the server HTML, rather than an empty shell that only fills in once JavaScript runs.
  • Authentication walls — deployment protection and access rules that return 401 or 403 to a crawler.
  • Sitemap reachability, and whether robots.txt points at it.
  • http vs https, and apex vs www serving the same content.

Indexable is not the same as indexed

These checks tell you whether anything is blocking Google. They cannot tell you when it will actually index the page, and nobody honestly can. A brand-new domain with no inbound links commonly waits weeks. If every check here passes and you are still invisible, the problem is no longer technical — it is that nothing links to you yet.

Where the usual culprits hide, by host

If a check above fails, this is where the setting normally lives. Names change, so treat these as where to look rather than exact menu paths.

Vercel

Deployment Protection is the usual cause of a 401 — it is on by default for preview deployments, and can be switched on for production. Preview URLs are also served noindex deliberately, so always test the real domain rather than a *.vercel.app preview alias. Custom headers set in vercel.json are the other place an X-Robots-Tag can come from.

Netlify

Deploy Previews and branch deploys are served with noindex on purpose. Password protection returns a 401. Check _headers or netlify.toml for a lingering X-Robots-Tag.

Webflow

Two separate switches catch people out: a site-wide setting that disables indexing of the .webflow.io staging subdomain, and a per-page SEO toggle that adds noindex. A page can be fine on your custom domain and blocked on the staging one, or the reverse.

Framer

There is a per-page "hide from search engines" option and a site-wide equivalent. If you started from a template, check the canonical too — templates sometimes ship pointing at the template author's own domain.

Carrd

SEO controls including the description and indexing sit behind the paid tier. A free *.carrd.co site is also a different hostname from your domain, so make sure you are testing the one you actually promote.

Cloudflare Pages

Every deployment gets a permanent *.pages.dev alias that serves the same content as your custom domain — a duplicate you probably do not want indexed. Check whether both are reachable, and redirect or noindex the alias.