How to Read Google Search Console (And What to Do With the Data)

A business owner logs in and sees 80,000 impressions, 600 clicks, 0.8% CTR, average position 21, 450 pages not indexed, a failed Core Web Vitals group, and an XML sitemap marked 'Success'. They do not know whether performance is improving, whether 450 excluded pages are a crisis, whether the title tags need replacing, or whether the site is stuck on page two.

Every number needs context: which pages, which searches, which device, which country, which period, whether the traffic is branded, whether the page should be indexed, and whether the pattern is seasonal. This guide explains how to read each report, what action to take, and when not to take action. It connects to the broader SEO strategy this guide sits inside.

Search Console becomes useful when every number leads to a question, and every question leads to a clearly defined action.

Straight answer

Google Search Console tells you how your site appears in Google: which searches you show up for, which pages earn clicks, and what Google can and cannot index. Read it monthly, not daily. Separate branded from non branded traffic first, then look for page two rankings and indexing problems. Everything else in this guide builds on those three habits.

What Google Search Console is

Google Search Console is Google's first party platform for understanding how a verified website appears and performs across Google Search. It can show search impressions, clicks, click through rate, average position, queries, ranking pages, device and country breakdowns, page indexing status, sitemap processing, Core Web Vitals groups, structured data enhancements, links, security issues, and manual actions.

What it does not show:

• Website sessions, time on page, or bounce rate

• Form submissions, sales, phone calls, or revenue

• Meta or Google Ads performance

• Every Google Business Profile action

• Every backlink or every search query

Use Search Console to understand Google visibility and technical eligibility. Use GA4, CRM, ecommerce, and call tracking data to understand what visitors did after arriving.

Search Console tells you how people reached the front door. It does not tell you whether they became customers after entering.

Before reading any report, confirm the property

A business may have separate properties for http, https, www, non www, subdomains, a blog folder, staging, an old domain, and the full root domain. A report can look incomplete simply because the wrong property is selected.

Domain property

A Domain property combines the root domain, subdomains, and different protocols. Google generally recommends using a Domain property where possible because it gives the broadest view, although it requires DNS verification.

URL prefix property

A URL prefix property covers only URLs beginning with the exact specified prefix. For example, https://www.example.com/ does not automatically include http://www.example.com/ or https://example.com/ or https://shop.example.com/.

Check Access, Ownership, and Account Continuity

Search Console access should not sit only with a former employee, an external developer, an old agency, or one personal Gmail account. Google's current permission levels include verified owner, delegated owner, full user, and restricted user.

Recommended access structure for a small business:

• Business controlled verified owner (not the agency)

• Second internal owner or recovery owner

• Agency as delegated owner or full user

• Developer as full user only where necessary

• Former suppliers removed after handover

Add an annual permission audit: check who has access, whether former staff remain, whether the business controls DNS verification, and whether the recovery email is current. Search data should remain an asset of the business, not disappear when a contractor relationship ends.

Connect Search Console with the rest of the measurement stack

The Google Ads association is worth doing if you run paid search, because comparing paid and organic queries side by side shows what Google Ads actually costs you to win versus what organic wins for free.

Recommended measurement stack:

• Search Console for organic visibility and indexation

• GA4 for on site behaviour

• CRM for lead quality and sales

• Call tracking for phone enquiries

• Ecommerce platform for orders and revenue

• Google Business Profile for local profile actions, backed by consistent local citations so the business details Google sees match everywhere else.

• Merchant Center for shopping feed diagnostics

Do not force Search Console to answer questions it was not designed to answer.

Start with the overview page, but do not stop there

The Overview page surfaces recent performance, indexing summaries, recommendations, Core Web Vitals, enhancements, manual or security warnings, and shopping features. It is useful as an early warning dashboard, not a complete SEO report. Recommendations appear only where Google believes there is an actionable suggestion, and they are optional rather than mandatory.

Check for:

• Sudden performance changes

