Start with the exact URL
Choose one commercially important page and copy its full public address, including the correct domain and final path. Confirm it opens for someone who is not logged into the website. A draft, password screen or broken destination cannot serve the same purpose as a normal public page.
Inspect that URL in the matching Search Console property. Google’s URL Inspection distinguishes information about the indexed version from a live test. A successful live test does not establish that the page is already indexed.
If the page is not indexed
Read the specific reason rather than treating every exclusion as an error. A redirect may be intentional. An alternative URL may correctly point to another canonical version. A page you deliberately excluded should not be submitted merely to increase a count.
For a page intended to appear, check the public status, indexing directives, canonical destination, links from useful existing pages and sitemap inclusion. Ask the developer to explain any discrepancy between the intended URL and the version Google recognises.
If the page is indexed but you cannot find it
An indexed page does not have to appear prominently for your preferred phrase. Look at the page’s actual query data and whether those searches match the offer. A highly competitive broad term and a specific local service question are different opportunities.
Check whether the page clearly explains the service, who it helps, where it applies and how to take the next step. Avoid creating several near-identical pages for the same question. Improve the most appropriate page rather than fragmenting its purpose.
Make discovery straightforward
An important page should be reachable through normal links from relevant parts of the website. A sitemap can support discovery, but it is not a substitute for a coherent customer journey.
Link from a service overview, relevant guide or related page using wording that explains the destination. You do not need to insert the same keyword in every link. The link should help a reader decide whether to continue.
Request indexing once where appropriate
After a genuine issue is fixed or useful new content is published, use the available Search Console request process where appropriate. Keep the date and outcome. Request acceptance means processing has been requested; it is not confirmation of indexing.
Google says repeated requests for the same URL do not make crawling faster. If progress remains unclear, return to the page’s actual status and evidence rather than repeatedly pressing the request button.
PUT IT INTO PRACTICE
A diagnosis you can hand to a developer
Use these prompts in your own notes or when discussing the work. This is a reading checklist, with no submission or data collection.
| What you observe | Check next | Avoid assuming |
|---|---|---|
| Public URL fails or asks for a login | Publication, status and access | That more text will fix access |
| Inspection says not indexed | Specific reason, canonical and discovery links | That every exclusion is a defect |
| Inspection says indexed | Relevant query visibility and content fit | That indexing guarantees page one |
| Request accepted | Later dated inspection | That acceptance is indexing |
Questions, answered
Does submitting a sitemap guarantee indexing?
No. It helps Google discover URLs, but does not guarantee that every page is indexed or ranks.
Should I keep requesting indexing?
No. Keep the outcome of an appropriate request and allow processing. Repeated requests do not speed up crawling.
Can KSJ check the cause?
The SEO Audit is a starting point for reviewing the website’s technical and content priorities. Share the exact pages and the business outcome you need.
Official guidance
For the platform rules and technical detail behind the relevant checks:
YOUR NEXT STEP
Make the next decision with a clearer brief.
Tell KSJ Growth what you offer, what is not working and what you want the website to help you achieve. We can discuss a suitable scope before you commit to further work.
Discuss your business