Google Search Console: Using Data to Diagnose Website Visibility Problems

Key Takeaways

• Set up a Domain property in Search Console first, because a URL-prefix property can hide traffic and indexing data from other versions of your site.
• The Page Indexing report’s status labels, such as “Crawled – currently not indexed” and “Discovered – currently not indexed,” each point to a different cause and a different fix.
• Match the symptom to the report: a sudden drop in impressions, a few missing pages, and pages ranking low all call for different checks.
• Filtering the Performance report by page, query, device, and date comparison shows you where visibility is slipping, not just that it is.
• A 30-minute weekly routine catches most problems before they cost you calls, and most fixes take days to several weeks to show up in the data.
• If Search Console shows no errors and visibility is still weak, the cause is usually content quality, internal linking, or authority rather than a technical fault.

Set Up Search Console Correctly Before You Diagnose Anything

Start with a Domain property, not just a URL-prefix property. A Domain property combines data from every protocol and subdomain (http, https, www, and non-www), so you see the whole picture in one place.

A common setup mistake is verifying only the exact address you type into the browser. If Google has indexed another version, such as the non-www address, your data looks incomplete and your diagnosis will be wrong. Domain properties are verified through a DNS record at your domain registrar, which usually takes a few minutes if you have access to the account.

Setup checklist

• Verify a Domain property using the DNS method.
• Add your web developer, marketing contact, or agency as a user with the appropriate permission level instead of sharing one login.
• Submit your XML sitemap under Sitemaps, and confirm it lists only pages you want indexed.
• Turn on email notifications so critical issues reach someone who will read them.
• Note the date you set it up. Search Console only shows data from when the property was verified, plus a limited recent history, so earlier problems may not be visible.

If you inherited a site from a previous developer, check the Settings page for the list of verified owners. Remove anyone who should no longer have access.

How to Read the Page Indexing Report Status by Status

The Page Indexing report (the successor to the older Coverage report) sorts every URL Google knows about into “Indexed” or “Not indexed” and gives a reason for each excluded page. The reason is the diagnosis, so read it before you change anything.

Not every “Not indexed” label is a problem. Pages such as login screens, cart pages, and filtered URLs are meant to stay out of search. The goal is to make sure the pages that bring in customers are in the indexed group.

What “Crawled – currently not indexed” tells you

This status means Google looked at the page and decided it wasn’t worth keeping, at least for now. It is common on service pages that repeat the same paragraphs with a different city name, or on short pages that say little beyond a heading and a phone number.

Improve these pages with specifics only your business can provide: the jobs you handle, how pricing works, service area details, photos of real work, and answers to questions customers ask on the phone. Our guide to evaluating your site for thin content walks through how to judge which pages to expand, merge, or remove.

What “Discovered – currently not indexed” tells you

This status usually means Google found the URL, often in your sitemap, but hasn’t prioritized crawling it. On a small site, the most common reason is that nothing else on the site links to the page, which signals low importance.

Add links to the page from related service pages, blog posts, and your main navigation where it makes sense. Our article on contextual internal linking explains how to place those links so they help both visitors and crawlers.

Diagnose by Symptom: Which Report to Open First

Pick the report based on what you’re seeing, not on habit. Opening the wrong report first is how people spend hours fixing things that aren’t broken.

If the symptom is a site-wide disappearance, check recent changes first. Ask who touched the site in the last few weeks: a redesign, a plugin update, a new host, or a staging site pushed live. Most sudden drops trace back to a change someone made.

Get More From the Performance Report

The Performance report is most useful when you filter it, because the site-wide totals hide what’s actually changing. Four filters do most of the work: date comparison, page, query, and device.

Compare date ranges properly

Compare the last 28 days to the previous 28 days, or to the same period last year if your business is seasonal. An HVAC or lawn care company will naturally see swings between seasons, so a year-over-year comparison avoids false alarms.

Sort by the difference in clicks or impressions to find the pages and queries that lost the most. That list is your priority queue.

Separate branded from non-branded searches

Filter queries to exclude your business name. Branded searches come from people who already know you, so they don’t tell you whether new customers can find you. Non-branded queries, such as “roof repair near me” or a service plus your city, show whether your visibility is actually growing.

Find pages that are close to ranking well

