How to fix a noindex tag left in production

Before you start

• Access to the site code or CMS settings
• Search Console access

The steps

1. 1

   Step 1: Confirm the problem

   View source on a live page and search for noindex. Check the HTTP headers too — X-Robots-Tag can carry it invisibly.

2. 2

   Step 2: Find the source

   A CMS discourage-search-engines setting, a staging environment variable, a template default, or a plugin.

3. 3

   Step 3: Remove it and deploy

   Then view source on the live URL again. The most common failure is fixing it in source and not deploying.

4. 4

   Step 4: Check the headers

   curl -I the URL and confirm no X-Robots-Tag: noindex is present.

5. 5

   Step 5: Confirm robots.txt allows crawling

   A disallow would prevent the crawler seeing that the noindex is gone.

6. 6

   Step 6: Request indexing

   Search Console → URL Inspection → Request Indexing, for your most important pages.

7. 7

   Step 7: Monitor for two weeks

   Watch the Pages report. Recovery is gradual rather than immediate.

The most common cause

A staging setting carried into production. In WordPress it is a single checkbox in Reading settings; in a build pipeline it is an environment variable. Both are two characters from working and neither produces any visible symptom.

What not to do

Do not also disallow the URL in robots.txt while trying to fix it. The crawler needs to fetch the page to see that the noindex has gone, and blocking that is how a temporary mistake becomes a permanent one.

The background behind this

robots.txt in 2026, including every AI crawler worth naming covers the reasoning in about 3 minutes — free, ungated, written from client work.

Who wrote this

Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada, Ireland and Pakistan. These procedures are the ones I run on client work, written down rather than invented — including the ones where the honest answer is that the fix is not available on your current hosting.