โ† All posts
๐Ÿšซ
SEO Indie Hackers SaaS

The noindex Tag Is Silently Killing Your SaaS Launch

After auditing 50+ indie SaaS landing pages, the #1 issue isn't bad copy or slow load times โ€” it's a single meta tag leftover from staging that tells Google to ignore your site entirely.

By Cooper ยท May 11, 2025 ยท 6 min read

If you've launched a SaaS in the last 12 months and you can't figure out why nobody's finding you on Google โ€” there's about a 76% chance it's this one tag.

The tag in question

Open your site, hit Cmd+U (Mac) or Ctrl+U (Windows). Search the page source for noindex.

If you see this:

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

...you've found your problem. That single line tells every search engine: "Do not include this page in your index. Pretend it doesn't exist."

You can spend $5,000 on a marketing campaign, ship the prettiest landing page on the planet, and rank on exactly zero queries โ€” because your own HTML is telling Google to skip you.

Why this keeps happening in 2026

Every modern AI builder (v0, Lovable, Cursor, Bolt, Replit) ships starter templates with noindex on by default. The reasoning is sound: while you're building in a preview environment, you don't want Google indexing half-finished pages. So the template sets noindex in the head.

The problem: when you deploy to production, the tag stays. There's no "you're live now, please remove this" alert. Most founders never look at their <head> after the initial build.

I audited 50 indie SaaS landing pages over the last month. Findings:

  • 38 of 50 (76%) had noindex still active in production
  • 41 of 50 had no sitemap.xml at the root
  • 47 of 50 were missing SoftwareApplication schema markup
  • 50 of 50 had broken Open Graph tags (the preview image when shared on X, LinkedIn, Discord)
  • 32 of 50 were blocking GPTBot / PerplexityBot / ClaudeBot in robots.txt by accident

The most painful audit was a SaaS doing ~$2k MRR. They were paying Google Ads for traffic because organic was zero. noindex had been live for 8 months without anyone noticing.

How to verify (90 seconds, no tools needed)

Method 1: View source

  1. Open your live site (not localhost, the real production URL)
  2. Right-click anywhere on the page โ†’ "View Page Source"
  3. Hit Ctrl+F / Cmd+F and search noindex
  4. If anything matches, you have the problem

Method 2: Google Search Console

If you've added your site to Search Console, go to "Pages" โ†’ "Why pages aren't indexed". If you see "Excluded by 'noindex' tag", that's a confirmed positive.

Method 3: Just run an audit

If you'd rather not dig through HTML manually, drop your URL into RankRadar โ€” we'll surface the noindex tag (if it exists) in about 30 seconds, along with 8-12 other SEO issues with revenue-loss estimates attached.

How to fix it

The fix depends on your stack. Here's the most common ones:

Next.js (App Router)

Check app/layout.tsx for a metadata export. If it has:

export const metadata = {
  robots: { index: false, follow: false }
}

Remove that block (or set index: true).

Next.js (Pages Router)

Check pages/_document.tsx and your Head components for any <meta name="robots" content="noindex" /> tags. Delete them.

Astro

Look in src/layouts/ for layout files importing a meta robots tag. Often there's a conditional like {import.meta.env.PROD ? null : <meta name="robots" content="noindex" />} that's inverted.

Vite + plain HTML

Open index.html at the project root. Look for <meta name="robots"> in the <head>. Delete or change to content="index, follow".

v0 / Lovable / Bolt outputs

These platforms inject the tag in a layout component. The location varies by template โ€” search your project for the string "noindex" across all files (most editors have a project-wide find). Delete every match.

After you fix it

Removing the tag isn't enough. You need to actively tell Google to re-crawl:

  1. Add your site to Google Search Console if you haven't
  2. Go to URL Inspection โ†’ enter your homepage URL
  3. Click "Request Indexing"
  4. Repeat for /pricing, /about, /features, and any other key pages

Indexing takes 24-72 hours after the request. You can verify by searching site:yourdomain.com on Google. If pages start showing up, you're good.

What else could be blocking indexing

The noindex tag is the most common cause but not the only one. Other indexing blockers I've seen:

  • robots.txt blocking โ€” Disallow: / in your robots.txt blocks all crawlers
  • X-Robots-Tag HTTP header โ€” some hosts (especially Vercel preview environments) send this header even on production
  • Auth wall โ€” if your homepage redirects to /login, Google can't crawl past it
  • JavaScript-only content โ€” Google can render JS but it's slower and less reliable than server-rendered HTML

RankRadar checks all of these in a single 30-second audit. See a sample report if you want to know what you'd get back.

TL;DR

  • 76% of indie SaaS sites have a noindex tag left in production from staging
  • This tag tells Google to skip your site entirely โ€” no rankings possible
  • Check via Ctrl+U + search "noindex" โ€” 90 seconds, free
  • Fix involves removing one meta tag, then requesting re-indexing in Search Console
  • Indexing returns in 24-72 hours after fix

Run a free audit on your site

Drop your URL into RankRadar. In 30 seconds you'll see your top 3 SEO issues with revenue-loss estimates attached. No signup required for the preview.

โšก Audit my site โ†’