If people can’t find your website on Google, inspect the affected page in Search Console first. Find out whether Google indexed the preferred URL, then check the searches that show it. An indexing problem and a low ranking need different fixes.
Start with one page that matters to your business, such as a service page. Your homepage appearing for your company name doesn’t tell you whether that service page appears for the searches customers use.
Choose the right diagnostic path
| What you find | What it means | Next action |
|---|---|---|
| URL Inspection says the page is not indexed | That URL is not currently eligible as an indexed result | Read the reason and check whether another canonical represents it |
| Page is indexed and relevant queries have impressions, but low positions | Google shows it, often below results people choose | Improve the page for those specific searches |
| Page is indexed but queries describe a different service or topic | Its content may be attracting the wrong audience | Clarify the page purpose and inspect competing pages on your own site |
| Page appears for others but not for you | Search context or the query may differ | Compare the same country, device and query in Search Console |
Treat this as a route through the evidence. A zero in a query table alone cannot prove why a page is absent, especially on a new site with little data.
Check the exact URL in Search Console
Open your verified property and paste the full page URL into the inspection bar. Use the HTTPS hostname and path that visitors should reach. If you haven’t verified ownership, follow how to get your website on Google first.
Read the stored indexing result before running a live test. The stored result describes Google’s indexed version. A live test checks the page as it is now, so it helps verify a recent repair but cannot confirm that Google has indexed that repair.
Expand the indexing details and record the reported reason, last crawl, whether crawling is allowed, and the Google-selected canonical. A canonical is the URL Google treats as the main version when it finds similar pages.
For example, suppose you inspect https://example.com/services/ but Google selects an old hostname. Check your redirects, internal links, canonical tag and sitemap for conflicting addresses. The www and non-www guide explains how to test the hostname behavior. This is an illustrative example, not a diagnosis of your site.
Google’s URL Inspection documentation explains the report fields and what the live test cannot establish.
A site: search is only a rough check
You can search site:example.com to look for pages from your domain. Results can help you spot an unexpected hostname or old URL, but the list is not a complete inventory of Google’s index. No results do not conclusively prove that the site is unindexed. Use URL Inspection for a specific page rather than counting site-search results.
Fix the reported indexing problem
Some excluded URLs are intentional. A redirected old URL, a duplicate version and a private account page generally do not need to become separate search results. Focus on the useful public page you want people to find.
| Reported issue | Check | Suitable response |
|---|---|---|
| Excluded by noindex | Page HTML and HTTP headers | Remove the directive only when the page should be public in search |
| Blocked by robots.txt | The matching user-agent group and path | Correct an accidental crawl block and retest |
| Redirect or duplicate | Destination and selected canonical | Keep intentional consolidation; fix a wrong destination |
| Server error or failed fetch | Hosting, firewall and response status | Restore reliable access before changing content |
| Crawled, currently not indexed | Duplication, content usefulness and internal links | Give the page a distinct purpose and a clear discovery path |
| Discovered, currently not indexed | Access and links from existing pages | Make the page reachable and useful, then monitor rather than repeatedly submitting |
The robots.txt checker can show fetch results and listed rules. It cannot prove Google indexing, and a flat list of rules needs the context of the crawler group. Also remember that robots.txt controls crawling, not access security. A login protects private information.
After fixing a genuine blocker, publish the change and run a live test. Request indexing when appropriate, then record the date. Repeated requests for the same unchanged URL do not provide a dependable shortcut.
Find the searches that already show your page
In Search Console’s Performance report, select Web search and add an exact Page filter for your preferred URL. Turn on clicks, impressions, click-through rate and average position, then read the Queries tab.
An impression means your result appeared according to Google’s reporting rules. A click means someone selected it. CTR is clicks divided by impressions. Average position describes the recorded appearances; it is not a permanent rank for everyone.
Search Console omits some queries for privacy and has reporting limits, so the query rows may not add up to the chart totals. Keep page totals and query totals separate when recording a baseline.
Suppose a repair guide gets impressions for a relevant troubleshooting question at an average position around 25. Check whether the page actually helps the reader identify and fix that fault. Add a clear diagnosis, an example and limits on when professional help is needed. Changing only the meta description leaves that content question unresolved.
If the page instead attracts searches for a service you do not offer, do not add that service just to chase impressions. Clarify the page and links that describe it. Useful traffic comes from people whose needs match the business.
Compare like-for-like periods
Compare the latest complete 28 days with the preceding 28 days. Keep the page, search type, country and device filters consistent. On a seasonal business, a year-over-year view may add context once you have enough history.
Read impressions and position together. If impressions fall while average position improves, low-ranking queries may have disappeared from the mix. That does not establish a recovery. Check individual queries with enough appearances to make the comparison useful.
For a small site, a handful of impressions or one click can swing percentages sharply. Record the actual counts alongside percentages, and avoid declaring a winning title after a few visits. Google’s Search Console performance guide explains the metrics.
Decide what to change on an indexed page
Use the relevant queries to check the opening answer, title and page content. A searcher asking how to fix something needs the repair steps and the checks that prove the repair worked. A person comparing products needs actual differences and constraints.
Look at internal links next. Can someone reach the page from a related guide or the main site navigation? Use descriptive link text where that next step helps the reader. Creating another article with the same purpose can make the site harder to navigate, so inspect overlap before publishing.
Technical access remains worth checking even when the page is indexed. A recent deployment could introduce an error that Google’s stored report has not yet reflected. Test the published page on a phone, follow its main links and complete its important action, such as a test enquiry.
Avoid misleading tests
A private browser window removes some account and history effects, but location, language, device and changing results still matter. Use personal searches to inspect the result presentation, not as your only ranking measurement.
Keep branded searches separate from general searches. Finding your company name is useful, but it does not prove visibility for the service you sell. Also check the spelling and exact search phrase before comparing your result with someone else’s.
Do not infer a penalty from a traffic dip alone. Search Console has separate Manual actions and Security issues reports. Inspect them when investigating a significant decline, and compare the timing with deployments and page changes before choosing a cause.
Your next check
Record the preferred URL, its indexing status, selected canonical and latest complete 28-day clicks and impressions. Choose one fix supported by that evidence, assign an owner, and write down how you will verify it.
After the change, separate the technical retest from the traffic review. A redirect reaching the right page proves the redirect works. More relevant impressions or enquiries require later measurement. The DIY SEO guide includes a downloadable checklist for keeping those steps together.
FAQ
Does no result for a site: search mean Google hasn’t indexed me? No. Site searches are incomplete. Inspect the exact URL in Search Console and check its stored indexing status and Google-selected canonical.
Can a page be indexed without getting clicks? Yes. It may appear infrequently, rank too low for the relevant searches, or attract searches it does not answer well. Review the page-filtered performance report before deciding what to change.
Does passing the live URL test guarantee indexing? No. The live test checks current accessibility and some indexability conditions. It cannot guarantee indexing, predict the canonical Google will select or confirm future rankings.
How long should I wait after a fix? Verify the published technical change immediately. Google needs time to recrawl and process it, with no guaranteed deadline. Record the date and compare complete reporting periods instead of resubmitting the unchanged page every day.