How to Use Google Search Console: Beginner’s Guide for 2026

How to use Google Search Console

To use Google Search Console, add your site as a property (a Domain property if you can edit DNS), verify that you own it, submit your XML sitemap, then use the Performance report to see which queries and pages earn clicks and the Pages report to find pages Google hasn’t indexed. After the first week, a 15-minute weekly look at the Overview, Performance and Pages reports, plus any alert emails, is enough for most sites. It is free and works with any Google account.

Because the data comes from Google itself, Search Console is the only place to see your real queries, real clicks and Google’s verdict on whether each page is indexed. It says nothing about competitors, and it doesn’t track what visitors do after they land; that is Google Analytics’ job (see Search Console vs Google Analytics 4). Menu names and limits below come from Google’s Search Console Help and the Search Central blog, checked on 30 October 2026.

Step 1: add your site (Domain vs URL-prefix)

Go to search.google.com/search-console, sign in, open the property selector at the top left and choose + Add property, then pick a property type. It is the one setup decision that is awkward to change later.

Google’s add a property help page explains both types. An account can hold up to 1,000 properties, and the two types coexist happily: a Domain property for the whole site plus URL-prefix properties for sections that need their own view.

Step 2: verify that you own the site

Search Console only shows data to people who prove they control the site. Verification is per person: the token Google gives you belongs to your Google account, and a colleague who verifies gets their own. Google’s verification help page lists these methods:

Search Console keeps checking the token. If it disappears, you are notified and lose access after a grace period, so treat the DNS record, file or tag as permanent. A DNS record that isn’t found straight away is usually still propagating: wait a day and click Verify again. Once a parent property is verified, child properties you create under it are verified automatically.

Step 3: add users and set permissions

Never share your Google login with an agency. Owners can give people their own access under Settings → Users and permissions → Add user: enter their Google account email and pick a level.

According to Google’s users and permissions page, a property can have up to 100 non-owner users. Keep at least two verified owners so access never depends on one person, and when an owner leaves, remove their verification token as well as their user entry: removing the user doesn’t delete the token.

Step 4: submit your sitemap

Google can find pages without a sitemap, but submitting one can speed up discovery and gives you a report to monitor. Most CMSs generate one, often at /sitemap.xml or /sitemap_index.xml.

1. Open Indexing → Sitemaps, paste the URL into Add a new sitemap and click Submit.
2. Check the Status column. Success means Google read it; Has errors means it read it but some entries couldn’t be parsed; Couldn’t fetch means Google couldn’t download it. Click a row for details.
3. Add a Sitemap: line to robots.txt too, so other search engines find it.

The report shows how many pages Google discovered in each sitemap, not how many are indexed. For that, open the Pages report and change the filter from All known pages to your sitemap. Google’s Sitemaps report documentation sets the limits at 50MB uncompressed and 50,000 URLs per file, and notes that deleting a sitemap from the report doesn’t stop Google crawling it.

While you are here, add the site to Bing Webmaster Tools too, which can import your verified sites and sitemaps from Search Console. Microsoft Copilot grounds its answers in Bing search, which is why Bing Webmaster Tools matters for AI search visibility.

The Performance report: where most of your time goes

Open Performance → Search results. The chart shows four metrics you can switch on and off: Total clicks, Total impressions, Average CTR and Average position. Below it, tabs break the data down by Queries, Pages, Countries, Devices, Search appearance and Dates. Average position in particular is easy to misread, so skim Search Console metrics explained before drawing conclusions.

The controls worth learning first

• Search type. The filter at the top now offers Web: text-based, Web: multimodal (searches that start from an image, such as Google Lens or Circle to Search), Image, Video and News.
• Date range. Anything from the last 24 hours, shown hourly, to the last 16 months. The newest data is preliminary and drawn with a dotted line.
• Weekly and monthly views. Switch the chart from daily to weekly when comparing periods, so weekends don’t add noise.
• Filters. Click + Add filter to narrow by query, page, country, device or search appearance. Query and page filters accept Custom (regex); the Search Console regex cheat sheet has patterns to copy.
• Compare. The date picker’s Compare tab puts two periods side by side, with a difference column in the table.
• Branded queries filter. On eligible sites it shows whether you are growing beyond people who already know your name; see branded vs non-branded queries.

