The clearest way to check if your website is indexed is to inspect its important page addresses in Google Search Console. A website is a group of pages, so one indexed homepage does not prove that every article or service page is indexed.
Use this guide to build a small status record. It covers what to check and what the evidence means. If you find a problem, use the separate missing website guide to plan the repair.
The short answer
- Check important page addresses, not just the homepage.
- Keep live test results separate from recorded index status.
- Use exact counts and clear scope when reporting a batch of pages.
How this guide was made
Google's search operator, URL Inspection and Page indexing documentation was checked on October 10, 2026. The worksheet and sample report are original teaching examples. They do not claim actual index coverage for SnapRebuild or another site.
Sources checked .
Make a list of the pages that matter
Start with the homepage, each main service page and the articles you recently published. Use the final public addresses copied from your browser. Keep a page name beside each address so someone else can understand the list.
If you launched twenty articles, keep all twenty in the list. You can inspect a few first to look for a shared problem, but call that a sample. Do not report that the whole batch is indexed after checking only one article.
Leave account pages, private drafts and internal tools out of your success target. The goal is to check content meant for public search. A larger indexed page total is not automatically better for the business.
Record the scope before the results
Write a sentence such as: this review covers the homepage, three service pages and five new guides. This prevents a later reader from treating a limited check as a review of the whole site. Keep old and new addresses distinct if a redesign changed them.
Use a site search as a quick clue
You can type site:example.com into Google to look for results from a domain. Replace the example with your own domain. You can also narrow the search to a page address or part of the site.
Google says the site operator does not always return every indexed URL. Its result count is not a complete inventory. Finding a page is useful evidence that it appears in that search, but not finding it is a reason to investigate further.
Save the date and the query if you use this check. Search results change, and two people may not see the same set. Avoid putting a rough result count into a report as an exact number of indexed pages.
Source for this section: [1] Google guidance on the site search operator
Inspect the exact page in Search Console
Select the property that contains your page. Paste its complete URL into URL Inspection. Read the recorded indexing result, then note the last crawl date and Google's chosen canonical address if available. That address is the version Google prefers.
Write down the status as shown. If it is not indexed, save the reason instead of replacing it with a broad label such as SEO error. The reason may describe an intentional duplicate or a real access issue.
Do not change the address halfway through the check. The www version, a redirected old address and a new destination may have different records. Put each in its own row when you need to compare them.
Source for this section: [2] Google URL Inspection help
Keep the live test separate from the index record
The recorded result describes Google's stored information. The live test checks the current page for some access and indexing conditions. Passing that live test does not mean the page is already indexed, and it does not check every condition for search appearance.
This difference matters after a repair. For example, your team may remove an unwanted setting today while the stored crawl record is older. Record both times. You can then say the current page passes the live check while the index record still needs another review.
Source for this section: [2] Google URL Inspection help
Use a page status worksheet
The worksheet below is a suggested format, not a result from a live site. Fill it with actual evidence from your own review. A blank field is more honest than a guessed status.
For each row, attach a screenshot or exported result when available. Include the date you checked it and the person who checked it. If the result is unclear, keep the exact message for the builder to review.
| Field | What to record | Why it helps |
|---|---|---|
| Page address | Exact public URL | Identifies the page checked |
| Intended state | Should appear in public search | Makes intentional exclusions clear |
| Recorded status | Status and stated reason | Shows the current report |
| Last crawl | Date shown, or unavailable | Separates old evidence from a new change |
| Preferred address | Chosen canonical when shown | Explains some duplicate results |
| Live check | Result and test time | Records the current access check |
| Next review | Owner and review date | Keeps open questions assigned |
Use the Page indexing report for patterns
The Page indexing report groups known URLs by status and reason. Use it to spot patterns, such as many pages affected after a template change. Its example URL lists are limited, so use URL Inspection for a specific page.
Google does not expect every possible URL to be indexed. Duplicate versions and removed pages can be excluded for valid reasons. Check whether your important preferred pages are present, rather than trying to make every excluded count disappear.
For a small site, begin with the short list you made. If several important pages share a reason, give that group to the builder. If only one new guide differs, focus the next review on that guide.
Source for this section: [3] Google Page indexing report help
Report confirmed results without overstating them
Use counts with a clear denominator. For example, an imaginary report might say that eight of ten planned pages were inspected, six were reported indexed, and two need review. The remaining two have not been checked. This is a reporting example, not a benchmark.
Keep published, submitted and indexed totals in separate rows. Publishing makes a page public. Submitting asks a search engine to discover or revisit it. Indexing is a search engine decision. A receipt for one step cannot confirm the next.
Close each review with the open task and its owner. If all important pages are indexed but visitors are scarce, move on to search queries and useful enquiries. Rechecking the same status every hour adds little to that question.
Common questions
Can I check indexing without owning the site?
You can search for its pages publicly, but that is incomplete evidence. Detailed Search Console reports require access to the relevant property.
Does URL is on Google mean I rank for my target keyword?
No. It means the page is indexed and eligible to appear, with stated limits. It does not prove a position for your target search.
How often should a small business check?
Choose a routine tied to publishing and meaningful site changes. Keep a follow up date for open issues. There is no need to treat repeated daily checks as a way to make indexing happen faster.
Sources and further reading
Numbered links beside each section point to the source used there. Our examples and checklists are guidance from SnapRebuild. They are not claims of test results. Product details can change.
SnapRebuild sells a website building service. These guides are published under our editorial team name and use AI for research and writing. This is not a claim of independent expert review. Read how we make and update our content. Found an error? Tell us.
Ready for a fresh start?
Bring your website or your business idea. Explore a SnapRebuild preview and decide what comes next.
Try your free preview