Page is indexable

A googlebot-specific noindex was the old trick to hide AdWords landing pages from organic search. It now removes the page from Google entirely — so it earns no organic traffic at all, regardless of how well its tracking is configured.

Why this matters

How this tool detects it

The tool checks two kinds of noindex directive, and they are judged differently: one applied to every crawler (name="robots"), and one applied only to googlebot. The googlebot-only version is the older trick for hiding AdWords landing pages from organic results.

The googlebot variant is treated as a failure — it removes the page from Google Search entirely while still letting paid crawlers through, which is the worst of both outcomes. A plain robots noindex is reported as a warning, because it is normal practice on privacy and legal pages.

Either way, if the page is one you want in search, the directive has to go. Nothing about your tracking configuration matters if the page never receives organic traffic.

Where this check can mislead you

Static analysis has limits. These are the cases where this particular check will report a result that does not match reality — worth knowing before you act on it.

Only page-level meta tags are checked. A noindex set through robots.txt or an HTTP header (X-Robots-Tag) is outside the scope of this tool — confirm those with a different tool.
Incorrect canonical targets are not checked. A canonical pointing at a different URL produces the same deindexed result, and this tool will not see it.
Intent cannot be determined. A noindex on a privacy or legal page is normal practice. The tool flags it either way and cannot read intent.
JavaScript-injected meta is not checked. A robots meta inserted by a script is invisible in static source.

Examples

WrongWrong: an AdWords-era googlebot noindex left behind

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

The trick stopped working long ago. Now it only removes the page from the index entirely while still letting paid crawlers through — the worst of both outcomes.

WrongSubtle case: set by an SEO plugin default, not by hand

<!-- emitted by an SEO plugin or page builder, nobody typed this -->
<meta name="robots" content="noindex, follow">

Several plugins ship with search visibility set to discouragement, and owners rarely know it. The page loads, tracking works, it simply never appears in search results.

How to fix it

Search for googlebot and noindex, and confirm each hit is deliberate.
Work out where the directive comes from — a theme template, the page builder, or a plugin. WordPress SEO plugins commonly ship a "search engine visibility" toggle that defaults to discourage.
If the page is meant to be indexed, remove the directive.
Request re-indexing for the URL in Google Search Console.
While you are there, check robots.txt for over-broad Disallow: rules — they do not deindex a page, but they do block crawling, which has a similar effect.

Verify it worked

After making changes, confirm delivery rather than assuming. These steps require your Google login, which is exactly why this tool stops short of them.

Test the URL in Search Console URL Inspection and look at the noindex state Google actually sees, plus its source.
Open /robots.txt directly and confirm the Disallow rules are not too broad — Disallow: / blocks crawling of the entire site.
Check the HTTP response header for X-Robots-Tag: curl -I https://yourdomain.com/page
In WordPress, check the SEO → Search Engine Visibility setting, and look for a second setting in the theme template or page builder.

Related checks

One thing static analysis cannot tell you: this page reads published code, so it shows what is installed, never what actually fires. To confirm delivery, use GTM Preview and GA4 DebugView — both require your Google login.

Check whether your site has this problem — no login required.