• A sharp indexation drop

• New warnings or manual actions

• Core Web Vitals deterioration

• Security issues

• Recommendations worth investigating

Then open the underlying report before acting. The Overview page tells you where to look. The detailed report tells you what may have happened.

The performance report: the four numbers that confuse everyone

Clicks

How often someone clicked a qualifying link from Google to the site. A click does not equal a user, a session, an enquiry, or a sale.

Impressions

How often a qualifying result from the site appeared in Google. The exact impression rules depend on the result type. Some elements count when loaded, while carousel elements may need to be scrolled into view.

Click Through Rate (CTR)

Clicks divided by impressions. CTR is influenced by position, title, snippet, brand recognition, search intent, result format, competing results, ads, local packs, images, AI features, and whether the query can be answered without a click. Our guide to zero click search strategy explains how to measure value when impressions do not convert to clicks.

Average Position

The average topmost position occupied by the property or page across its impressions. It is not one live ranking, not a fixed position, and not necessarily the location seen by any individual user. Google recommends using average position primarily as a trend indicator. Search location, personalisation, device, query, and result type can all affect what an individual user sees.

Average position 12 does not mean the website permanently sits at number 12. It means its topmost result averaged position 12 across the impressions included in that view.

Read the four metrics together

Never interpret one metric in isolation.

Choosing the right date range

Different questions need different time windows.

Do not compare an incomplete current month against a complete previous month.

Use custom annotations to explain changes

Search Console now allows owners and full users to place custom annotations on performance charts. Use them for website redesigns, migrations, major content releases, technical outages, robots.txt mistakes, title tag rewrites, schema deployments, Core Web Vitals fixes, agency changes, and tracking changes.

Annotations are shared across the property and can make future changes far easier to interpret. They do not appear in comparison mode or the 24 hour view.

Six months later, 'traffic dropped around here' is not enough. Record what changed while the context is still known.

Queries: what people searched before seeing your website

The Queries tab reveals searches for which the property appeared. Use it to find existing demand, new topic opportunities, unexpected searches, service terminology, location modifiers, comparison and cost questions, brand searches, and problem led queries. Our Topical Authority Gap Mapper can help you identify which content topics you are missing relative to your industry cluster.

Recommended query classifications

Branded: Searches containing your business name (Elev8d, Elev8d Melbourne, Elev8d SEO).

Non branded commercial: Service searches without your name (SEO agency Melbourne, website development Melbourne).

Informational: Questions and research (how much does SEO cost, what is schema markup).

Local: Location specific searches (accountant Annandale, plumber Bankstown). Use our Local SEO Readiness Checker to assess how well your business is set up for these searches.

Irrelevant: Searches caused by ambiguous wording, unrelated meanings, or weak topic focus.

Branded versus non branded search

A website may appear to perform strongly because existing customers repeatedly search its name. That is valuable, but different from acquiring new demand. Search Console now provides a branded versus non branded filter for eligible properties.

Branded growth may indicate: Stronger reputation, offline marketing, referrals, advertising, social activity, or repeat customers.

Non branded growth may indicate: Category discovery, content visibility, local service visibility, new audience acquisition, or improved topical authority. Building genuine experience, expertise, and trust signals is what drives non branded visibility over time.

Report both separately each month: Branded clicks, non branded clicks, branded impressions, non branded impressions, and leads from organic traffic.

Branded search shows how many people already know who you are. Non branded search shows how often Google introduces you to someone new.

Pages: which URLs Google is presenting

The Pages tab shows the URLs receiving visibility and clicks. Use it to identify top traffic pages, pages gaining or losing visibility, articles generating impressions, commercial pages without visibility, unexpected URLs, old URLs, and parameter pages.

Important: Most Performance data is assigned to the canonical URL, not necessarily the exact duplicate URL a user landed on. A click to a duplicate can therefore appear under the canonical page in the Pages table.

