Organic visits have dropped, an important page is missing from Google, or a new article is earning impressions but almost no clicks. Google Search Console helps you find where the change occurred and decide what to address first.
Google Search Console is Google's free platform for monitoring a website's presence in Google Search. It shows which searches surface your pages, which URLs are indexed, how Google reports their performance, and whether it has detected specific problems.
Search Console does not improve your website for you, and it cannot explain every decline on its own. Its value comes from the decisions you make with its reports: which page to inspect, what to compare, which issue to correct, and when one symptom calls for a broader analysis.
Google's official Search Console overview describes its core uses: monitoring Google Search traffic, checking indexing, receiving issue alerts, and reviewing links to your website.
For a business, that translates into five practical questions:
| Business question | Relevant report or tool | Possible decision |
|---|---|---|
| Which topics and pages are gaining or losing interest? | Performance | Update, expand, or retarget a page |
| Are important pages indexed? | Page indexing | Check the template, internal links, canonical, noindex, or quality |
| What does Google know about one URL? | URL Inspection | Correct and retest one page |
| Is a problem affecting a group of similar pages? | Core Web Vitals or an enhancement report | Prioritize technical work at the template level |
| Is there an urgent risk? | Manual Actions and Security Issues | Investigate immediately, fix the cause, and request a review |
The platform does not show sales, leads, or what visitors do after arriving. For that, you need an analytics system such as Google Analytics 4 and correctly configured conversion measurement.
In Search Console, a website is added as a property. According to Google's guide to adding a property, there are two main website property types:
For most business websites, a Domain property provides the most complete view. A separate URL-prefix property can be useful when a team needs to analyze a specific section or limit access to a narrower scope.
Do not share a personal Google password. Add each person's work account with the access level they need, and keep at least two verified owners. Google explains why ownership verification is sensitive: owners can see nonpublic data and take actions that affect a website's presence in Google Search.
The Performance report shows how a website performs in Google Search results. Its main metrics are clicks, impressions, CTR, and average position. You can analyze the data by query, page, country, device, date, and search type.
The most useful approach is to start with the change, not the total:
Google's official examples for using the report recommend focusing on trends in impressions and clicks rather than treating average position as a stand-alone measure.
Google documents how these metrics are calculated. Average position is not a fixed ranking in an identical list. It changes with the query, location, device, result format, and data grouping.
| What you observe | What to investigate | Next decision |
|---|---|---|
| Impressions rise, but clicks do not | The page appears for more searches, but the result does not earn enough selections | Review the queries, title, description, and match with search intent |
| Impressions and clicks fall | Lost demand, a technical issue, a change in the results, or weaker interest | Break down the decline by page, query, country, and device |
| Clicks fall while position looks similar | A change in demand or in the search results layout | Compare CTR, queries, and the actual result presentation |
| One page grows while another on the same topic declines | Google may have changed its preferred URL | Compare the queries and clarify the role of each page |
These patterns are starting points, not automatic diagnoses. Search Console hides some queries for privacy, and the chart and table can use different aggregation methods. These limitations are explained in Google's documentation about Performance report data.
In June 2026, Google announced separate reports for impressions in AI Overviews, AI Mode, and generative features in Discover. Google's announcement states that access is being rolled out gradually to a subset of websites.
If the Search generative AI report is available for your property, it can help you determine:
Google's report documentation notes an important limitation: the initial report includes impressions, not the complete set of clicks, CTR, and average position. If you do not see the report, it may not be available to your property yet or your website may not have enough data.
You do not need special code or separate schema markup just to appear in AI Overviews or AI Mode. Google says the same core requirements for crawling, indexing, and helpful content continue to apply. See Google's official guide to AI features and websites.
The URL Inspection tool answers one question: what does Google know about this specific page? It can show indexing status, the last crawl, the canonical Google detected, possible indexing blocks, and related enhancements.
Use it when:
Google's URL Inspection guide distinguishes information about the indexed version from a live URL test. A successful live test means Google can probably access and process the current version, but it does not guarantee indexing or rankings.
Request indexing after a meaningful change to an individual page. The request asks Google to recrawl the URL; it is not a promise about timing or inclusion in the index. For many pages, use an XML sitemap and strong internal navigation instead of submitting URLs one by one.
This report provides the overall picture for URLs Google knows about. The goal is not to index every technical, duplicate, or redirected URL. The goal is for important canonical pages to be indexed and for the remaining statuses to make sense.
Google recommends using the report to identify patterns and groups of issues, and using URL Inspection for one specific page.
Check these points first:
A redirected page, duplicate variation, or intentional noindex can correctly remain outside the index. Do not change a page simply because it appears under "Not indexed." When the causes overlap across site structure, canonicals, internal links, and technical access, you need a broader diagnosis rather than one report.
The Sitemaps report shows whether Google can fetch and read a submitted XML sitemap. Google's documentation emphasizes that a sitemap tells Google which pages you want it to know about, but it does not guarantee indexing.
The business decision is whether the sitemap contains the right set of canonical pages. If it includes redirected, missing, duplicate, or intentionally excluded URLs, correct the sitemap source. If Google reads the sitemap successfully but important pages remain unindexed, investigate the Page indexing report and the individual URLs. The guide to crawling and indexing explains how to trace problems that extend beyond a single report.
The Core Web Vitals report uses real-world user data and groups similar URLs as Good, Need improvement, or Poor. Its three metrics are LCP, INP, and CLS.
Google's Core Web Vitals report documentation explains that the report works with groups of pages and does not necessarily include every indexed URL. It is useful for identifying an affected template and setting priorities, but it is not enough to find the exact technical cause. The Core Web Vitals and page speed guide connects these signals with the checks needed to diagnose the page experience.
If an issue affects many product pages, categories, or articles that share a template, the solution usually belongs at the template level. Then test representative URLs with PageSpeed Insights and real-world checks.
The Links report provides sample data about external and internal links Google has found. You can review the most linked pages, top linking websites, and pages with the most internal links.
It is not a complete list of every link, and it does not evaluate link quality by itself. Google documents the report's limitations, including canonical grouping, duplicate link consolidation, and table limits.
Use the report to ask:
These two reports have a higher priority than routine ranking monitoring.
The Manual Actions report shows whether a human reviewer at Google found that pages violate its spam policies. Affected pages or the entire website can be ranked lower or removed from results.
The Security Issues report shows detected signs of hacked content, malware, or deceptive behavior. These issues can trigger warnings in search results or browsers.
When you receive a notice, identify the scope and affected examples first. Then remove the cause everywhere it appears. Request a review only after the issue is fully corrected and you can explain what changed.
Crawl Stats shows the history of Google's requests to your website, server responses, response time, and availability issues. Google describes it as an advanced report and notes that smaller websites generally do not need this level of analysis.
The report is useful when you see:
It shows symptoms from Googlebot's perspective, but it does not replace server logs or infrastructure monitoring.
Search Console shows how people saw and selected your website in Google Search. Google Analytics shows what they did after arriving, when measurement is configured and consent settings allow data collection.
Do not expect Search Console clicks and Analytics organic sessions to match exactly. Differences can result from measurement methods, time zones, filtering, canonical grouping, consent settings, and blocked analytics code. Google's guide to analyzing the two data sources together explains how they cover different parts of the user journey.
The practical connection is simple:
You do not need to monitor Search Console continuously. Google recommends periodic overview checks for small website owners and closer review after important changes.
A practical business cadence is:
Keep a note of every major website change. Without that timeline, it is easy to confuse seasonality, a technical correction, new content, and a change in Google's results.
Your team can often solve a problem internally when one known page is affected, the cause is clear, and the correction does not touch other templates or systems. An incorrect noindex directive, a missing internal link, or an inaccurate title can each have a specific fix and a clear verification step.
A broader analysis is more appropriate when:
A technical SEO audit and website analysis combines Search Console data with checks of the technical implementation, site structure, content, and measurement. The result should be a prioritized list of proven problems and actions, not another general report without a decision.
