Quick answer: "Crawled – currently not indexed" in Google Search Console means Google fetched your page but has not added it to its index. The usual suspects are thin or generic content, posts that overlap each other, and pages with no internal links pointing at them. Fix those first, then check your canonical and sitemap. Recrawling can take a few days to a few weeks, and Google may still choose not to index the page.
If you publish AI-assisted blog posts on a regular schedule, this status tends to show up sooner or later. Below is what it means, the causes Google’s own documentation points to, and the fixes in the order we would do them.
What the status means
Google Search works in three stages: crawling, indexing and serving. In its guide to how Search works, Google says not every page passes through every stage. Crawling means Googlebot fetched the URL. Indexing means Google stored the page so it can appear in results.
This status sits between the two: the page was crawled, but it is not in the index. Google’s technical requirements page says: "indexing isn’t guaranteed." The how-Search-works guide names low-quality content as a common reason pages are not indexed, along with robots meta rules that block indexing and designs that make indexing difficult.
Why AI posts often land here
They tend to be generic or overlap each other. Google’s docs point to four common causes.
- Generic content. A post that repeats what every other article on the topic already says gives Google little reason to keep it. Google’s helpful content guidance asks whether a page provides original information, reporting, research or analysis.
- Near-duplicate posts. Three posts aimed at the same question look, to Google, close to one page. Its canonicalization page explains that Google groups near-duplicates and picks one as the canonical. The others are crawled less often.
- No internal links. A post that nothing else on your site links to is harder to find and gives Google no sign that you care about it.
- Technical signals that point somewhere else. A wrong canonical, or a sitemap whose dates don’t match reality, can muddy things even on a good page.
Each of these can be fixed.
The fixes, in order
1. Add something only you could write
Start here. Go back to the post and add a real example from your own work: a job you did, a number you measured, a step you always take that others skip. Google’s guidance asks whether the page adds original information or first-hand experience. One or two paragraphs of real detail can change what a page is worth to a reader.
2. Merge posts that answer the same question
List your posts with the query each one targets. Where two or more overlap, keep the strongest, move the best parts of the others into it, and 301-redirect the old URLs to it. Google’s guidance on generative AI features says a high page count doesn’t make a site higher quality, and warns against separate pages for every query variation.
3. Link to the page from your own posts
Find two or three related posts and link to the stuck page from inside the body text, with anchor text that says what the reader will get. Google’s link best practices say: "Every page you care about should have a link from at least one other page on your site." Use a normal <a href> link; Google only crawls links that are <a> elements with an href.
4. Check which canonical Google chose
Yoast and Rank Math already add a self-referencing canonical tag to each post, so the tag in your HTML is usually fine. What matters is the canonical Google picked. Paste the URL into the URL Inspection tool in Search Console and compare the Google-selected canonical with your own URL. Google’s canonical troubleshooting page notes that a declared canonical can still be overridden.
We hit a version of this on this blog. The canonical tags on our posts pointed at a raw IP address instead of the domain. The cause was in wp-config.php: the site URL was built from the visitor’s host header, so a visit by IP produced IP-based URLs. The fix had three parts. We pinned WP_HOME and WP_SITEURL to the https domain, added a 301 redirect from the IP to the domain, and rebuilt Yoast’s SEO data so it regenerated the stored URLs. After that, every URL showed the right canonical. If your canonicals look odd, check those two settings first.
5. Check the sitemap instead of just resubmitting it
Check the post is listed in your sitemap (/wp-sitemap.xml, or /sitemap_index.xml with Yoast or Rank Math) and that lastmod is right. Resubmit only if the sitemap URL changed. Google’s build-a-sitemap page says to use lastmod only when it is consistently and verifiably accurate, and calls submission a hint. Its sitemap overview adds that a small site, roughly 500 pages or fewer, that is fully linked internally may not need a sitemap at all.
6. Request indexing once, then wait
In URL Inspection you can click "Request Indexing." According to Google’s recrawl page, crawling can take a few days to a few weeks, and a request does not guarantee the page will be included. The tool has a quota, and repeat requests don’t speed anything up. Make your changes first, request once, and leave it.
How to keep it from happening again
- Before a post goes live, give it at least one first-hand example and at least one internal link from an existing post. Our checklist for writing an SEO-optimized blog post covers the rest.
- Don’t publish a second post for a query you already cover; update the first one.
- Keep a simple list of each URL and the question it answers, so overlap is obvious before you write.
- Look at the Page indexing report in Search Console every couple of weeks, not only when traffic drops.
Frequently asked questions
Why is my page crawled but not indexed when the content is good?
Quality is one reason, not the only one. Check that other posts link to it, that URL Inspection shows the canonical you expect, and that the page is in your sitemap with an accurate lastmod. Google says plainly that indexing isn’t guaranteed, so a good page can still wait.
Will "Request Indexing" fix it?
It asks Google to recrawl. It doesn’t guarantee inclusion, it is limited by a quota, and asking again doesn’t make it faster. Fix the page first, then request once.
How long should I wait?
Google’s recrawl page says crawling can take a few days to a few weeks. Give it that long after your changes before deciding the page needs more work.
Summary
This status means Google fetched the page and chose not to index it for now. Make the post more original, merge posts that overlap, link to it from your own pages, and confirm in URL Inspection that Google sees the canonical you intended. Publishing more won’t fix it; better pages might.
We make Rozzpost, which writes and publishes posts to WordPress; you approve every post first.