Why Are My Blog Posts Not Indexed by Google? Causes and Fixes

October 26, 2026

If you're asking why are my blog posts not indexed by Google, the cause is almost always one of three things. Google can't reach the post (a noindex tag, robots.txt, a private store or a bad canonical). Google hasn't found it yet (no sitemap entry, no internal links). Or Google crawled it and decided it wasn't worth adding to the index. Search Console tells you which one applies. The fix depends on that label, so read it before you change anything.

This guide matches each Search Console status to its likely cause, gives you a two-minute check for each one and tells you what to fix. It has separate notes for WordPress and Shopify, and a section for blogs that publish a lot of posts or use AI to write them.

If you'd rather not deal with any of this by hand, AI SEO Crew writes each post for a real Google search, then resubmits your sitemap and pings IndexNow after it's published. Get your free keyword plan and read your first article before you pay.

First, check whether the post is indexed at all

"Indexed" and "ranking" are different problems. An indexed post is stored by Google and can appear in results. A ranking post shows up high enough for someone to see it. If your post is indexed but nobody finds it, you have a ranking problem (search intent, competition or content quality), and that needs a different fix.

How to check if a blog post is indexed

URL Inspection in Search Console. Paste the full post URL into the bar at the top. It tells you whether the URL is on Google and, if it isn't, why. This is the check to trust.
The Pages report (Indexing > Pages). It lists every non-indexed URL grouped by reason. Open a reason to see which posts it covers.
The site: operator. Search site:yourdomain.com/blog/post-slug. It's quick, but Google says site: results aren't guaranteed to be complete. No result proves nothing, so confirm with URL Inspection.

Read your Search Console status: a decision table

Find your status in the left column. The definitions come from Google's Page indexing report documentation.

Status	What Google means	Likely cause on a blog	2-minute check	Fix
Crawled, currently not indexed	Google crawled the page but hasn't indexed it. It may be indexed later	Thin, generic or near-duplicate post	Compare the post with your closest other post and the top 3 results	Improve, merge or link it (see below)
Discovered, currently not indexed	Google knows the URL but put off crawling it, because crawling then could have overloaded the site	Weak internal links, lots of new URLs at once, slow server	Count the indexed pages that link to the post	Add links from indexed pages, keep the sitemap clean
Excluded by 'noindex' tag	Google found a noindex rule and skipped the page	SEO plugin setting, theme code, staging setting left on	View the page source and search for "noindex"	Remove the rule, then request indexing
Blocked by robots.txt	Your robots.txt file blocks the page	A Disallow rule covering /blog/ or a tag path	Open yourdomain.com/robots.txt	Delete or narrow the rule
Duplicate without user-selected canonical	The page duplicates another one and no preferred version is set	Tag pages, category archives, URL parameters	Find the duplicate shown in URL Inspection	Add a canonical tag or merge the pages
Duplicate, Google chose different canonical than user	You set a canonical, but Google thinks another URL fits better	Two posts on the same topic	Look at which URL Google picked	Merge the posts or make each one clearly different
Page with redirect	The URL redirects, so it won't be indexed	Slug changed, old URL still in the sitemap	Load the URL and see where it ends up	Put only the final URL in sitemaps and links
Soft 404	The page returns a normal status but looks like "not found"	Empty post, broken template, very short page	Open the post logged out	Add real content, or return a true 404

Some statuses are normal. "Alternate page with proper canonical tag" means the page points correctly to an indexed canonical version, so nothing is broken.

Crawled currently not indexed vs discovered: what each one asks you to do

When the status stays "Crawled, currently not indexed"

Google's help page says the URL may or may not be indexed later and that you don't need to resubmit it. Requesting it again won't help. What helps is giving Google a better reason to keep the page:

Add something your other pages don't have. A worked example, a real screenshot, a checklist or a clear answer to one specific question. A post that says the same things as ten others is easy to skip.
Check for overlap with your own posts. Two posts called "best running shoes for beginners" and "beginner running shoe guide" compete with each other. Merge them into one stronger post and redirect the weaker URL.
Link to it from pages that are already indexed. Your homepage, a category page or a popular post. An orphan post with no internal links looks unimportant.
Check the whole blog, not just one post. A guide on why posts don't rank notes that low-quality content in one part of a site can affect the whole site. Lots of thin posts can hold back the good ones.

When the status is "Discovered, currently not indexed"

This is a discovery and crawl scheduling problem, not a quality verdict. Google delayed the crawl so it wouldn't overload your site. It's common when a site adds many URLs at once. Make sure the post is in your sitemap, link to it from two or three indexed pages, and remove junk URLs (empty tag pages, parameter URLs) that take up Google's attention.

Discovery is also where your publishing routine matters. A sitemap that updates and gets resubmitted after every new post is the simplest way to make sure Google knows the post exists. After each article is published, AI SEO Crew resubmits your sitemap in Search Console and pings IndexNow. The free plan starts with a keyword plan and a first article, so you can see the work before paying. Get your free keyword plan.

Blog posts not indexed on WordPress or Shopify: platform checks

WordPress