Group pages by type: Service, article, industry, location, product, category, comparison, tool, report, and conversion page. Do not only list the ten URLs with the most traffic. Ask which page types are growing, which generate commercial searches, and which important pages receive almost no impressions. For ecommerce sites, product and category pages need separate analysis from editorial content.

Connect queries to pages

This is where Search Console becomes genuinely actionable. To see which pages appear for one query, open Queries, select a query, then switch to Pages and compare the URLs shown.

Questions to ask:

• Is the right page ranking for this query?

• Are several pages sharing the same intent?

• Is an article ranking where a service page should be?

• Is an old page outranking the current page?

• Is the homepage ranking for a service that has no dedicated page?

• Is a PDF appearing instead of the web page?

Two pages appearing for one query does not automatically mean harmful cannibalisation. Investigate whether they serve different intents, whether both receive meaningful clicks, and whether consolidating would improve customer experience. Multiple ranking pages are a clue, not an automatic diagnosis.

Finding high impression, low click opportunities

The common advice is: 'High impressions plus low clicks equals a title tag problem.' That is too simplistic. A low CTR may be caused by weak titles, but also by low average position, irrelevant query visibility, informational intent with no need to click, strong ads, local packs, featured answers, AI Overviews, or brand unfamiliarity. Use our Meta Title and Description Checker to test how your titles display in search results.

Recommended process:

• Step 1: Filter to one page, not site wide CTR

• Step 2: Open Queries to identify which searches created the impressions

• Step 3: Check position. A 1% CTR at position 18 means something different from 1% at position 2

• Step 4: Inspect the live search result. Look at the title Google used, the snippet, competing results, and search features

• Step 5: Compare mobile and desktop. Mobile result layouts may differ

• Step 6: Decide the action: improve title, improve content, strengthen the page, or leave it alone because the impressions are irrelevant

The CTR opportunity matrix

Do not use universal CTR benchmarks. CTR should be compared against the same page, similar queries, the same search type, a similar position, and an equivalent period.

Finding page two opportunities

One of the most commercially useful workflows is identifying queries with meaningful impressions, average position around 6 to 20, a relevant existing page, and clear commercial intent.

For trade and local service businesses, these page two queries are often suburb and service pages that need one more push, not a rewrite.

Possible actions:

• Improve the page's direct answer and missing sections

• Update outdated information

• Strengthen internal links to the page

• Add expert evidence and original data

• Improve title and heading alignment

• Earn relevant external links

• Merge overlapping weak pages

Do not optimise based only on the keyword. Open the ranking page and determine whether it deserves to rank, whether the query matches its purpose, and whether the business can genuinely satisfy the searcher.

Finding content decay and declining pages

Use date comparison (last 28 days versus previous 28, last three months versus previous three, or current period versus same period last year) and sort pages by click difference, impression difference, or position difference. A decline that hits many pages at once, on similar dates, usually lines up with recent algorithm changes rather than anything you changed on the site.

Common causes of decline:

• Search demand fell or seasonal period ended

• Content became outdated or competitors improved

• Search intent changed

• Internal links weakened or page was redirected

• Canonical changed or page was deindexed

• Website migration or technical outage

Before rewriting a declining page, check which queries declined, whether impressions or CTR fell, whether demand dropped across the category, and whether Google still indexes the correct URL.

Device, country, and search type analysis

Device: Compare mobile, desktop, and tablet. Look for lower mobile CTR, pages ranking differently by device, and mobile only performance losses. Mobile result layouts differ, and ecommerce or form interactions may vary.

For an Australian business, investigate unexpected visibility from the US, India, or UK. Possible causes include globally broad content, ambiguous currency, no Australian context, or imported product data. Do not automatically block international users. Decide whether the traffic is useful. See our guide on mobile SEO for Australian businesses for the mobile specific picture.

Search type: Search Console separates Web, Image, Video, and News. Do not combine their CTR or position expectations. Use the search appearance filter to detect which enhanced formats contribute impressions and clicks.

