Overview
Google Search Console (GSC) is the only first-party view of how Google sees a site. Every other tool estimates; GSC reports. Master it by setting up the right property type, reading the four reports that matter, and treating the URL Inspection tool as the authoritative source for index state. Skip the dashboards on the home page; the value is in the side-nav reports.
Prerequisites
- A Google account (any Google account; ownership is per-property, not per-account).
- DNS control over the root domain, or upload access to the site root for HTML file verification.
- The site’s
robots.txtandsitemap.xmllive at the expected paths; see discoverability-files.
Steps
1. Verify a domain property, not a URL prefix
GSC offers two property types: Domain (covers every subdomain and protocol) and URL prefix (covers only the exact protocol-plus-host combination). Always create a Domain property first.
Domain property: example.com
Covers: https://example.com, https://www.example.com,
https://blog.example.com, http://example.com, etc.
A URL-prefix property for https://example.com/ is blind to www, http, and every subdomain. Domain verification requires a DNS TXT record; the GSC UI gives the exact value. Add it at the registrar, wait for propagation (usually under 5 minutes), and click Verify.
2. Submit the sitemap
Open Sitemaps in the left nav. Enter the path (/sitemap.xml) and click Submit. GSC fetches the sitemap within hours and lists every discovered URL.
If the site uses a sitemap index, submit the index URL only. GSC follows the children automatically. Re-submit only if the sitemap URL itself changes; refetches happen on Google’s schedule.
3. Read the Performance report
Performance is the top-of-funnel view: queries, pages, devices, countries, dates. Open it, set the date range to the past 28 days, and tab through the four sub-reports.
- Queries: the search terms that triggered impressions. Sort by clicks; the top 20 queries are the page’s center of gravity.
- Pages: the URLs that received impressions. Sort by impressions; high-impression, low-CTR pages are the title-and-description optimization candidates.
- Devices: mobile vs desktop split. Mobile under 70% is unusual; investigate the breakdown.
- Countries: traffic by country. Use this to decide whether hreflang is worth the implementation cost.
The “Average position” column lags reality by roughly 48 hours. Treat trends, not single days, as signal.
4. Read the Coverage (Pages) report
Coverage answers a single question: which URLs has Google indexed, and which has it rejected? Three statuses matter.
- Indexed: the URL is in Google’s index and eligible to rank.
- Excluded: Google saw the URL but chose not to index it. Reasons include “Discovered, currently not indexed,” “Crawled, currently not indexed,” “Duplicate, Google chose different canonical,” and “Noindex tag.”
- Error: a hard failure. Server error, redirect loop, 404 in the sitemap.
“Discovered, not indexed” is the most common diagnostic miss. It means Google knows the URL exists but has not spent crawl budget on it; the page is competing for budget against the site’s stronger pages. See crawl-budget.
5. Use URL Inspection for live and indexed state
URL Inspection answers two different questions: what does the current index say about this URL, and what would Google see if it crawled the URL right now?
URL Inspection > paste URL > read the indexed state.
Then click "Test live URL" > read the live state.
The indexed view shows the version Google last crawled, with the canonical it picked, the structured data it parsed, and the last crawl date. The live view shows what would be indexed on the next crawl. A diff between the two reveals stale content, canonical drift, or recent fixes that have not propagated.
Request indexing only after a meaningful change. Spamming “Request indexing” does not speed up future crawls.
6. Monitor Core Web Vitals and the Page Experience report
Core Web Vitals reports field data from the Chrome User Experience Report (CrUX): LCP, INP, CLS, at the 75th percentile per URL group. URLs are grouped by similarity, not listed individually; click a group to see representative URLs.
Three states: Good, Needs improvement, Poor. The threshold is the 75th percentile of real users over 28 days. See core-web-vitals for the thresholds and audit-site-for-core-web-vitals for the fix loop.
7. Watch the Enhancements reports
Enhancements lists every structured data type Google detected on the site: Sitelinks search box, Breadcrumbs, FAQ, Article, Product, Video, and others. Each report shows Valid, Valid with warnings, and Error counts.
Fix Errors first; they suppress the rich result entirely. Warnings only suppress optional fields. See structured-data for the JSON-LD that powers each enhancement.
8. Respond to Manual Actions and Security Issues immediately
Manual Actions is empty on healthy sites. If a notice appears, a human reviewer has applied a penalty: unnatural links, thin content, cloaking, structured data spam. Read the notice, fix the cause, then click “Request review” with a written summary of the fix. Reviews take 1 to 4 weeks.
Security Issues lists hacks, malware, deceptive content. Same loop: fix, then request review.
9. Use Removals only for emergencies
The Removals tool hides a URL from search results for 6 months. It does not delete the URL from the index and does not affect ranking signals. Use it only when a page must disappear immediately: leaked data, PII exposure, legal takedown. For ordinary removals, use noindex plus a deindex wait.
Verify it worked
# 1. Domain property verified.
# GSC home > property switcher shows "example.com" with the domain icon.
# 2. Sitemap status is "Success" with a Discovered URLs count > 0.
# GSC > Sitemaps > status column.
# 3. Coverage Indexed count is within 10% of the sitemap URL count.
# Large gaps mean Google is rejecting indexable URLs; investigate Excluded.
# 4. URL Inspection on a recent URL shows "URL is on Google."Common errors
- Setting up a URL-prefix property and missing subdomain traffic. Always start with a Domain property; URL-prefix is for legacy edge cases.
- Ignoring “Discovered, currently not indexed.” It looks benign because the URL is not marked an error. It means Google is choosing not to crawl. See helpful-content-update for the site-wide signal that fixes this.
- Using URL Inspection on the staging hostname and then assuming the production URL is indexed. Inspection is per-property; check the production property.
- Treating Performance “Average position” as a real-time rank tracker. It is a 28-day rolling average across impressions. Use a dedicated rank tracker for daily moves.
- Re-submitting the sitemap on every deploy. GSC refetches on its own schedule; manual re-submission does not accelerate it.
- Filing a Manual Action review without fixing the underlying issue. Google’s reviewers re-check; a denied review extends the penalty.