Your main service deserves a place in the searches that matter to your business. When that page seems to be missing, start with one decision: is it absent from Google’s index, or indexed but not appearing for the search you care about?
Those are different investigations. Establishing which one you have gives your web or SEO team a useful starting point and keeps a single missing page from becoming an unnecessary rebuild.
This guide is for owners of service businesses and the people responsible for their sites. Work on one priority URL first. If you want help reading the finding, book a free Clarity Call.
For a wider decline across previously visited pages, start with the Google traffic-drop diagnostic. Its worked record separates tracking faults, search losses and unresolved update effects before choosing a repair.
Start with the page buyers should find
Choose the page that explains a service you actually want to sell. Write down its exact address, intended buyer and business purpose. For example, an advisory firm might want its fractional finance service found by growing businesses considering outside support.
Check the final address in the browser. An old URL that redirects to the right replacement has a different job from the replacement itself. Parameters, an alternative hostname or a missing trailing slash can also lead you to inspect a different version.
Ask the person with Search Console access to inspect the intended URL. A manual search can show that you did not see the page in that result; it cannot give you the same indexing diagnosis.
Read Google’s stored result before deciding on a fix
In URL Inspection, record the page indexing result, last crawl, fetch result, crawl permission, indexing permission and both canonical addresses. The canonical is the version Google treats as the main page among duplicates.
These fields belong together. For example, an “indexing allowed” field does not rule out a hidden noindex instruction if Google was blocked from fetching the page in the first place. Google’s URL Inspection guidance explains these limits.
Use the result to choose the next check:
| The recorded result | What your team should establish next |
|---|---|
| Submitted and indexed, or URL is on Google | Check the selected canonical. If it is the intended page, investigate the searches and buyers it reaches rather than treating it as a missing-index problem. |
| Excluded by noindex | Confirm whether exclusion is intentional. If this public service page should be indexed, locate the actual directive before proposing its removal. |
| Blocked by robots.txt | Confirm the intended access policy and the rule affecting this URL. Keep deliberate private or excluded areas protected. |
| Page with redirect | Check whether the destination is the correct replacement, then inspect that destination separately. |
| Alternate page with proper canonical | Check the intended main version. This can be an expected exclusion, with no repair needed on the alternate. |
| Google chose a different canonical | Compare both pages, their purpose and the canonical signals. A status alone is not a reason to merge or redirect them. |
| Discovered, currently not indexed | Google knows the URL but has not crawled it. Review discovery and current access; do not diagnose weak copy from this status. |
| Crawled, currently not indexed | Google crawled it but did not index it. Review the page and its signals before deciding whether any change is justified. |
| Soft 404 or a fetch error | Inspect what the URL actually returns, including the main content. Decide whether the page should exist before repairing or retiring it. |
The Page indexing report helps find a wider pattern. Start with important affected pages; making every excluded URL turn green is not the business objective.
Check what the page does now
The stored inspection result can describe an earlier version. Compare its crawl date with recent changes, then ask your team to check today’s response and run a live inspection where appropriate.
The review should cover:
- Response and content: the intended page loads, with its important information visible, without an error, login or unexpected redirect.
- Crawl and indexing instructions: the relevant robots rule, robots meta tag and
X-Robots-Tagheader match the intended policy. - Canonical signals: the declared main address, relevant internal links and sitemap agree on the intended version.
- Discovery: buyers and crawlers have relevant links to the page. An absent referring-page entry in Search Console does not prove there are no links.
A successful live test means the inspection tool could access and parse the current page. It does not select Google’s canonical or establish every condition for indexing. Check redirects separately: the live test can follow them without displaying the final tested URL.
Robots rules control crawling. A noindex instruction controls indexing only when Google can read it. Combining a crawl block with noindex can prevent that instruction being seen. Have the responsible team apply the intended policy using Google’s noindex guidance.
A check on our own service page
On 5 October 2026, we inspected our AI SEO service page in our connected Search Console property. Its stored result was “Submitted and indexed”. The declared canonical and Google’s selected canonical both matched that service URL; the recorded crawl was 3 October 2026.
That finding points away from an indexing repair for that recorded version. The useful next investigation is whether the page reaches relevant buying questions and helps a suitable prospect evaluate the work. It does not establish today’s crawler access or selection in an AI answer.
That check keeps the next action focused on the information buyers need and the evidence available.
Give the next action to one person
Copy these fields into your team’s existing task or document. Keep screenshots and inspection exports beside the record.
| Field | What to record |
|---|---|
| Priority page | Exact URL, service, intended buyer and why the page matters. |
| Finding | The observed status or response, evidence source, check date and stored crawl date where available. |
| Intended state | Indexed main page, deliberate alternate, redirect or deliberate exclusion. |
| Next action | Repair a confirmed issue, inspect a specific uncertainty, or leave an expected result alone. |
| Responsible person | Who can make or investigate the change, and who approves it. |
| Recheck | What will be tested after the change, who records it and the agreed review date. |
A review date is your team’s appointment to check progress. It is not Google’s indexing deadline.
After an approved fix, recheck the response and the relevant inspection fields. A crawl request can be appropriate for an eligible new or updated page. Repeated submissions do not accelerate it, and submission does not ensure indexing. See Google’s recrawl guidance.
Choose the work the finding calls for
A confirmed access problem belongs with the person managing technical SEO. A question about whether two pages have different jobs belongs in the overlapping-page decision guide. An indexed page missing from an AI answer needs the separate Google AI eligibility check.
Bring the URL and the finding to a free Clarity Call if you want to decide the next step with us. If you would prefer an initial written review, get your free Outside View.