Search Console insights

The Insights report provides a simplified view of clicks, impressions, top content, trending content, declining content, queries, countries, branded versus non branded traffic, and additional sources such as Images, Video, News, and Discover. It can group similar queries for sites with substantial data and lets users move into the full Performance report for deeper analysis.

Use Insights to answer: what changed, which pages are growing, and what people are searching for. Use the main Performance report to answer: why it changed, which device or country contributed, and what action should be prioritised.

Insights is the summary. Performance is the investigation.

Generative AI reporting in Search Console

Google introduced dedicated generative AI performance reports in June 2026 for a subset of eligible properties. The reports can show generative AI impressions over time, pages receiving AI feature impressions, country, device, and visibility from generative features on Search and within Discover. This data also remains included in overall Performance reporting. For the broader picture of how AI search is changing visibility, see our guide to generative engine optimisation.

What the report does not tell you:

• The exact prompt or full generated answer text

• Whether the business was recommended or just cited

• Brand sentiment or conversion from AI features

• Visibility across ChatGPT, Perplexity, or other non Google platforms

AI feature impressions are a visibility signal. They are not the same thing as a recommendation or a customer enquiry.

The page indexing report

Older tutorials call this the Coverage report. The current Search Console interface uses the Page indexing report. It shows indexed pages, not indexed pages, reasons Google did not index certain URLs, trends over time, and example URLs.

What to monitor:

• Important pages unexpectedly excluded

• Sudden drops in indexed page count

• Rapid increases in duplicate URLs

• Large increases in crawled not indexed pages

• Old staging URLs appearing

• Sitemap URLs not being indexed

• Google selecting an unexpected canonical

The ideal indexed page count is not 'as high as possible'. It is the number of useful canonical pages the business genuinely wants people to find.

Common page indexing reasons and what to do

For every reason: inspect example URLs, determine whether they belong in Google, identify whether the pattern is template wide, fix only genuine problems, validate the fix, and monitor whether new affected URLs continue appearing.

'Crawled, currently not indexed' does not have one universal fix

This status can involve thin content, duplicative content, low value archive pages, poor internal linking, near identical location pages, expired products, automatically generated tags, pages Google has not prioritised, or temporary processing.

Ask:

• Is the page genuinely unique and useful?

• Does it satisfy a clear search intent?

• Is it linked internally and in the sitemap?

• Does it duplicate another page?

• Is the canonical correct?

• Is it strategically important to the business?

Do not:

• Repeatedly request indexing as a fix

• Add random words to make the page 'unique'

• Buy links to force indexing

• Change the date without updating content

Indexing is not an entitlement attached to every published URL. Google still has to decide whether the page belongs in its searchable index.

URL inspection: diagnosing one page at a time

The URL Inspection tool shows whether a URL is indexed, the last crawl date, crawl and indexing permissions, the Google selected canonical, the user declared canonical, referring page, sitemap discovery, rendered HTML, HTTP response, detected structured data, and a screenshot in the live test.

Recommended workflow:

• Enter the exact canonical URL (including HTTPS and correct path)

• Read the indexed verdict: is it on Google, which canonical did Google choose, when was it crawled?

• Run the live test after fixing noindex, robots rules, server issues, or schema changes

• View the tested page: check rendered text, screenshot, blocked resources, and response code

• Request indexing only for genuinely new important pages, substantially updated pages, or corrected technical issues

Sitemaps: discovery, not guaranteed indexing

The Sitemaps report shows submission history, parsing errors, and discovered URL counts. A sitemap tells Google which pages the business considers important. It does not force indexing, replace internal links, prove page quality, repair canonical errors, or overcome noindex.

Include in the sitemap: Canonical, indexable URLs: homepage, services, products, categories, articles, location pages, and current reports.

Exclude from the sitemap: Redirects, 404s, noindex pages, duplicate filter URLs, tracking URLs, staging pages, cart and checkout, and outdated HTTP versions.