Settings > Reading > "Discourage search engines from indexing this site". When this box is ticked, WordPress adds a noindex, nofollow robots meta tag to every page. People often leave it on after building the site in private.
Your SEO plugin. Check the post's own robots setting and the plugin's global setting for posts, categories and tags. A single toggle can noindex every post.
Plugin sitemaps. Open the sitemap your SEO plugin generates and check that the post URL is in it. Submit that sitemap URL in Search Console.
The noindex header. A noindex rule can also be sent as an X-Robots-Tag HTTP header, and Google says it has the same effect as the meta tag. Security or caching plugins sometimes add one. URL Inspection shows it.

Shopify

Password protection. Shopify says Google can't read your sitemap while the store is in private mode. Turn the password page off before you expect any indexing.
The automatic sitemap. Shopify generates yourstore.com/sitemap.xml, and it includes blog posts. Submit it in Search Console, once for each domain you use.
Blog URLs live under /blogs/. Inspect the full URL (for example /blogs/news/post-slug), not a shortened version.
Theme and app code. Some themes and SEO apps add noindex to tag or blog listing pages. View the post's source and search for "noindex".

One more rule applies to both platforms. Google says noindex only works if the page isn't blocked by robots.txt. If robots.txt blocks a page, Google can't crawl it, so it never sees the noindex tag. To remove a page from Google, use noindex. To get a page indexed, make sure neither one applies.

New blog post not showing on Google? Timing and "Request indexing"

A post published this morning usually won't be there by lunch. Google says indexing after a crawl request can take anywhere from a few days to a few weeks. The same page sets out the limits of the button:

There's a quota on individual URL requests, and requesting the same URL more than once doesn't speed it up.
For many URLs, Google recommends submitting a sitemap.
A request doesn't guarantee the page will appear in results, quickly or at all.
On hosted platforms like WordPress, new content is usually submitted automatically, so a manual request is often unnecessary.

Google is also clear that a page that follows every guideline still isn't guaranteed to be crawled, indexed or shown. So request indexing once for an important post, then spend your time on links and quality instead of clicking the button again.

Blogs that publish in volume or with AI

If you publish many posts quickly, and especially if AI writes them, "Crawled, currently not indexed" usually means one thing: the posts look too much alike. Google's guidance on AI content says the focus is on the quality of content, not how it is produced. Its spam policies also target scaled content abuse, meaning many pages made mainly to manipulate rankings rather than to help people.

What makes a post in a series worth indexing:

One search query per post. If two posts answer the same question, one of them is redundant. Merge them.
Facts from real sources, with links. Specific facts set a post apart from generic text.
Details from your own business. Your products, your process, your customers' real questions.
Internal links that create clusters. Each post links to its main topic page and to related posts, so Google sees how they fit together. Our guide to blog SEO explains how to plan this.
A steady pace. Publishing regularly lets you keep the sitemap and internal links up to date with each post.

For the bigger picture on using AI without hurting your site, see our pillar guide on AI SEO.

A 15-minute checklist for any unindexed post

Run these steps in order. Stop at the first one that fails and fix it.

Run URL Inspection on the exact URL and write down the status.
Open the post logged out, in a private window. Does it load with full content?
View the source and search for "noindex". Check the WordPress Reading setting or the Shopify password page.
Open robots.txt and check that no Disallow rule covers the post's path.
Check that the canonical tag points to the post itself, not to another page.
Open your sitemap and find the post URL. Make sure the sitemap has been submitted in Search Console.
Count the internal links pointing to the post from indexed pages. Add at least two.
Compare it with your closest other post. If they overlap, merge them.
Compare it with the top 3 Google results. Add whatever they're missing.
Request indexing once. Then wait, and check the status again in a week or two.

How AI SEO Crew handles this

AI SEO Crew writes each article for a single real search query, with linked sources. Its Editor agent checks every fact and every link and adds internal links before anything goes live. After each article is published, AI SEO Crew resubmits your sitemap in Search Console and pings IndexNow, so new posts don't sit waiting to be discovered. Your dashboard shows clicks and impressions for each article, so you can see which ones Google picks up.

Indexing is still Google's decision, and no tool can guarantee it. What you get is the part you control, done every time: $49 per site per month for 50 researched articles, published to WordPress, Shopify, GitHub or by webhook. Run it on autopilot or switch to review mode and approve each article yourself. Cancel anytime, and the published articles stay on your site. See the details on the pricing page.

Get your free keyword plan

Frequently asked questions

How long does it take Google to index a new blog post?

Google says indexing after a crawl request can take anywhere from a few days to a few weeks. There's no fixed delay, for a new site or an established one. Internal links and a submitted sitemap help Google find the post sooner.

Should I click "Request indexing" again if nothing happens?

No. Google says requesting the same URL more than once doesn't get it crawled faster, and there's a quota on these requests. Fix whatever the status points to, then request indexing once.

Is a sitemap enough to get my blog posts indexed?

A sitemap helps Google discover your URLs, and Google recommends one when you have many of them. It doesn't make Google index a page. Posts also need internal links and something worth indexing.

Does AI-written content stop Google from indexing my posts?

Google's guidance says it looks at the quality of content, not how it was produced. Posts that repeat each other or add nothing new are easy to leave out of the index, whoever wrote them. Mass-producing pages to manipulate rankings breaks Google's scaled content abuse policy.