Start with one page that matters
Crawled currently not indexed means Google fetched the URL but has not included it in its search index. The label alone does not identify the cause.
A WordPress service page deserves attention when customers need it to understand or book your work. Start there before investigating every excluded archive or feed.
For example, choose your boiler-repair page, rather than an empty tag archive. Copy its exact public address from Search Console.
- Crawled, not indexed
- Google fetched the URL. Check its current status, content, and relationship to other pages.
- Discovered, not indexed
- Google knows the address but has not fetched it yet. This is a different stage.
- Excluded by noindex
- Google found an instruction that excludes the page. Find that instruction before rewriting the content.
Google says a crawled page may or may not enter its index later. Repeated submission is not required for this status.
1. Check the exact URL in Search Console
Paste the address into URL Inspection. Read the stored indexing result and note the last crawl date.
Then run Test live URL. This checks the current page, while the stored result describes Google's earlier information.
- Check whether Google can fetch the page now.
- Check whether indexing is allowed.
- Open the tested page view. Confirm that your service information appears.
- Compare the crawl date with your last meaningful edit.
A successful live test does not prove that Google indexed the page. Keep these two results separate in your notes.
If URL Inspection already reports the URL as indexed, avoid rewriting it solely because an older report disagrees.
2. Look for a specific technical problem
Open the address while signed out of WordPress. Confirm that it shows the intended page without a login or error.
Compare that view with the tested page from Search Console. A broken template can leave visitors with navigation and no service details.
If the current test reports a fetch failure, solve that failure first. Save the address and error for your host or developer.
If it reports noindex, inspect the page source and response headers. Your WordPress or SEO plugin settings may explain the instruction.
Do not change every plugin setting at once. Record the current setting, make one relevant change, and check the public output.
A missing sitemap entry does not explain why an already crawled page remains unindexed. Keep discovery and indexing decisions separate.
If the page works and indexing is allowed, move to the content checks. A green technical test is a starting point.
3. Compare pages that answer the same question
Look for another page on your site that offers the same service to the same customer.
Compare the page title, main heading, service details, and booking path. Two different addresses can still offer almost identical information.
A canonical tells search engines which version you prefer among duplicate or very similar pages. It is a signal, not a command.
For an accidental duplicate, choose the version you want customers to find. Keep links and sitemap entries consistent with that choice.
For distinct services, preserve both pages and explain their different scope. Do not point every service page's canonical at your homepage.
In WordPress, check which plugin or theme owns the canonical output. Verify the published tag before adding another setting.
4. Give the service page a useful job
Ask what a customer can learn here that your homepage does not already answer. Add information from your actual work.
A longer page is not automatically more helpful. Google does not prescribe a word count for helpful content.
Google: assess helpful, reliable content ↗
Example: a boiler-repair service page
This is an illustrative rewrite, not a customer result. A generic opening might say: "We offer reliable boiler repairs."
A useful page lets a homeowner decide whether to call. Build it around facts the business can confirm:
- The boiler types and brands your team actually services.
- The areas you cover and your normal opening hours.
- What a diagnostic visit includes, with any known call-out charge.
- How booking works and which details the customer should prepare.
- An original job photo, with permission, explaining the work shown.
Do not invent emergency coverage, qualifications, prices, or customer reviews. If you cannot confirm a detail, leave it out.
Give nearby-location pages distinct information only when you genuinely have it. Changing a town name in the same paragraph adds little.
Before publishing, ask a colleague to use the page to answer a real enquiry. Note each answer they still need.
5. Make the page easy to reach
Link to the service from the relevant services page. Use words that tell visitors what they will find.
For the example above, "boiler repairs" is clearer than "click here". Add the link where it helps someone choose a service.
Check that the link opens the final public address. Avoid sending people through an old URL when you can update it.
Google: crawlable links and useful link text ↗
Include the preferred public URL in your sitemap. If the page changes substantially, keep its last-modified date accurate.
A sitemap helps Google discover URLs. It does not guarantee that Google will crawl, index, or rank them.
Know what changed before checking again
Save a short record: the URL, original status, crawl date, problem found, and change made. Include the new live-test result.
Check again after Google has had time to revisit the page. There is no guaranteed indexing deadline.
If the next crawl still leaves an important page unindexed, compare it with your stronger service pages. Review the whole customer journey.
A working page, an indexed page, and a page that brings enquiries are different outcomes. Measure each without assuming the next.
For WordPress owners exploring ongoing search work, the Tin GEO page explains its setup and offer. Start with your public website address.
