Live site missing from Google? Look for a stray noindex

Your site has been live for weeks. It loads fine, friends can sign up, and yet searching for its name on Google shows nothing, or only an old preview URL. One common cause is a leftover "don't index me" signal. Humans never see it, so the site looks healthy while search engines are told to stay away.

Why it happens

There are three ways a site can ask search engines to keep out, and AI builders and hosts can leave any of them behind:

  • A robots meta tag in the page head: <meta name="robots" content="noindex">. Builders and templates sometimes add it while a project is a draft, and nobody removes it at launch.
  • An X-Robots-Tag: noindex response header. Vercel and Cloudflare Pages add this to preview deployments on purpose. That's correct for previews, but if the URL you share or submit is a preview URL, Google will never index it.
  • A robots.txt rule such as Disallow: /. This blocks crawling rather than indexing, but the effect is similar: Google can't read your pages, and it can't see that you removed a noindex either.

There's one more trap on single-page sites. If the first HTML your server sends contains noindex, Google may skip rendering the page, so JavaScript that removes the tag later never gets a chance to run.

Step-by-step diagnosis

  1. Use your real domain. Check the exact URL people should find, such as https://yourdomain.com, not a .lovable.app, .vercel.app, .pages.dev or .replit.app address.
  2. Read the raw HTML. Run curl -s https://yourdomain.com | grep -i robots, or open View Source (not DevTools, which shows the page after JavaScript ran). Look for noindex or none.
  3. Read the headers. Run curl -sI https://yourdomain.com | grep -i x-robots. Any noindex here overrides a clean page.
  4. Read robots.txt. Open https://yourdomain.com/robots.txt. Disallow: / under User-agent: * blocks everything.
  5. Ask Google. In Google Search Console, use URL Inspection on your homepage. "Excluded by 'noindex' tag" or "Blocked by robots.txt" confirms it. While you're there, check the canonical URL Google chose. If it points at a preview domain, fix that too.
  6. Repeat on one inner page, such as /pricing. Some setups only add the tag to certain routes.

Fixes per builder and host

Lovable

Look in index.html and in any SEO or head component for a robots meta tag. Ask Lovable: "Remove any noindex robots meta tag from the production site and show me the diff." Make sure your custom domain is connected and is the URL you share.

Bolt

Check index.html and public/robots.txt. If you deploy to Netlify, also check netlify.toml and any _headers file for X-Robots-Tag.

Replit

Share and submit your deployed domain, not the workspace dev URL. If an Express server sets headers, search the code for X-Robots-Tag.

v0 and Next.js

Look for robots: { index: false } in the metadata export of app/layout.tsx or a page, and check app/robots.ts. On Vercel, make sure your custom domain points at the production deployment. Previews are meant to be noindexed.

Cursor

Ask Cursor to "search the repo for noindex, nofollow, X-Robots-Tag and Disallow", then review each hit before changing it.

Netlify, Vercel and Cloudflare Pages

Check _headers, netlify.toml or vercel.json for a header rule. On Cloudflare Pages and Vercel, confirm that your custom domain serves the production branch, not a preview.

How to verify

  • Redeploy, then repeat the three curl checks on the homepage and one inner page. All three should be clean.
  • In Search Console, run URL Inspection again and click "Test live URL". When it reports that the page can be indexed, click "Request indexing".
  • Submit your sitemap if you have one. Expect indexing to take days, not minutes.

Keep it from coming back

  • Add "no noindex on the live domain" to your launch and redeploy checklist.
  • If you want previews hidden, rely on the host's preview header rather than a tag in your code that can leak into production.
  • Keep robots.txt short. Block only private paths, never /.
  • Recheck after big builder changes or template swaps, since head tags can be regenerated.
A site can be fast, working and useful and still be invisible in search because of one line in the head.

FlowCanary's free check looks at your live site the way Google sees it, including robots tags, headers and robots.txt, and gives you a copy-paste fix prompt for anything it finds.

Run the free 30-second check

Run the free 30-second check

← All posts

FlowCanary on SaaSHub