A live website is not automatically an indexed or competitive website.
First establish whether Google has indexed the intended page, selected another URL for the same content, or indexed the right page without showing it prominently for your desired search. Those three situations call for different work.
What does “not showing on Google” mean?
Write down one complete page URL and one search you expected it to appear for. “Our website is missing” is too broad to diagnose. A homepage appearing for the business name does not establish that a new service page is indexed or that it can compete for a service search.
Use Search Console's URL Inspection tool for that exact URL. Record the indexed status, last crawl and Google-selected canonical. The indexed report describes Google's stored version; a live test checks the page now. A successful live test does not prove that indexing has happened or predict which canonical Google will select.
A site: search can be a useful clue, but it is not a complete inventory. Google says its results are not necessarily exhaustive. An absent result is a reason to inspect the URL, not enough evidence to rebuild the page.
Which problem does the evidence point to?
| Observed state | Question to resolve | Next action |
|---|---|---|
| The intended page is not indexed | Is access blocked, is Google still processing it, or has it decided not to index it? | Read the specific indexing reason and compare the crawled version with the live page. |
| Google selected another URL | Is that the correct equivalent page? | Inspect the selected URL before changing redirects or canonical signals. |
| The intended page is indexed | Does it appear for the right queries and audience? | Review query-level performance and the usefulness of the page for that search. |
The site's excluded-page total is not a repair queue. Old redirecting URLs and duplicate versions can correctly remain outside the index. Prioritize the public pages that should represent the business. Google's Page indexing guidance explicitly distinguishes expected exclusions from problems.
If the page is not indexed, inspect the actual barrier
Ask your developer to verify the response Google receives. Does the URL return the intended page, a login screen, an error or a redirect? If a preview-site noindex setting reached production, remove it from pages meant for search. Also check response headers. A robots.txt crawl block and a noindex instruction do different jobs: Google must be able to crawl a page to read its noindex rule. See Google's noindex documentation.
If access succeeds but the page remains unindexed, review its content and discovery path. Is it linked from a useful part of the site? Does its main service information render for Google? Does it add something distinct beyond another page? “Crawled, currently not indexed” alone does not identify a specific content defect.
After a verified correction, request indexing for an important URL and keep the sitemap current. Google's recrawl guidance says processing can take days to weeks and repeated requests do not speed it up. Submission is a request, not a guaranteed inclusion date.
A worked example: the wrong URL is being investigated
This is an illustrative diagnostic, not a claim about a particular client. Suppose a business searches for its old service address after a redesign and sees that it is excluded. Its new service page opens normally, but the owner is considering another rewrite.
- Inspect the old address and follow its redirect. Confirm that the destination is the equivalent service, not an unrelated homepage.
- Inspect the destination separately. Suppose its indexed record identifies that destination as Google's selected canonical.
- Review the destination's search performance. If it earns impressions for the desired query but receives few clicks, the evidence points to a visibility or relevance investigation, rather than a missing-page diagnosis.
The decision is to keep the correct redirect and investigate the destination. Do not remove a useful redirect just to make an exclusion count smaller. If Google instead selects an unintended duplicate, align the preferred URL, internal links, sitemap and canonical signals. Google explains how those signals support canonical selection.
If the page is indexed, what should improve next?
Compare the page with the decision the searcher is trying to make. Does someone seeking a local service find the actual service, coverage, relevant project evidence and a clear way to enquire? A general company introduction may leave those questions unanswered. Improve the missing information rather than repeating the target phrase.
In Search Console, filter the Performance report to the page and relevant queries. Separate business-name searches from service searches, and keep country, device and comparison periods consistent. A sitewide average position can change because the mix of queries changes; it is not a fixed rank for this page.
Slow or awkward pages also deserve attention, especially when visitors cannot read or submit a form. They do not, by themselves, establish why a URL is unindexed. Connect each proposed fix to an observed problem.
Leave the developer a decision, not a vague request
A compact record is enough: the intended URL and query; indexed status and inspection date; selected canonical; live-response or rendering issue; the proposed change and its reason; who owns it; and what will be checked afterward. Include what should remain intact, especially existing URLs and useful content.
If URLs changed at launch, review their mappings using Google's migration guidance. Our home-services redesign story illustrates the separate need to protect an established search presence; it is not a numerical recovery promise.
For a new project, explore website design or our Fresno website work. For an existing page that needs diagnosis, see SEO services. If the evidence has not yet justified a redesign, start with the business plan before another website.