Indexability is whether Google can add your page to its index after it has crawled it. Crawling is Google reading the page. Indexing is Google deciding to keep it and actually show it in results. Indexability is the yes-or-no on that second step. If the answer is no, the page can be fast, well written, and beautiful, and still show up nowhere. As far as search is concerned, a page that is not indexed does not exist.
Here is the part that trips people up. Your page can look completely fine to you. It loads. It scrolls. You can send the link to a friend. None of that means Google put it in the index. Indexability is a decision Google makes in private, and it does not send a text to let you know.
So let me explain what indexability actually is, how it is different from crawlability, what blocks a page from getting indexed, and how to check any URL in a couple of minutes.
Crawling and indexing are two different steps
Search engines work in stages. Google describes it as crawling, indexing, and serving results. Crawlability and indexability are the first two, and they are not the same job.
Crawlability is whether Googlebot can reach and read the page at all. Can it follow a link to the URL, download the HTML, and see the content? That is crawling. It is the door.
Indexability is what happens after the door. Google has the page in hand and now decides whether to file it away in the index so it can appear in search. That is the room behind the door.
The order matters, because it is one-way. A page has to be crawlable before it can be indexable. You cannot file a page you were never allowed to read. But the reverse is not true. A page can be perfectly crawlable and still not indexable, because Google read it and then chose to leave it out.
That distinction is where most confusion lives. People assume that if Google can see a page, Google will list it. Not always. Crawling opens the door. Indexing decides whether anything in the room was worth keeping.
What actually makes a page indexable
For a page to be indexable, a few things all have to line up. Miss one and the page can quietly fall out of the index while everything else looks healthy.
Here are the usual things that decide whether a page gets indexed, and what each one does.
| Signal | What it does | Indexable? |
|---|---|---|
noindex meta tag or header | Directly tells Google to leave the page out | No |
robots.txt disallow | Blocks the crawl, so Google may never even read the page | Usually no |
| Canonical pointing elsewhere | Tells Google the “real” version is a different URL | The other URL, not this one |
| Redirect (301 / 302) | Sends both users and Google to a different URL | The destination, not this one |
| Thin, duplicate, or low-value content | Google decides the page is not worth storing | Often no |
| Soft 404 | Page returns “OK” but looks empty or broken to Google | No |
| Clean, useful, unique page with no blockers | Nothing telling Google to skip it | Yes |
A page becomes indexable when the boring things are all in order. It returns a normal 200 status. It is not blocked in robots.txt. It has no noindex tag. Its canonical points to itself. It is not redirecting somewhere else. And it says something worth keeping.
That last one is easy to skip past, but it is real. Google does not have to index every page it crawls, and it does not. If a page is thin, near-identical to ten other pages, or reads like it was written to fill a slot rather than answer a question, Google can simply pass. Google cannot rank a page it cannot understand, and it will not bother storing a page that says nothing. Being technically indexable is the floor, not the finish line.
Why your page is not getting indexed
“Why is my page not indexed” is one of the most common questions I hear, and the answer is almost always one of a short list of causes. Work down it in order.
- A stray
noindextag. This is the classic. A page gets set tonoindexduring a redesign or a staging build, then goes live with the tag still attached. The page looks perfect. Google is politely obeying an instruction to ignore it. - Blocked in robots.txt. If the URL is disallowed, Google may never read it. Whole sections of sites get wiped from search this way, usually by a rule someone added for a reason nobody remembers.
- A canonical pointing at the wrong URL. Canonical tags tell Google which version of a page is the main one. Point it at the wrong URL and you are telling Google to index a different page instead of this one.
- The page redirects. If the URL 301s or 302s somewhere else, that is not the page Google keeps. It keeps the destination.
- Duplicate or thin content. If the page is a near-copy of another one, Google often picks one and drops the rest. Ten pages saying the same thing do not get ten spots. They compete for one.
- It is brand new. Indexing is not instant. Google has to discover the URL, crawl it, and decide. A page published this morning is not a mystery when it is missing this afternoon. Give it time.
Notice how many of these are self-inflicted. Most indexability problems are not Google being difficult. They are a setting somewhere on the site quietly telling Google to stay away, left behind by a plugin, a template default, or a launch checklist that missed a box.
How to check indexability in Google Search Console
You do not have to guess whether a page is indexed. Google will tell you, for free, in Search Console. Two tools do the work.
The URL Inspection tool checks one page at a time. Paste the full URL into the search bar at the top of Search Console and it reports whether the URL is on Google, and if not, why. It will name the reason: excluded by noindex, blocked by robots.txt, marked as a duplicate, crawled but not indexed, and so on. This is the fastest way to answer “is this specific page in the index and if not, what is stopping it.”
The Page Indexing report zooms out to the whole site. It groups every URL into indexed and not-indexed buckets, and for the not-indexed pages it lists the reason for each group. This is how you find patterns. If four hundred pages all fell out under “excluded by noindex tag,” that is not four hundred problems. That is one bad setting hitting four hundred pages.
Run the URL Inspection tool on a page you expect to see in search and cannot find. Nine times out of ten it hands you the exact reason in one line. That beats an afternoon of theories. Check the data before guessing. Real reports beat confident opinions, even your own.
If you want the broader technical picture around this, we cover the foundation in technical SEO basics, and how to run the whole review in how to do a website audit.
The gotcha nobody warns you about: robots.txt can hide your noindex
Here is one that catches even experienced people, and it is worth its own section because the fix is the opposite of what feels natural.
Say you want a page out of the index. You do the sensible thing and add a noindex tag. Then, to be extra safe, you also block the page in robots.txt. Belt and suspenders, right?
Wrong, and here is why. Blocking a page in robots.txt stops Google from crawling it. But if Google cannot crawl the page, it cannot read the noindex tag inside it. The instruction you added to remove the page is now locked behind a door Google is not allowed to open. So the URL can hang around in the index anyway, usually shown without a description, because Google knows the address but was never allowed inside.
The two directives do opposite jobs. robots.txt controls crawling. noindex controls indexing. If you want a page removed from the index, let Google crawl it and see the noindex. Do not block it in robots.txt at the same time. Google spells this out in its own guidance on blocking indexing with noindex. It is a small thing that quietly defeats a lot of good intentions.
This is also why I like clean, hand-built pages over stacked plugins and builder defaults. The more layers between you and the raw HTML, the more places a stray directive can hide. Schema is not optional, and neither is knowing what your own <head> actually says.
Indexing takes time, and that is normal
One honest note before the checklist. Even when everything is set up correctly, indexing is not instant. Google has to find the URL, crawl it, and decide whether to keep it. For a new page or a new site, that can take days or longer.
At the bare minimum, give SEO and AEO three months before judging results, and honestly, more time is better. Indexing is the very first step of that timeline, not the finish line. SEO is not a vending machine. You do not put in a blog post and get a lead before lunch.
You can nudge it along. Make sure the page is in your XML sitemap. Add internal links to it from pages Google already crawls often, so it gets discovered faster. And because Google now indexes the mobile version of your pages first, make sure the content you want indexed actually exists in the mobile view, not just on desktop. What is missing on mobile can be missing from the index.
Frequently asked questions
What is the difference between crawlability and indexability?
Crawlability is whether Google can reach and read a page. Indexability is whether Google adds that page to its index after reading it. Crawling comes first and opens the door. Indexing is the separate decision about whether to keep the page. A page can be crawlable but not indexable, which is why some pages get read and still never appear in search.
How do I make a page indexable?
Make sure the page returns a normal 200 status, is not blocked in robots.txt, has no noindex tag, and has a canonical that points to itself. Then make sure it is genuinely useful and not a near-duplicate of another page. Once those line up, add it to your sitemap and link to it internally so Google can discover it.
Why is my page crawled but not indexed?
“Crawled, currently not indexed” usually means Google read the page and decided it was not worth storing yet. That often points to thin, duplicate, or low-value content, or a page Google is still evaluating. Improve the content so it clearly answers something, remove duplication, and give it time. It can also resolve on its own as Google revisits the page.
How do I check if a page is indexed?
Use the URL Inspection tool in Google Search Console. Paste in the full URL and it tells you whether the page is on Google and, if not, the exact reason. For a site-wide view, open the Page Indexing report, which groups your URLs into indexed and not-indexed and lists the reason for each not-indexed group.
Does a noindex tag remove a page from Google?
Yes, as long as Google can crawl the page to see the tag. The catch is that if you also block the page in robots.txt, Google cannot read the noindex and the URL may stay in the index. To remove a page, allow the crawl and keep the noindex in place until Google recrawls it and drops it.
How long does it take Google to index a new page?
It varies. It can take a few days to a few weeks, sometimes longer for a new site with little authority. Adding the page to your sitemap, linking to it from established pages, and requesting indexing in Search Console can speed up discovery. Indexing is only the first step, so do not expect rankings the moment a page appears.
Can a page be indexed and still not rank?
Yes. Being indexed means the page is eligible to appear in search results. It does not guarantee a good position. Ranking depends on relevance, content quality, and competition. Indexing gets you into the search results pool. Where you land in that pool is a separate contest.
Get a read on your own indexability
Most indexability problems are quiet. The page looks fine, so nobody thinks to check, and it sits invisible for months while everyone wonders where the traffic went.
The fix starts with looking. Run a free audit to see how crawlable and clear your site is right now, and if you want a hand turning that into indexed, useful pages, that is the work we do in our organic SEO service. Fix the setting first. Then worry about ranking.