How to check if a page is no index?

20 June 2026 · By John Carlsson

View the page's source and look in the head section for a robots meta tag containing noindex. Also check the HTTP response headers for an X-Robots-Tag with noindex, because that does not appear in the page's HTML. Browser developer tools show both, and Google's URL Inspection tool reports it too.

To check whether a page is no index (that is, whether it has a noindex directive), view the page's source code and search for a robots meta tag in the head section — look for a meta tag with content='noindex'. Also check the HTTP response headers, as noindex can be delivered there via the X-Robots-Tag header rather than in HTML. Browser developer tools allow you to inspect both. An online noindex checker tool analyses HTML source and HTTP headers simultaneously.

Checking if a page is no index: where noindex directives can hide

Noindex directives can live in two places, and when checking if a page is no index, looking at only one while missing the other is a common mistake. The first is the HTML <head> section: a meta tag like <meta name='robots' content='noindex'> or similar tells crawlers not to index the page.

The second is the HTTP response header: a server can send an X-Robots-Tag header with a noindex value, which has the same effect but isn't visible in the page's HTML source at all — it requires inspecting the HTTP headers, which means using developer tools or a dedicated checker. Both are equally respected by Google.

How noindex tags end up on pages accidentally

The most common cause of accidental noindex tags is CMS or theme settings. Many content management systems include a checkbox or setting to 'noindex' a page, and these are sometimes applied by default to category pages, tag pages, paginated pages, or search result pages. When a developer migrates a site or switches themes, they sometimes forget to transfer these settings correctly, accidentally leaving noindex on pages that should be indexable. A full site crawl that reports the noindex status of every URL is the most reliable way to audit for accidental noindex at scale.

Should you ever intentionally noindex pages?

Yes — noindex is a legitimate and useful directive for pages that genuinely shouldn't appear in search results. Common intentional uses: internal search result pages (e.g. site.com/search?q=...), paginated versions of long archives, thank-you and confirmation pages, login or account management pages, and any pages that contain content you don't want publicly searchable. The key discipline is being intentional about which pages carry noindex directives, auditing for them regularly to confirm they're still correctly applied, and ensuring no pages are accidentally noindexed that should be visible in search.

Key Takeaways

Noindex can appear in HTML meta tags OR in HTTP response headers — check both locations.
Accidental noindex from CMS settings is common after redesigns or theme switches.
Intentional noindex is valid for search pages, confirmation pages, and account areas.

Frequently asked questions

Where should I look to check if a page is no index?

A noindex directive can live in two places, and checking only one is a common mistake. The first is the HTML head section, where a robots meta tag with a noindex value tells crawlers not to index the page. The second is the HTTP response header, where a server can send an X-Robots-Tag header with a noindex value. That header has the same effect but is not visible in the page's HTML source at all, so you need browser developer tools or a dedicated checker to see it. Google respects both locations equally, so both should always be checked.

How do noindex tags end up on pages by accident?

The most common cause of accidental noindex tags is content management system or theme settings. Many CMS platforms include a checkbox or setting to noindex a page, and these are sometimes applied by default to category pages, tag pages, paginated pages or search result pages. When a developer migrates a site or switches themes, these settings are sometimes not transferred correctly, leaving noindex on pages that should be indexable. A full site crawl that reports the noindex status of every URL is the most reliable way to audit a site for accidental noindex directives at scale.

Which pages should be set to noindex?

Noindex is a legitimate and useful directive for pages that genuinely should not appear in search results. Common intentional uses include internal search result pages, paginated versions of long archives, thank-you and confirmation pages, login or account management pages, and any pages containing content you do not want to be publicly searchable. The key discipline is being deliberate about which pages carry noindex, auditing for it regularly to confirm it is still applied correctly, and making sure no pages that should be visible in search have been noindexed by mistake.