Why Your New Blog Post Isn't Getting Indexed by Google (and How to Fix It)

If you run a dev blog, a portfolio site, or any project where you publish content, you have probably hit this frustrating moment: you publish a new post, search Google for it a day later, and it is simply not there. Not ranking low. Not there at all.
The first time it happened to me, I refreshed Google more times than I would like to admit, convinced I had broken something in my setup. I had not. The post just was not indexed yet, and for a new site, that turned out to be completely normal.
Here is what "not indexed" actually means, why it happens, and the practical steps to fix it, written for people who build their own sites and want to understand what is going on under the hood.
Indexing vs ranking: not the same thing
This trips up a lot of people, so it is worth being precise.
Indexing is Google adding your page to its database so it is eligible to appear in search results at all.
Ranking is where your page shows up once it is already in the index.
A page cannot rank until it is indexed. So when your new post is nowhere in search, the question usually is not "why is my SEO so bad," it is "why is my page not in the index yet." Different problem, different fix.
How to check indexing status
Before assuming the worst, confirm it. Two quick methods:

Google Search Console URL Inspection tool. Paste your URL and it tells you plainly whether the page is indexed, and if not, often why. This is the reliable way.
The site: operator. Search site:yourdomain.com/your-post-path in Google. If it appears, it is indexed. If nothing shows, it is not.

Why new posts sit unindexed
A few common reasons, roughly in order of how often they are the real cause:

1. The site is new and Google has not gotten to it. This is the big one. Google has to discover, crawl, then decide to index a page. On an established site that can take hours. On a new, low-authority site, days to a couple of weeks is normal. If your post is recent, you are often just early.
2. "Discovered, currently not indexed." Search Console found the page but has not crawled it yet. Common on new sites with limited crawl budget and few backlinks. Google is essentially saying "we see it, but we are not convinced yet."
3. "Crawled, currently not indexed." Different status, and people confuse the two. Here Google actually visited the page but chose not to index it, usually because it did not find enough unique value. This one is a quality signal, not just a waiting game.
4. Thin or duplicate content. Google does not promise to index every page on the web. If a page is thin or closely resembles existing content, it may get skipped.
5. Weak internal linking. Orphan pages with no internal links pointing to them get discovered and indexed slowly. If nothing on your site links to the new post, Google has a harder time finding and valuing it.
6. A technical block. The usual suspects: an accidental noindex meta tag, a robots.txt rule blocking the path, a sitemap that is missing the page or full of errors, or a canonical tag pointing somewhere else. The URL Inspection tool usually flags these directly. How to get indexed faster The practical checklist, in order:

Request indexing in Search Console via the URL Inspection tool. It puts the page in the queue and often speeds things up.
Add internal links to the new post from 2 to 3 related pages, so Google can find it and sees it matters.
Make sure the content is genuinely worth indexing. Thin pages get skipped. Add real value.
Check for technical blocks: no stray noindex, no robots.txt block, correct canonical, page present in a clean submitted sitemap.
A few quality backlinks help too, since Google discovers a lot of content by following links. You do not need many.
Then wait. After doing the above, give it days to a couple of weeks. Constantly resubmitting will not force it faster.

The mental model that helped me
The thing that finally calmed my refresh-Google-every-hour anxiety was reframing it: indexing is an invitation, not a guarantee.
Your job is to publish something valuable, make it easy for Google to discover through internal links and a clean sitemap, and remove any technical barriers in the way. After that, time is usually the final ingredient. Your post did not vanish into a void. Google just has not gotten to it yet, and on a new site, that is normal.

I went deeper into every one of these causes and fixes, with the exact Search Console steps, in a full guide over on my site: Why Is My New Blog Post Not Getting Indexed? I write there about SEO, AI tools, and building a blog from scratch, including the messy early days.
If you have your own indexing horror story or a tip that worked for you, drop it in the comments. Always curious how others handle this.