Google Search Console: A Beginner's Guide

Google Search Console is the free tool where Google tells you how it crawls, indexes and shows your site in search results. To use it you add your site as a property, prove ownership (DNS record, HTML file, meta tag, Google Analytics or Tag Manager), submit a sitemap, and then check three reports regularly: Performance, Page indexing and URL Inspection. Everything else is there for when something specific goes wrong.

This guide covers setup first, then each report in the order a beginner should learn them.

What Search Console is, and what it is not

It is Google's own data about your site: the queries you appear for, which pages are indexed and why others are not, crawl errors, manual actions and security problems.

It is not an analytics tool. It knows nothing about what visitors do after the click. It is not a rank tracker either: "average position" is an average over every impression, not a daily ranking for a keyword. And it does not influence rankings. It reports.

Step 1: choose a property type

When you click Add property, Search Console offers two types.

	Domain property	URL-prefix property
Example	example.com	https://www.example.com/
Covers	All subdomains (www, m, blog, shop) and both http and https	Only URLs that start with exactly that prefix, including protocol and host
Verification	DNS record only	HTML file, HTML tag, Google Analytics, Google Tag Manager, DNS
Good for	The complete picture of a domain	One subdomain, one subfolder such as /blog/ or /de/, or when you cannot edit DNS
API identifier	sc-domain:example.com	https://www.example.com/

My recommendation: create the Domain property as your main one. Then add URL-prefix properties where they earn their place:

• Subfolders you want to look at alone, such as https://www.example.com/blog/. Each property has its own reports, and its own quotas: the URL Inspection API allows 2,000 inspections per day per property, so sections as separate properties give large sites more room.
• When a tool or feature needs it. A few legacy reports and some third-party integrations work only with URL-prefix properties.

You can have many properties for the same site. They do not conflict.

Step 2: verify ownership

Verification proves to Google that you control the site. There are five main methods, and you can set up more than one as a backup.

DNS record (works for both property types, required for Domain)

1. Search Console shows a TXT record that looks like google-site-verification=AbC123....
2. In your DNS provider (your registrar, Cloudflare, Route 53 and so on), add a TXT record on the root domain. Host or name is usually @, value is the full string.
3. Go back and click Verify. DNS changes can take from minutes to a day or two to propagate. If it fails, wait and try again.

For some providers Search Console offers a guided flow that logs in to the DNS host and adds the record for you. A CNAME option exists too, for DNS hosts that make TXT records awkward.

Leave the record in place permanently. Google rechecks it.

HTML file upload

Download the googleXXXXXXXX.html file and upload it to the root of the site so that it is reachable at https://www.example.com/googleXXXXXXXX.html. It has to be served without a login and without being redirected elsewhere. Simple and reliable, as long as you can upload to the web root and the file survives deployments.

HTML tag

Add the meta tag Search Console gives you inside <head> on the homepage:

<meta name="google-site-verification" content="AbC123..." />

Most CMSs and SEO plugins have a field for this. Yoast and Rank Math in WordPress both do. The risk is a theme change or plugin removal taking the tag with it.

Google Analytics

Works if the homepage carries your Google Analytics tag in the <head> and your Google account has edit rights on that Analytics property. No code changes needed if Analytics is already installed correctly.

Google Tag Manager

Works if the GTM container snippet is on the homepage and your account has publish permission on the container.

Which method should you pick?

Situation	Use
You control DNS	DNS TXT, with a Domain property
No DNS access, you can edit the site	HTML tag or HTML file
Marketing team with Analytics or GTM access only	Analytics or Tag Manager
Site on Blogger or Google Sites	Usually verified automatically for the account that owns it

A common failure: verifying http://example.com when the site lives on https://www.example.com. With URL-prefix properties the prefix has to match exactly. A Domain property avoids the whole problem.

Step 3: add people

Settings > Users and permissions. Three levels:

• Owner. Full control, including adding users. A verified owner proved ownership with a token. A delegated owner was added by a verified owner.
• Full user. Sees all data and can take some actions.
• Restricted user. Read-only on most data.

Give agencies and freelancers Full access unless they truly need Owner, and remove people when they leave. If someone verified with their own token (say, a meta tag from their account), removing the user is not enough. Remove the token as well, from Settings > Ownership verification.

One thing that needs Owner: using Google's Indexing API. The service account or user that calls the API has to be an owner of the property.

Step 4: submit a sitemap

Indexing > Sitemaps, enter the sitemap URL (for example sitemap.xml or sitemap_index.xml) and click Submit.

