Free Indexability Checker
Can Google index this page? One line of code, a robots.txt rule or a server header, can hide a page from Google, and it often happens during a redesign. Paste any page and get one clear verdict from every signal that matters.
Free · No sign-up · Nothing stored
One line of code can hide a page from Google
Most pages that vanish from Google weren't penalised. They were switched off by a single line: a leftover tag from a staging site, a robots.txt rule meant for one folder that matches the whole site, or a header added by a CDN or security plugin. Each lives in a different place, so checking one isn't enough. The indexability checker checks all six, for the exact page you enter, and gives one verdict.
The six signals behind the verdict
| Signal | Pass when | If it fails |
|---|---|---|
| Status code | The page (after redirects) returns HTTP 200 | Fix the page, or 301-redirect it to its replacement |
| robots.txt | Googlebot is allowed to crawl this exact path | Remove or narrow the Disallow rule |
| Robots meta tag | No robots or googlebot meta tag says noindex | Remove the tag (WordPress: Settings → Reading) |
| Server header | The response doesn't send X-Robots-Tag: noindex | Check your CDN, hosting panel or security plugin |
| Canonical | The canonical tag points to this page | Point it to the page itself unless it's a duplicate |
| Sitemap | The page is listed in your XML sitemap | Add it so Google finds it faster |
Reading your verdict
- Google can index this page
- Every signal passes. Whether Google actually indexes it now depends on the page's quality and links.
- Google can index this page, with things to fix
- Nothing blocks it, but something weakens it: a redirect, a canonical pointing elsewhere, or a page missing from your sitemap.
- Google can't index this page
- At least one signal blocks it. The reason is listed first, with the fix.
- We couldn't check this page fully
- Your server turned away our visit both as Googlebot and as a browser. Use URL Inspection in Search Console for the final word.
Three real results from our own site
Not every page should be indexable. We ran the checker on three of ours, and each verdict is the one we want:
| Page | Verdict | Why |
|---|---|---|
| Our homepage | Can be indexed | All six signals pass |
| Our /login page | Can't be indexed | robots.txt blocks it on purpose; private pages don't belong in search |
| A job page that no longer exists | Can't be indexed | Returns 404 with a robots noindex tag, both on purpose |
The lesson: a "can't be indexed" verdict is only a problem when it's on a page you want people to find. The checker tells you which signal is responsible, so you can decide.
After a redesign, check these first
- Turn off "discourage search engines" in your CMS and remove leftover noindex tags from the live site.
- Open robots.txt and make sure it didn't come over from staging with Disallow: /. The Robots.txt Generator builds a verified one.
- Redirect old URLs to their new pages with 301s. The Redirect Checker finds the ones that 404.
- Check your sitemap lists the new addresses with the Sitemap Checker.
- Run your most important pages through this checker, then request indexing in Search Console.
When your firewall answers instead of your page
The checker visits as Googlebot first. Many firewalls verify the real Googlebot by its IP address and refuse anyone else using its name, which includes us. When that happens, we re-check as a normal browser so a correctly configured firewall isn't reported as a blocked page, and we tell you it happened. A block on the real Googlebot would show up in Search Console's URL Inspection.
What the indexability checker can't tell you
- Whether the page is indexed right now. Only Search Console knows that.
- Content quality. Google may choose not to index a page that's allowed but thin or duplicated.
- Very large sitemaps. We read the first few sitemap files; check the rest in Search Console.
Indexability on one map
For how robots.txt and noindex differ in detail, read our guide What Is Robots.txt?.
Check every page, not just one
Owl-gorithm Hacker audits indexing, robots rules and rendering across your whole site, and Watch Owl catches problems after every change.
Frequently asked questions
Is the indexability checker free?
Yes. It's free with no sign-up, and we don't store the pages you check.
What does indexable mean?
A page is indexable when Google is allowed to add it to its index: it loads, robots.txt lets Googlebot crawl it, and nothing on the page or in the server's response says noindex. Indexable doesn't mean indexed: Google still decides whether the page is worth including.
Does blocking a page in robots.txt keep it out of Google?
Not reliably. robots.txt stops Google crawling a page; noindex stops Google indexing it. They don't mix: if robots.txt blocks a page, Google can't read its noindex tag, and the bare address can still appear in results when other sites link to it. To keep a page out of Google, allow crawling and use noindex.
Why would a page have noindex by mistake?
Usually because a site was built on a staging server with "discourage search engines" switched on and went live unchanged. Plugins and theme settings can add it too. One line of code, and the page disappears from Google.
What is the X-Robots-Tag header?
The server-level version of the robots meta tag, sent with the page instead of written in its HTML. It's often set by a CDN, a hosting control panel or a security plugin, which is why it's easy to miss when you only look at the page's code.
The checker says the page is fine. Why isn't it on Google?
Being allowed isn't the same as being chosen. New and low-authority pages can sit in "Discovered, currently not indexed" for weeks. Request indexing in Search Console, link to the page from pages Google already indexes, and earn mentions from other sites.
Why does the checker visit as Googlebot?
Some sites show crawlers something different from visitors, on purpose or by accident. Visiting as Googlebot shows what Google would get. If a firewall turns that visit away, we re-check as a normal browser and tell you, because many firewalls rightly block fake Googlebots.
Should every page on my site be indexable?
No. Login pages, carts, internal search results, thank-you pages and thin filter pages are often better kept out. The point is to make sure the pages you want found are indexable, and that nothing important is switched off by accident.
How do I get a page indexed faster?
Make sure it passes every check here, add it to your sitemap, link to it from a page Google already knows, and use URL Inspection in Google Search Console to request indexing.
Agents that do this for you
Related reading