Monthly checks: Status remains successful, discovered URL count is plausible, sitemap loads in a browser, important new content appears, and removed URLs disappear after processing.

Core Web Vitals inside Search Console

The Core Web Vitals report groups indexed URLs by mobile or desktop, performance status (Good, Needs Improvement, Poor), metric type, and groups of similar pages. It uses real user field data rather than a one off lab test. URLs without enough field data may not appear. For a full explanation of what each metric means and how to fix them, see our guide on Core Web Vitals explained for non developers.

What to do: Prioritise Poor groups. Identify important affected templates. Open example URLs and test in PageSpeed Insights. Fix the shared root cause. Confirm forms and tracking still work. Start validation and monitor the 28 day field data window.

Why there is no mobile usability report anymore

Google retired the Mobile Usability report and Mobile Friendly Test on 1 December 2023. Google said mobile usability still matters, but other tools such as Lighthouse had become available for evaluating mobile experience.

What to use instead: Core Web Vitals report, PageSpeed Insights, Chrome Lighthouse, manual phone testing, browser responsive mode, accessibility testing, and real user analytics.

Manual mobile checklist: Readable text, tappable targets, no horizontal scrolling, working menus, usable forms, visible call buttons, stable layout, no intrusive overlays, fast loading, and correct viewport.

Mobile usability still matters. The retired report simply means Search Console is no longer the only place to evaluate it.

HTTPS report

The HTTPS report shows whether indexed URLs are served through HTTP or HTTPS and may identify reasons Google cannot index the HTTPS version. Check that important indexed pages use HTTPS, HTTP redirects consistently to HTTPS, canonical tags use HTTPS, sitemaps contain HTTPS, and internal links use HTTPS.

Enhancement and rich result reports

Search Console displays enhancement reports when Google detects supported structured data. Possible reports include Product, Merchant listings, Breadcrumb, Article, Event, Job posting, Video, and other supported features. Each report groups items as valid, valid with warning, or invalid. For a detailed guide on which schema types matter and how to fix errors, see our article on schema markup explained.

Important: 'Invalid' means a required property or structural issue may prevent eligibility. 'Warning' means a recommended property is absent but the item may remain eligible. 'Valid' does not guarantee Google will display a rich result. Not every schema type produces a Search Console report.

The links report: useful sample, not a backlink database

The Links report shows top externally linked pages, top linking sites, common link text, and top internally linked pages. However, Google states it is not a complete list of every link. Tables are limited and links may be grouped, deduplicated, or retained after they have disappeared.

Useful questions:

• Which pages naturally attract links?

• Are reports and tools earning recognition?

• Are important service pages internally linked?

• Are obsolete URLs still heavily linked?

• Does one page receive almost all authority?

Do not use the report to calculate exact total backlinks, audit every toxic link, or compare counts directly with another tool.

Manual actions and security issues

These are high priority reports. A manual action means a human reviewer determined some or all of the site breaches Google's spam policies. Affected pages may rank lower or disappear. Security issues may identify hacked content, malware, unwanted software, or phishing.

Immediate response: Notify the website owner. Involve the developer or security provider. Identify affected URLs. Preserve evidence. Remove the cause, not only visible symptoms. Test the cleanup. Request review through the relevant report. Document the incident.

Do not treat these reports as ordinary SEO warnings. Search Console normally sends notifications when new issues arise.

Recommendations: investigate before accepting

Recommendations may highlight opportunities, configuration suggestions, or issues. They are useful prompts, but not automatic instructions. Google explicitly says they are optional and may change or expire.

For each recommendation, ask: does it apply to our business model? Is the page strategically important? Could the change create another problem? What evidence will confirm success? 'Google recommended it' is a reason to investigate, not permission to skip judgement.

Why Search Console and GA4 do not match

Business owners regularly assume one system is broken when the numbers differ. Search Console measures events in Google Search. GA4 measures activity after the website and its tracking scripts load.

