To use Google Search Console for SEO, verify a Domain property, submit your XML sitemap, then work through three reports: Performance for queries and pages, Page indexing for coverage, and URL Inspection for single URLs. Turn every finding into one action, such as a new title for a low CTR page or a fix for an excluded URL.
Google Search Console is a free service from Google that helps you "monitor, maintain, and troubleshoot your site's presence in Google Search results," according to About Search Console. It is the measurement layer of SEO: Google says you do not need it to appear in Search, but without it you cannot see which queries earn impressions or why a page is missing.
The Google Search Console SEO tools covered here follow the order of a real setup, as of October 2026. The main recommendation: read the data per page, not per keyword, and stop at one concrete fix per pattern.
How do you add and verify a property in Search Console?
Adding a property in Search Console means telling Google which site you want data for, then proving you own it. A Domain property covers every subdomain and protocol and verifies only through a DNS record. A URL-prefix property covers one exact address and accepts several methods, such as an HTML file or meta tag.
A property is the unit Search Console reports on. Google's property help page says a Domain property "Includes all subdomains (m, www, and so on) and multiple protocols," while a URL-prefix property "Includes only URLs with the specified prefix, including the protocol." As of October 2026, one account can hold up to 1,000 properties.
| Criterion | Domain property | URL-prefix property |
|---|---|---|
| What it covers | All subdomains plus http and https | Only URLs under the exact prefix and protocol |
| Verification methods | DNS record (TXT or CNAME) only | HTML file, HTML tag, Google Analytics, Google Tag Manager or DNS |
| Who can set it up | Someone with access to the DNS provider | Anyone who can edit the site or its tags |
| Fits | The default view of the whole site | One section, one host or a team without DNS access |
- Choose the property type. Pick Domain unless you lack DNS access or only need one section.
- Copy the verification token. Search Console shows a TXT record for a Domain property, or a file or tag for a URL-prefix property.
- Add the record or file. Add the TXT record at your DNS provider, or upload the file to the site root.
- Click Verify. Search Console checks the token and opens the property once it finds it.
- Leave the token in place. Google's verification help page says verification lasts "as long as Search Console can confirm the presence and validity of your verification token."
Do you need to submit a sitemap in Search Console?
Submitting a sitemap in Search Console is optional but worth the few minutes it takes. Google finds pages through links alone, yet its getting started guide says a sitemap may speed up discovery, and the Sitemaps report then shows whether Google fetched the file and how many URLs it parsed.
An XML sitemap is a file that lists the canonical URLs you want Google to crawl. Open Sitemaps, paste the sitemap URL into "Add a new sitemap" and submit. The Sitemaps report help page adds four facts worth knowing:
- Only owners can submit. Other users can list the sitemap in robots.txt instead.
- Three statuses. Success, Has errors and Couldn't fetch tell you whether Google could read the file.
- Hard limits. One sitemap holds at most 50,000 URLs and 50MB uncompressed; larger sites split it and use a sitemap index.
- Discovered pages is not an index count. Google writes that there is "no guarantee that a page URL discovered in a sitemap has been or will be crawled or indexed."
When a sitemap index shows only one child sitemap or a count that looks wrong, the guide to sitemap index issues in Search Console walks through the fix.
How do you read the Search Console Performance report?
The Search Console Performance report shows how a site does in Google Search through four metrics: clicks, impressions, click-through rate (CTR) and average position. You read it by setting a search type and date range, grouping by query, page, country, device, search appearance or date, and comparing periods.
Google's Performance report help page defines the metrics:
- Clicks are "the number of times a user clicked your site from Google Search results."
- Impressions count "how many times your site appeared in Search results."
- CTR is "the click count divided by the impression count."
- Average position is "the average position of the topmost result from your site."
The search types are Web: text-based, Web: multimodal, Image, Video and News. The default view shows the last three months, and the newest data "can be preliminary," drawn as a dotted line.
Filters do most of the work. The advanced filtering page lists substring filters and Custom (regex) filters in RE2 syntax, one comparison at a time, and a Difference column for sorting the biggest changes. Google added a Branded and Non-branded query filter in November 2025; it is not available for sub-properties or sites with few impressions.
Two limits shape every analysis as of October 2026. Tables show at most 1,000 rows, per About Search Console data, and rare queries are left out as anonymized queries, which still count in chart totals unless a query filter is applied.
How do the Page indexing report and URL Inspection work together?
The Page indexing report and URL Inspection answer the same question at two zoom levels. The Page indexing report shows how many URLs on a property are indexed and groups the rest by reason, while URL Inspection shows Google's stored data for one URL and can run a live test before you request indexing.
The Page indexing report splits known URLs into Indexed and Not indexed. As of October 2026, its example list per reason is limited to 1,000 URLs, and a Validate fix run "typically takes up to about two weeks." Google also writes: "Don't expect every URL on your site to be indexed."
The URL Inspection tool is the feature that checks one URL. Three details change how you read it:
- The default view is not live. Results come from the "most recently indexed version of a page, not the live version on the web."
- URL is on Google means eligible. The page is "eligible to appear in Search results, but is not guaranteed to be there."
- Request indexing has a daily limit. Google does not publish the number and points to sitemaps for large batches.
A practical rule: use Page indexing to find which reason affects pages you care about, then inspect a few URLs per reason. The full status by status fix list lives in the guide to Google indexing.
Which SEO actions should Search Console data trigger?
Search Console data should trigger one action per pattern, not a slide full of charts. The Search Console Action Map below is the author's own rule, not Google guidance: it pairs six patterns from the Performance, Page indexing and Sitemaps reports with the likely cause and the first fix to try.
Google supports the first row directly: its common tasks page says a low CTR "can indicate that users see your page in Search results but don't think it answers their query" and suggests "updating the page's title and description." The same page recommends watching trends in impressions and clicks rather than position alone.
| Pattern in the data | Where to see it | Likely cause | First action |
|---|---|---|---|
| High impressions, low CTR on a page | Performance, Pages tab, sorted by CTR | Title or snippet does not match the query | Rewrite the title and meta description |
| Queries ranking just off page one with steady impressions | Performance, Queries tab, sorted by position | The page is relevant but not the strongest answer | Expand the section that answers the query and add internal links to the page |
| One query showing two or more pages | Click the query, then the Pages tab | Two pages compete for the same intent | Pick one page, then merge or refocus the other |
| Clicks fall while impressions hold | Date comparison, Difference column | The result shows less often near the top or the snippet changed | Check position, search appearance and the snippet for the top queries |
| Important URL under Crawled, currently not indexed | Page indexing, then URL Inspection | Google judged the page not worth storing yet | Improve or merge the page, add links, request indexing once |
| Sitemap URLs far above indexed URLs | Sitemaps vs Page indexing | The sitemap lists duplicate or low value URLs | Keep only canonical, indexable URLs in the sitemap |
For the title and snippet rewrites in the first row, the guide to the meta description character limit covers length and wording.
What changed in Search Console in late 2026?
Search Console changed in three ways between June and October 2026. Google added a Generative AI performance report for AI Overviews and AI Mode, added a Web: multimodal search type for searches that start from an image, and said in October that a Page indexing report that looks stale is no reason for alarm.
Generative AI performance report (officially confirmed). Google introduced the report in June 2026. The help page says it counts "how many times links to your site were shown to a user in a generative AI feature on Google Search" and that "As of August 31, 2026, we've rolled out these insights to all websites worldwide." Search Engine Journal reported that click data was not included at rollout. These impressions are the first Google-reported measure for work on optimizing for AI Overviews, and they show where GEO vs SEO measurement overlaps.
Web: multimodal (officially confirmed). Google announced a search type in September 2026 for searches made with Google Lens, Circle to Search, image uploads and Chrome. It has no queries dimension; the guide to Search Console multimodal search covers the analysis.
Indexing report lag (reported). Search Engine Journal reported on October 27, 2026 that a Reddit user saw no Page indexing update since October 16. John Mueller of Google replied: "Indexing doesn't change quickly, and when it does, you see that reflected in the performance reports first." Google gave no refresh schedule, so any timeline is speculation.
Common mistakes when using Search Console for SEO
The common mistakes with Search Console come from reading the data more precisely than it is, or from setting it up for only part of the site. Each one leads to a wrong conclusion about traffic or indexing, and each has a fix that needs nothing more than the reports and a spreadsheet.
- Verifying only one URL-prefix version. A property for the https www prefix misses data from other hosts and protocols. Add a Domain property as the main view.
- Reading average position as a ranking. It is the average topmost position across impressions. Track impressions and clicks per page next to it.
- Expecting table rows to add up to the chart. Anonymized queries and the 1,000 row limit create the gap. Use the chart totals for reporting.
- Requesting indexing again and again. Requests have a daily limit. Fix the page, request indexing once and wait.
- Panicking over a stale indexing report. Check the last updated date first, then look at impressions per page in the Performance report.
- Removing the verification token after setup. Verification ends when Google can no longer find the token. Keep the DNS record or file in place.
