Investigate a service page marked crawled, currently not indexed

Confirm that this URL deserves its own search entry

Write the customer task in one sentence before changing anything. A drain-repair page and a drain-cleaning page might address different needs, or might describe the same visit with different labels. If visitors cannot explain the difference, two separate URLs may create unnecessary duplication. The objective is a worthwhile destination, not an indexed count that matches every URL in your website builder.

Source checks: Google Search Console: Page indexing report · Google Search Console: URL Inspection · Google Search Central: Fix canonicalization issues

Record what Google last received

Inspect the complete URL in the correct Search Console property. Save the reported reason, last crawl date, declared canonical, and selected canonical when available. Run a live test separately and look at the rendered content. The historic report describes a previous observation; the current test describes present access. Do not overwrite one with the other in your repair notes.

Compare the page with its closest alternative

Open the nearest overlapping service page beside the affected URL. Compare eligibility, scope, process, exclusions, estimate requirements, and evidence. Ignore cosmetic differences and repeated city names. Ask whether a customer would make a different decision using this page. If it contains unique information, identify that information explicitly so the technical reviewer knows what should survive.

Choose the repair that matches the evidence

Use one of three paths rather than applying every SEO setting at once.

• Repair missing or broken rendered content if the visitor sees a useful page but the test does not.
• Correct an accidental canonical pointing at an unrelated destination; inspect that destination too.
• Consolidate genuinely redundant content into the stronger appropriate URL and plan the redirect.
• Keep a distinct useful page, strengthen its relevant navigation path, and record the publication date.

Avoid changes that hide the real cause

Changing the slug creates another URL to manage and does not explain why the original was excluded. Adding noindex simply changes the intended outcome. Repeating an indexing request without a substantive repair creates no new content evidence. Do not conclude that a manual action occurred from this label alone; investigate an actual warning separately if one exists.

Review a small evidence trail afterward

Maintain a row with URL, problem, chosen repair, owner, deployment date, and follow-up observation. Check the live page immediately, then revisit indexed evidence after Google has observed the change. Keep useful inquiries and page-level search performance separate from index status. A page becoming eligible does not prove it will rank for the phrases you want.

Illustrative drain-service decision

An illustrative website has /drain-cleaning and /blocked-drain-service. The second repeats the first except for its heading. Both respond successfully and point canonicals at themselves. The owner discovers that both represent the same appointment, combines the second page's useful emergency-preparation note into /drain-cleaning, and redirects the retired URL there. The decision follows genuine overlap; the indexing label alone did not prove duplication.

For this example, the transfer list contains the emergency-preparation note, its approved wording, and its new page section. The owner also changes any current menu link to the surviving destination. A later editor can see that the retired URL represents the same appointment and should not recreate it.

Questions about this task