Pages not indexed by Google:
published is not the same as visible
The post is up, the URL works, and after weeks it still returns nothing when you search for it. Search Console has a report that explains why, and it uses two labels that look almost identical and mean opposite things. Telling them apart decides everything you do next.
Publishing does not oblige Google to index anything. A URL has to be discovered, then crawled, and only then does Google decide whether to store it. Search Console reports the failure at two different points and the distinction is the whole diagnosis: «Discovered — currently not indexed» means it never even downloaded the page, which is a budget problem and almost always a page nothing links to; «Crawled — currently not indexed» means it did read it and chose not to store it, which is a judgment about the page. On a young domain, neither one is a technical error you can fix by rewriting: what moves the needle is authority and internal links.
How to know which of the two is happening to you
Four checks in order. Do not skip the first one: the answer to everything else depends on it.
-
Read the exact state in the Page indexing report
Indexing → Pages, and open the list of reasons under «Why pages aren't indexed». You are looking for which bucket your URLs fall into. Discovered and Crawled sit next to each other in that list and describe two different failures: one is a queue, the other is a verdict.
If most of your URLs are in Discovered, the pages were never read. Nothing you write changes that. -
Inspect one specific URL
Paste it into the URL Inspection bar at the top. It tells you whether Google has crawled it, when it last did, which canonical it picked and whether it considers the page a duplicate of another one of yours. That last field explains a good share of the cases where everything else looks fine.
A canonical pointing somewhere other than the URL itself is a self-inflicted no-index. -
Rule out the cheap blockers before the expensive theories
Check that the page does not carry a
Adding URLs to the sitemap file is not enough: you have to resubmit it from the panel so Google rereads it. The old ping endpoint was deprecated in 2023.noindextag, thatrobots.txtis not blocking the path, and that the URL is actually in your sitemap. These three take five minutes and they are the only causes on this list with an immediate fix. -
Count how many internal links point to the page
Open your own site and try to reach that post by clicking from the home page. If the only route in is the sitemap, the page is orphaned. This is the most common cause on a store blog and the one that gets missed most often, because the page looks perfectly fine on its own.
The sitemap is a list, not a recommendation. Internal links are how you tell Google what matters.
Where the chain breaks
Four steps between publishing and appearing. The report names the step where it stopped.
The page was never read. Rewriting it changes nothing, because nothing of it was ever seen.
This is the only one of the two where rewriting is the right move — and even then, not always.
The four causes, in the order they actually show up
1 · The domain has no authority yet
Google spends a limited amount of effort on each site, and it decides how much based on how established the site looks. A store whose blog nobody links to from outside gets a small share, and with a small share it processes the pages it already knows before the new ones. It is the least satisfying cause because it cannot be fixed by writing.
It is also the one that unlocks everything else: a single relevant external link changes the budget for the entire site, not just for the page it points to.
2 · The page is orphaned
Nothing on your own site links to that post. It reaches Google through the sitemap, which is a list of addresses with no indication of importance. When there is competition for crawl budget, orphan pages lose it. This is the cheapest cause to fix on the whole list, and the one that shows up most often on a blog built post by post with no plan for how they connect.
3 · The content already exists, on your site or someone else's
If the page repeats what another of your posts already says, Google may treat it as a duplicate and keep only one. And if the text came from the supplier's catalog description, it is on dozens of other stores word for word, so there is no reason to store yours specifically. Search Console reports this under duplicate-related states, not under Crawled.
4 · Something is blocking it, technically
A leftover noindex, a robots.txt rule that covers more than it was meant
to, a canonical pointing at another URL. It is the rarest cause of the four and the first one people
check, which is usually a waste of the afternoon — but it is worth ruling out precisely because it is
the only one with an instant fix.
What to do with each case
| What Search Console says | What to do | |
|---|---|---|
| Never read | Discovered — currently not indexed | Link to it from pages that are already indexed. Do not rewrite: nothing of it has been read |
| Read and rejected | Crawled — currently not indexed | Give the page a reason to exist: make it answer something specific and completely, or merge it into the post that already covers the topic |
| Seen as a copy | Duplicate, Google chose a different canonical | Check whether it really duplicates one of yours. If it does, consolidate. If it does not, differentiate the content until it stops looking like one |
| Blocked | Excluded by noindex, or blocked by robots.txt | Remove the tag or the rule and request indexing. This one is immediate |
| Points elsewhere | Alternate page with proper canonical tag | Review the canonical. If it names another URL, that is what you told Google to do |
| Not in the queue | URL is unknown to Google | Add it to the sitemap and resubmit the sitemap from the panel so it gets reread |
On a domain a few months old, a share of pages sitting unindexed is the normal state and not a symptom. Reacting to it by rewriting or deleting is the most common mistake, and it is expensive twice over: rewriting resets whatever the page had accumulated, and deleting throws away the URL along with its history. If the page is in Discovered, it was never read, and it cannot have been rejected for anything it says.
And not every page deserves to be indexed. Tag listings, filter combinations and internal search results are pages nobody would ever search for. Having them out of the index is not a failure, it is the correct outcome, and forcing them in only spends budget that your posts need.
Frequently asked questions
Why are my pages not indexed by Google?
Publishing does not oblige Google to index anything. A page has to be discovered, then crawled, and only then does Google decide whether it is worth storing. Most pages that never get indexed on a small store fail at the last step for a reason that has nothing to do with a technical error: the domain has little authority, so Google limits how much of it it is willing to process, and the pages nobody links to are the first ones it skips.
What is the difference between Discovered and Crawled but not indexed?
Discovered — currently not indexed means Google knows the URL exists but has not spent the time to download it yet. It is a budget queue, and the usual cause is that nothing links to that page. Crawled — currently not indexed means Google did download it, read it and decided not to store it. That is a judgment about the page. They look alike in the report and they have opposite fixes.
Should I rewrite or delete a post that is not indexed?
Not as a reaction. On a young domain, waiting is part of the process and rewriting resets the clock without fixing the cause. Deleting is worse: you lose whatever the URL had accumulated. First find out which of the two states it is in, because if it is Discovered the page was never even read and no amount of rewriting will change that.
How long does Google take to index a new page?
On an established site with regular traffic it can be hours. On a domain a few months old with no external links it can be weeks, and some pages never make it. There is no guaranteed deadline: indexing is a decision Google makes, not a service it owes you. What shortens it is authority and internal links, not resubmitting the same URL over and over.
Does submitting the sitemap again help?
It helps for discovery, not for the decision. Adding URLs to the sitemap file is not enough on its own: you have to resubmit it from the Search Console panel so Google rereads it, because the old ping endpoint was deprecated in 2023. That gets the URL into the queue. Whether it comes out of the queue depends on everything else.
Why do orphan pages struggle to get indexed?
Because internal links are how Google works out what matters on your site. A page that nothing links to reaches it only through the sitemap, which is a list, not a recommendation. On a domain with limited crawl budget, the pages nobody points to are the first ones to be left in the queue. It is the cheapest thing to fix on this whole list and the most often overlooked.
Find out which of your posts Google is ignoring
The free diagnosis reads your blog and your Search Console data and tells you which posts are not indexed, which ones are orphaned, which ones overlap with each other and how many link to your catalog.
Get my diagnosisno card · the diagnosis is free · we email you once