How to Fix “Excluded by ‘noindex’ Tag” in Google Search Console

Quick Answer

“Excluded by ‘noindex’ tag” means Google found an instruction telling it not to index the affected URL. If the page should appear in search results, remove the unintended instruction from its HTML robots tag or HTTP response header, then test the live URL in Google Search Console and request indexing. If the exclusion is intentional, leave it in place. :chatgpt-content-reference{index="0"}

Removing the instruction makes the page eligible for indexing; it does not guarantee inclusion or a particular ranking. Google must revisit and process the updated page. :chatgpt-content-reference{index="1"}

What the Notification Means

The notification identifies an indexing restriction on specific URLs. It does not, by itself, establish that your entire website is excluded or that Google has imposed a penalty. Open the affected-page report to determine the scope.

Google can receive a noindex instruction through either of these mechanisms:

• HTML robots tag: An instruction included in the page’s HTML.
• X-Robots-Tag: An HTTP response header sent with the page or file. This can also affect PDFs and other non-HTML resources.

A page can load normally in your browser while its indexing instruction prevents it from appearing in Google Search. :chatgpt-content-reference{index="2"}

1. Decide Whether the Page Should Be Indexed

Review the affected URLs before changing settings. Use their purpose to decide what action is appropriate.

2. Inspect an Affected URL

1. Open Google Search Console and select the correct website property.
2. Open the Page indexing report and select the noindex-related reason. Wording can vary, including “Excluded by ‘noindex’ tag” or “URL marked ‘noindex’.”
3. Select an example URL and open URL Inspection.
4. Record the last crawl date and reported indexing restriction.
5. Select Test live URL to check the currently published version.

The initial inspection reflects Google’s stored information. A live test helps establish whether the restriction still exists after a recent change. :chatgpt-content-reference{index="3"}

3. Find the Source of the Instruction

Check the HTML

Open the affected page while logged out and use your browser’s page-source viewer. Search for robots-related tags containing noindex or none. The following are examples of blocking instructions, not code to add:

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

The value none means noindex and nofollow. Inspect all applicable tags: adding an index instruction elsewhere does not cancel an existing noindex restriction. Google applies the more restrictive applicable rule. :chatgpt-content-reference{index="4"}

Check the HTTP Response Headers

In your browser’s developer tools, open the Network panel, reload the page, select the main document request, and inspect its response headers. Look for an instruction such as:

X-Robots-Tag: noindex

A Google-specific header can also block indexing:

X-Robots-Tag: googlebot: noindex

Removing an HTML tag will not resolve a separate header restriction. Check the final destination if the URL redirects. :chatgpt-content-reference{index="5"}

Use the Pattern to Narrow Your Investigation

The following patterns are diagnostic clues, not proof of a particular cause:

4. Remove the Unintended Restriction

Record the original setting and back up any configuration file before editing it. Make the smallest change needed for the affected public pages.

For WordPress Websites

1. Sign in with an account permitted to manage site settings.
2. Open Settings → Reading.
3. Under Search Engine Visibility, check whether Discourage search engines from indexing this site is selected.
4. If this is a public production website intended for search discovery, clear the checkbox and save changes.

This WordPress setting can generate a noindex instruction. After changing it, recheck the delivered page rather than assuming every indexing restriction has disappeared. :chatgpt-content-reference{index="6"}

If the problem remains, inspect the affected page’s SEO plugin settings and any content-type defaults. Labels differ between plugins; consult the installed plugin’s documentation before changing unfamiliar options.

For Other Content Management Systems

Check both site-wide and page-specific search visibility controls. Google notes that content management systems may manage robots tags through settings rather than direct HTML editing. Save and publish the change, then inspect the public output. :chatgpt-content-reference{index="7"}

For Custom Websites or Header-Based Restrictions

Have the developer or hosting administrator locate the rule generating the restriction. Possible places to investigate include page templates, application middleware, server configuration, and content delivery network response-header rules.

Remove the unintended noindex value for the relevant pages while preserving unrelated directives. Avoid changing every page’s policy simply because one public article is affected.

For JavaScript-Rendered Websites

Compare the initial HTML with the rendered page. Do not serve noindex in the initial response and rely on JavaScript to remove it later: Google may skip rendering when it encounters that instruction. Correct the initial output and check that application scripts do not reintroduce the restriction. :chatgpt-content-reference{index="8"}

If your site caches pages or response headers, refresh the relevant cached output after publishing. Retest while logged out.

5. Verify the Fix and Request Indexing

Run another live URL inspection. For a public page intended for indexing, check these results together:

• Crawl allowed? Yes.
• Page fetch: Successful.
• Indexing allowed? Yes.

Do not rely on “Indexing allowed?” alone when crawling is blocked: Google cannot read the page’s indexing instructions in that situation. A successful live test also does not evaluate every reason Google might exclude a page. :chatgpt-content-reference{index="9"}

After the live restriction is resolved, select Request indexing for important individual URLs. This requires owner or full-user access to the Search Console property. For many updated URLs, submit an updated sitemap. Repeated requests for the same URL do not accelerate crawling. Google advises that crawling can take days to weeks. :chatgpt-content-reference{index="10"}

If the issue report offers Validate fix, use it after addressing the unintended restrictions covered by that issue. Validation checks the reported problem; it does not guarantee indexing. Intentionally excluded pages do not need to be made indexable merely to clear the report. :chatgpt-content-reference{index="11"}

If the Page Still Does Not Appear

• Noindex remains in the live test: Recheck both HTML and response headers, including duplicate rules and cached responses.
• The live test passes but the stored report still shows noindex: Compare the last crawl date with your change date.
• The reported reason changes: Investigate the new reason, such as a fetch failure or duplicate-page status.

After Google recrawls the URL, inspect its stored indexing status and selected canonical URL—the version Google treats as the main page. Removing noindex resolves that restriction, but Google may still choose another canonical or decide not to index the content. :chatgpt-content-reference{index="12"}

Rollback and Prevention

If a change affects the wrong pages, restore the recorded setting or backed-up configuration, refresh relevant caches, and retest representative URLs. Restoring a directive does not immediately reverse changes already processed by Google.

For future releases, check one public article, one page from each major template, and one intentionally excluded page. Keep production and staging visibility settings separate, and include robots tags and response headers in deployment checks.

Frequently Asked Questions

Should I block the page in robots.txt to fix this?

No. A robots.txt block prevents crawling and may stop Google from seeing the corrected indexing instruction. Google does not support a noindex rule placed in robots.txt. :chatgpt-content-reference{index="13"}

Does nofollow cause the same exclusion?

No. Nofollow concerns following links; noindex concerns including the page in search results. However, the robots value none includes both instructions. :chatgpt-content-reference{index="14"}

Can adding the URL to a sitemap override noindex?

No. A sitemap helps Google discover URLs. Remove the unintended indexing restriction before requesting that the page be reconsidered. :chatgpt-content-reference{index="15"}

Sources

• Google Search Console Help — Page indexing report
• Google Search Central — Block Search indexing with noindex
• Google Search Central — Robots meta tag and X-Robots-Tag specifications
• Google Search Console Help — URL Inspection tool
• Google Search Central — Ask Google to recrawl your URLs
• Google Search Central — JavaScript SEO basics
• WordPress Documentation — Settings Reading screen