Free Indexability Checker
Can Google index this page? Yes or no.
Paste any URL and get one clear answer: can search engines index it? We check the HTTP status, robots.txt, meta robots noindex, the X-Robots-Tag header and the canonical tag together, so you don't have to. Free, no signup.
Free plan · Real fetch, five signals, one answer Enter a URL
We fetch the page and its robots.txt in real time, follow redirects, and read the actual HTML and HTTP headers.
This checks the signals that block indexing. It can't see directives added by client-side JavaScript, or treatment that differs for the real Googlebot (firewalls, geo rules). "Can be indexed" also isn't "will be indexed": Google still decides on quality and duplication.
Fetching the page and reading robots.txt…
What's blocking indexing
Every signal we checked
Worth knowing
Page is indexable. Is it any good?
Being allowed into the index is only step one. Run the free website audit to check titles, meta tags, headings, content and technical SEO.
Run Free Website AuditAbout the Indexability Checker
A page can look perfectly healthy and still be invisible in search, because indexing can be switched
off in four different places, and they don't all show up in the page you see. A
robots.txt rule can stop crawlers fetching it. A meta robots tag can say
noindex in the HTML. An X-Robots-Tag HTTP header can say the same thing
where you'd never look. And a canonical tag can tell search engines that a different URL is
the real version, so this one gets dropped. Add a 404 or a redirect and there are five ways to quietly
lose a page.
This tool checks all five together, with real requests. It follows redirects, reads
robots.txt with a proper parser (user-agent groups, * and $ wildcards,
longest-match precedence, and how Google treats a missing or erroring file), parses the HTML with a real DOM
parser, reads the response headers including bot-specific googlebot: noindex values, and
compares the canonical to the URL actually served. Any single blocker turns the answer into a
No, and the report lists exactly which signal caused it and how to fix it.
It also flags the traps: a robots.txt block that hides a noindex from crawlers so it never
takes effect, a Noindex: line in robots.txt that Google no longer honors, and directives that
apply only to a different crawler. It can't see directives injected by JavaScript, and a "Yes" means nothing
is blocking the page, not that Google will choose to index it.