Differences arise from:

• Clicks versus sessions (different events entirely)

• Privacy filtering and anonymised queries

• Data processing timing and time zone differences (Pacific Time vs local)

• JavaScript blocking or consent settings preventing GA4 from loading

• Users leaving before GA4 loads (creates a Search Console click but no GA4 session)

• Canonical URL reporting and duplicate filtering

Compare trends rather than forcing exact equality. Use Search Console for visibility, GA4 for engagement, and CRM for commercial outcome. If your website gets traffic but not enquiries, that is a separate problem. See our guide on why website traffic does not convert.

Search Console data limitations

A trustworthy guide must explain the limits.

Anonymised queries: Some low volume searches are omitted for privacy.

Row truncation: Standard exports and visible tables may be limited to 1,000 rows, while top line totals include more data.

Canonical aggregation: Clicks and impressions are commonly credited to canonical URLs, not the exact URL visited.

Property versus page aggregation: The chart and table can use different methods. Property level reporting may count the site once and use the topmost position, while page level reporting treats URLs separately.

Preliminary data: Recent values can change while collection completes. Dotted chart lines indicate preliminary data.

Report sampling: Many reports show representative examples rather than complete URL lists.

Reporting anomalies: Google maintains a data anomalies page for known logging and processing issues. Before diagnosing a sudden unexplained chart change, check whether a known reporting issue exists.

Search Console is authoritative about its own data, but that does not mean every table is a complete record of every query, page, or link.

Exporting and preserving Search Console data

Spreadsheet export: Suitable for small sites, monthly reports, filtered opportunity lists, and simple comparisons. Available as Google Sheets, Excel, or CSV.

Search Console API: Suitable for medium sites needing more rows and automated reporting. Supports filtering, sorting, and up to 50,000 rows per day per search type and property.

BigQuery bulk export: Suitable for large sites needing long term data retention, combining Search Console with internal data, advanced analysis, and custom dashboards. Sends daily data to BigQuery without the normal interface row limit.

Most SMBs do not need BigQuery immediately. They do need monthly exports, saved annotations, consistent reporting periods, a record of major site changes, and preserved year on year benchmarks. Use our SEO ROI Calculator alongside Search Console data to model the revenue impact of organic growth.

How to diagnose a sudden organic traffic drop

Use a fixed sequence rather than guessing.

Step 1: Confirm the drop is real. Check Search Console, GA4, CRM, server uptime, and reporting anomalies.

Step 2: Identify the starting date. Add or inspect annotations.

Step 3: Segment the drop. By page, query, country, device, search type, and branded versus non branded.

Step 4: Separate impressions from CTR.

Impressions fell? Possible: demand decline, rankings fell, indexing issue, season ended, pages removed, or manual action.

Impressions stable but clicks fell? Possible: lower CTR, SERP layout change, title or snippet change, stronger competitors, AI or zero click result, or lower average position.

Step 5: Check Page indexing. Look for sudden excluded page increases, canonical changes, server errors, noindex, or robots issues.

Step 6: Inspect affected URLs using URL Inspection.

Step 7: Check site changes. Migration, redesign, plugin, CDN, internal linking, title rewrite, content deletion, or template change.

Step 8: Check Manual Actions and Security.

Step 9: Compare year on year to rule out seasonality. If an algorithm update coincides with the drop, our algorithm updates guide (linked earlier in the content decay section) covers the diagnosis process.

Step 10: Create a documented recovery plan. Do not react by mass rewriting every page.

A monthly Search Console review routine

This should take about 60 to 80 minutes once the process is established.

Part 1: Account health (5 minutes)

Check the correct property is selected, new messages, manual actions, security issues, recommendations, and ownership or access changes.

Part 2: Performance (15 minutes)

Compare last 28 days versus previous 28, and current period versus previous year. Review clicks, impressions, CTR, and average position. Segment by branded versus non branded, mobile versus desktop, and Australia versus other countries.

