Google Search Console: the guide to steering your SEO and GEO visibility

This guide is for SEO managers, marketers and executives who want to use Google Search Console to steer their SEO and GEO visibility, to make decisions rather than simply observe. It covers setting up the property, reading the Performance report, indexing, errors, page experience, the API and visibility in AI Overviews.

For each report, you will know what it tells you, which decision it calls for and which article in this series goes deeper, along with a monitoring routine you can apply straight away.

Google Search Console: Definition, Purpose and Why It Matters for SEO and GEO

Google Search Console (GSC) is Google's free tool that shows how a website appears in search results and whether its pages can be crawled and indexed.

It shows which pages appear, for which queries, with how many clicks, and which barriers prevent Googlebot from crawling or indexing them. Formerly known as Google Webmaster Tools, it remains the most direct way to understand how Google sees your pages.

What GSC Actually Measures, and What It Does Not

Search Console collects data from the interaction between your website and Google's index. It covers four complementary dimensions:

• Visibility: queries, pages, clicks, impressions, CTR and average position, in the Performance report.
• Indexing and crawling: URL status, exclusion reasons, the Pages report, the Sitemaps report and the URL Inspection tool.
• Page experience: the Core Web Vitals report and the HTTPS report.
• Trust and security: Manual actions and Security issues.

GSC stops at the click: it tells you nothing about visitor behaviour on the site, conversions or attribution. That ground belongs to Google Analytics. Since June 2025, the Search Console Insights report has been built into GSC and works without Google Analytics (at the time of writing).

Creating a Google Search Console Account and Connecting Your Site

Choosing the Right Property Type: Domain vs URL Prefix

A Domain property covers all variants of the site (HTTP and HTTPS, subdomains): it is the best option for an overall view, but it can only be verified via DNS. A URL-prefix property is limited to a specific prefix, such as https://www.example.com/, and is used to segment by subdomain or directory. Methods, required roles and troubleshooting are covered in the verification guide at the end of this page.

Essential Settings After Connection: Users, Permissions and Alerts

Once the property is verified, share access across SEO, content and technical teams using three permission levels:

• Owner: manages the property, verifications and other users.
• Full user: sees all data and can take action in most reports.
• Restricted user: sees most data, without making changes.

Also monitor notifications in the interface and by email (indexing, security, unusual error spikes): they are your first warning signals.

Understanding the Performance Report to Manage Organic Traffic

The Four Metrics and Their Pitfalls

The Performance report keeps 16 months of data and displays 1,000 rows in the interface, up to 50,000 per request via the Search Analytics API (at the time of writing). The most recent days are preliminary data, so avoid comparing them too early. The table below summarises each metric:

A featured snippet counts as position 1. Always compare equivalent periods and track mobile and desktop separately: a ranking improvement does not always translate into clicks if an AI module appears.

Filters, Comparison and the Quick-Win Zone

Filters combine queries, pages, countries, devices, search types and search appearance; comparison mode sets two periods side by side. Position matters: the first position captures 27.6% of clicks (Backlinko, 2026), as detailed in our SEO statistics. Pages in positions 4–10 with high impressions therefore form the quick-win zone. Three analyses pay off particularly well there:

• Rising queries with low CTR: rework the title, meta description, answer angle and structure.
• Pages in positions 4–10 with high impressions: complete the content, strengthen internal linking and verify intent.
• Cannibalisation: two pages splitting impressions across similar queries; consolidate, differentiate intent or adjust canonicalisation.

For a page in decline with no obvious cause, compare it with competing pages: content and links remain the levers.

Indexing and Crawling: Fixing Issues That Block Your SEO

The Indexing Cycle, the Pages Report and URL Inspection

Googlebot discovers a URL, crawls it and renders it, then Google decides whether or not to index it. A page that is not indexed appears neither in search results nor in AI Overviews. The pace and health of this crawling can be read in the Crawl stats report, explained in our article on monitoring crawling in GSC.

The Pages report lists indexed and non-indexed URLs, with the reason for each exclusion. Prioritise based on the business importance of the URL and the number of URLs affected. The full table of statuses, their causes and the actions to take is in the dedicated indexing article.

