Most SEO tools guess how Google sees your site. Google Search Console doesn’t have to guess, because the data comes from Google itself. This guide walks through every report that matters for SEO, explains what each number means according to Google’s own documentation, and ends with a monthly routine you can run in under an hour.
What Search Console Does for SEO, in One Minute
Google Search Console is “a free service offered by Google” that helps you “monitor, maintain, and troubleshoot your site’s presence in Google Search results,” according to Google’s About Search Console page. You don’t need it to appear in Google. You need it to see what Google sees.
So what does it actually do for SEO? Google lists five jobs on that same page:
- Confirm that Google can find and crawl your site.
- Fix indexing problems and request re-indexing of new or updated content.
- Show your Google Search traffic: queries, clicks, impressions and positions.
- Send alerts when Google finds indexing, spam or other issues on your site.
- Show which sites link to yours.
Paid SEO suites estimate traffic and rankings from their own crawlers and panels. Search Console reports what happened inside Google Search for your verified site. That makes it the one free tool every site owner should open before paying for anything else. Google’s own comparison of Search Console and Google Analytics says it plainly: “The source of truth for Search performance will always be Search Console.”
The catch is that Search Console has a lot of reports, and the left-hand menu doesn’t tell you which ones matter. The rest of this guide sorts them by the SEO question each one answers.
Key Takeaways
Search Console keeps data for the last 16 months, according to Google Analytics Help, so you can compare this year with last year without any paid tool. Use the Performance report to find queries and pages with room to grow, the Page indexing report to confirm your key pages are in Google, and the experience, security and manual action reports to catch problems early. Google itself suggests checking about once a month.
Before You Start: Add and Verify Your Site
You can’t see any data until you add a property and prove you own it. Google’s property guide says data “should begin to appear in your property in a few days,” and an account can hold up to 1,000 properties.
Which property type should you pick? There are two:
| Property type | What it covers | How you verify it |
|---|---|---|
| Domain property | The whole domain: all subdomains (www, shop, blog) and both http and https | DNS record only |
| URL-prefix property | Only URLs that start with the exact prefix, protocol included | HTML file, HTML tag, Google Analytics, Google Tag Manager or DNS |
For SEO, a Domain property is usually the better start because nothing falls through the cracks. If you type example.com, you get data for https://www.example.com/, http://example.com/ and https://blog.example.com/ in one place. A URL-prefix property is handy when you only control one section of a site, or when you can’t edit DNS.
Google’s verification help page adds two practical warnings. First, keep the token in place: “To stay verified, don’t remove the DNS record from your provider, even after verification succeeds.” Deleting an HTML file or tag has the same effect. Second, a new DNS record can take “up to two or three days” before your provider serves it, so a failed first attempt is normal.
Working with a freelancer or an agency? Don’t share your Google login. Search Console has three permission levels: owners have full control, full users can view all data and take some actions, and restricted users get simple view rights on most data. A property can have up to 100 non-owner users.
For the full walkthrough of each verification method, read our step-by-step guide to setting up Google Search Console. One more tip: Google starts collecting data as soon as anyone adds the property, even before verification, so add it today even if you plan to finish later.
The Performance Report: Clicks, Impressions, CTR and Position
The Performance report is where most Search Console SEO work happens: it shows how often your pages appeared in Google Search and how often people clicked, with 16 months of history according to Google Analytics Help. The Performance report help page defines the four metrics like this:
| Metric | Google’s definition | What it tells you for SEO |
|---|---|---|
| Clicks | “The number of times a user clicked your site from Google Search results” | Real visits from Search |
| Impressions | “How many times your site appeared in Search results” | Visibility, even without clicks |
| CTR | “The click count divided by the impression count” | How well your title and snippet persuade |
| Average position | The topmost position of your result, averaged across queries | Roughly where you rank |
Why do these four matter together? Because each one alone misleads. A page with rising impressions and falling CTR may be ranking for broader queries, not getting worse. A page with a great position but few impressions targets a query almost nobody searches.
How to read the report
The default view covers the last three months. Below the chart, a table lets you switch between six dimensions: Queries, Pages, Countries, Devices, Search appearance and Dates. You can also switch the search type between web, image, video and news results.
Three details from Google’s data documentation save a lot of confusion:
- Tables show a maximum of 1,000 rows. Larger sites need the API or an export for the long tail.
- Rare queries and queries with personal information are hidden for privacy, so query rows rarely add up to the site total.
- Daily data uses Pacific time, and collected data normally appears in 2 to 3 days. A newer 24-hour view shows hourly, preliminary numbers.
Features added in 2025 and 2026
Google has added three features that change how you can use the report. On November 20, 2025, Google introduced a branded queries filter that splits queries into Branded and Non-branded views. It only works for top-level properties with enough queries and impressions, and Google says it “has no effect on how Google Search ranking works.”
On November 17, 2025, Google added custom annotations: you right-click the chart, choose “Add annotation,” and write a note of up to 120 characters for a date. Everyone with access to the property can read them.
Then, on June 3, 2026, Google announced Search Generative AI performance reports. They show impressions in generative AI features such as AI Overviews and AI Mode, plus AI features in Discover, broken down by page, country, device and date. The post says the reports reached all websites worldwide as of August 31, 2026. They show impressions only, with no clicks or CTR yet, and the same data stays included in the overall Performance report. For how those AI answers pick their sources, see our guide to Google AI Overviews.
Want to go deeper on queries and positions? Read our guide to Search Console’s average position metric.
Finding Quick SEO Wins in Your Query Data
The fastest SEO wins in Search Console come from pages that Google already shows but people rarely click. Google’s advanced filtering guide gives you the tools to find them: filters on queries, pages, countries, devices, search appearance and date, plus regex and a compare mode.
Where should you start? We suggest three filters, in this order.
1. High impressions, low CTR. Sort the Queries table by impressions and turn on the CTR column. Queries near the top with a CTR far below your site average are the cheapest wins. The page already ranks; its title or description just isn’t earning the click. Google’s title link documentation explains how Google chooses the title shown in results and how to influence it.
2. Average position on page two. Turn on Average position and look for queries in roughly the 8 to 20 range. This range is our rule of thumb, not a Google number. Pages there are close enough that a better section, a clearer answer or a few internal links can move them up.
3. Branded versus non-branded. If the branded queries filter is available for your property, check the Non-branded view. That is the traffic your content earns from people who didn’t already know your name, and it is usually the number SEO work is supposed to grow.
Regex and comparisons
The “Custom (regex)” filter uses RE2 syntax and is case-insensitive by default. One useful pattern is ^(how|what|why|when|can|does)\b, which isolates question queries. Those questions are good FAQ and heading material.
Compare mode lets you put two values of one dimension side by side, such as last 28 days versus the previous period, or mobile versus desktop. Google adds a Difference column, and only one comparison can run at a time.
One warning from that same guide: filtering by query or page can change report totals because anonymized queries drop out. Treat filtered totals as directional, not exact.
Indexing: Make Sure Google Can Find Your Pages
A page that isn’t indexed can’t rank, and the Page indexing report shows which of your pages Google has indexed and why the rest are missing. Google’s Page indexing help page splits every known URL into two groups, Indexed and Not indexed, and lists a reason for each non-indexed URL.
Is a long Not indexed list a disaster? Usually not. Google says: “Don’t expect every URL on your site to be indexed.” Duplicates, redirects and thin pages are often fine to leave out. What matters is that your key pages, starting with your homepage, are indexed.
The most common reasons you’ll see:
| Reason | What it usually means | Typical next step |
|---|---|---|
| Not found (404) | The URL no longer exists | Fine if intended; redirect it if it had links or traffic |
| Page with redirect | The URL redirects elsewhere | Usually fine; make sure internal links point to the final URL |
| URL marked ‘noindex’ | A noindex tag or header blocks it | Remove the tag if the page should rank |
| Blocked by robots.txt | A robots.txt rule blocks crawling | Change the rule if the page should rank |
| Duplicate without user-selected canonical | Google sees duplicates and picked one | Add a canonical tag to the version you want |
| Crawled - currently not indexed | Google crawled it but chose not to index it yet | Improve the content and internal links |
| Discovered - currently not indexed | Google knows the URL but hasn’t crawled it yet | Add internal links; check site speed and server load |
| Soft 404 | The page looks empty or like an error | Add real content or return a true 404 |
| Server error (5xx) | Your server failed when Google asked | Check hosting and server logs |
Validating a fix
After you fix every instance of an issue, click Validate fix. Google says validation “typically takes up to about two weeks,” and you shouldn’t click again until it succeeds or fails. Each issue shows up to 1,000 example URLs, which may not be every affected page.
Google’s guidance for non-experts adds a useful shortcut: sites with fewer than 500 pages usually don’t need this report much, as long as their important pages show up in Search. For every status, cause and fix, read our full guide to Google Search Console indexing issues.
Sitemaps and URL Inspection
Sitemaps tell Google which URLs you care about, and URL Inspection tells you exactly what Google knows about a single URL. According to Google’s getting started guide, submitting a sitemap “might speed up your site’s discovery,” though Google can find pages without one.
The Sitemaps report
You submit a sitemap by pasting its URL into “Add a new sitemap.” The Sitemaps report help page lists three statuses: Success, Has errors and Couldn’t fetch. Each row shows the type, the submitted and last read dates, and how many pages Google discovered.
Do sitemaps have size limits? Yes. One sitemap can list up to 50,000 URLs and must stay under 50MB uncompressed. Bigger sites split their URLs across several sitemaps and list them in a sitemap index. Most site builders and SEO plugins generate all of this for you; your job is to submit the index once and check that it says Success.
A sitemap is a hint, not an order. Google notes that “it is possible that not all URLs in a sitemap will be crawled.”
URL Inspection
Paste any URL from your property into the search bar at the top of Search Console. The URL Inspection help page explains what comes back: whether the URL is on Google, when it was last crawled, whether crawling and indexing are allowed, the canonical you declared, and the canonical Google selected.
Two buttons matter most:
- Test live URL fetches the page right now. Use it after a fix, because the default view shows the indexed version, and Google states plainly: “This is not a live test.”
- Request indexing asks Google to crawl the URL. There is a daily limit per property, and Google warns that a request “does not guarantee that the page will appear in the Google Index.” Indexing often takes about a day but can take a week or two.
Got hundreds of new URLs? Submit a sitemap instead of requesting each one. URL Inspection works best for a handful of important pages, such as a new pillar article or a fixed product page.
Experience Reports: Core Web Vitals and HTTPS
The experience reports show whether real visitors get a fast, stable and secure page. Google’s Core Web Vitals report uses field data from the Chrome UX Report and rates groups of similar URLs on three metrics over the last 28 days:
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | Loading speed of the main content | 2.5s or less | 4s or less | More than 4s |
| INP (Interaction to Next Paint) | How fast the page responds to input | 200ms or less | 500ms or less | More than 500ms |
| CLS (Cumulative Layout Shift) | How much the layout jumps around | 0.1 or less | 0.25 or less | More than 0.25 |
How does a group earn “Good”? According to the report’s help page, 75% of visits must meet the threshold, and a group’s status is its worst metric. Mobile and desktop are rated separately, so a page can be Good on desktop and Poor on mobile.
New or small sites often see “No data available.” That only means the Chrome UX Report doesn’t have enough real-user data yet. It isn’t a penalty.
After you fix an issue, click Start Tracking. Search Console then watches the group for 28 days and marks the issue fixed only if it stays absent for the whole period. That is why a speed fix can look “stuck” for a month.
The HTTPS report
The HTTPS report counts how many of your indexed URLs are HTTP versus HTTPS, and explains why an HTTPS version wasn’t indexed. Common reasons include an invalid certificate, a sitemap that still lists HTTP URLs, an HTTPS page that redirects back to HTTP and a robots.txt rule that blocks HTTPS URLs.
The report only appears for Domain properties and HTTPS URL-prefix properties. Google says that when a page has both addresses, it “prefers to index the HTTPS version.”
Need a simple target? Aim for zero HTTP URLs in this report and every Core Web Vitals group in Good, checking mobile and desktop separately.
Rich Results and Structured Data Reports
If your pages use structured data, the rich result reports show whether Google can read it and which items qualify for rich results. They live under Enhancements in the menu, with product snippets and merchant listings under Shopping, as described on Google’s rich result reports page.
Which reports will you see? Only the ones for markup Google actually found on your site. Supported types include Breadcrumbs, Events, Job postings, Merchant listings, Product snippets, Profile pages, Recipes, Review snippets, Videos and several others.
Each report splits items into two groups:
- Valid items have no critical issues and “can appear on Google as a rich result.”
- Invalid items have at least one critical issue that prevents a rich result.
Non-critical issues appear under “Improve item appearance.” They don’t block a rich result, but fixing them can add details such as ratings or prices to the snippet.
Two points to remember. First, counts are structured data items, not pages, and the report shows a sample rather than every item. Second, there’s no fix button: the markup lives in your site’s code, so you fix it in your theme, plugin or template, then validate in the report.
Want to test a page before it goes live? Use Google’s Rich Results Test, which checks any public URL or code snippet. Search Console tells you what Google found after crawling; the test tells you what it would find right now. Used together, they close the loop: test a template change first, publish it, then watch the report’s Valid count rise over the following weeks.
The Links Report: Internal and External Links
The Links report shows which sites link to you, which of your pages get the most links, and how your pages link to each other. Google’s Links report help page splits it into external links and internal links.
The external side has three main tables: top linked pages, top linking sites and top linking text. You can drill into any page to see which sites link to it. The internal side shows your most-linked pages from within your own site.
What should you look for? Three things:
- Pages you care about that few other pages link to. If a key guide sits near the bottom of the internal links table, add links to it from related articles.
- Anchor text that doesn’t describe the page. The top linking text table shows how other sites describe you.
- Strange domains. A sudden burst of links from unrelated sites is worth a look.
Know the limits before you draw conclusions. Google says the report “isn’t a comprehensive list of every link on your site.” Tables stop at 1,000 rows, links are grouped by root domain, removed links can linger, and the report doesn’t show whether a link is nofollow.
That’s why many site owners pair it with a third-party backlink tool. Our guide to free backlink checker tools compares what their free plans show. Still, Search Console’s list is the only one that comes from Google itself, which makes it the best place to start an internal linking review.
Security Issues and Manual Actions
These two reports are rare but serious: they tell you when Google has found a hacked page, malware or a spam policy violation on your site. Google’s guide on how to use Search Console says Search Console will email you when it finds new issues, which is one more reason to verify your site early.
Security issues
The Security Issues report groups problems into hacked content, malware and unwanted software, and social engineering. Specific issues include code injection, content injection, URL injection, deceptive pages and harmful downloads.
Why does this matter for SEO? Affected pages can carry a warning label in search results, and visitors may see a full-page browser warning before they reach your site. Traffic can drop overnight. After you clean every affected page, click Request Review; Google says most reviews take a few days to a few weeks.
Manual actions
A manual action means “a human reviewer at Google has determined that pages on the site are not compliant with” Google’s spam policies, according to the Manual Actions report. Most result in pages ranking lower or dropping out of results.
The list of types is long: unnatural links, thin content with little or no added value, cloaking and sneaky redirects, hidden text and keyword stuffing, user-generated spam, structured data issues, site reputation policy violations and more. If your site has none, the report simply shows a green check mark.
If you do get one, fix it everywhere. Google warns that “fixing the issue on just some pages will not earn you a partial return to search results.” Then request a review that explains the issue, the fix and the result. Reviews “can take several days or weeks,” and link-related ones take longer.
Is there a quick way to tell an algorithm drop from a manual action? Yes: open this report. If it shows a green check mark, the drop has another cause.
Search Console vs Google Analytics: Which Numbers to Trust
Search Console and Google Analytics measure different things, so their numbers never match exactly, and Google says that’s expected. Its guide to using both tools notes that “clicks and sessions are calculated differently” and that “what’s important is that the general trends have the same pattern”.
Why the gap? Google’s data documentation lists the main reasons:
- Search Console counts clicks from Google Search; Analytics counts sessions from every source.
- Search Console removes duplicates and robot visits.
- Analytics only tracks visitors with JavaScript enabled, and it uses your local time zone, while Search Console uses Pacific time.
- Search Console data lags by 2 to 3 days.
So which one do you use for what? Use Search Console for anything that happens before the click: queries, impressions, positions, CTR and indexing. Use Analytics for what happens after the click: engagement, sign-ups and sales. You can link the two so that a few Search Console reports appear inside Analytics.
For a beginner, that split is enough. If Search Console clicks and Analytics organic sessions trend the same way, your tracking is healthy.
A Monthly SEO Audit Routine Using Only Search Console
You don’t need a paid tool for a basic SEO audit. Google’s getting started guide says “there is no need to sign in to the tool every day” and suggests checking “around once every month,” or after content changes. Here is a routine built only from the reports in this guide.
| Step | Report | What to check | Action if something is off |
|---|---|---|---|
| 1 | Overview, Security issues, Manual actions | Any new message, warning or action | Fix first; everything else waits |
| 2 | Page indexing and Sitemaps | Key pages indexed; sitemaps say Success | Inspect the URL, fix, then Validate fix |
| 3 | Performance | Last 28 days vs previous period; high-impression, low-CTR queries; page-two queries | Rewrite titles, expand sections, add internal links |
| 4 | Core Web Vitals and HTTPS | New Poor or Needs improvement groups; HTTP URLs | Fix templates, then Start Tracking |
| 5 | Links and rich result reports | Key pages with few internal links; new invalid items | Add internal links; fix markup in code |
How long does this take? For a small site, often well under an hour. Add a custom annotation on the chart whenever you publish or change something big, and next month’s comparison becomes much easier to read.
Two habits make this routine work. First, write down three numbers each month: total clicks, total impressions and the count of indexed pages. Trends matter more than any single month. Second, change one thing at a time where you can, so the next audit tells you what worked.
When will you outgrow it? When you need data on competitors, keywords you don’t rank for yet, or a full crawl of every page. That is where paid suites earn their price. New to them? Our guide to what Semrush is and who it’s for explains how a paid suite differs from Google’s own data, and our roundup of free SEO marketing tools shows what other free plans add. Our Semrush review shows what a free Semrush account adds, and our comparison of SEO tools to check a website covers dedicated audit tools.
Your First Week With Search Console
Start small: verify a Domain property, submit your sitemap, and come back in a few days when data appears. That alone puts you ahead of many sites that never open the tool.
Then work through this short list:
- Inspect your homepage and your three most important pages. Are they all on Google?
- Open Page indexing and read the reasons for non-indexed URLs. Which ones are intentional?
- Open Performance, switch to the last 28 days, and note your top 10 queries.
- Check Security issues and Manual actions. A green check mark means you can move on.
- Set a calendar reminder for your first monthly audit.
None of this costs money, and Google keeps adding features. The branded queries filter, custom annotations and the generative AI reports all arrived in the last year. Search Console rewards site owners who show up once a month and act on what it tells them.
References
- Google Search Console
- Search Console Help: About Search Console
- Google Analytics Help: Queries report
- Search Console Help: Add a website or platform property to Search Console
- Search Console Help: Verify your site ownership
- Search Console Help: Managing owners, users, and permissions
- Search Console Help: Performance report (Search results)
- Search Console Help: About Search Console data
- Search Console Help: Advanced filtering and comparison
- Search Central Blog: Introducing the branded queries filter in Search Console
- Search Central Blog: Adding context to your Search Console data with custom annotations
- Search Central Blog: Introducing Search Generative AI performance reports in Search Console
- Search Central: Influencing Title Links in Google Search
- Search Console Help: Page indexing report
- Search Console Help: Sitemaps report
- Search Console Help: URL Inspection tool
- Search Console Help: Core Web Vitals report
- Search Console Help: HTTPS report
- Search Console Help: Rich result report overview
- Google Rich Results Test
- Search Console Help: Links report
- Search Console Help: Security issues report
- Search Console Help: Manual actions report
- Search Central: How to Use Search Console
- Search Central: Using Search Console and Google Analytics data for SEO