After it is processed you see a status (Success, Couldn't fetch, Has errors) and the number of discovered pages. Click through to see the index coverage for that sitemap alone, which is one of the most useful views in the tool.

If you get "Couldn't fetch", open the sitemap URL in a browser, then test it with the XML Sitemap Validator. On brand-new properties this status often appears for a day and clears without any action. If you do not know where your CMS puts the sitemap, the Sitemap Finder checks robots.txt and common locations. Sitemap rules are covered in the XML sitemap guide.

The reports that matter

Performance: how you appear in search

Performance > Search results shows four metrics:

Metric	Meaning
Clicks	Clicks from Google Search results to your site
Impressions	How often a link to your site was shown in results the user loaded
CTR	Clicks divided by impressions
Average position	Average of your topmost position over all impressions

Below the chart are tabs for Queries, Pages, Countries, Devices, Search appearance and Dates. Things beginners should know:

• The report holds 16 months of data. Export regularly if you want longer history.
• Tables show a maximum of 1,000 rows in the interface. The API and the BigQuery bulk export return more.
• Some queries are hidden for privacy (anonymised queries), so query rows add up to less than the total.
• Filter, then compare. Click + Add filter > Page, enter a URL, then open the Queries tab to see what that page ranks for. Use Date > Compare to see what changed after an update.
• Use a regex filter on Query to separate brand from non-brand traffic.

A useful first exercise: filter to queries with an average position between 8 and 20 and sort by impressions. These are pages close to the first page, where improving the content and internal links pays back quickest. If pages are indexed and get no impressions at all, read indexed but not ranking.

URL Inspection: one URL, Google's view

Paste any URL of your property into the search bar at the top. You get:

• whether the URL is on Google, and if not, why;
• how Google discovered it (sitemaps, referring page);
• the last crawl date, the crawler used, whether the fetch succeeded;
• the canonical you declared and the canonical Google selected;
• detected enhancements such as structured data.

Test live URL fetches the page right now, which is how you check a fix before Google recrawls. Request indexing adds the URL to a priority crawl queue. It has a small daily limit and no guarantee. The complete walkthrough is in the URL Inspection tool guide, and the limits are in request indexing limits.

Page indexing: what is indexed and what is not

Indexing > Pages. The chart shows indexed and not indexed counts over time. Under it, "Why pages aren't indexed" lists each reason with a count. Click a reason to get example URLs (up to 1,000).

Not every entry is a problem. "Page with redirect", "Alternate page with proper canonical tag" and "Excluded by 'noindex' tag" are usually Google confirming that your setup works. Focus on:

• Server error (5xx), Redirect error, Not found (404) for URLs that should exist
• Blocked by robots.txt or noindex on pages you want indexed
• Discovered and Crawled - currently not indexed on important pages
• Duplicate, Google chose different canonical than user

The most useful trick: switch the filter at the top from "All known pages" to All submitted pages. Now you see only sitemap URLs, the ones you explicitly want indexed. Every status is explained in the Page indexing report guide.

After fixing an issue, open it and click Validate fix. Google says validation usually takes up to about two weeks and sometimes longer.

Sitemaps, Removals and Video pages

Also under Indexing:

• Sitemaps: covered above.
• Removals: temporarily hides a URL from results for about six months. It does not delete anything from the index permanently. For a permanent removal you need a 404, 410 or noindex on the page itself. Use it for emergencies, such as leaked private content.
• Video pages: appears if Google detects videos on your pages, and shows whether the video was indexed.

Experience

• Core Web Vitals: groups URLs as Good, Needs improvement or Poor for LCP, INP and CLS, based on real Chrome user data. New or low traffic sites often show "Not enough usage data", which is normal and harmless.
• HTTPS: lists pages that are not served over HTTPS and why.

Enhancements and Shopping

These reports appear only when Google finds the relevant structured data: Breadcrumbs, FAQ, Product snippets, Merchant listings, Review snippets, Videos and so on. Each shows valid and invalid items with the specific error, for example Missing field "price". To see the markup on a page, use the Structured Data Viewer.

Security and Manual actions

Two pages you hope stay empty.

• Manual actions: a human reviewer at Google found a violation of the spam policies. The report says what and where. After fixing it you file a reconsideration request from the same page.
• Security issues: hacked content, malware, deceptive pages.

Search Console emails owners when either appears, so keep the notification emails switched on.

Links

Top linked pages (external and internal), top linking sites and top linking text. The data is a sample and lags, but it is free and comes from Google. Use the internal links table as a quick check that important pages are near the top.

Settings

Worth knowing about:

• Crawl stats: total crawl requests, download size, average response time, breakdowns by response code, file type, purpose (discovery or refresh) and Googlebot type, plus host status for robots.txt fetch, DNS and server connectivity. Check it whenever indexing slows down.
• robots.txt report: which robots.txt files Google found, when it last fetched them, and any parsing warnings.
• Change of address: tells Google about a move to a new domain. Used together with 301 redirects during a site migration.
• Bulk data export: daily export of performance data to BigQuery, for sites that outgrow the 1,000 row interface.

A simple routine

Weekly (10 minutes)

1. Performance, last 7 days compared with the previous 7. Any sharp drop? Check which pages and queries.
2. Page indexing, All submitted pages. Any new reason, or a growing count?
3. Check email for Search Console alerts.

Monthly

1. Crawl stats: response time trend and any 5xx or host issues.
2. Performance, last 28 days against the previous period and the same period last year.
3. Enhancements: new invalid items.
4. Sitemaps: all still "Success", with a recent last read date.

After every release or redesign

1. Live test the main templates in URL Inspection.
2. Confirm the verification token survived.
3. Watch Page indexing for a week.

Common beginner mistakes

• Panicking over the "Not indexed" total. It includes redirects, duplicates and noindexed URLs that should not be indexed. Look at reasons, not the grand total.
• Verifying the wrong prefix, then wondering why there is no data.
• Reading average position like a rank tracker. It averages over all queries, countries and devices. Filter to one query and one country before drawing conclusions.
• Requesting indexing for the same URL every day. Google states that repeated requests do not speed things up.
• Using Removals to deindex pages permanently. It expires.
• Comparing Search Console clicks with Analytics sessions and expecting a match. They measure different things in different ways.
• Removing the DNS record or meta tag after verification. Verification is rechecked.

Going beyond the interface

The Search Console API exposes performance data, sitemaps and URL Inspection. The inspection endpoint returns the indexed version only (there is no live test through the API), with a quota of 2,000 queries per day and 600 per minute per property. That is what makes index monitoring at scale possible: TurboIndex uses it to check every URL in your sitemaps on a schedule and show which ones are indexed, which are waiting and why, so you do not have to paste URLs into the inspection bar one at a time.