Part 3: Winners and losers (15 minutes)

Export top rising pages, top declining pages, top rising queries, and top declining queries. Investigate the largest absolute changes, not only percentages.

Part 4: Opportunity analysis (15 minutes)

Find high impression page two queries, relevant low CTR pages, service queries without suitable pages, articles ranking for commercial intent, and commercial pages with weak visibility. Use our 30 minute SEO audit checklist alongside this process for a broader technical check.

Part 5: Indexing (10 minutes)

Review indexed trend, unexpected exclusions, server errors, sitemap health, and important new pages.

Part 6: Experience and enhancements (10 minutes)

Check Core Web Vitals, HTTPS, structured data reports, merchant or product issues, and video indexing where relevant.

Part 7: Action register (10 minutes)

For every action, record the issue, evidence, affected URL, proposed fix, owner, priority, due date, expected outcome, and review date.

The goal of the monthly review is not to produce more charts. It is to leave with a short, prioritised list of decisions.

The Search Console opportunity register

Keep a running log so repeated audits do not rediscover the same issues without implementing them.

What to send a developer or SEO specialist

Do not send: 'Search Console has loads of errors. Please fix them.'

Send a structured ticket containing:

• Issue: exact Search Console reason or metric

• Scope: affected report, URL pattern, example URLs, number of pages, date first observed

• Expected behaviour: should these pages index, remain excluded, redirect, return 404, or load faster?

• Evidence: screenshot, export, URL Inspection result, sitemap status, relevant timeline

• Requested investigation: root cause, recommended fix, deployment risk, template impact

• Acceptance criteria: e.g. 'All canonical service pages should return 200, allow indexing, use self referencing canonicals, appear in the sitemap, and remain internally linked'

'Not indexed' describes an outcome. A good development ticket defines the intended outcome and the conditions needed to achieve it.

A 90 day Google Search Console action plan

For the broader SEO picture beyond Search Console, the strategy framework in our SEO guide covers the full approach. For quick wins on the technical side, our website speed and SEO guide covers the performance foundations. Use the SEO Timeline Estimator to set realistic expectations for how long improvements typically take to show in Search Console data.

Common Google Search Console mistakes

Selecting the wrong property. Important data appears missing. Use a verified Domain property.

Treating impressions as traffic. Impressions do not mean a visit. Use clicks and GA4 together.

Treating average position as a live rank. It averages many searches and result types. Use it as a trend indicator.

Acting on site wide CTR. Different queries have different intents. Analyse page and query combinations.

Assuming low CTR means a bad title. Position, SERP layout, and AI features may be responsible. Inspect the actual result first.

Panicking over every excluded URL. Many exclusions are correct. Decide whether the URL should index before fixing it.

Repeatedly requesting indexing. Does not solve quality or architecture problems. Fix discovery and page value.

Using old Coverage report instructions. The interface and naming have changed. Use the Page indexing report.

Searching for Mobile Usability. The report was retired in December 2023. Use Core Web Vitals, Lighthouse, and manual testing.

Comparing GSC clicks with GA4 sessions directly. They measure different events. Compare trends and understand the collection differences.

Adding query rows to recreate totals. Anonymised and truncated rows are missing. Trust top line totals.

Reporting only traffic without connecting to leads. Traffic may not produce customers. Connect to leads and revenue data.

Checking daily without a structured action process. Creates noise. Use a monthly routine with an action register.

Making changes without annotations. Future reports lose context. Mark important releases and fixes.

FAQs

What is Google Search Console used for?

It helps verified site owners understand Google Search visibility, clicks, impressions, indexing, sitemaps, Core Web Vitals, structured data enhancements, and certain technical or policy issues.

Is Google Search Console the same as Google Analytics?

No. Search Console measures visibility and clicks from Google Search, while Analytics measures behaviour after visitors arrive on the website.

