Crawling, indexing and ranking are different
Crawling is fetching a page, indexing is processing and potentially storing information about it, and ranking is deciding which results suit a search. Passing one stage does not guarantee the next. A page can load perfectly for you without already appearing in Google’s index.
Useful context
- Keep the exact public page address you are checking.
- Use your own verified Search Console property if you have access.
How it works
Start with discovery
Imagine a new catering page linked only from an unpublished draft. Customers and search engines may have no practical route to it. Add a relevant public navigation or content link, and include the intended canonical address in your generated sitemap where appropriate.
Check whether fetching succeeds
If a crawler cannot access the page, identify the barrier: a login, a server fault or a crawl restriction. Record the actual result rather than concluding that Google dislikes the wording. A website owner or developer can then address that particular problem.
Read the indexing result
Search Console’s URL Inspection describes what Google knows about the address. A fetched page might be excluded deliberately or treated as another version of an existing page. Inspect the stated reason and preferred address before attempting to make every reported URL indexable.
Consider relevance after eligibility
Once a page is eligible and indexed, its position still depends on the search and competing information. An indexed café menu is not automatically a relevant result for wedding catering. Improve the answer to the genuine query instead of treating every low position as a technical fault.
What to check
- You know which stage your evidence describes.
- The address is the real public page rather than a preview.
- You have a specific next action or a sensible review date.
Sources and further reading
Platform features can change. Check the provider’s current guidance before changing a live service.