How to use Google Search Console for SEO
Google Search Console is Google's free tool for seeing how your site does in Google Search. Add your site as a domain property, submit a sitemap, then use four reports: Performance for clicks, impressions, CTR and position; Page indexing for pages Google left out; URL Inspection for one page at a time; and the AI performance report for AI Overviews. Once a week, look for pages that rank just off the top, pages with low CTR for their position, pages losing clicks, and pages competing for the same search.
What Search Console tells you, and what it does not
Search Console reports what Google saw: which searches showed your pages, how often people clicked, where you ranked on average, and which pages Google indexed or skipped. It is the only place that shows the actual searches behind your Google traffic, so it is the starting point for most SEO work.
It does not show other search engines, what happened after the click, or why Google ranked a page where it did. Use Bing Webmaster Tools for Bing, and your analytics tool for visits and sign-ups. Rare searches are hidden for privacy, so query tables never add up to the site total.
Set it up in fifteen minutes
Choose a domain property if you can. It covers every subdomain and both http and https in one view, and you verify it once with a DNS record at your domain registrar. A URL-prefix property covers one exact address and suits a site you cannot add DNS records for.
After verification, submit your sitemap in the Sitemaps report. If your site splits its sitemap by section, submit each section file too, so the Page indexing report can be filtered by section. Then add teammates under Settings, Users and permissions, giving full access only to people who change the site.
Recent days usually arrive about two days late, and the Performance report keeps 16 months of history, so set it up early even if you will not use it yet.
- Add a domain property and verify it with a DNS TXT record.
- Submit the sitemap index and each section sitemap.
- Add teammates with the least access they need.
- Link Search Console to your analytics tool if you use one.
Read the Performance report: four numbers
Impressions count how often a link to your site appeared in results a person loaded. Clicks count how often someone clicked through. CTR is clicks divided by impressions. Average position is the mean of your highest position in each result, so a page at position 8 in one search and 40 in another shows about 24, which matches neither.
Read the numbers by page and by query, never only as a site total. Set the date range to the last 28 days or 3 months, then use Compare to set it against the previous period or the same period last year. Filter by country and device when your audience is mostly in one place or on one kind of device.
Treat impressions as demand and position as distance. A page with thousands of impressions at position 80 is being considered for a search it does not yet answer well. A page with a few hundred impressions at position 12 is close enough that a better answer can move it onto page one.
| Number | What it counts | Common misreading |
|---|---|---|
| Impressions | Times a link to your site appeared in loaded results | Assuming every impression was seen. A result far down the page counts too. |
| Clicks | Clicks from Google Search to your site | Expecting it to match visits in analytics. The two count differently. |
| CTR | Clicks divided by impressions | Comparing CTR across positions. Position 2 and position 9 have very different normal CTRs. |
| Average position | Mean of your top position in each result | Reading it as a rank. It is an average across many searches and places. |
Read the Page indexing report: why a page is not in Google
The Page indexing report, under Indexing then Pages, splits your URLs into indexed and not indexed, with a reason for each one that is not. Most sites have many URLs that are rightly not indexed, such as redirects, filtered listings and old pages. The question is whether a page you care about is in the wrong group.
Start from your sitemap, not the whole list. Filter the report to your submitted sitemap, so it only shows the pages you asked Google to index. Then open each reason and look at the example URLs.
| Status in the report | What it means | First thing to check |
|---|---|---|
| Crawled, currently not indexed | Google fetched the page and chose not to index it for now. | Is the page thin, a near copy of another page, or hard to reach through internal links? |
| Discovered, currently not indexed | Google knows the URL but has not fetched it yet. | Do other pages link to it? Is the sitemap current? Is the server slow or returning errors? |
| Duplicate, Google chose different canonical than user | Google treats another URL as the main version. | Which URL did Google pick in URL Inspection, and is that the page you want shown? |
| Excluded by 'noindex' tag | The page asks not to be indexed. | Was the noindex deliberate? Check the HTML and the X-Robots-Tag header. |
| Page with redirect | The URL redirects somewhere else, so the target is indexed instead. | Usually fine. Fix internal links and sitemap entries that still point at the old URL. |
| Not found (404) and Soft 404 | The page is missing, or looks empty enough that Google treats it as missing. | Restore it, redirect it to the closest page, or let it go if nothing replaces it. |
| Blocked by robots.txt | Google is not allowed to fetch the URL. | Was the rule deliberate? A blocked URL can still be indexed from links, without its content. |
Use URL Inspection for one page at a time
Paste a URL into the search bar at the top of Search Console. URL Inspection shows whether the page is indexed, the canonical Google chose, when Google last crawled it, and whether it found the page through your sitemap or links.
Test live URL checks the page as it is now, which helps after a fix. If the live test looks right, Request indexing asks Google to crawl it again. Use it for pages you changed in a meaningful way; requesting the same page over and over does not speed anything up.
Compare Google's chosen canonical with the one in your page. If they differ, Google is treating another page as the main version, and the fix is usually to make the two pages clearly different or to point one at the other.
Six checks to run every week
These six checks find most of the work worth doing. Each one starts from the Performance report with the last 28 days or 3 months selected. The thresholds in parentheses are the ones RankEcho uses; they are a sensible starting point, not Google rules.
| Check | How to find it by hand | What to do |
|---|---|---|
| Pages just off the top | Queries at positions 4 to 20 with real impressions (RankEcho: 100 or more in 28 days) | Answer the query near the top of the ranking page and use its wording in a heading. |
| Low CTR for the position | Pages in the top 10 whose CTR is well below your site's normal CTR at that position (RankEcho: under 60%) | Check the title and snippet against what the searcher wants, then rewrite one. |
| Pages losing clicks | Compare the last 90 days with the 90 before and with last year (RankEcho: a 30% drop on pages with 30+ clicks) | See which queries dropped, then update the page. |
| Pages competing for one search | Filter by a query and open the Pages tab; two or more of your pages share the impressions (RankEcho: each with 15% or more) | Pick the page that should own the search and give the other a different job. |
| Searches with no page | Queries beyond position 10 that no page on your site is about | Write a page or a section that answers it. |
| Indexed pages with no impressions | Pages in the Page indexing report that never appear in the Performance report | Check the search the page targets, its internal links and its canonical. |
A real example: rankecho.io's own Search Console
From June to October 2026, rankecho.io had 24,584 impressions and 15 clicks in Google Search. In October alone it had 4,603 impressions and 5 clicks at an average position of 55.8. That is a young site: Google shows it for many searches, but mostly far down the results.
The query rows from 1 August to 29 October 2026 covered 841 searches across 113 pages. Two checks from the table above found the clearest work. First, pages competing: "search intelligence tools" had 391 impressions at an average position of 13.1, split across 8 RankEcho pages. Second, searches with no page: "ai visibility checkers" (412 impressions, position 89.1), "best ai overview checkers" (273, position 84.9) and "ai overview checkers" (231, position 95.1) all landed on a roundup article, when the searcher wanted a tool to use.
So we gave "search intelligence tools" one owning page and rewrote the others for their own searches, without redirecting any of them, and built a free AI visibility checker and AI Overview checker for the tool searches. Whether those changes work will show in the same reports over the next weeks; nothing here is a result yet.
AI Overviews and AI Mode in Search Console
Google's Generative AI performance report shows link impressions when your pages appear in AI Overviews and AI Mode. Read it like the Performance report: by page, over a consistent period, and with clicks and conversions checked separately.
If a page earns AI impressions but few clicks, the answer may already be in the overview. Check what the overview says about your topic, and whether your page offers something the summary cannot, such as a tool, data or a worked example.
Do it by hand, or let RankEcho read it for you
Everything above works by hand in Search Console with a spreadsheet. Expect about an hour a week for a site with a few hundred pages, mostly spent exporting, filtering and comparing periods.
SEO/GEO/AEO Intel in RankEcho connects to Search Console with Google's read-only permission. It collects up to 16 months of site and page data and the latest 90 days of queries, runs the first five checks from the table after each daily sync, and ranks the results by likely extra clicks measured against your own site's CTR at each position. From a result you can open the Writer to refresh or write a page, or a Fix for a title and description, and mark the work done to compare the 28 days before and after.
It is free for 3 days on one site, with no card. Growth and Agency plans include it; on Solo it is an add-on at $29/month. Your team still reviews and publishes every change, and before-and-after numbers describe what happened, not why.
Sources reviewed
Search and publication principles below were checked against primary documentation. The worked examples are fictional; these sources do not establish a traffic outcome or a guaranteed ranking.
5 claim-level source records
| Claim reviewed | Official source | Review record |
|---|---|---|
| The Performance report shows clicks, impressions, CTR and average position for Google Search, and can be grouped and filtered by query, page, country, device, search appearance and date. | Google Search Console: Performance report | Checked 2026-11-02 · Google public documentation, reviewed 2 November 2026 · Defines the four numbers used on this page. It does not say what a good value is for any site. · Confidence: High |
| The Page indexing report lists the URLs Google knows about on a property, whether each is indexed, and the reason a URL is not indexed. | Google Search Console: Page indexing report | Checked 2026-11-02 · Google public documentation, reviewed 2 November 2026 · Status names are quoted as Google uses them. The first checks in the table are RankEcho's suggestions, not Google's. · Confidence: High |
| URL Inspection shows the indexed version of a URL and can run a live test of the current page; a person with access can request indexing from it. | Google Search Console: URL Inspection tool | Checked 2026-11-02 · Google public documentation, reviewed 2 November 2026 · A live test passing does not mean Google will index the page. A request to index is not a promise. · Confidence: High |
| The Sitemaps report lists sitemaps submitted through the report or the API and the status of Google's last fetch of each one; submitting needs owner permission. | Google Search Console: Sitemaps report | Checked 2026-11-02 · Google public documentation, reviewed 2 November 2026 · Sitemaps listed only in robots.txt can still be used by Google but do not appear in this report. · Confidence: High |
| Search Console has a Generative AI performance report with link impressions from AI Overviews and AI Mode. | Google Search Console: Generative AI performance report | Checked 2026-11-02 · Google public documentation, reviewed 2 November 2026 · Impressions in AI features are not clicks or conversions. Availability can differ by property. · Confidence: High |
Frequently asked questions
Yes. Search Console is free for anyone who can verify they own or manage a site.
Recent days usually arrive about two days late. The Performance report keeps up to 16 months of history.
Use a domain property when you can add a DNS record. It covers every subdomain and protocol in one view. Use a URL-prefix property for one exact address, or when DNS is out of your hands.
They count different things. Search Console counts clicks from Google Search; analytics counts visits it can record, which depends on consent, blockers and how the visit is attributed.
There is no single target. Read position per query: under 10 is page one, 11 to 20 is close enough to improve, and beyond 50 usually means the page does not yet answer that search well.
No. The free AI visibility audit uses only your public domain. Connecting Search Console is optional and adds the Google Search checks on this page.