WordPress indexing checks including visibility, noindex, canonicals, redirects, and access blocks
Get Found on Google — WordPress Guide

HomeGoogle Indexing ProblemsWordPress Site Not Showing on Google
Quick answer: If a WordPress site is not showing on Google, start with Search Console, then check the Reading visibility setting, SEO-plugin noindex controls, canonicals, redirect variants, staging passwords, security/CDN blocks, and rendered HTML. The visibility setting is one common cause — not the only one — so verify with URL Inspection before assuming.

WordPress gives you many ways to accidentally hide a site from Google — and several plugins that can each set a noindex. Do not guess which one is the culprit. Diagnose in order, starting with Google’s own report.

Check Google Search Console First

Open URL Inspection for the affected URL and read the status against the Google Indexing Fix Series hub. Confirm the current state in Google’s Page indexing status documentation, and inspect the WordPress URL with Google’s URL Inspection tool to see exactly what Google sees — status, canonical, and any noindex.

The WordPress Search Engine Visibility Setting

Under Settings → Reading, the “Discourage search engines from indexing this site” checkbox outputs a site-wide noindex, nofollow directive when enabled. This is a frequent launch or migration issue — especially when a staging site is pushed live with the box still checked.

See the official WordPress Reading settings documentation for the setting location. Uncheck it on production, save, then re-inspect the URL.

This setting is one issue to check, not a diagnosed cause. Confirm with URL Inspection before assuming it is the reason.

Page-Level Noindex Controls

SEO plugins (Yoast, Rank Math, AIOSEO) can set individual posts, pages, categories, tags, authors, dates, and archives to noindex. Google explains how these directives work in Google’s noindex documentation. Check the exact affected URL — not just the homepage.

Categories, Tags, Authors, Dates, and Attachment URLs

WordPress generates many URL types automatically. Some (empty tag archives, attachment pages) should not be indexed, while others may compete with your main article or service page if left unmanaged. Decide which archive types add value and noindex the rest.

URL type Usually index? Note
Posts & pages Yes Your primary content.
Category archives Sometimes Index if curated and useful.
Tag archives Rarely Often thin; noindex unless intentional.
Author/date archives Rarely Noindex on single-author or low-value sites.
Attachment pages No Redirect attachments to the file or parent.

Canonicals and Redirect Variants

Confirm HTTP/HTTPS, www/non-www, trailing-slash, duplicate-slug, and old-URL variants resolve to the preferred URL without avoidable redirect hops. If Google chose a different canonical, follow the canonical troubleshooting guide.

Staging Passwords and HTTP Authentication

After migration, ensure the live site is not behind a staging password, Basic Auth prompt, “coming soon” plugin, or maintenance mode that blocks Googlebot.

CDN, Firewall, and Security-Plugin Blocks

Security tools and CDNs can block Googlebot or serve challenge pages. Verify the public server response and rendered output, not only the WordPress editor.

Rendered HTML and JavaScript Checks

Use URL Inspection’s rendered view and browser testing to confirm Google can see the main content, internal links, canonical tag, and robots directives in the rendered HTML — not just the raw source.

Post-Migration Indexation Checklist

  • Uncheck the Reading visibility “discourage” box on production.
  • Remove staging passwords, Basic Auth, and maintenance mode.
  • Confirm sitemap URLs are canonical and return HTTP 200.
  • Test homepage, key service pages, and important posts in URL Inspection.
  • Check that old URLs 301 to the new structure.
  • Verify no stray page-level noindex remains from staging.

Do not deactivate plugins on a live production site without a backup or staging test. If you suspect a plugin conflict, document current settings and test safely.

For broader on-site improvements, see our WordPress SEO tips, and if the build itself needs work, WordPress development in Atlanta and WordPress design services can rebuild a search-friendly foundation.

Get Your WordPress Site Indexed Correctly

Our team diagnoses the exact WordPress setting, plugin, redirect, or block keeping you out of Google — then fixes it and verifies indexing in Search Console.

Fix My WordPress Indexing

Frequently Asked Questions

Why is my WordPress site not showing on Google?

Common causes include the Reading visibility setting, a plugin-set noindex, canonical or redirect conflicts, staging passwords, security/CDN blocks, or content Google crawled but did not index. Diagnose with URL Inspection.

Can the WordPress visibility setting block indexing?

Yes. When “Discourage search engines” is checked, WordPress outputs a site-wide noindex. Uncheck it on production and re-inspect.

Can Yoast or Rank Math accidentally noindex a page?

Yes. SEO plugins can set noindex on posts, pages, archives, and taxonomies. Check the exact URL’s plugin settings.

Should WordPress category and tag pages be indexed?

Only if they are curated and useful. Thin tag and date archives are usually better left noindexed.

Where is the WordPress XML sitemap?

Typically at /sitemap.xml or /sitemap_index.xml, generated by your SEO plugin. Submit it in Search Console and keep it canonical-only.

How long does Google take to index a WordPress site?

There is no guaranteed timeline; clean access, strong internal links, and quality content speed it up.

How do I know which plugin is adding a noindex tag?

Inspect the page source or URL Inspection for the robots meta tag, then check each SEO plugin’s settings for that URL and its archive type.