Why do Search Console and GA4 show different numbers?

They measure different events and use different data processing, privacy filtering, timing, and technical collection methods. Compare trends rather than expecting exact matches.

What is an impression in Search Console?

An impression is counted when a qualifying result from the site is shown in Google. Exact rules vary by result format.

What is a good click through rate?

There is no universal good CTR. It depends on position, query intent, brand familiarity, device, and the search result format. Compare against the same page and similar queries rather than using a benchmark.

Is average position my Google ranking?

No. It is an average of the topmost position recorded across the impressions included in the report. It is best used as a trend indicator, not a live ranking check.

Why are some queries missing?

Google omits some queries for privacy and limits the number of rows visible in reports. Top line totals still include the omitted data.

Should every page be indexed?

No. Only useful canonical pages intended for search should generally be indexed. Admin pages, duplicates, filters, cart pages, and tracking URLs should normally remain excluded.

What happened to the Coverage report?

Current Search Console uses the Page indexing report. The data is similar, but the naming and interface have changed.

What happened to Mobile Usability?

Google retired the Mobile Usability report and Mobile Friendly Test on 1 December 2023. Use Core Web Vitals, PageSpeed Insights, Lighthouse, and manual phone testing instead.

Does submitting a sitemap guarantee indexing?

No. A sitemap supports discovery but does not guarantee that Google will crawl or index every submitted URL.

How far back does Search Console performance data go?

The Performance report provides up to 16 months of history in the standard interface.

Can Search Console show AI Overview performance?

Google is testing dedicated generative AI performance reports with a subset of eligible properties. AI feature data also remains included in overall Performance reporting.

Can Search Console show leads and sales?

Not by itself. Connect its visibility data with GA4, CRM, call tracking, or ecommerce data to understand commercial outcomes.

What we recommend at Elev8d

When we work with a new client, Search Console is one of the first things we open. Not to generate a 30 page report, but to understand how Google sees the site, which pages are earning visibility, where the obvious leaks are, and whether the tracking setup tells the full story. That is part of how we approach our SEO work for businesses.

For most small businesses, the highest value Search Console work is three things: separating branded from non branded traffic so you know whether you are growing or just being found by existing customers, identifying page two opportunities where small improvements can move the needle, and keeping the Page indexing report clean so Google is not wasting crawl budget on pages that should not be in the index.

We teach every client to run the monthly review routine so they understand what the data means, not just what the charts look like.

Next steps: pick your path

Path 1: Start the monthly routine

Follow the 60 to 80 minute monthly review process in this article. Start with the correct property, separate branded and non branded traffic, and build an action register so every finding leads to a decision.

Path 2: Diagnose a specific problem

If your traffic dropped or your indexing looks wrong, use the diagnosis sequence in this article. Check the right dates, segment by page type and query, and rule out technical causes before assuming content needs rewriting. The SEO audit checklist linked earlier covers the broader technical check alongside Search Console.

Path 3: Get help reading the data

If Search Console looks confusing or your reports do not match what you expected, get in touch. We will walk through your data, explain what the numbers mean, identify the highest impact opportunities, and build a reporting process your team can maintain.

Search Console does not tell you whether your SEO is good or bad. It gives you evidence about how Google discovers, indexes, and displays your website. The value comes from knowing which patterns require action and which ones are perfectly normal.

Sources and further reading

• Google Search Console Help - Complete Search Console documentation and guides.

• Google Search Central: Search Console Training - How to use Search Console for search performance.

• Google: Performance Report Documentation - How clicks, impressions, CTR, and position are calculated.

• Google: Page Indexing Report - Understanding indexing status and exclusion reasons.

• Google: URL Inspection Tool - How to inspect individual URLs.

• Google: Data Anomalies - Known Search Console reporting issues and data anomalies.

General information only. Rules vary by situation, particularly around advertising claims, privacy, reviews and consumer law. If you are unsure about compliance, get professional advice.