First, decide whether this is a problem
Excluded by noindex tag means Google found an instruction to keep that URL out of search results. A sitemap cannot override it.
Start with one exact address from Search Console. For example, a plumber might check a missing boiler-repair page before changing site-wide settings.
- A public service page
- Investigate. Customers should be able to find this service through search.
- A thank-you or internal search page
- Check its purpose. The exclusion may be intentional and need no change.
- A staging site or private area
- Keep it protected. Noindex controls search visibility; it is not a password or access control.
Do not try to make the excluded count reach zero. The useful outcome is making the right public pages eligible.
1. Find the instruction Google received
Open the affected URL while signed out of WordPress. Use the final address after any redirect.
View its page source and search for noindex. Look for a robots or googlebot meta tag:
<meta name="robots" content="noindex">The instruction can also arrive in an HTTP response header. In browser developer tools, open Network and reload the page. Select the main document, then read Response Headers for X-Robots-Tag.
A header containing noindex has the same exclusion effect. If the page source looks clear, do not skip this check.
Record the URL, the exact instruction, and where you found it. These three facts tell you which fix to try.
2. Change the setting that owns it
Save a screenshot of the current setting before editing. Work on the chosen service page first, then check the public output.
If many public pages are affected
In WordPress, open Settings → Reading. Find Search Engine Visibility. On a production site intended for search, clear the option that discourages indexing, then save.
Confirm that you are editing the live site, not a staging copy. This control affects the whole site.
If you use Yoast SEO
Edit the affected page and open the Yoast SEO sidebar or box. Under Advanced, allow search engines to show this content in search results. Save the page.
If several pages of one type are affected, inspect that content type under Yoast SEO → Settings too. Do not enable all archives just to fix one service page.
Yoast: individual and content-type controls ↗
If you use Rank Math
Edit the page and open Rank Math → Advanced. In Robots Meta, remove No Index and select Index. Update the page.
If Advanced is hidden, enable Advanced Mode in Rank Math's dashboard. Check Titles & Meta for unwanted content-type defaults as well.
Rank Math: fix noindex exclusions ↗
If the instruction comes from a header
Send the recorded header and URL to whoever manages your hosting or site code. Ask which rule adds it.
A page-level plugin setting may not control a server or hosting rule. Avoid changing server files without identifying that rule.
3. Check the result, not just the checkbox
Clear the affected page from your WordPress and hosting caches. Reload it while signed out, then repeat both checks.
Check every robots and googlebot tag, plus the response headers. Adding an index instruction does not cancel a remaining noindex instruction.
The more restrictive applicable rule wins. The value none also includes noindex, so treat that as an exclusion.
Google: conflicting robots rules ↗
If the instruction returns, note whether it appears after publishing, a cache refresh, or a plugin update. Give your developer that repeatable trigger.
Do not install a second SEO plugin to fight the first. Identify which component writes the instruction and fix that source.
4. Separate a fixed page from an indexed page
In Search Console, inspect the exact URL and run a live test. Check whether indexing is allowed now.
The stored inspection result describes Google's earlier crawl. Compare its crawl date with the time you made the change.
A successful live test does not mean the page is indexed. Google still decides whether to crawl and include it.
Google: live tests and indexed information ↗
Keep a normal internal link to the service page and include its preferred address in your sitemap. Do not block crawling in robots.txt to solve a noindex exclusion.
If the status changes to a different exclusion, investigate that reason next. A canonical mismatch needs a different fix from noindex.
Your record of the fix
Keep one short record per affected service page. It makes a recurring problem easier to trace without repeating every check.
- The public URL and why customers need to find it.
- The old instruction and the setting or rule that produced it.
- The saved change and the time you cleared the cache.
- The new public meta tags, response headers, and live-test result.
That record proves what changed on your website. Search impressions and customer visits are separate outcomes to measure later.