Choose the next step from the evidence
Discovered currently not indexed means Google found the URL but has not fetched it for indexing. The empty last-crawl date fits that status.
Google says it typically reschedules these crawls to avoid overloading a site. The label alone does not prove your host is broken.
Start with one public service page that customers need. An appointment page matters more than an unused tag archive.
- New page, live test passes
- Check its links and sitemap entry, then allow time for discovery to become a crawl.
- Live test fails
- Save the exact error. Fix the access problem before changing the page copy.
- Many important pages affected
- Compare their publication dates and templates. Check for shared access or host problems.
If the status says crawled rather than discovered, Google has already fetched the page. Use the separate crawled-page guide below.
1. Keep the stored result and live test separate
Paste the exact public address into Search Console's URL Inspection. Record the status, last-crawl field, and inspection date.
Then run Test live URL. The stored result describes Google's existing information; the live test checks current access.
Read the fetch and indexing-allowed results. Open the tested page view and confirm that your service details appear.
A passing live test does not mean the URL is indexed. It also does not guarantee that Google will select it.
For example, a page published yesterday can pass today's live test while its stored result still says discovered.
Keep both results in your notes. Otherwise, a later reviewer may mistake a working page for a confirmed search listing.
2. Check WordPress access before changing content
Open the same address in a signed-out browser. A visitor should see the intended page without a password or maintenance screen.
Confirm that WordPress lists the page as published and public. Check whether a maintenance or security plugin changes the public view.
In Settings → Reading, review the search engine visibility option. A public business site should not accidentally discourage search engines.
Keep staging sites and private pages private. Do not change a site-wide setting just to expose one page.
If the live test reports noindex, check the page's SEO plugin setting and the published output. Record the setting before editing it.
If it reports a robots.txt block, give your developer the exact blocked URL and rule. Avoid replacing the whole file.
A current block is a separate finding, not proof of what caused the older discovered status. Re-test after a specific fix.
3. Give the page a useful route in
Start at your homepage and try to reach the page through normal links. Note where the route stops.
For a new drain-repair service, add a link within your services page. Place it beside the related work customers already browse.
Use a clear label such as "drain repairs". The link should open the final public address, not a preview or old redirect.
Google generally discovers links through anchor elements with an href address. A clickable visual alone may not provide that route.
Ask a developer to inspect custom cards or buttons if the destination exists only in a script.
One relevant link is more useful to a visitor than an unrelated list pasted onto every page. Keep the surrounding explanation natural.
4. Check the sitemap's exact address
Open the sitemap listed in Search Console. If it is a sitemap index, open the child sitemap containing your pages.
Find the service page's final URL. Compare its hostname, path, and trailing slash with the public page.
If it is missing, check which WordPress plugin generates the sitemap. Look for an exclusion affecting that page or content type.
Do not install a second sitemap plugin before checking the first. You need one clear source of preferred public URLs.
A sitemap is a discovery hint, not an indexing guarantee. Since Google already knows this URL, submission alone may change nothing.
Keep last-modified dates tied to real changes. Refreshing every date without changing the content does not make the pages new.
5. Escalate a pattern, not just a label
If several important pages remain affected, group them by publication date and template. Compare a working page from each group.
A shared maintenance setting or a failing template gives your developer a narrower problem to investigate.
In Search Console's Crawl Stats, look for host availability problems. Ask your host about repeated server errors around the same dates.
Responses such as 429 and 5xx can reduce Google's crawling. Ask for evidence from logs before buying a larger hosting plan.
Google's advanced crawl-budget guidance mainly addresses large or rapidly changing sites. A small service site rarely needs that whole programme.
Do not mass-delete pages or block sections in robots.txt to force attention elsewhere. First establish which URLs matter and what fails.
Google: crawl demand, capacity, and server errors ↗
A useful note for your host
Replace the brackets with your findings. Send this only when you have a specific access failure to investigate.
Our public page [URL] failed Google's live test at [time and timezone]. The error was [exact message]. A signed-out browser showed [result]. Please check server and firewall logs around that time and explain any blocked requests.
Know when to wait
If access works, the page has a relevant link, and the sitemap is correct, record that baseline.
A useful record includes the exact URL, publication date, stored status, live-test result, linking page, and any change made.
Google says crawling can take days to weeks. Repeated requests do not speed it up, and inclusion is not guaranteed.
Do not treat an unchanged report tomorrow as proof that today's fix failed. Check whether a crawl occurred after your change.
If the status becomes crawled currently not indexed, the question changes. Review the page's value and duplication rather than discovery alone.
If it becomes indexed, search impressions and customer enquiries still need separate measurement.
Google: recrawl timing and limits ↗
Tin GEO's small-business page explains its WordPress setup and offer. No tool can promise Google's crawl or indexing decision.