New Blog Post Not Indexed by Google? What Each Page Indexing Status Means and What to Do (2026)
Why isn't my new blog post indexed by Google?
Usually because Google hasn't crawled it yet, has crawled it and chosen not to index it for now, or has been told not to index it. Search Console tells you which. Inspect the post's URL with the URL Inspection tool, read the status in the Page indexing section, and fix only what that status points to. A brand-new post on a small site often shows as "Discovered – currently not indexed" or "URL is unknown to Google" for days or weeks. Google says crawling can take from a few days to a few weeks, and that requesting a crawl doesn't guarantee the page will be included in search results. The things you control are whether Google can find the post, whether it's allowed to index it, and whether the post is worth indexing.
This page is a troubleshooter for one post at a time. For the bigger picture of how long a new blog takes to show in Google, see our realistic timeline for a new SEO blog.
First, inspect the URL
- Open Search Console for the property that contains the post. You need to be an owner or full user to request indexing.
- Paste the full post URL into the inspection bar at the top.
- Read the verdict ("URL is on Google" or "URL is not on Google") and, under Page indexing, the specific reason.
- Run Test live URL to see whether Google can fetch the current version of the page. The stored result may be out of date.
Google notes that "URL is on Google" doesn't guarantee the page appears in results. To check that, search for the exact URL.
What each status means, and what to do
| Status | What Google says it means | What to do |
|---|---|---|
| URL is unknown to Google | Google hasn't found the URL yet | Make sure the post is in your sitemap and linked from your blog page and from older posts |
| Discovered – currently not indexed | Found, not crawled yet; Google rescheduled the crawl, often to avoid overloading the site | Usually wait. Add internal links from pages that are already indexed |
| Crawled – currently not indexed | Crawled but not indexed; it may or may not be indexed later, and there's no need to resubmit | Improve the post: a clearer answer, more original detail, and links to and from related posts |
| Excluded by "noindex" tag | The page tells Google not to index it | Remove the noindex if you want the post indexed. Check your CMS or SEO plugin settings |
| Blocked by robots.txt | A robots.txt rule stops Google crawling the URL | Fix the rule if the block is unintended |
| Duplicate without user-selected canonical | Google sees another page as the main version and serves that one | Make the post clearly different, or set a canonical to the page you want indexed |
| Page with redirect | The URL redirects elsewhere, so it isn't indexed itself | Use the final URL in your sitemap and links |
| Soft 404 or Not found (404) | The page looks like or returns a "not found" page | Fix the URL or the page content, and use the right status code |
Google is clear that not every URL needs to be indexed. A noindex on a tag page or a 404 for a deleted post is fine. The point is to fix the posts you actually want in search. Duplicate versions of the same post are a common example; our guide to canonical tags for a small business blog shows how to tell Google which one to show. Just don't use robots.txt to keep a page out: it blocks crawling, not indexing; see what to block in robots.txt.
Make the post easy to find
- Sitemap with an accurate lastmod. Google uses the
lastmoddate in sitemaps if it's consistently accurate. It retired the old sitemap "ping" endpoint in 2023, so updating your sitemap and letting Google read it is the way to tell it about new posts. Submitting a sitemap is a hint, not a guarantee. - A link from your blog page. New posts should appear on your
/blogpage, which Google already knows about. - Links from older, indexed posts. Add a sentence and a link from two or three related posts. This also helps readers. Our guide to internal linking for small business blogs shows how.
Request indexing once, then wait
When the live test passes, you can click Request indexing. Use it for a few important URLs, not for every post. Google says there's a quota for individual URL submissions, and that requesting a recrawl of the same URL several times won't get it crawled any faster. For many new or updated pages at once, Google recommends a sitemap with updated lastmod dates.
Then give it time. Write down the date you published and the date you requested indexing, and check again in a week or two rather than every day. Our monthly Search Console check keeps that routine short. If you also republished the post on Medium, check which copy Google shows; see the 5-step Medium republish method.
If the post still isn't indexed after a few weeks
When a post stays at "Crawled – currently not indexed", the problem is usually the post, not a technical setting. Ask:
- Does it answer one clear question better than what's already in search? Put the answer near the top.
- Does it repeat another post on your own site? If two posts cover the same question, Google may pick one. Decide whether to refresh the older one instead. Our refresh or write new test helps you choose.
- Is it thin? Add the detail only you can give, such as prices, steps, examples from your own work, or photos.
- Is it isolated? Check it has links in from related posts, not only from the blog page.
Make one real improvement, update the lastmod date, and check again after a couple of weeks.
How we handle it on our own blog
On pilotaseo.com, each new post goes into the sitemap with its real publish or update date, appears on /blog, and gets links from related older posts on the day it goes live. We check the live page's status code and noindex rules after publishing. None of this guarantees indexing or rankings, which no one can promise, but it removes the avoidable reasons a post gets missed. If you want this done for your own site, PilotaSEO's plans are Autopilot at €322 a year and Growth at €8,250 a year, listed on the PilotaSEO homepage.
FAQ
How long does it take Google to index a new blog post?
Google says crawling can take anywhere from a few days to a few weeks, and a crawl request doesn't guarantee inclusion in search results. Small and new sites often take longer.
Should I request indexing for every new post?
No. There's a quota for individual URL requests, and repeating a request doesn't speed things up. Keep your sitemap and its lastmod dates accurate, and save manual requests for a few important pages.
What does "Crawled – currently not indexed" mean?
Google crawled the page but didn't index it. It may or may not be indexed later, and Google says there's no need to resubmit it. Improving the post and its internal links is usually the useful next step.
Can I still ping Google with my sitemap?
No. Google deprecated the sitemaps ping endpoint in 2023. Submit your sitemap in Search Console or list it in robots.txt, and keep lastmod dates accurate.
Sources
- Google Search Central: ask Google to recrawl your URLs (checked 2026-10-26)
- Search Console Help: Page indexing report (checked 2026-10-26)
- Search Console Help: URL Inspection tool (checked 2026-10-26)
- Google Search Central Blog: sitemaps ping endpoint is going away (checked 2026-10-26)
- Google Search Central: build and submit a sitemap (checked 2026-10-26)