Why is Google excluding my published WordPress page from indexing?
Open the final page signed out, then inspect its HTTP status, robots meta tag, and X-Robots-Tag header. Check WordPress Settings → Reading and any settings for the affected content type. Remove only the unintended instruction and verify that exact URL again in Search Console.
What does the problem look like?
The page is published but absent from Google, or URL Inspection reports noindex. The exclusion may affect a whole site, archive type, or single page.
Before you make changes
Confirm which URL should be public and which environments should remain protected. Record the original settings and confirm access to WordPress, hosting, and the relevant Search Console property.
Step-by-step troubleshooting
Start with the public destination
Follow the URL to its final address. Record HTTP status and the canonical declared by the final page.
Inspect both instruction locations
Read the HTML and the document response headers. Record the exact source of a noindex signal and the observed time.
Identify the responsible configuration
Compare Settings → Reading, any per-page or content-type controls, and host or CDN header rules. Change one confirmed cause at a time.
Retest representative URLs
Verify the affected URL and a second page with the same intended rule. Check that restricted staging and private content still require authorization.
Use URL Inspection
Compare the current live result with Google’s previously processed information. Keep change and inspection dates to avoid mixing snapshots.
Worked example
A community organization moves a staging build into production. Its event pages and homepage both contain noindex. The editor updates the intended public site’s Reading setting, retests both page types, and confirms the staging host still requires login.
Common mistakes
- Using a Sitemap success report as proof of eligibility for individual URLs.
- Changing global visibility to solve a single content-type setting.
- Waiting for a search result before confirming the actual response changed.
Verify the fix and plan a rollback
How to verify the fix
Verify that the intended public URL now serves the expected document and headers. A current live test and a later index report answer different questions. Record both.
If the change fails
Restore the former control if content was made public accidentally. Use your existing access restrictions for confidential pages and coordinate further actions with the site owner.
Practical follow-up questions
Can Google find a sitemap URL and still exclude it?
Yes. A sitemap lists addresses for discovery. Check the status and index instructions of each representative destination to understand whether it is eligible.
How do I inspect a PDF or another file with no HTML head?
Check the final file request in your browser’s Network panel. Read X-Robots-Tag on the response. Verify that you selected the file rather than its linking page.
What does it mean if only author archives show noindex?
Compare an archive and a published page. Inspect the settings for that exact content type. An intentional archive policy can coexist with indexable posts.
How do I verify that the current page is the one Google has in mind?
Look at the final HTTP URL, the declared canonical and the inspected address. If the indexed report is available, compare Google’s selected canonical with your own.
Can a crawl block hide an indexing instruction?
A crawler unable to fetch a page may not see its meta tag or response header. Inspect crawl permission and indexing instructions as distinct signals.
Why does Search Console still show yesterday’s exclusion after I fix it?
Compare the recorded crawl date with the change time. Use a live check to validate the current response, then review the processed result later.
Should I lift an exclusion on every staging copy?
Keep project staging access-controlled. Verify production on its own hostname. A configuration imported from staging needs a separate production check.
How can I make a repeatable check for a post and an archive?
Record one exact URL for each intended rule, the final status, canonical and robots signals. Retest the same set after the targeted change.
What if a live test succeeds but the page remains absent in Search?
Check the index report’s reason, any canonical choice and the page’s internal discovery links. Record what is verified and what remains pending.
What documentation should I give a colleague after the fix?
Record public URL, observed directive location, scoped change, timestamps and follow-up inspection result. Keep private account details out of screenshots.
Free tools and website checks
- Redirect checker (German)
Inspect status codes and targets for a publicly reachable URL.
- Launch checklist (German)
Record manual release checks and export the remaining tasks.
Frequently asked questions
Does WordPress search visibility make my site private?
Use authentication or another access control to hide content. Search visibility settings communicate crawler instructions.
Which tool helps when I cannot tell what URL I am checking?
Use a public redirect trace to obtain the final URL, then inspect its source and headers.
Does requesting indexing provide a publication deadline?
Treat it as a request. Inspect recent crawl and indexing information as Google processes the page.
Official references and scope
Sources checked