Why Most Founders Should Block Their Old Blog Posts

The Problem Nobody Talks About

You shipped. You wrote blog posts. Some ranked. Most didn't. Now you have 50+ pieces of mediocre content sitting on your domain, burning crawl budget and diluting your site authority.

Google crawls your site with limited resources—your crawl budget. Every second spent crawling a 2-year-old post about a feature you killed is a second not spent crawling your new, revenue-generating content. Every old post that ranks for nothing is a page that doesn't help your domain authority.

The brutal truth: most founders should noindex their old blog posts. Not delete them. Not redirect them. Noindex them. Here's why, and exactly how to do it.

Why Old Content Tanks Your SEO

Your domain has a finite amount of authority. Google allocates crawl budget based on your site's perceived importance and freshness. When you have 100 pages and only 20 matter, you're wasting 80% of your crawl equity on noise.

Old blog posts—especially thin ones that never ranked—are authority sinks. They:

• Waste crawl budget. Google spends time crawling pages that don't drive business value. That time could go to your core product pages, your updated guides, or your new content.
• Dilute internal link equity. Every internal link from your navigation, footer, or blog archives points to old posts. That's equity that could flow to high-value pages.
• Create duplicate or near-duplicate content. You probably wrote similar posts multiple times. Search engines penalize sites with thin, repetitive content.
• Confuse your topical authority. If you wrote 20 posts about "React best practices" in 2022 and none ranked, Google thinks you're weak on that topic. Keeping them signals you're unfocused.
• Hurt your brand. Old posts with outdated advice, dead links, or broken formatting hurt your credibility. Visitors land on a 3-year-old post and think you're not maintaining your site.

The fix isn't to delete them. It's to block them from search engines with noindex.

Prerequisites: Before You Start

Before you noindex anything, you need three things:

1. Google Search Console access. You need to see which old posts actually get impressions or traffic. If a post gets zero traffic, you're safe to noindex it. If it gets 50 clicks a month, you need to think harder.

Set up Google Search Console in 10 minutes if you haven't already. Then check your Performance report to identify which blog posts drive actual traffic.

2. A clear content strategy. You need to know which topics matter to your business. If you're blocking all old content, you need a plan for replacing it with new content that ranks. Otherwise, you're just deleting SEO opportunity.

The 100-day SEO roadmap from Day 0 to Day 100 includes building a keyword roadmap. Do that first. Then noindex the old posts that don't align with your roadmap.

3. A backup of your old content. You're not deleting anything. You're just hiding it from search engines. Keep a spreadsheet of every post you noindex—title, URL, noindex date, reason. You might need to reverse the decision later.

Understanding noindex vs. robots.txt

There's a critical difference between noindex and robots.txt, and most founders get it wrong.

robots.txt tells search engines not to crawl a page. Google sees the directive, respects it, and doesn't crawl the page. But if another site links to your page, Google might still index it (without crawling it). It's a crawl directive, not an indexing directive.

noindex tells search engines not to index a page. Google can still crawl it, but it won't appear in search results. If a page is already indexed and you add noindex, Google will remove it from the index within days or weeks.

For old blog posts, noindex is the right choice. You want Google to stop indexing them, even if they have external links. Check out the decision tree for when to use noindex vs. robots.txt for a detailed breakdown of when to use each.

Step 1: Audit Your Old Content

Don't noindex everything. Audit first.

Open Google Search Console and go to Performance. Filter by your blog section (e.g., example.com/blog/). Sort by "Clicks" in descending order. You'll see which blog posts actually drive traffic.

Export this data. Create a spreadsheet with:

• Post URL
• Post title
• Impressions (how many times it appeared in search results)
• Clicks (how many people clicked it)
• Average position (where it ranks)
• Date published
• Date last updated

Now, apply this logic:

Definitely noindex:

• Posts with zero clicks and zero impressions in the last 90 days
• Posts with outdated information (e.g., "Best React Patterns in 2021")
• Posts that are duplicates or near-duplicates of newer posts
• Posts about features you no longer offer
• Posts with broken links, missing images, or formatting issues

Maybe noindex:

• Posts with 1–5 clicks per month but low average position (rank 50+). These might rank better if you update them.
• Posts that are "okay" but not aligned with your current business

Never noindex:

• Posts that drive consistent traffic (10+ clicks/month)
• Posts that rank in the top 10 for valuable keywords
• Posts that link to your product or core pages
• Cornerstone content that defines your expertise

If you have 50 posts and 30 of them have zero traffic, you're probably safe to noindex 20–25 of them immediately. Start there.

Step 2: Add noindex Meta Tags

The simplest way to noindex a post is to add a meta tag to the page's HTML <head> section.

Add this line to every post you want to noindex:

<meta name="robots" content="noindex">

Or, if you want to be more specific:

<meta name="robots" content="noindex, follow">

This tells search engines: "Don't index this page, but you can follow the links on it." This is useful if the old post links to important pages on your site.

For WordPress users: Most WordPress SEO plugins (Yoast, Rank Math, All in One SEO) have a "Robots Meta" setting in the post editor. Open the post, find the SEO section, and set it to "Noindex." Save. Done.

