How to Check If a Page Is Indexed by Google: URL Inspection and site:
Before you work on why a page is not ranking, you need to know whether Google has indexed it at all. That sounds simple, but the common checks answer different questions. A site: search can miss pages that are indexed, the live test in Search Console shows whether a page could be indexed rather than whether it is, and a crawl by Googlebot does not mean the page was kept. This guide shows the reliable ways to check if a page is indexed: URL Inspection for a single address, the Pages report for the whole site, site: searches as a quick hint and your own server logs for crawling. It also explains how each can mislead and what to do when a page is missing.
What indexed actually means
A page is indexed when Google has crawled it, processed it and stored it in its index, so it is eligible to appear in search results. Being indexed does not mean the page ranks for anything useful; it only means it can be shown. Equally, a page that Google has crawled is not necessarily indexed: Google crawls far more URLs than it keeps.
There are three separate stages, and each check in this guide looks at a different one:
| Stage | Question | Where to look |
|---|---|---|
| Discovered and crawled | Has Googlebot fetched the URL? | Your server access logs, Crawl stats, URL Inspection last crawl date |
| Indexed | Is the URL stored and eligible to show? | URL Inspection, the Pages report |
| Shown in results | Is it appearing for searches? | Performance report impressions, a search for the page |
There is also the question of which URL is indexed. If Google treats your page as a duplicate of another address, it indexes that other address, the canonical, and your URL is reported as not indexed even though its content is in Google.
Check with URL Inspection in Search Console
URL Inspection is the only check that tells you directly what Google's index holds for an exact URL on a site you own. Open the property in Search Console, paste the full address into the search bar at the top and press Enter. The top result is one of these:
- URL is on Google. The page is indexed and can appear in results.
- URL is on Google, but has issues. It is indexed, but something such as a structured data item or a video has a problem.
- URL is not on Google. It is not indexed. Open Page indexing below to see the reason, such as Crawled, currently not indexed or Excluded by noindex tag.
Under Page indexing you will also see whether the page is in a sitemap, the referring page, the last crawl date, whether crawling and indexing are allowed, and two canonical fields: the user-declared canonical and the Google-selected canonical. If those differ, Google has indexed a different URL instead of yours.
The inspection result reflects Google's last processed crawl, so a change you made today will not show until the page is recrawled. You can request indexing from the same screen; there is a daily limit, and a request does not guarantee indexing.
Check many pages with the Pages report
For a site-wide view, open Indexing and then Pages in Search Console. It splits known URLs into Indexed and Not indexed, and lists the reasons for the second group with the number of URLs under each. Click a reason to see example URLs. Typical reasons include:
| Reason shown | What it usually means |
|---|---|
| Crawled, currently not indexed | Google fetched it and chose not to index it, often a quality or duplication judgement |
| Discovered, currently not indexed | Google knows the URL but has not crawled it yet |
| Excluded by noindex tag | The page told Google not to index it |
| Alternate page with proper canonical tag | Your canonical points elsewhere and Google agreed |
| Duplicate, Google chose different canonical than user | Google picked another URL as the main version |
| Page with redirect, Not found (404) | The URL no longer serves a page of its own |
The report lags by a few days and the example lists show up to 1,000 URLs, so for a large site filter it by sitemap: choose a submitted sitemap from the menu at the top, and the counts then cover only the URLs you care about. For what to do about each reason, see crawled, currently not indexed, discovered, currently not indexed and Search Console errors explained.
Confirming with the Performance report
Impressions are a strong sign of indexing, because a page can only be shown in results if it is in the index. Open Performance, choose Search results, add a Page filter with the exact URL and set the date range to the last 28 days or longer. Any impressions mean Google has indexed the page and shown it to someone. No impressions does not prove the page is missing, because an indexed page can simply rank too low to be seen, but together with an inspection result it gives you a fuller picture.
For Bing, Bing Webmaster Tools has its own URL Inspection with similar wording, and it is worth checking separately, because other search services also draw on Bing results. A page can be in one index and not the other.
Using site: searches, and why they mislead
A site: search is quick and works for any site, including ones you do not own:
site:example.com/menu/cakes
site:example.com inurl:cakes
site:example.com "Lemon drizzle loaf"If the page appears, it is indexed. If it does not, that is not proof it is missing. Google says the site: operator does not return every indexed URL, and the count it shows at the top is a rough estimate that can swing widely from one search to the next. Results can also show the Google-selected canonical rather than the URL you typed, and they vary by location.
Use site: as a quick sign, not as evidence. Searching for a distinctive sentence from the page in quotation marks is another useful hint, because it shows whether Google has the text and which URL it attributes it to.
Check crawling in your own server logs
Your access logs show whether Googlebot has requested the page at all, and when. That answers a different question from indexing, but it is the first thing to establish when a page is missing. On a typical Linux server, Plesk or nginx host:
sudo grep -h "Googlebot" /var/log/nginx/access.log* | grep " /menu/cakes " | tail -20
# Plesk keeps per-domain logs
sudo grep -h "Googlebot" /var/www/vhosts/example.com/logs/access_ssl_log | grep "/menu/cakes" | tail -20Each line shows the date and the status code returned. A 200 means Google received the page; 3xx, 4xx or 5xx responses explain why it may not be indexed. Anyone can claim to be Googlebot, so verify an address with a reverse lookup followed by a forward lookup:
host 66.249.66.1
# expect a name ending in googlebot.com or google.com, then
host crawl-66-249-66-1.googlebot.comIf the page has never been requested, Google probably has not discovered it, so improve internal links to it and list it in your XML sitemap.
A worked example
Example Bakery publishes /menu/lemon-drizzle and, a week later, site:example.com/menu/lemon-drizzle shows nothing. URL Inspection reports URL is not on Google with the reason Discovered, currently not indexed, and no last crawl date. The server log has no Googlebot request for the path. The page is linked only from a seasonal banner loaded by JavaScript. The bakery adds a normal link from the cakes category page, confirms the URL is in the sitemap and requests indexing. Three days later the log shows a Googlebot request with a 200, and URL Inspection reports URL is on Google.
The fix, step by step
Step 1
Inspect the exact URL
Open the correct Search Console property, paste the full address including https into the inspection bar and press Enter. Read the headline result: URL is on Google, URL is on Google but has issues, or URL is not on Google. Copy the address straight from the browser so the protocol, www and trailing slash match exactly, because each variation is a different URL to Google.
Step 2
Read the indexing details
Expand Page indexing in the inspection result. Note the reason if the page is not indexed, the last crawl date, whether crawling and indexing are allowed, and the sitemap the URL was found in. Compare the user-declared canonical with the Google-selected canonical. If they differ, Google has indexed another address in place of yours, and the fix is about duplication rather than discovery.
Step 3
Run the live test
Press Test live URL to see whether Google could index the page as it is now. The test reports robots.txt blocks, noindex tags, server errors and redirects. Check the rendered HTML and screenshot to confirm the main content is present. Remember that passing this test only shows the page is indexable; the headline result from the previous step is what tells you if it is in the index.
Step 4
Check the Pages report
Open Indexing and then Pages, and filter by your submitted sitemap. Look at the counts for Indexed and Not indexed, and open each reason to see example URLs. This shows whether the page is an isolated case or part of a pattern, such as a whole template that is noindexed or a section that Google is crawling but choosing not to index. Note that the report lags by a few days.
Step 5
Try a site: search as a hint
Search Google for site: followed by the exact URL, then for a distinctive sentence from the page in quotation marks. If the page appears, it is indexed. If it does not, treat that as a hint only, since the operator does not list every indexed page. Look at which URL is shown, because it may be the canonical Google chose rather than the address you checked.
Step 6
Look for Googlebot in your logs
Search your server access logs for requests from Googlebot to the page path with grep, and note the dates and status codes returned. Verify a sample of the addresses with a reverse and forward DNS lookup. No requests means a discovery problem; error or redirect codes mean a server problem; regular 200 responses with no indexing point to a quality or duplication decision instead.
Step 7
Fix the cause and request indexing
Act on what you found: remove a stray noindex or robots.txt block, fix errors and redirects, add internal links from relevant pages, list the URL in the sitemap, or improve thin or duplicated content. Then press Request indexing in URL Inspection. Requests are limited per day, so prioritise your most important pages, and do not submit the same URL repeatedly, because it does not speed things up.
Step 8
Recheck after recrawl
Wait several days, then inspect the URL again and check the last crawl date has changed. Confirm the headline now says URL is on Google, and check the Performance report filtered to the page for impressions. If it is still not indexed after a few weeks with a fresh crawl date, the reason shown now is the one to work on, so follow the guide for that specific status.
Edge cases worth knowing
- Wrong property. URL Inspection only works inside the property that owns the URL. An http, www or subdomain address needs a matching property, or a Domain property covering all of them.
- Indexed under another URL. Check the Google-selected canonical. If it is a different page, the content is indexed but your URL is not. See alternate page with proper canonical tag.
- Indexed but invisible. A page can be indexed and get no impressions because it ranks too low. Check the Performance report filtered to that page before assuming it is missing.
- Recently removed. A temporary removal hides a URL from results while it stays indexed, so check the Removals section if a page vanishes suddenly.
Keeping track of indexing
Submit an accurate sitemap and use the sitemap filter in the Pages report as your main monthly check. Inspect each important new page a few days after publishing, and look for Googlebot requests in your logs rather than guessing. If a page should be out of Google, use noindex and confirm it the same way. For a wider review of whether your SEO work is landing, see how to check your SEO is working.
1. How do I check if a page is indexed by Google?
Use URL Inspection in Google Search Console: paste the exact URL into the bar at the top, and the result says either URL is on Google or URL is not on Google, with the reason. That is the only direct check of Google's index for a specific address. For a site you do not own, search for site: followed by the URL, but treat a missing result as a hint rather than proof, because that operator does not show every indexed page.
2. How do I check whether a page is indexed or not without Search Console?
Search Google for site: followed by the full page address, or for a distinctive sentence from the page in quotation marks. If the page appears, it is indexed. If it does not, it may still be indexed, because site: results are incomplete and can show a canonical URL instead. Your server logs can confirm whether Googlebot has fetched the page. For a reliable answer on your own site, verifying it in Search Console is worth the few minutes it takes.
3. Why does site: show fewer pages than Search Console?
The site: operator is not designed to list a full index and the count it shows is a rough estimate that can change from one search to the next. Search Console's Pages report is based on Google's indexing data for your property, so it is the figure to rely on. Differences of hundreds or thousands are normal on larger sites. Use site: for quick spot checks of single pages and Search Console for counts.
4. What does URL is not on Google mean?
It means the exact URL you inspected is not in Google's index, so it cannot appear in results. The Page indexing section explains why, for example Discovered, currently not indexed, Crawled, currently not indexed, Excluded by noindex tag, or a redirect or 404. It can also mean Google indexed a different URL as the canonical for the same content. Read the reason and the two canonical fields before deciding what to fix.
5. Does passing the live test mean my page is indexed?
No. The live test checks whether Google could index the page as it stands now, by fetching it and looking for blocks, errors and noindex tags. It does not show whether the page is actually in the index. The headline result at the top of URL Inspection, based on Google's last processed crawl, answers that question. A page can pass the live test and still be left out because of quality or duplication.
6. How long does it take for a new page to be indexed?
There is no fixed time. Pages on established sites with good internal links are often indexed within a few days, while pages on new or rarely crawled sites can take weeks. Linking to the page from relevant existing pages, listing it in your sitemap and requesting indexing in URL Inspection all help Google find it sooner. If your server logs show no Googlebot visit at all, discovery is the problem to solve first.
7. Can a page be crawled but not indexed?
Yes, and it is common. Google crawls many URLs it then decides not to store, often because the content is thin, very similar to other pages, or seen as low value. In Search Console these appear as Crawled, currently not indexed. Your logs will show Googlebot requesting the page with a 200 status, but URL Inspection reports it is not on Google. The fix is usually to make the page more useful and distinct.
The site audit crawls your pages and flags noindex tags, robots.txt blocks, redirects, errors and canonical conflicts, so you know which missing pages have a technical cause.
Open Site Audit Fixes →