Practical checklist
Five checks to start with
- Record the exact missing URL and search phrase.
- Distinguish a missing page from a low-ranking page.
- Compare indexed information with current live behaviour.
- Confirm whether the reported canonical is intentional.
- Assign one corrective action and a follow-up date.
Describe what “not showing” means
A missing homepage, a service page outside the first results and a Chinese page replaced by its English counterpart are three different observations. Write down the exact URL, search phrase, language, country and date. Avoid beginning with a general conclusion that the whole website has disappeared.
A business-name search is also different from a competitive service search. If people can find your firm by name but not for a broad phrase, a developer may not be able to solve that with one setting. A precise problem statement helps you avoid buying an unnecessary rebuild or repeatedly submitting a page that already appears in the index.
Use the indexed record and the live test for different questions
Search Console’s URL Inspection reports on Google’s indexed record; its live test checks the currently accessible page. The two can differ after a change. Review the reported indexing status and selected canonical, then use a live test when you need to investigate the current version.
Build a small record for the homepage, one priority service and one newly published article. Save the inspection date and the page owner alongside the result. If only the new article has a problem, keep the investigation focused there instead of changing the entire domain’s settings.
Give technical findings a business interpretation
Ask whether the URL is intended to be public. A quotation preview or internal thank-you page may correctly be excluded. For a public service page, ask the developer to explain any inaccessible response, unintended indexing restriction or unexpected preferred URL in plain language.
For example, if a new Traditional Chinese service page identifies the English homepage as its preferred version, ask whether that reflects the intended content relationship. Do not indiscriminately remove every canonical or robots instruction. Record the desired public URL and have the responsible person test the change against it.
If the page is indexed, inspect relevance and competition
An indexed page can still receive few impressions. Read it as someone who has never met your company. Does it name the service, who it helps, what is included and how to proceed? Can a buyer distinguish a design service from hosting, ongoing SEO or a ready-made template?
Compare the kinds of pages returned for the target phrase. A service-oriented search may need a service page, while a diagnostic question may suit an article. Use that observation to improve the existing destination. Creating several lightly rewritten articles around the same phrase can make the site harder to organise without answering a new question.
Write a repair ticket and a follow-up date
A useful ticket says: “This public service URL should be discoverable; the inspection reports this condition; here is the expected destination and content.” Attach evidence privately to your developer brief. Ask for a description of the fix, the pages affected and a simple check that confirms the intended behaviour.
After the change, record when it went live and review the same URL later. A successful live test is not a promise of indexing or a ranking deadline. If the technical route works, continue improving the page’s usefulness and how relevant visitors discover it. Repeatedly changing titles, URLs and content at once makes the next diagnosis harder.
Sources and scope
- Google: URL Inspectionsupport.google.com
Technical reference; examples and review procedures in this article are editorial recommendations.