The URL Inspection tool tells you whether the "URL is on Google", which canonical Google has selected and how the page is rendered. The indexing request it offers should be reserved for strategic pages (a new business page, a major update): it remains manual, guarantees nothing and cannot be automated through the API.

Sitemaps, robots.txt and Canonicals: Avoiding Contradictions

The sitemap declares the URLs you want indexed; the Sitemaps report then compares submitted URLs with indexed URLs, as explained in our guide to managing sitemaps in GSC. Include its location in your robots.txt file, whose syntax is detailed in our guide to the robots.txt file.

A URL listed in the sitemap but blocked by robots.txt or marked noindex sends Google two contradictory signals and slows down useful indexing. Also check canonical consistency on key pages: an inconsistent canonical can cause Google to drop a page from the index in favour of another variant.

Errors and Redirects: Which Status, Which Decision

Each status in the Pages report calls for a different decision. The table below maps the most common ones to their meaning and the expected action:

A 404 is not an error to fix in itself and does not affect the ranking of the rest of the site: only redirect to a genuine equivalent, otherwise leave the 404 or switch to a 410. Detailed cases are covered in our guides to 404 errors in GSC, the noindex status in GSC and the robots.txt report in GSC. 403 errors, redirects and URL removal are covered at the end of this page.

Rich Results, Page Experience and Security: Reports Worth Monitoring

Structured Data and Rich Results Reports

For each type of markup detected, GSC shows valid items, errors (which block eligibility) and warnings (partial markup). Depending on your pages, the most useful types are the following:

• Breadcrumbs: clarify site hierarchy and how it is displayed in search results.
• Reviews and ratings: enrich the display if the markup is compliant and the reviews are verifiable.
• Videos: help index videos hosted on your site.
• Events: highlight your events in search results.
• Datasets: surface published data in specialised searches.

FAQ and HowTo rich results have been withdrawn for most sites since 2023: they are no longer priorities. The markup itself is detailed in our guide to structured data. Then cross-reference these reports with the Performance report: if impressions rise but clicks do not, the issue is CTR (snippet, title, intent) rather than indexing.

Core Web Vitals, HTTPS and Security

Four reports monitor experience and trust, each with its own decision:

• Core Web Vitals report: groups URLs by real-world performance measured among users (CrUX data), on mobile and desktop, to prioritise the groups to fix.
• HTTPS report: flags pages still served over HTTP, to be migrated; certificate configuration is a hosting matter.
• Manual actions: indicates a penalty applied by a Google team; once fixed, you can submit a reconsideration request.
• Security issues: alerts you to a hack, malware or content injection.

In the last two cases, document your fixes (URLs, dates, measures taken): the review will be all the faster.

Advanced Google Search Console Features

Links and Removals: When to Use Them

The Links report shows which sites link to yours, your most linked pages and your most internally linked pages. Start with high-potential pages (high impressions, positions 4–10) and check that they receive enough links.

The Removals tool, reserved for property owners, hides a URL from search results for around 6 months or clears its snippet. The public Remove Outdated Content tool is different: it is used on a site you do not own, provided the page has changed or disappeared. A lasting removal requires a 404, a 410 or a noindex.

Google Search Console API: Use Cases and Quotas

The API lets you go further than the interface, within documented limits (at the time of writing):

• Performance: extract up to 50,000 rows per request, compared with 1,000 in the interface.
• Inspection: check URLs in bulk, within a limit of 2,000 inspections per day per property.
• Sitemaps: submit, delete and list sitemaps.

These quotas are detailed in our article on Search Console quotas. The API does not request indexing, and the Indexing API is reserved for JobPosting and BroadcastEvent pages.

GSC and Generative Engines (GEO)

AI Overviews and AI Mode rely on Google's index: a page that is not indexed cannot appear in them. Their impressions and clicks are counted in the Performance report, under the "Web" search type, with no dedicated filter (AI Mode since June 2025, at the time of writing). You cannot isolate this visibility, but you can see its effect: stable impressions, falling clicks.

The trend is massive: more than 50% of Google searches display an AI Overview (Squid Impact, 2025), as our GEO statistics point out. Tracking impressions and CTR together becomes a leading indicator. To be reused or cited, structure your content so it is easy to extract:

