WordPress Is Blocking Google (Noindex / Discourage Search Engines)

Your WordPress site is telling Google to stay away — usually through the "Discourage search engines" checkbox, an SEO plugin noindex setting, or a robots.txt rule left over from building or staging the site.

Common signs of this issue

• Search Console shows pages as "Excluded by 'noindex' tag" or "Blocked by robots.txt".
• Your WordPress dashboard's At a Glance box says "Search engine discouraged".
• Searching site:yourdomain.com shows nothing, or only a handful of old pages.
• The site recently launched, was redesigned, or was moved from a staging or development copy.
• Only certain pages or post types are missing from Google, such as all your services pages or all your products.
• Google shows your page with the note "No information is available for this page".

Safe checks you can do yourself

None of these require sharing passwords with anyone.

• In WordPress, go to Settings, then Reading, and look at Search engine visibility. If "Discourage search engines from indexing this site" is ticked, that is almost certainly your problem. Untick it and save. This is the classic launch-day oversight.
• View the source of any page (right-click, View page source) and search for noindex. A line like meta name='robots' content='noindex means the page is asking Google to leave it out.
• Open your SEO plugin's settings. In Yoast, check the content-type settings that control whether posts and pages show in search results, plus the Advanced tab on individual pages. In Rank Math or All in One SEO, look for global and per-page robots settings set to No Index.
• Visit yourdomain.com/robots.txt in a browser. A line reading Disallow: / under User-agent: * blocks every well-behaved search engine from crawling the whole site.
• Check whether you are looking at the real site. Staging copies on hosts like WP Engine, Kinsta, or SiteGround are deliberately set to noindex — if the live site was created by copying staging, that setting may have come along with it.
• Look for coming-soon, maintenance-mode, or membership plugins that hide the site from logged-out visitors. Google sees what a logged-out visitor sees.
• In Search Console, use URL Inspection and Test live URL on your homepage. It reports in plain words whether indexing is allowed and whether robots.txt blocks the page.
• Once fixed, request indexing for your homepage and a few key pages, and resubmit your sitemap. Then allow days to a few weeks for pages to return.

What this usually means

Websites have two separate ways to keep Google out. A noindex instruction lets Google visit a page but tells it not to list it. A robots.txt block tells Google not to visit at all. WordPress's "Discourage search engines" checkbox, in current versions, adds a noindex instruction to every page — so one tick in one box can quietly remove an entire site from Google.

The usual story is innocent: a developer switched it on while building the site, or an SEO plugin was configured to noindex a content type, or the live site was cloned from a staging copy that was supposed to stay hidden. Nobody notices because the site works perfectly for visitors. The only symptom is silence from Google, often for weeks.

Worth knowing: the two methods can fight each other. If robots.txt blocks a page, Google cannot read its noindex tag, and it may still list the bare address with no description. If you are trying to remove a page, allow crawling and use noindex. If you are trying to get indexed, you need both out of the way.

What not to do

• Don't install a second SEO plugin to fix settings in the first one. Two plugins fighting over robots settings is itself a common cause of accidental noindex.
• Don't edit robots.txt on the server by guesswork. One wrong line can block the whole site, and some plugins generate this file for you.
• Don't turn off the noindex on your staging site to make it match live. The staging copy should stay hidden, or Google may index a duplicate of your business.
• Don't expect pages to reappear the same day. Google has to recrawl each page and see the new instruction, which takes time.
• Don't assume the problem is fixed because the checkbox is unticked. Caching plugins and CDNs can keep serving the old noindex version until the cache is cleared.

When to get help

If the checkbox is already unticked, your SEO plugin looks correct, and Search Console still says noindex, it is worth bringing in someone who can check the parts you cannot easily see: headers sent by the server or CDN, a theme or custom code adding its own robots tags, or a host-level setting carried over from staging. Help is also sensible after a site move or redesign that dropped your traffic sharply, because a noindex left on is only one of several launch mistakes that tend to travel together, and a quick audit catches the rest before they cost more weeks of visibility.

Frequently asked questions

Related free guides