Limits to keep in mind

The table and its export stop at 1,000 rows, rare queries are hidden for privacy (so rows won’t add up to the chart total), and data is kept for 16 months. For more rows or a longer history, the Search Console API guide explains the API and the BigQuery bulk export.

What to do with it

Three uses cover most of the value. Find queries in positions 8–20, close to page one (see the striking distance keywords playbook). Find queries with plenty of impressions but a low CTR, which usually need a better title. And mine the queries for topics you haven’t covered, the core of keyword research with Search Console.

Discover and Google News

The same menu holds Discover and Google News reports, which appear only once your site has enough impressions there and don’t show position. Google News means news.google.com and the News apps; the News tab in Search is the News search type above. Our Google Discover guide explains the Discover report.

What’s new in Search Console in 2025 and 2026

Many tutorials still describe an older interface. These are the changes announced on the Search Central blog since mid-2025:

The ones beginners should actually use

Annotations are the habit to start now. Mark launches, redesigns, migrations and big content updates, and in six months you will know why the line moved. The annotations help page allows 200 per property and deletes them after 500 days; restricted users can view but not add them.

AI-powered configuration, where you have it, turns “compare mobile clicks on blog pages with last quarter” into a view. It allows 20 requests per user per day and can’t sort or export, so check the filters it chose.

The generative AI performance report counts how often your pages appeared in AI Overviews and AI Mode: impressions only, no clicks or queries. If it is missing, your site may not have enough AI impressions yet, or it is excluded under Settings → Search generative AI. See our guide to the generative AI report.

A guided tour of every other report

Some reports appear only when they apply to your site: no products means no Shopping section, and no videos means no Video pages report.

Overview, Insights and Achievements

Overview summarises performance, indexing and enhancements, and lists recommendations when Google spots an issue or an opportunity. Insights is the friendlier summary, with cards for your content, queries leading to your site, top countries, branded and non-branded traffic and other sources such as Discover: a good page for colleagues who will never open Performance. Achievements tracks click milestones; pleasant, not diagnostic.

URL inspection

Paste any URL from your property into the search bar at the top. The result says URL is on Google, URL is on Google, but has issues or URL is not on Google, with the last crawl date and the user-declared canonical next to the Google-selected one. Test live URL checks the current version, and Request indexing asks Google to recrawl a new or updated page. Requests have a daily limit and don’t guarantee indexing, so save them for pages that matter.

Indexing: Pages, Video pages, Sitemaps and Removals

The Pages report (Google’s help calls it the Page indexing report) shows indexed and not-indexed counts and a Why pages aren’t indexed table. Don’t panic at the not-indexed number: redirects, intentional noindex tags and duplicates belong there. Focus on pages you want in Search, especially under Crawled – currently not indexed (see how to fix “Crawled – currently not indexed”). After a fix, click Validate fix; it typically takes up to about two weeks. Video pages does the same job for videos. Removals hides a URL for about six months; for good, add noindex or delete the page.

Experience: Core Web Vitals and HTTPS

Core Web Vitals uses real-user Chrome data, split into mobile and desktop. Good means LCP at or under 2.5 seconds, INP at or under 200 milliseconds and CLS at or under 0.1. Low-traffic sites often see no data, which is normal. HTTPS counts indexed URLs still served over http and explains why.

Shopping and Enhancements

When Google finds structured data, each rich result type (Breadcrumbs, Review snippets, Videos and so on) gets a report of valid and invalid items. Stores get Product snippets and Merchant listings, and eligible sites also get Merchant opportunities, with suggestions for how products appear; our ecommerce SEO guide covers them.