For static sites or custom platforms: You'll need to edit the HTML directly or use your platform's meta tag settings. If you're using a headless CMS, add the meta tag to your template for blog posts marked as "noindex."

For Webflow, Framer, or no-code platforms: Most have a "SEO" or "Advanced" tab in the page settings. Look for "Robots Meta" or "Meta Tags" and add the noindex directive there.

Don't overthink this. If you have 20 posts to noindex and your platform doesn't make it easy, do it in batches. Spend 30 minutes and knock out 10 posts.

Step 3: Update Your robots.txt (Optional)

You don't need to update robots.txt if you're using noindex meta tags. The meta tags are enough. But if you want to be extra cautious and prevent Google from even crawling certain posts, you can add a directive to robots.txt.

For example, if you want to block all posts from a specific year:

User-agent: *
Disallow: /blog/2022/

This tells Google not to crawl anything in the /blog/2022/ directory. But remember: Google might still index those pages if they have external links. That's why noindex meta tags are better for this use case.

For a detailed guide on writing robots.txt files, check out the founder's template for robots.txt. And if you're confused about the difference, the guide to robots.txt, sitemaps, and canonicals breaks down what most founders get wrong.

Step 4: Remove Old Posts from Your Sitemap

Your XML sitemap tells Google which pages to crawl. If you're noindexing posts, you should remove them from your sitemap too. This signals to Google: "These pages aren't important. Don't bother crawling them."

If you use WordPress, your sitemap is usually generated automatically. You'll need to:

1. Go to your SEO plugin (Yoast, Rank Math, etc.)
2. Find the "Sitemap" or "XML Sitemap" settings
3. Look for an option to exclude posts by status, date, or custom rule
4. Set it to exclude posts marked as "noindex"

If you're on a static site or custom platform, manually edit your sitemap.xml file and remove the URLs of noindexed posts.

Your sitemap should only list pages you want Google to crawl and index. If a page has noindex, it shouldn't be in the sitemap.

Step 5: Monitor with Google Search Console

After you noindex your old posts, monitor them in Google Search Console. This is critical.

Go to Coverage in Search Console. You'll see a breakdown of:

• Indexed pages
• Excluded pages (including noindex pages)
• Error pages

Within a few days, your noindexed posts should move from "Indexed" to "Excluded." This is good. It means Google processed your noindex directive.

If a post stays "Indexed" for more than 2 weeks, Google might not have recrawled it yet. You can manually request a recrawl using the URL Inspection Tool. Open the tool, paste the URL, and click "Request Indexing." Google will recrawl it, see the noindex directive, and remove it from the index.

For a deeper dive into Coverage Issues, read the plain-English guide to Coverage Issues in Google Search Console. It covers exactly what to look for and how to fix problems.

