Crawlability vs. Indexability: Why Your Pages Might Be Invisible to Google

Two pages can look identical to a visitor and be completely different to Google. One shows up in search results. The other never will, no matter how good the content is or how many people link to it. The difference almost always comes down to two separate, easily confused concepts: crawlability and indexability.
Most people use these words interchangeably. They shouldn’t. A page can be crawlable but not indexable, or indexable but not crawlable, and each problem needs a completely different fix. This is the more granular follow-up to What Is Technical SEO? A Practical Definition for 2026, since crawlability and indexability together make up the first of the "three jobs" covered there.
The Simple Version
Crawlability is whether Googlebot can reach a page at all. Think of it as whether the front door is unlocked.
Indexability is whether Google, having reached the page, is allowed and willing to add it to its index, the massive database it pulls search results from. Think of it as whether Google decides the room behind that door is worth remembering.
A page needs both. Crawlable but not indexable means Google visited and chose not to keep it. Indexable but not crawlable means Google would happily index it, but can’t get in to check.
Crawlability vs. Indexability at a Glance
| Crawlability | Indexability | |
|---|---|---|
| What it answers | Can Google reach the page? | Will Google keep the page in its index? |
| Stage | Discovery | Decision |
| Common causes | Robots.txt blocks, orphaned pages, broken internal links, exhausted crawl budget, JavaScript-dependent navigation | Noindex tags, misconfigured canonicals, thin or duplicate content, soft 404s |
| How it shows in Search Console | "Blocked by robots.txt," "Not found," "Server error," "Discovered, currently not crawled" | "Crawled, currently not indexed," "Excluded by noindex tag," "Alternate page with proper canonical tag" |
| Wrong fix that wastes effort | Adding more content or backlinks to a page Google can’t reach | Editing robots.txt or internal links when the crawler was never the bottleneck |
| Right fix | Unblock the path: fix robots.txt, add internal links, repair redirects, confirm sitemap inclusion | Fix the judgment call: remove stray noindex tags, correct canonicals, add real depth to thin content |
Crawlability: Can Google Even Get There?
Crawling is the discovery phase. Googlebot follows links from page to page, reads your sitemap, and builds a map of what exists on your site. A few specific things break this process:
Robots.txt blocking. This file, sitting at yourdomain.com/robots.txt, tells crawlers which parts of a site they’re allowed to visit. A single misplaced Disallow: / in the wrong section can accidentally block an entire section of a site, sometimes the whole thing, without anyone noticing until traffic quietly disappears.
Orphaned pages. A page with no internal links pointing to it is invisible to a crawler that navigates by following links. It might be in your sitemap, and it might even get crawled occasionally because of that, but a page with zero internal links is treated as low priority and crawled far less often than one embedded in your site’s link structure.
Broken internal links. If the path to a page runs through a link that’s broken, redirected incorrectly, or points to the wrong URL, the crawler either never arrives or arrives somewhere unintended.
Crawl budget exhaustion on large sites. Google allocates a rough "budget" of how many pages it will crawl on a given site in a given period. On very large sites (tens of thousands of pages or more), if crawl budget gets spent on low-value pages (filtered URLs, paginated archives, duplicate parameter variations), the pages that actually matter may get crawled less frequently, or not at all.
JavaScript-dependent navigation. If the links to other pages only render after JavaScript executes, and that execution fails or times out during Google’s rendering pass, the crawler never discovers the links, and therefore never finds the pages they point to.
Indexability: Will Google Keep What It Found?
Indexability problems happen after the crawl succeeds. Google reached the page, read it, and then decided, for one of several reasons, not to add it to the index.
A noindex tag. This is a direct instruction in a page’s HTML (or HTTP header) telling Google explicitly not to index the page. Sometimes intentional (a thank-you page, an internal search results page). Often accidental, left over from a staging environment or added by a plugin default that nobody checked.
Canonical tags pointing elsewhere. A canonical tag tells Google "this page is a duplicate, the real version lives at this other URL." If a canonical tag is misconfigured and points to the wrong page, or to itself incorrectly across multiple pages, Google may index the wrong version, or none of them.
Thin or duplicate content. Google actively chooses not to index pages it judges as low-value, near-duplicates of other pages, or too thin to be useful to a searcher. This shows up in Search Console as "Crawled, currently not indexed" - the page was visited, and Google decided it wasn’t worth keeping.
Discovered but not crawled, due to low perceived value. Sometimes Google finds a URL (through a sitemap or a link) but deprioritizes actually crawling it because early signals suggest it’s not worth the resources. This is a borderline case that sits between crawlability and indexability, and is common on large sites with many low-quality URLs.
Soft 404s. A page that returns a normal 200 status code but has almost no content (an empty category page, a "no results found" search page) can get treated by Google as functionally a 404, even though the server says otherwise.
How to Actually Check Which Problem You Have
If you’re not yet comfortable navigating Search Console generally, How to Read a Google Search Console Report Without Getting Lost covers the dashboard itself. From here on, this section assumes that baseline.
The fastest diagnostic is Search Console’s URL Inspection tool. Paste in the specific URL, and it tells you directly:
- If it says the page isn’t on Google and lists a crawling issue (blocked by robots.txt, server error, redirect issue), that’s a crawlability problem.
- If it says the page was crawled but shows "Crawled, currently not indexed" or "Discovered, currently not indexed," that’s an indexability problem - Google reached it and chose not to keep it.
- If it shows the page is indexed but under a different URL than expected, check the canonical tag. That’s often a signal Google picked a different canonical version than the one intended.
For a broader check across many pages at once, the Coverage report (now integrated into the Pages report under "Indexing") groups excluded pages by reason, which is the fastest way to spot a pattern affecting dozens or hundreds of URLs rather than checking one at a time.
Why This Distinction Actually Matters for What You Do Next
Treating both problems the same way wastes effort in a specific way: if a page has a crawlability problem, adding more content to it or building more backlinks to it does nothing, because Google still can’t reach it. If a page has an indexability problem instead, fixing the robots.txt file or internal linking does nothing either, since the crawler was never the bottleneck in the first place.
The right fix depends entirely on which one it is:
- If it’s a crawlability problem: check robots.txt for accidental blocks, confirm the page is linked from somewhere else on the site, verify the sitemap includes it, and check that no broken redirect sits between the crawler and the page.
- If it’s an indexability problem: check for a stray
noindextag, verify the canonical tag points to the correct URL, and honestly assess whether the content is thin or too similar to another page on the site. Sometimes the fix is adding real depth, not a technical tweak at all.
A Quick Mental Model to Keep This Straight
Crawlability is about access. Indexability is about judgment. Google has to be able to get in before it can decide whether to keep what it finds, but getting in is no guarantee it will. Diagnosing which stage a page is stuck at, rather than assuming "it’s not ranking, must be an SEO problem" in general, is what turns a vague frustration into a specific, fixable issue.
"Crawlability is about access. Indexability is about judgment. Indexability is the entry ticket, not the seat."
Sachin Pokharel
Further Reading
On this site:
From Google:
Tags: crawlability, indexability, Google Search Console, robots.txt, canonical tags
Frequently Asked Questions
Can a page be indexed without ever being crawled?
No. Crawling has to happen first. Google occasionally indexes a URL based on strong external signals, like many sites linking to it, even before fully crawling its content, but this is rare, temporary, and usually resolves once a full crawl happens. As a practical matter, treat crawling as the required first step.
If a page shows up when I search its exact URL, does that mean it is indexed?
Not necessarily. Searching site:yourdomain.com/page-url is a reasonable quick check, but Google's site: operator can behave inconsistently and is not treated as fully reliable by Google itself. The URL Inspection tool in Search Console gives a direct, accurate answer instead of an inferred one.
How long does it take for a fixed crawlability issue to show results?
There is no fixed timeline. A high-authority page on a frequently crawled site might get re-crawled within hours to days. A low-priority page on a smaller site might take weeks. Requesting indexing manually through the URL Inspection tool can speed this up for individual pages, but it does not guarantee immediate re-crawling.
Does a noindex tag stop Google from crawling the page too?
No, and this trips people up. A noindex tag still allows crawling; it just tells Google not to keep the page in the index after visiting it. To stop crawling entirely, that is a robots.txt job, not a noindex job. Using both together on the same page can actually cause problems, since Google needs to crawl the page to see the noindex tag in the first place.
Why does Search Console show a page as indexed, but it still does not rank for anything?
Being indexed just means the page exists in Google's database. It says nothing about ranking well. A page can be perfectly indexable and crawlable and still rank poorly for reasons that have nothing to do with either concept: thin content, weak relevance to the query, or strong competition. Indexability is the entry ticket, not the seat.
![Top Business Listing Sites in Nepal For Local SEO [Free + Paid]](/_next/image?url=%2Fassets%2Fimages%2Fblog%2Fpost%2FBusiness-Listing-Sites-in-Nepal-For-Local-SEO.webp&w=1080&q=75)