How to check Google indexing and prepare useful sitelinks
Inspect the exact URL in Search Console, resolve any access or indexing issue, and connect useful pages through clear navigation. Google selects sitelinks automatically from the pages it understands.
Identify which stage needs attention
Start with the exact public URL you want customers to find. Record the date and inspect it in the verified Search Console property. A page can be known to Google, fetched by its crawler, included in the index, and shown for a query at different times. Each stage needs its own evidence.
| Question | Useful evidence |
|---|---|
| Has Google discovered the URL? | Discovery details in URL Inspection, including a referring page or sitemap when reported. |
| Has Google fetched it? | The recorded crawl date, response, and crawl permissions. |
| Is it indexed? | The indexed URL status and Google-selected canonical. |
| Has it appeared in searches? | Search performance impressions for the page and selected reporting period. |
URL Inspection provides indexed-page information and a separate live test. Use the timestamp on each result to keep an older crawl distinct from today’s page. Google’s URL Inspection documentation
For an undiscovered page, inspect its internal links and sitemap. For a failed crawl, investigate the recorded access error. For a crawled page that remains unindexed, review its usefulness, duplication, and canonical choice. Use the reported reason to choose the next investigation. Google’s indexing status guidance
Inspect the page customers can open today
- Open the URL while signed out. Confirm that it reaches the intended page and shows the useful content.
- Inspect the document response. A published service page should return its content successfully. Investigate errors, login redirects, and redirects to unrelated pages.
- Run Search Console’s live URL test. Open the tested-page details and examine the available HTML and screenshot.
- Find a distinctive sentence from the main content. If it is missing, inspect script failures, blocked resources, or content requiring interaction.
Google can render JavaScript, while other crawlers may have different capabilities. Server rendering or prerendering can make important text available directly in the initial response. Compare both versions when investigating a page whose source contains only an empty app shell. Google’s JavaScript SEO guidance
Check indexing instructions and the preferred URL
Look for a robots meta tag and an X-Robots-Tag response header. If a public page is intended for search, investigate an unexpected noindex. Preserve intentional exclusions for private or operational pages. Google must be able to fetch a page to read its noindex instruction. A robots.txt block can prevent that instruction from being seen. Google’s noindex guidance
Check the canonical URL against the page’s purpose. A genuinely distinct service page should identify the intended URL for that content. Equivalent URL variants can point to a shared preferred version. Keep canonical declarations, internal links, redirects, and sitemap URLs consistent, then compare the Google-selected canonical in the indexed result. Google’s canonical URL guidance
Give each useful page a route from the site
The following is a fictional room-hire website. Its pages serve distinct customer needs, with navigation labels that describe the destination.
/roomscompares available rooms and links to each room’s details./rooms/cedarexplains the Cedar Room’s capacity, facilities, and access./pricingexplains hire prices and links to the relevant room pages./bookingexplains how to reserve an available room.
A person on the Cedar Room page should be able to find its price and booking process. Use links such as “Room hire prices” or “Book the Cedar Room” where they fit the surrounding text. Implement navigation with real links whose href resolves to a public URL. Give each important page an internal link from another relevant page. Google’s link guidance
Submit the canonical URLs and recheck after changes
Include the public canonical pages you want discovered in your sitemap. Open the sitemap in a browser, confirm that its URLs work, and submit it in Search Console. Read the processing status and discovered-page count. Each URL’s indexed status still needs its own check.
If you supply lastmod, use the date of the page’s last significant update. Keep it accurate when the main content, meaningful links, or structured data change. An automatic daily date obscures when the page actually changed. Google uses this value when it is consistently accurate. Google’s sitemap guidance
After fixing a specific URL, test it live and request indexing when available. Save the test date and change made, then revisit the indexed result after Google recrawls it. Google describes crawling times ranging from days to weeks. Repeated requests for the same URL do not accelerate that process. Google’s recrawl guidance
Prepare pages that would make useful sitelinks
Sitelinks are extra links to pages within a site, grouped below a search result. Google selects them automatically when they help with the query. Make the site easy to navigate, use concise descriptive titles and headings, and link to important destinations with meaningful text. Google’s selection can vary by search. Google’s sitelinks guidance
For the fictional venue, rooms, pricing, and booking are useful destinations because they answer different needs. Review those pages on their own. Someone landing directly on pricing should understand the offer and be able to continue to the relevant room.
When checking results, record the query, date, language, device, and links actually shown. Keep that observation with the page changes you made. A screenshot can document a particular result for later comparison.
In Search Console’s Performance report, filter by the page and compare consistent date ranges. Impressions measure appearances under Google’s reporting rules. Clicks count selections of search-result links to your site. Google’s search performance metrics
Common questions about indexing and sitelinks
The live test passes. Why does the index report still show an issue?
The live test checks the current URL. The indexed result reflects Google’s stored information. Compare their dates and revisit after a new crawl. The live test also has limits, including its ability to predict Google’s canonical choice. URL Inspection results
Should I create more pages to get more sitelinks?
Create a page when it answers a distinct need with useful information. First improve the important destinations already on your site. Multiple thin pages with overlapping purposes can make navigation and maintenance harder.
Where does a CiteMaybe audit fit?
The free audit inspects one public page’s source HTML, metadata, crawl policy, and question coverage. Use its evidence to investigate page-level issues, and use Search Console for Google’s recorded indexing and search performance. Technical SEO audit scope