Step 6: Set Up Redirects (If You're Replacing Old Posts)

If you're replacing an old post with a new one, don't just noindex the old one. Set up a 301 redirect.

A 301 redirect tells Google: "This page moved permanently to this new URL." Google transfers the old page's authority to the new page. The old page is removed from the index, and the new page gets a boost.

For example:

• Old URL: example.com/blog/react-best-practices-2022/
• New URL: example.com/blog/react-best-practices-2024/
• Redirect: Old → New

Google will index only the new URL and pass the old post's authority to it. This is much better than just noindexing.

If you're using WordPress, plugins like Redirection or Yoast make this easy. If you're on a static site, you'll need to add the redirect to your .htaccess file (Apache) or your server configuration (Nginx).

For a complete step-by-step guide, see the article on setting up 301 redirects for a domain migration. The logic is the same whether you're migrating domains or consolidating old posts.

Step 7: Update Internal Links

If you have internal links pointing to old noindexed posts, update them.

For example, if your navigation menu links to a noindexed "Blog Archive" page, remove it. If your footer links to old posts, update those links to point to new, relevant posts instead.

Internal links are precious. Every link is a vote for that page. Don't waste votes on noindexed content.

Use a tool like Screaming Frog or your platform's built-in link checker to find all internal links to noindexed posts. Then update them in batches.

Pro Tips and Warnings

Tip: Start small. Don't noindex 50 posts at once. Start with 5–10 obviously bad posts. Monitor them in Search Console for a week. Make sure nothing breaks. Then do the next batch.

Tip: Noindex before you delete. Never delete a page outright. Always noindex first, wait 30 days for Google to remove it from the index, then delete if you want. This prevents 404 errors and gives you a safety net if you change your mind.

Warning: Don't noindex everything. If you noindex 80% of your site, Google will think your site is mostly junk. Keep your best content indexed. The goal is to cut the bottom 20–30%, not everything.

Warning: Monitor your traffic. After you noindex old posts, watch your organic traffic for 2–4 weeks. If traffic drops significantly, you might have noindexed something valuable. Use Google Search Console's Performance report to see which pages are driving traffic.

Tip: Use noindex as a temporary measure. If you're not sure about a post, noindex it for 60 days. Monitor the impact. If traffic doesn't drop, keep it noindexed. If it does, remove the noindex directive and keep the post indexed.

Warning: Noindex doesn't delete backlinks. If an external site links to your noindexed post, that link still exists. The link equity still flows to your domain, but the page won't appear in search results. This is fine—it's actually good. You get the link equity without the page being indexed.

The Bigger Picture: Authority Consolidation

Noindexing old posts is part of a larger SEO strategy: authority consolidation. The idea is to concentrate your domain's authority on the pages that matter most.

Instead of spreading your authority across 100 mediocre posts, you focus it on 20 great posts. Those 20 posts rank higher, drive more traffic, and generate more business value.

This is why quarterly SEO reviews matter. Every 90 days, audit your content. Identify what's working. Noindex what's not. Update what's close. This is how you build a lean, high-authority site.

If you're building from scratch, the 100-day SEO roadmap includes a keyword strategy that prevents you from writing junk content in the first place. But most founders didn't follow that. You have old posts. Noindex them.

Real-World Impact

Here's what happens when you noindex old content:

Week 1–2: Google recrawls your old posts, sees the noindex directive, and removes them from the index. Your indexed page count drops. This looks scary but it's good.

Week 3–4: Google reallocates crawl budget to your remaining pages. Your high-value posts get crawled more frequently. Google sees fresh content more often.

Month 2: Your remaining posts start ranking higher. You see an uptick in impressions for your core content. Click-through rate improves because your search snippets are for relevant, current posts.

Month 3: Organic traffic increases, even though you have fewer indexed pages. This is the power of authority consolidation.

One founder reported a 40% increase in organic traffic after noindexing 60 thin blog posts. Another saw their top 10 keywords move from position 8 to position 3 within 6 weeks. The pattern is consistent: fewer, better pages rank higher.

Content Control in the Age of AI

There's another reason to noindex old content: AI scraping. As major news publishers have started blocking the Internet Archive's Wayback Machine to prevent AI companies from accessing their content, founders should think about what content they want preserved and what they don't.

Noindexed pages are less likely to be scraped by AI models. If you have outdated advice or proprietary information in old posts, noindexing them reduces the chance that AI companies will use that content for training data.

As EFF researchers have noted, controlling your content's visibility is becoming more important. Noindex gives you that control.

When NOT to Noindex

Before you start noindexing, know when not to:

Don't noindex if the post ranks well. If a post ranks in the top 5 for a keyword and drives 20+ clicks per month, keep it indexed. The ranking is valuable.

Don't noindex if it's a cornerstone piece. Cornerstone content defines your expertise. If you wrote a definitive guide to your product or industry, keep it indexed even if it's old. Update it, but keep it indexed.

Don't noindex if it has external backlinks. If other sites link to a post, that link equity is valuable. Keep the post indexed to capture that value. If the post is outdated, update it instead of noindexing it.

Don't noindex if you haven't replaced it. If you're noindexing a post about "React best practices," you should have a new post about "React best practices in 2024" ready to go. Otherwise, you're just deleting SEO opportunity.

Don't noindex your entire blog. Some founders think: "My blog doesn't drive revenue. Let me noindex the whole thing." Wrong. A blog is long-term SEO infrastructure. It builds authority, drives organic traffic, and generates leads. Be selective, not blanket.

Implementation Checklist

Here's a step-by-step checklist to noindex your old posts:

• Set up Google Search Console (if not done)
• Export Performance data for your blog section
• Create a spreadsheet of posts to noindex
• Add noindex meta tags to old posts (WordPress plugin or HTML)
• Update your sitemap to exclude noindexed posts
• Remove internal links pointing to noindexed posts
• Set up 301 redirects for posts you're replacing
• Submit a recrawl request in URL Inspection Tool
• Monitor Coverage Issues in Search Console
• Check organic traffic after 2–4 weeks
• Repeat quarterly

Building Better Content Habits

Noindexing old posts is a cleanup task. The real win is preventing junk content from accumulating in the first place.

If you're shipping new content, follow a simple rule: every post should target a keyword with search volume and align with your business. If it doesn't, don't publish it.

The 7 SEO habits every founder should build in 30 days includes a process for validating content before you publish. Do this, and you won't accumulate junk.

Also, track your metrics. The 5 SEO metrics that matter are organic traffic, rankings, click-through rate, conversion rate, and crawl health. Monitor these weekly. If a post isn't contributing to any of these metrics after 90 days, noindex it.

The Takeaway

Most founders have old blog posts that don't drive traffic, don't rank, and don't help their business. These posts waste crawl budget, dilute authority, and hurt your brand.

The solution: noindex them. It's not deletion. It's strategic pruning. You're telling Google: "These pages aren't important. Focus on my core content."

When you do this, your remaining posts rank higher. Your organic traffic increases. Your site authority concentrates on what matters.

Start with an audit. Identify the bottom 20–30% of your blog posts by traffic and relevance. Noindex them. Monitor the impact. Repeat quarterly.

Your domain will thank you. Your traffic will thank you. And your SEO will finally work.