• descriptive headings that announce the answer;
• a short answer at the start of each section;
• lists and tables for comparisons;
• cited sources and relevant structured data;
• regular updates to key pages.

The full method is presented in our guide to Generative Engine Optimization.

Best Practices for Using Google Search Console Day to Day

One Cadence: Alert, Decide, Validate

Search Console is there to connect a signal to a prioritised action. Each review rhythm therefore has its own role, reports and decision:

A fix can take several weeks to be reflected: measure before and after over comparable periods before drawing conclusions.

Turning GSC Data into Content Decisions

Data from the monthly review feeds directly into the editorial plan:

• spot emerging queries to plan new content, especially long-tail topics;
• rewrite or enrich pages with high impressions and low clicks;
• strengthen internal linking to strategic pages and reduce cannibalisation;
• plan updates for pages whose impressions or rankings are declining.

Depending on Your Situation

Depending on the problem you are facing, here is the article in this series to open first:

• You are creating your property: choose the method that suits your access with the guide to verifying a property in Google Search Console.
• Important pages are not indexed: read each status and its action in the guide to indexing in Google Search Console.
• Your organic traffic is declining: isolate the cause by query, page and device with the guide to the GSC Performance report.
• You want to automate your exports: discover the available resources in the guide to the Google Search Console API.
• Your GSC clicks and GA4 sessions do not match: understand the gap with the guide to connecting Search Console and Google Analytics.
• Googlebot is being refused access: find the cause of the block with the guide to 403 errors in GSC.
• A URL must disappear from search results: choose between temporary and lasting removal with the guide to removing outdated content from Google.
• You are migrating or merging pages: check your redirect chains and migrations with the guide to 301 redirects in GSC.

To cross-reference GSC alerts with a technical and semantic audit and get a prioritised list of fixes, you can rely on our 360° SEO and GEO audit.

Google Search Console FAQ

How Does Google Search Console Work?

Google Search Console gathers data about how Google crawls, indexes and displays your site. It provides visibility metrics (impressions, clicks, CTR, average position) and technical reports (indexed pages, sitemaps, errors, security). This data helps you diagnose blockers and prioritise the actions that improve visibility in Google Search.

How Do I Set Up and Verify Google Search Console for a Website?

You add a property in Google Search Console, then prove that you control the site. Choose a Domain property, which can only be verified via DNS, or a URL-prefix property, which accepts several methods depending on your access. Once the property is verified, add users with the right permissions and submit your sitemaps.

Why Use Google Search Console Alongside an SEO Tool?

Google Search Console is the only source that gives you Google's perspective on your performance and technical blockers before the click. An SEO or analytics tool is better suited to prioritising, industrialising analysis and linking work to business outcomes. The two uses are complementary.

What Is the Difference Between Google Search Console and Google Analytics?

Google Search Console measures visibility in Google Search, whereas Google Analytics measures what happens on the site after the click. The former tracks impressions, clicks, CTR, position and indexing; the latter tracks sessions, engagement and conversions. Their figures do not line up, because they neither count the same unit nor count at the same moment.

What Should I Do If a Page Is Crawled but Not Indexed?

A page marked "Crawled – currently not indexed" first needs to gain value and importance in Google's eyes. Check the intent, quality and uniqueness of the content, then strengthen internal linking to the page. In the URL Inspection tool, check the selected canonical and that no noindex applies. If everything is correct, earn external links to the page and the domain.

How Can I Tell Whether an Issue Comes from robots.txt, noindex or a Canonical?

The URL Inspection tool answers all three questions in a single analysis. It indicates whether crawling is allowed by robots.txt, whether a noindex directive has been detected and which canonical URL Google has selected. Then check the robots.txt file and the canonical tag in the HTML or the HTTP header.

Do AI Overviews Appear in Google Search Console?

Yes, AI Overviews and AI Mode are counted in the Performance report, but without a dedicated filter. Their impressions and clicks are included in the "Web" search type; AI Mode has been included since June 2025, at the time of writing. A page that is not indexed cannot appear in them: indexing remains the prerequisite.