URL marked 'noindex'
This status is not an error
“URL marked ‘noindex'” is one of the “Not indexed” reasons in the Page Indexing report, and means Google tried to index the page, found a noindex directive and stopped. It’s not that Google did something wrong or that your site has a problem; it’s the result of Google following the “don’t index this” instruction the site placed on the page. Google’s official documentation describes this status as: “When Google tried to index the page it encountered a ‘noindex’ directive and therefore did not index it. If you do not want this page indexed, congratulations!” GSC Help Center
A note on naming: this entry’s English heading, “Excluded by noindex tag,” is the name used in older versions of the report; current official documentation and the report use “URL marked ‘noindex’.” Both refer to the same status. GSC Help Center
What is a noindex directive?
Google’s robots meta tag specifications define the noindex rule as an instruction: “Do not show this page, media, or resource in search results.” Google (official) There are two ways to set it. First, you can add a meta tag inside the head of an HTML document.
<meta name="robots" content="noindex">
Second, you can set it with an HTTP response header. The specification says, “Any rule that can be used in a robots meta tag can also be specified as an X-Robots-Tag,” and this method is used for non-HTML files such as PDFs. Google (official)
X-Robots-Tag: noindex
How to tell if it’s a problem: intentional vs. accidental noindex
The judgment is simple. Open the list of URLs with this status and check just one thing: “Is there a page here I want indexed?”
No action needed: intentional noindex
- Login and admin pages, cart and checkout pages
- On-site search results pages, filter and sort parameter pages
- Thin listing pages such as tag archives, thank-you pages after form submission
If pages like these are on the list, noindex is working as intended. Just as Google’s documentation says, “If you do not want this page indexed, congratulations!”, no action is needed. GSC Help Center
Action needed: accidental noindex
The most common mistake is leftover development or staging settings. Ahrefs warns, “It’s good practice to block crawling and indexing of your entire staging environment, but if that setting gets deployed to production and forgotten, organic search traffic plummets.” Ahrefs (measured) A classic example is launching a WordPress site with the “Discourage search engines from indexing this site” option still turned on. If you see pages on the list that should be indexed, check them following the steps in Google’s official documentation.
- In the report, click the inspect icon next to the URL to open the URL Inspection tool.
- Under “Indexing allowed?”, check whether noindex is blocking indexing, and search for noindex in the page source or HTTP response headers.
- Use “Test live URL” to check whether noindex still remains in the current live version.
- Remove the tag or header, then click “Request indexing.” The GSC Help Center documentation states, “If you want this page to be indexed, you should remove the ‘noindex’ directive.” GSC Help Center
The crucial difference between noindex and robots.txt blocking
Many people assume “blocking it with robots.txt has the same effect,” but Google’s official documentation says the opposite. Its introduction to robots.txt states that the file “is used mainly to avoid overloading your site with requests; it is not a mechanism for keeping a web page out of Google.” Google (official) In particular, you must not combine the two methods. Google’s noindex guide warns: “If the page is blocked by a robots.txt file or the crawler can’t access the page, the crawler will never see the noindex rule, and the page can still appear in search results.” Google (official) In other words, if you block crawling, Google can’t read the noindex.
| Aspect | noindex | robots.txt blocking |
|---|---|---|
| What it controls | Indexing (appearing in search results) | Crawling (visiting the page) |
| Crawling | Must be allowed to work | Blocked |
| When Google reads the instruction | After reading the page | Before reading the page |
| Guaranteed removal from search results | Yes (when crawlable) | No: the URL can be indexed from links alone |
The introduction to robots.txt explains, “If other pages point to your page with descriptive text, Google could still index the URL without visiting the page.” Google (official) That’s why the Page Indexing report documentation also says, “If you don’t want Google to index the page, remove the robots.txt block and use a ‘noindex’ directive.” GSC Help Center Ahrefs explains the same principle from a practical angle: “Don’t block crawling of content you want removed from the index in robots.txt, because it prevents search engines from recrawling the page and discovering the noindex directive.” Ahrefs (measured) To sum up: use noindex to keep pages out of search results and robots.txt to reduce server load, and if you use both on the same page, the noindex becomes useless.
References
Jul.2026By Studio JT