Google can find your WordPress page and still leave it out of search results. The cause usually falls into one of five common issues, including site settings that block indexing and content Google considers too similar to existing pages.
These indexing problems are usually fixable, and a WordPress page not indexed by Google rarely signals a penalty. At Fiddlers Convention, we trace most Google indexing problems back to the same few plugin settings, server rules, and thin pages.
In this guide, we cover five WordPress settings that block indexing and the Search Console indexing statuses that point to each one. We also show which thin pages Google drops and the order to fix everything this week. Each step below names the exact menu or file to open.
Why Does Google Crawl a WordPress Page but Leave It Out of the Index?
Google crawls and indexes in two separate steps, so a Googlebot visit never guarantees a spot in search results. First, search engine crawlers fetch your page and read its code. A second process then decides whether to store the page in Google’s index.
Most Google indexing problems on WordPress sites start at that second step. A noindex tag tells Google to drop the URL, and Google follows the directive. A canonical tag pointing elsewhere acts as a strong hint, so Google stores the other URL in your page’s place. Robots.txt rules work one step earlier, because they stop the crawl itself.
A page that clears all those settings still faces a quality review. Google weighs whether the page adds anything new before giving it a slot.
Google records which check a page failed, and the Page Indexing Report in Search Console shows the matching label. A settings problem usually takes one cleared checkbox to solve, while a quality problem means improving the content.
We start every audit by placing the page in the settings group or the content group. Sorting first keeps you from rewriting a page whose content was never the issue.
Noindex Signals: The WordPress Settings That Tell Search Engines to Skip Your Pages
Noindex signals are instructions in your page code or server response that ask search engines to drop a URL from their results. WordPress core, SEO plugins, hosting setups, and a post’s own visibility status can all send that signal. Below are the five places to look, in the order we check them on client sites.
The “Discourage Search Engines from Indexing” Box in Reading Settings
WordPress core has one checkbox that can cut your site’s visibility across every page. You’ll find it under Settings, then Reading, next to the label Search engine visibility.
The WordPress documentation on Reading Settings explains that checking Discourage search engines from indexing this site asks search engines to stay away. The same page notes that each search engine decides whether to honor the request. Developers often check the box during a build and forget to clear it before launch.
Log in to your WordPress admin and clear the box to allow search engines back in. Click Save Changes so the new setting goes live. Then open Google Search Console and request indexing for your homepage so Google rechecks the site sooner.
SEO Plugins Can Set Noindex on the Page or Its Post Type
An SEO plugin can set a page to noindex from a tab most owners never open. The Yoast SEO plugin and Rank Math SEO both add a robots meta tag to any page you mark. Some setups also add a nofollow tag beside the noindex rule.
Both plugins can apply the same rule to whole post types and taxonomies. A single post-type setting can hide every product, category, or tag archive on the site. A coming-soon or maintenance WordPress plugin can add the same tag site-wide.
Check the Advanced tab in the page’s plugin panel first, then the plugin’s content-type settings. After saving any change, open the page source and search for “noindex.” If the word still appears, clear your site and server cache, then check the source again. A noindex sent in the HTTP header won’t show in the source, so run the URL Inspection tool if the source looks clean.
A Robots.txt Disallow Rule Left Over from Staging or Site Migration
Your robots.txt file controls crawling by telling search engines which paths they may visit. A leftover “Disallow: /” line from staging can block your entire website after a site migration.
Robots.txt blocking works differently from noindex. Google can’t crawl a blocked page, so its content can’t be indexed, and any noindex tag on it goes unread. Blocked URLs can still appear in Google Search without a description, since Google may index the address from links alone.
To check, load yourdomain.com/robots.txt in a browser and delete any rule covering pages you want indexed. WordPress serves a virtual version by default. A physical robots.txt file on your server replaces that version, and some SEO plugins let you edit the rules directly. If a deleted rule keeps coming back, ask your hosting support whether a server setting restores it.
Password Protection and Private Status Keep the Page Out of Search
Many owners preview a private page while logged in and assume everyone can see it. Googlebot never logs in, so it gets a password form on protected pages and a 404 error on private ones. Search engines index only what a logged-out visitor can reach on your WordPress site.
Password protection, membership plugins, and LearnDash course settings all lock pages from Google’s crawler. To fix a core setting, open the post editor and check Visibility in the Status panel. Switch Visibility to Public once the page is ready for visitors. For pages locked by a membership plugin, change the plugin’s access rule, because WordPress visibility settings don’t control those restrictions.
A Canonical Tag That Points Google to a Different URL
A canonical tag tells Google which URL holds the main copy of a page. When the tag points to a different address, Google will index that URL in most cases and treat yours as a duplicate.
Duplicator plugins can copy the original page’s custom canonical, and a permalink change can leave a manual canonical on the old address. Search Console then lists your URL under Alternate page with the proper canonical tag.
Open the canonical field in your SEO plugin for that URL and point it at the page’s own address. Leave the field blank if you want the plugin to set a self-referencing canonical automatically. Self-referencing canonical tags are the safe default for any page you want in search results. Keep a cross-page canonical only if you want Google to merge the two pages.
How to Read Search Console Indexing Statuses
The Page indexing report in Search Console confirms which of those five settings affects your page. The report also groups every excluded URL under a named reason, including pages no setting explains.
The table below matches four common labels to the action each one needs.
| Status | What It Means | What to Do |
|---|---|---|
| Excluded by noindex tag | A meta tag or header blocks indexing | Clear the plugin or Reading setting |
| Blocked by robots.txt | Google can’t fetch the page at all | Remove the disallow rule |
| Alternate page with the proper canonical tag | Google chose a different URL | Fix the canonical or accept the merge |
| Crawled – currently not indexed | Google fetched the page and passed on it | Improve the content, then request indexing |
Google’s Page indexing report help page says pages with that last status were crawled but not stored, and they may still get indexed later. No setting causes the crawled, currently not indexed status, so upgrade the content before you request indexing again. Resubmitting an unchanged URL rarely helps.
For the other three rows, run the URL Inspection tool on one affected URL before changing anything. The live test shows whether Google still sees the noindex tag, the robots.txt block, or the wrong canonical.
Once your fix is live, click Validate Fix so Google rechecks every URL in that group. Validation can take two weeks or longer, so review your Search Console indexing data weekly.
Duplicate Content Issues: Why Google Skips Thin Pages Without a Noindex Tag
After your settings check out, a crawled but not indexed page most likely has a content problem. Google stores web pages that add something new and drops pages that repeat what its index already holds. Thin pages say too little, while duplicate content repeats what another URL already says.
WordPress creates many thin URLs by default. Tag archives, author pages, and paginated category views all show the same post snippets. Pages drafted in bulk with AI tools add to the problem when they repeat advice already published on many other sites.
Five page types deserve the first look during a content review:
- Attachment Pages: Older WordPress installs create a separate page for every uploaded image. Each page shows one image and almost no text, so Google rarely stores it. Turn attachment pages off in your SEO plugin, or redirect them to the parent post.
- Thin Tag Archives: Merge small tags into broader ones, or set near-empty archives to noindex in your plugin. A tag that holds one or two posts creates an archive with almost no unique text.
- Near-Identical WooCommerce Products: Many stores copy one manufacturer description across products that differ only by size or color. Google sees the copied pages as repeats and picks one to store. Write at least one unique paragraph per product, or combine small differences into a single variable product.
- City-Swap Location Pages: A site that publishes one page per city with only the place name changed gives search engines near-identical text. Add real local details, like project photos, staff or service areas, or merge the pages into one.
- Overlapping Old Posts: Two posts that answer the same question compete for one spot in the index. Google will keep one and leave the other out. Merge the older post into the newer one, then add a 301 redirect from the old URL.
Rewrite, merge, or noindex each weak page so your page indexing numbers reflect URLs worth ranking. Begin with pages that once earned organic traffic, since they have the most to win back. For search engine optimization, a smaller set of detailed pages beats a pile of near-duplicates.
Get Your WordPress Page Back in Google’s Index This Week
So start with the quick settings checks: the Reading box, your SEO plugin, and robots.txt. They take about 15 minutes in total. Then confirm each page is public and carries a self-referencing canonical tag.
Then open the Page indexing report. Any WordPress page not indexed at that point goes on your content rewrite list. Request indexing for each fixed URL, and recheck the report weekly as Google recrawls your site.
Fiddlers Convention offers technical SEO and content support for WordPress website owners whose pages keep dropping out of search results. Contact Fiddlers Convention to book a site indexing review and get a clear fix list for each excluded page.