Look at queries where your average position is somewhere between 8 and 20 and impressions are meaningful. These pages already have Google’s attention but sit below the first page or low on it. Improving the title, adding missing subtopics, and linking to the page from related content often moves these further than writing something new.

Check our list of critical on-page SEO elements to see what these pages may be missing.

Read position and clicks together

• High impressions, low clicks, good position: your title and description aren’t earning the click. Rewrite them to match what the searcher wants.
• High impressions, low clicks, poor position: the page isn’t competitive for that query yet. Strengthen the content or target a more specific search.
• Low impressions on a page you care about: Google may not see it as relevant to the topic. Check indexing first, then content and internal links.

Average position is an average across many searches, locations, and devices, so treat it as a trend line rather than an exact ranking. Searchers in Greenville and Asheville can see different local results for the same phrase.

Use the Sitemaps, Crawl Stats, and Core Web Vitals Reports

These three reports explain why Google may be crawling your site slowly or ignoring parts of it. They’re easy to skip, but each answers a specific question.

Sitemaps report

The Sitemaps report shows when Google last read your sitemap and how many URLs it found. Your sitemap should list only canonical, indexable pages that return a normal response.

If it includes redirected URLs, 404 pages, or noindexed pages, you are sending Google mixed signals. Clean it up and resubmit. Many content management systems generate sitemaps automatically, so check the settings of your SEO plugin if the list looks wrong.

Crawl Stats report

You’ll find Crawl Stats under Settings. It shows how many requests Google made, how quickly your server responded, and whether it hit errors. A rising average response time or a pattern of server errors suggests hosting problems that can slow crawling.

For deeper fixes on blocked or unreachable pages, see our guide to fixing crawlability issues that block indexing.

Core Web Vitals and page experience

The Core Web Vitals report groups your URLs into good, needs improvement, and poor, based on real-user data for loading speed, responsiveness, and visual stability. It only appears if enough visitors have used your site, so a low-traffic site may show little or no data.

Fix groups of similar pages together. If every service page uses the same template and fails the same check, one template fix repairs all of them. For the mobile side of this, read about mobile-first indexing and invisible sites.

Check Manual Actions and Security Issues

Manual Actions and Security Issues are the first places to look when visibility collapses with no technical explanation. Both reports should say “No issues detected.” If they don’t, that becomes your top priority.

A manual action means a human reviewer at Google determined that your site violates its spam policies. Typical causes include unnatural links, spammy or auto-generated content, and hidden text. The report names the issue and shows which pages are affected, and you can submit a reconsideration request after cleaning it up.

Security Issues flags hacked content, malware, or deceptive pages. Small business sites on outdated plugins are common targets, and the injected pages are often invisible to you because they sit on odd URLs. If this report shows anything, have your developer or host clean the site and fix the vulnerability before requesting a review.

A 30-Minute Weekly Search Console Routine

A short, consistent check beats an occasional deep dive. Set a recurring calendar slot and work through the same list each time.

1. Read the Overview and any email alerts (2 minutes). Look for new issues Google has flagged.
2. Check Manual Actions and Security Issues (1 minute). Both should be clear.
3. Review Page Indexing (5 minutes). Look for new reasons or sharp jumps in the “Not indexed” count, and spot-check that your money pages are still indexed.
4. Compare Performance over the last 28 days (8 minutes). Sort pages and queries by change in clicks and note the biggest losers and gainers.
5. Check Core Web Vitals and Mobile experience (3 minutes). Watch for new groups of poor URLs after site updates.
6. Inspect new or updated pages (5 minutes). Use URL Inspection to confirm that pages you published or edited are indexed.
7. Log what you found (6 minutes). Write down the issue, the date, the owner, and the planned fix so patterns are visible later.

A simple shared spreadsheet is enough for the log. After a few months it also becomes a record that links site changes to traffic changes.

How Long Fixes Take to Show Up

Most fixes take from a few days to several weeks to appear in Search Console, and ranking gains can take longer. Requesting indexing speeds up discovery, but it doesn’t guarantee a page will be indexed or ranked.

After you click “Validate Fix” on an issue, Google re-checks the affected URLs over time. The validation can take a couple of weeks, and it may fail if some URLs still have the problem. Fix every example in the list, not just the first one.

If the problems are widespread, a structured plan helps. Our website recovery roadmap shows how to sequence the work.

