Academy › Publish › Get found on Google

The tag that tells Google to stay out

You find out which of the three blocks is keeping your page out of Google (a noindex tag, a robots.txt rule, or a redirect), check that it wasn't set on purpose, know how to remove it or who to ask, and ask Google to take another look.

By Yodai · Published September 6, 2026 · Updated October 13, 2026

In Search Console's page indexing report, your page shows up as not indexed for one of these reasons: a noindex tag, a robots.txt block, or a page with redirect. You read that and you're still stuck: you don't know what it means, where it's hiding, or whether you can fix it yourself or need to call someone.

The reason has a technical name, but the block itself is one specific line, written into the page's code, in a separate file, or in the server's settings. Today you'll track it down and learn how to remove it or who to ask.

Three places where the block can live

Google can leave a page out for other reasons too, like a 404 error or a page that requires logging in, but these three reasons point to three spots where it runs into a 'do not enter' sign. One lives with the page itself: in its code or in the server's response. Another sits in a separate file that lives at the root of your domain. The third is a redirect that sends Google somewhere else, so this page never gets indexed.

Each one is found and fixed in a different way. Mixing them up wastes days.

The tag that stays on after you publish

The noindex tag asks Google to keep that page out of its results. It can be added to a new site so it doesn't get indexed too soon. While you're building, it's useful. The problem starts when you publish the site and that tag stays in place, because publishing changes how the page looks but doesn't always remove the tag. That's why Google reminds you that if you added it to a new site for that purpose, don't forget to take it back off.

It shows up in the source code, not in what the browser displays. Right-click, choose View Page Source, and search for the word noindex. If it appears in a meta tag with name="robots" or name="googlebot", that's your block. If it doesn't show up there, it might be in the server's response, in a header called X-Robots-Tag that you can't see in the code: Google's documentation allows for both. Search Console's URL Inspection tool tells you whether Google is picking up the noindex.

Before you remove it, check that it wasn't put there on purpose: Search Console's help page notes that a noindex tag can be a valid reason to keep a page out of search results. And if your site is on your platform's free address (a subdomain), chances are that noindex tag, or a rule in robots.txt, was set up on purpose so Google only sees your homepage: it's usually removed once you connect your own domain, so ask about that before requesting a change. If it looks like a mistake and another tool built your site, look for a search engine setting in it. If a developer built it, or the noindex is in the header set by your hosting provider's server, you'll need to ask whoever manages that to change it.

Robots.txt and the redirect, the quick check

With the robots.txt file, there's nothing hidden to hunt for: it has to live at the root of your domain, so you type yourdomain.com/robots.txt into your browser's address bar and read the whole thing. It's a plain text file, one rule per line, grouped under a User-agent line that says which crawler each rule applies to. If under User-agent: *, which applies to every crawler, you see a plain Disallow: /, that file blocks the entire site, not just one page. If you see Disallow: /services/, the block only covers that folder. Anyone can read the file; changing it is a different story: if another tool built your site, it might not let you edit it directly and may have its own search engine setting instead, and if a developer built it, you'll need to ask them to make the change.

You test the redirect by opening the exact URL Search Console flags. If pasting it lands you on the new address for that same page, there's nothing to fix: according to Search Console's help page, the redirecting address doesn't get indexed, but the destination address can be. If you land on the homepage or on some other, unrelated page, that's where the problem is: someone set up all the old pages to redirect to the same place, and swept away a page you actually wanted to keep.

Asking Google to take another look

Removing the block doesn't get the page into the search engine that same day. Google has to crawl it again, and depending on how important the page is, that can take months to happen on its own. In Search Console, under URL Inspection, paste the exact address of the fixed page, click Test Live URL to confirm Google now sees it without the block, and if it does, click Request Indexing.

That asks Google to come back sooner, with no guarantees: Google notes that crawling can take anywhere from a few days to a few weeks, that requesting it doesn't guarantee the page will show up in results, and that asking more than once won't speed things up. It doesn't replace the earlier fix: first you remove the block, then you ask Google to take another look.

With the tag, the robots.txt, and the redirect all fixed, Google can now get in. But being able to get in doesn't mean it knows what's there: you tell it that with the sitemap, which helps Google discover your site's URLs, and it's worth checking that yours tells the truth about what actually exists.

In Yodai every site goes live with its padlock, its sitemap and its titles, with nothing to buy or set up. See what the hosting included with your website covers.