Does Google know your pages exist? A ten-minute check
Last checked:
Look at three things in Google Search Console: when Google last read your sitemap and how many pages it found there, how many pages the Pages report counts as indexed, and what the URL inspection says about one page that matters to you. If the dates are old, the counts are far below the number of pages you have, or the page is “unknown to Google”, your site is published but Google does not know most of it.
You do not need Savri or any analytics tool for this check. You need a Search Console property for your site, which is free, and about ten minutes. We did the three screens on our own site in a few minutes; the first time, finding the property and the inspection field takes longer than reading the results.
Why a working site can still be invisible
Our own website is the example. On 8 October 2026 we found that Google had indexed 20 addresses on the English domain, 19 of the 82 pages in the sitemap. Search Console said the sitemap had been submitted on 23 January and last read on 31 January, with 37 discovered pages. The URL inspection of the pricing page answered “URL is unknown to Google”. The site worked, brand searches brought clicks, and nobody had looked at the report for eight months.
The fault was ours. A static sitemap from 9 January listed the Swedish domain’s addresses on both domains, so the sitemap Google read for the English site pointed at another site. A host-aware sitemap replaced it on 11 June, but Google had not read the file again. Why Google did not re-read it for eight months is not something we have been able to establish. We know what was wrong in the file, not why it stayed unnoticed. The same thing can happen to anyone whose site generator produced the sitemap, including an AI builder; the fix is the same.
Step 1: the Sitemaps report
Where: in Search Console, open Indexing and then Sitemaps. The report lists the sitemaps you or your software submitted here; a sitemap only referenced in robots.txt does not appear until you submit it.
What is right: status Success, a Last read date that is recent, and a Discovered pages count close to the number of pages you expect. Google defines Last read as the last time it fetched the sitemap, and Discovered pages as the number of page addresses it parsed from the file. Google also says there is no guarantee that a discovered page has been or will be crawled or indexed.
What we saw when it was wrong: last read 31 January, 37 discovered pages, on a site with 82 pages, in October. After resubmitting on 9 October, the report showed last read 10 October with 86 discovered pages, the number of pages the live sitemap had by then.
Where readers get stuck: Discovered pages is the count in the file, not the count Google indexed. A recent date with the right count means Google has the list. It says nothing about the pages themselves.
Step 2: the Pages report
Where: Indexing and then Pages. The summary shows how many pages are indexed and how many are not, with a reason for each page that is not.
What is right: an indexed count near the number of pages you want in search, and reasons you understand for the rest, such as redirects or pages you excluded on purpose. Google describes “Discovered, currently not indexed” as a page it found but has not crawled yet, and “Crawled, currently not indexed” as a page it crawled but chose not to index, which may still change.
What we saw: 20 indexed and 7 not indexed on 8 October, with 82 pages in the sitemap. On 12 October the report showed 22 indexed and 7 not, but its data date was 9 October, the day before the sitemap was read. The report lags, so it cannot yet show whether the new sitemap reading changed anything.
Where readers get stuck: the report counts the pages Google knows about, not the pages you have. A site with 82 pages and 29 known addresses is missing from the report, not failing in it. Check the data date under the chart before you compare numbers from two days.
Step 3: the URL inspection of one page
Where: the search field at the top of Search Console. Paste the full address of a page that matters, for example your pricing or booking page, and press Enter. This reads Google’s stored result; the Test live URL button is a separate check of the page as it is now.
What is right: “URL is on Google”. Google adds that this does not guarantee the page appears in results; search for the address yourself for a definitive answer.
What we saw: on 8 October the pricing page was “URL is unknown to Google”, with no referring sitemap or page. Google’s help text for that label says it has never seen the address and that you should request indexing. On 12 October the same page showed “URL is on Google” after the request made on 9 October.
Where readers get stuck: the field expects the complete address with protocol and domain. A domain property covers all subdomains and both protocols; a URL-prefix property covers only addresses that start with that prefix, so make sure you are in the right property.
What the check does not tell you
- Nothing about ranking. An indexed page can sit on page nine.
- Nothing about traffic. Clicks and impressions are in the Performance report, and visits are in your analytics.
- Nothing about why Google chose not to index a crawled page.
- Nothing about Bing or other search engines, which keep their own tools and reports.
If something is wrong
The sitemap lists the wrong addresses or is stale: open the sitemap in a browser and read the addresses in it. They must be complete and belong to the site you are checking; Google will attempt to crawl them exactly as listed. Fix the file, then submit it again in the Sitemaps report. Google calls a submitted sitemap a hint and does not guarantee that it will download it or use it. Our Swedish domain was read the same evening; the English one two days later.
An important page is unknown or not indexed: use Request indexing in the URL inspection for that page. Google states that there is a quota for individual requests, that repeating a request does not speed anything up, and that crawling can take a few days to a few weeks with no guarantee of inclusion. We hit the quota after seven pages on 9 October and requested eight more on 12 October; Google does not publish the number, so we do not either.
Many pages are missing: do not request them one by one. A correct sitemap, internal links from pages Google already knows, and patience do more. Write down the date, the counts and what you changed, and look at the three screens again after a couple of weeks.
If you use Savri, the Google connection shows clicks and impressions per page in the dashboard, but the three screens above live in Search Console and work without any analytics tool.
Sources
Google, Sitemaps report, Page indexing report, URL Inspection tool, Ask Google to recrawl your URLs and Build and submit a sitemap, all read on 12 October 2026. Our own figures come from Search Console for our site on 8, 9 and 12 October 2026 and from the site’s version history.