What is Google Search Console and what is it for?
Google Search Console is a free tool from Google that shows how your website performs in Google Search. That is the short answer to what is Google Search Console: a dashboard, connected directly to Google's own data, that reports which of your pages appear in search results, how many clicks and impressions they get, what average position they hold, and whether Google can crawl and index them. It is the closest thing to seeing your site through Google's eyes.
You use it for four jobs that no other free tool does as well. First, measure search performance — the exact queries people type to find you, and how each page ranks for them. Second, check indexing — which URLs are in Google's index and which were excluded, with the reason. Third, submit and monitor sitemaps so Google discovers new pages faster. Fourth, catch problems early — Google emails you when it detects a crawl error, a manual penalty, or a Core Web Vitals issue.
One thing Google Search Console is *not*: it does not index your site for you. Adding a property and submitting a sitemap tells Google where your pages are, but ranking still depends on your content, links, and technical health. Search Console is a reporting and diagnostic tool — it shows you what is wrong so you can fix it, following the workflow in how to do an SEO audit.
Think of Search Console as Google's report card for your site. It grades the work; it does not do the work.
Is Google Search Console free, and GSC vs Google Analytics
Yes — Google Search Console is completely free, with no paid tier, no seat limits, and no signup cost beyond a Google account. Anyone who owns or manages a website should have it connected, because the data it exposes about how Google sees your site is available nowhere else at any price.
The most common confusion is Search Console versus Google Analytics, because both are free Google products. The difference is simple: Search Console reports what happens on Google before the click (impressions, ranking position, and the query someone searched), while Google Analytics reports what happens on your site after the click (page views, time on page, conversions, and traffic from every source, not just Google). They answer different questions and are strongest used together.
Here is a side-by-side so you know which tool to open for which question:
| Dimension | Google Search Console | Google Analytics |
|---|---|---|
| What it measures | Performance in Google Search (before the click) | Behavior on your site (after the click) |
| Key metrics | Impressions, clicks, position, CTR, indexing | Sessions, page views, time on page, conversions |
| Traffic sources | Google organic search only | All sources — search, social, direct, referral, ads |
| Shows search queries | Yes — the exact terms people searched | No — organic query data is not exposed |
| Shows indexing status | Yes — which pages are in Google's index | No |
| Best question to ask it | Why isn't this page getting search traffic? | What do visitors do once they arrive? |
A practical rule: when the question is *"why isn't this page getting search traffic?"* start in Search Console, because the answer is usually a ranking, indexing, or query-match problem it can show you. When the question is *"what do visitors do once they arrive?"* open Analytics. Neither replaces the other.
How to set up Google Search Console (verify ownership)
Setting up Google Search Console takes a few minutes and comes down to one core step: proving you own the site. Google will not show you private performance data until you verify ownership, which stops anyone from spying on a competitor's numbers. Here is the full flow:
- Sign in with a Google accountGo to search.google.com/search-console and sign in — the same account you use for Gmail works.
- Add your propertyChoose a Domain property (covers all subdomains and protocols) or a URL-prefix property (one exact address).
- Verify ownershipAdd a DNS TXT record for a Domain property, or upload an HTML file / add a meta tag for a URL-prefix property.
- Submit your sitemapOpen the Sitemaps report and submit sitemap.xml so Google can discover your pages efficiently.
- Request indexing of key pagesUse URL Inspection to ask Google to crawl your most important URLs first.
- Review reports as data arrivesPerformance and Pages populate within a day or two — then check them regularly and fix what they flag.
You choose one of two property types when you add the site. A Domain property covers every version of your site at once — http, https, www, and all subdomains — and is verified by adding a TXT record to your domain's DNS. A URL-prefix property covers only one exact address (for example https://www.example.com/) and offers more verification methods: uploading an HTML file, adding a meta tag, or connecting through Google Analytics or Tag Manager. For most people the Domain property is the cleaner choice because it captures all traffic in one place.
After verification, do two things immediately. Submit your sitemap under the Sitemaps report (usually sitemap.xml) so Google can discover your pages efficiently — this matters most for new sites and is closely tied to crawl budget. Then request indexing for your most important URLs using the URL Inspection tool. Data takes a day or two to start populating, so do not panic if the Performance report is empty on day one.
The key reports and how to use them for SEO
Google Search Console has four reports that do the heavy lifting, and knowing what each one answers is how you turn it from a dashboard into an SEO workflow. Learn these four and you can diagnose almost any organic-traffic problem.
Performance is where you live. It lists every query and page with its clicks, impressions, click-through rate, and average position. The highest-return move here is to filter for pages ranking in positions 11-20 — page two — because a small improvement often lifts them onto page one. Low CTR at a high position usually means a weak title or meta description you can rewrite. This is the raw material for how to improve website ranking on Google.
Pages (the indexing report) shows which URLs are indexed and which are not, grouped by reason — Crawled - currently not indexed, Discovered - not indexed, Excluded by noindex tag, and more. When a page is missing from Google entirely, this is the first place to look; the reasons map directly to the fixes in why is my page not indexed.
Sitemaps confirms Google read your sitemap and how many of its URLs were indexed. Enhancements / Experience reports on structured data, mobile usability, and Core Web Vitals, flagging invalid markup and slow pages. Together these four reports cover the technical side of SEO — pair them with the broader picture in what is technical SEO.
Search Console tells you *what* is wrong; it does not always tell you *why* or check the newer signals. To go further — including whether AI answer engines can read and cite your pages — run a free SEO + GEO audit on any URL and it flags on-page, indexing, and GEO issues in one pass.
Common Search Console mistakes to avoid
The biggest mistake is treating Search Console as a vanity dashboard you glance at once a month. Its value is diagnostic: the Performance and Pages reports are where you find specific, fixable problems, so the habit that pays off is reviewing them regularly and acting on what they surface, not just watching the totals rise and fall.
A second common error is misreading the average position metric. It is an average across every query and device where your page appeared, so a single number like "position 14" hides the fact that you might rank third for one query and fortieth for another. Always filter by query or page before drawing conclusions — the aggregate view is a starting point, never the answer.
Finally, people submit a sitemap and assume the job is done. A sitemap helps discovery, but pages still get excluded for reasons like noindex tags, duplicate content, or thin value. Check the Pages report a week after launch to confirm your important URLs actually made it into the index — discovery and indexing are two different steps, and only the Pages report tells you the second one succeeded.