If your WordPress pages have disappeared from Google, first confirm whether they are actually excluded from the index or have simply lost rankings. Google Search Console’s URL Inspection, Page indexing, Manual actions, and Security Issues reports can show which problem you are dealing with. Then fix the specific cause—such as an unintended noindex, blocked crawling, a server error, or a policy issue—and verify the affected URLs again.
Confirm whether your site is deindexed or just ranking lower
“Deindexed” is often used to describe any disappearance from search results, but a traffic drop or a missing result in a manual search does not prove that Google removed a page from its index. A page may still be indexed but rank lower, or attract less search demand.
Start with Google’s [Google guide to missing pages](https://support.google.com/webmasters/answer/7474347?hl=en). In Search Console, inspect the homepage and a small representative sample of affected URLs—such as a post, a page, and a custom post type if the issue appears site-wide. Use URL Inspection for each URL, then consult the Page indexing report for the broader pattern. Check Manual actions and Security Issues as well.
If only one URL or a particular template is affected, focus on that URL or template rather than assuming the whole domain has been removed. A site: search alone cannot identify why a page is missing.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11#1 Best Overall
Check WordPress’s site-wide search visibility setting
- In the WordPress dashboard, open Settings → Reading.
- Find Search Engine Visibility and review Discourage search engines from indexing this site.
- If the public site is meant to appear in Google, clear the checkbox and save the setting.
WordPress describes this as a request to search engines, not a way to restrict access: visitors can still view the site. Since WordPress 5.3, the setting can cause a noindex,nofollow meta tag to be generated in the page head when wp_head is used. See the [WordPress Settings Reading screen documentation](https://wordpress.org/documentation/article/settings-reading-screen/).
If the checkbox is already clear but a live page still contains noindex, look for another source: SEO plugin settings, a page-level robots setting, theme or custom code, or an HTTP response header. Google can read noindex in either a meta tag or an X-Robots-Tag response header. Its [noindex guidance](https://developers.google.com/search/docs/crawling-indexing/block-indexing) explains how these directives work.
Check whether Google can crawl and fetch the page
In Search Console, open URL Inspection, enter an affected URL, and use the live test to check current access and indexing permission. Google’s [URL Inspection tool documentation](https://support.google.com/webmasters/answer/9012289?hl=en) describes the information available. Also check the page and its response for these common barriers:
- Robots.txt rules: Confirm that the affected path is not blocked from crawling if Google is meant to read the page.
- Login or password protection: A public page should not require credentials for Google to fetch it.
- Server, firewall, or CDN responses: Check whether the site returns an error or otherwise prevents Googlebot from accessing the URL.
- Robots directives: Inspect rendered HTML for a meta
noindexand response headers forX-Robots-Tag: noindex.
Robots.txt controls crawling; it is not a supported way to implement noindex. If crawling is blocked, Google may be unable to see a noindex instruction in the page or response. To have Google read a noindex directive, leave the resource crawlable while that directive is in place.
For a page that has genuinely been removed and has no similar replacement, return a proper not-found response rather than leaving a misleading page in place. Google’s [crawling error guidance](https://developers.google.com/search/docs/crawling-indexing/troubleshoot-crawling-errors) recommends returning 404 for a gone page with no suitable replacement. Do not redirect an unrelated URL merely to make it appear indexed.
Review Manual actions and Security Issues
Manual actions
In Search Console, open Security & Manual Actions → Manual actions. A manual action means a human reviewer determined that pages do not comply with Google’s spam policies; it can affect some or all of a site’s search results. If the report lists an issue, fix every instance it identifies, confirm Google can access the repaired pages, and submit a review request describing the problem and your corrections. Google says fixing only some affected pages will not result in a partial return for that action. See the [Manual actions report documentation](https://support.google.com/webmasters/answer/9044175?hl=en).
Rank #4
Security Issues
Review Search Console’s Security Issues report for problems Google has identified, such as hacked content. Follow the report’s remediation instructions, clean or remove affected content, and verify that the relevant pages are accessible afterward. A drop in indexing by itself is not evidence that a site was hacked.
If the page is accessible and allowed but still not indexed
If URL Inspection shows no blocking directive or access failure and neither report identifies a relevant issue, avoid changing robots settings blindly. Google notes that a page may be hard to discover even when inspection shows no error and the page is not blocked. Check whether important pages are linked from relevant pages on your site, whether the content is available at a stable canonical URL, and whether it is useful and distinct from other pages on the site.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →These are practical site checks, not a guaranteed indexing formula. The available evidence does not establish a single content or technical change that guarantees Google will include a page.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Match the Search Console evidence to the next step
| Evidence | Where to investigate | Next step |
|---|---|---|
The WordPress visibility setting discourages indexing, or a live page outputs noindex. |
Reading setting, SEO plugin, per-page setting, theme or custom code, and response headers. | Remove only the unintended directive, then test the live URL. See the WordPress Reading documentation and Google’s noindex guidance. |
| URL Inspection reports a block or fetch failure. | Robots.txt, authentication, server, firewall/CDN, or HTTP response. | Restore the intended crawl access and correct the response; verify with the live test. See Google’s missing-page guide and URL Inspection documentation. |
| Manual actions names an issue. | The spam-policy problem described in the report. | Fix every listed issue, ensure the affected pages are accessible, and request a review. See the Manual actions report documentation. |
| Security Issues names a problem. | The reported security issue, including any affected content. | Follow Google’s remediation steps, clean or remove affected content, and verify the result. See Google’s missing-page guide and crawling error guidance. |
| No block or error is identified. | Internal discovery and whether the page offers useful, distinct content. | Review links and content without assuming a change will guarantee inclusion; monitor the Page indexing report. See Google’s missing-page guide. |
Verify the fix and request a recrawl
- Run URL Inspection’s live test again after changing a WordPress setting or repairing a page.
- Confirm Google can access the URL and that the unwanted
noindexor other barrier is gone. - For important corrected URLs, request indexing in Search Console and monitor the Page indexing report for a status change.
A request is not a promise of inclusion or a specific recovery date. Google Search Central states: “Requesting a crawl does not guarantee that inclusion in Google Search will happen instantly or even at all.” See [Ask Google to Recrawl Your Website](https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl).
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