Search Console Mistakes to Avoid

Most diagnosis errors come from acting on a single data point or fixing things that were never broken. These are the mistakes we see most often on small business sites.

• Panicking over every “Not indexed” page. Some exclusions are normal and expected, like duplicate parameter URLs and thank-you pages.
• Requesting indexing repeatedly. Submitting the same URL over and over doesn’t speed things up. Fix the underlying cause, then request once.
• Blocking pages in robots.txt to remove them from Google. Robots.txt stops crawling, not indexing, and it prevents Google from seeing a noindex tag. Use noindex or remove the page instead.
• Ignoring the date range. Judging performance from a few days of data, or comparing a busy month to a slow one, leads to wrong conclusions.
• Changing many things at once. If you rewrite content, redesign templates, and change URLs in the same week, you won’t know which change helped or hurt.
• Leaving junk in the sitemap. Redirected, noindexed, and error pages in your sitemap waste crawl attention.
• Treating Search Console as the whole picture. It shows Google search data only, so pair it with call tracking, form submissions, and Google Business Profile insights to see real lead impact.

When Search Console Shows No Errors but Visibility Is Still Weak

If your pages are indexed and no errors appear, the problem is almost always relevance or authority rather than a technical fault. Indexed only means Google has stored the page. It doesn’t mean Google thinks the page deserves to rank.

Work through these questions in order:

• Does the page match what searchers want? Look at what currently ranks for your target search. If competitors show pricing, process steps, and local proof and you offer a short description, you’re underserving the query.
• Is the page supported by the rest of your site? A service page with no related content, few internal links, and a buried place in the navigation looks unimportant.
• Do other sites vouch for you? Local citations, community links, and mentions from trusted sites build authority. Our guide to building a healthy backlink profile covers safe ways to earn them.
• Is your local presence complete? For map-style results, your Google Business Profile, reviews, and consistent business details matter alongside your website.

Pages that are indexed but absent from search results also can’t be cited in Google’s AI-generated answers, since those features draw on content Google can index and rank. Indexing is the entry requirement, and clear, specific, well-structured content is what earns the mention.

Want a Second Set of Eyes on Your Search Console Data?

If you’ve worked through these reports and still can’t tell what’s holding your site back, a short review of your data can usually pinpoint it. You can talk with the PushLeads team about your Search Console findings, and we’ll tell you what we see and what is worth fixing first.

Frequently Asked Questions

How often should I check Google Search Console?

A weekly check is enough for most small business sites. Set up email alerts so serious problems reach you sooner, and run an extra check after any redesign, migration, or major plugin update. Spending 30 minutes a week is better than a long review once a quarter.

Why does Search Console say “Crawled – currently not indexed”?

It means Google visited the page but decided not to include it in the index for now. The cause is usually thin, repetitive, or low-value content, though weak internal linking and site-wide quality issues can contribute. Improve the page with unique, specific information and link to it from related pages, then request indexing once.

Does requesting indexing guarantee my page will show up?

No, it only asks Google to recrawl the URL sooner. Google still decides whether the page is worth indexing and where it should rank. If a page keeps getting excluded after you request indexing, look at its content quality, canonical tags, and internal links.

How long after fixing an issue will Search Console show improvement?

Expect anywhere from a few days to several weeks for Google to recognize a fix, and often longer for rankings to change. Technical fixes like removing a noindex tag tend to show up faster than content improvements. Use the “Validate Fix” button and monitor the Page Indexing report over the next few weeks.

Why are impressions down when my pages are still indexed?

Impressions can drop because rankings fell, search demand changed seasonally, competitors improved, or Google changed how it shows results for that query. Compare the same date range from last year, then filter by page and query to see where the loss is concentrated. If the drop is sudden and site-wide, also check Manual Actions and recent site changes.

Do I need a Domain property or a URL-prefix property?

A Domain property is the better default because it covers every version of your site in one view. A URL-prefix property only tracks the exact address you enter, so it can miss data from other versions. You can keep a URL-prefix property as well for filtering specific sections.

Can Search Console tell me why my Google Business Profile isn’t ranking?

No, Search Console reports on your website’s organic search performance, not on your map listing. Your Google Business Profile has its own performance data inside the profile dashboard. Use both together to see how people find you through website results and local map results.