Security & Manual Actions

Manual actions lists penalties applied by a human reviewer, with a way to request review once fixed. Security issues flags hacked content, malware and deceptive pages. Both should say no issues detected.

Links

The Links report shows top linked pages, top linking sites and top linking text from other sites, plus your most internally linked pages. It is a sample, capped at 1,000 rows per table, and doesn’t mark nofollow links. The internal table quickly shows important pages your own site barely links to; see internal linking with Search Console.

Settings

Crawl stats shows Googlebot’s requests, response times and host status (root-level properties only), and the robots.txt report shows whether Google could fetch your robots.txt files. Settings also holds Ownership verification, Users and permissions, Associations (to link Google Analytics and other services), Change of address for domain moves (see our site migration monitoring guide), Bulk data export to BigQuery and the Search generative AI control.

Your first-week checklist

Spread setup over a week: DNS and data take a few days to arrive, and each step shapes the next.

1. Day 1: property and owners. Add and verify a Domain property, add a second verified owner, and give your agency or developer Full access.
2. Day 1: sitemap. Submit it, add the Sitemap: line to robots.txt, and check for Success the next day.
3. Day 2: health checks. Open Manual actions and Security issues; both should be clean. Check the robots.txt report and Crawl stats in Settings.
4. Day 3: inspect your key URLs. Run URL inspection on the home page and your five most important pages. Each should be on Google, with the Google-selected canonical matching yours.
5. Day 4: read the Pages report. Go through Why pages aren’t indexed and sort reasons into expected (redirects, intentional noindex) and worth fixing.
6. Day 5: set a baseline. Export the last 16 months of Performance data and note your top 20 queries and pages.
7. Day 6: annotate and link. Add annotations for past events you remember (launches, redesigns, migrations). Link Google Analytics under Settings → Associations.
8. Day 7: the rest. Glance at Core Web Vitals, HTTPS and any Enhancements reports, then import the site into Bing Webmaster Tools.

A 15-minute weekly routine

Google emails you when it finds new issues, and its getting started guide suggests checking about once a month. A short weekly look catches problems sooner.

1. Overview and inbox (2 minutes). Any new recommendations, issues or Search Console emails?
2. Performance (6 minutes). Compare the last 28 days with the previous period in the weekly view. Check clicks first, then the Pages tab sorted by click difference.
3. Pages and Sitemaps (3 minutes). Is the indexed count stable? Has a new not-indexed reason appeared? Do the sitemaps still say Success?
4. URL inspection (2 minutes). Inspect anything you published or changed this week.
5. Annotate (2 minutes). Record what you shipped, so next month’s chart explains itself.

Once a month, add Core Web Vitals, Enhancements, the generative AI report and Crawl stats. If clicks fall sharply across the site, stop the routine and work through the organic traffic drop diagnosis; if a few older pages slide slowly, that is content decay instead. Founders who want a fuller version with growth tasks can use the 30-minute weekly routine for SaaS founders.

Ask your Search Console data in plain English

Everything above works in the browser. The alternative is to ask an AI assistant to pull the numbers for you, through the Model Context Protocol (MCP): a server reads the Search Console API with your permission and exposes it as tools that Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex, Gemini CLI, Cline and other clients can call.

We make GSC MCP Server, a hosted Google Search Console MCP server that also reads Bing Webmaster Tools and changes nothing, so weigh this section accordingly. You connect Google once, add the server as a connector, and ask. The setup guide for Claude, ChatGPT and Cursor has the steps, and what a Search Console MCP server is explains how it works.

It covers the performance data above plus URL inspection (inspect_url), sitemaps (list_sitemaps) and Bing. It is read-only: it can’t request indexing, submit sitemaps or change settings, and it can’t read the Pages, Core Web Vitals, Links or generative AI reports (the API doesn’t expose them) or Google Analytics. The Free plan covers one account and 30 tool calls a month, and 40 more Search Console prompts are ready to copy.

Frequently asked questions