Google Search Console: Complete SEO & Indexing Guide
Google Search Console is Google's first-party platform for understanding how a website appears in Google Search, which queries and pages generate visibility, whether important URLs are indexed, how Googlebot is crawling the site and whether Google has detected technical, structured data or security problems. This guide explains the reports in practical SEO terms and connects them with the wider Google knowledge hub.
What Is Google Search Console?
Search Console is Google's own interface between website owners and the systems that crawl, index and surface their pages in Google Search.
Search Performance
Measure clicks, impressions, click-through rate and average position, then break the data down by query, page, country, device, search appearance and time period.
Crawling & Indexing
See whether Google discovered important URLs, whether they were crawled and indexed, which canonical Google selected and why groups of pages may remain outside the index.
Technical Signals
Monitor sitemaps, Core Web Vitals, HTTPS, structured-data enhancements, links, crawl activity, manual actions and security issues from one central property.
Domain Property vs URL-Prefix Property
The property type determines which protocols, subdomains and URL variations are included in the Search Console view.
Domain Property
A Domain property gives the broadest site-level view because it covers protocol and subdomain variations under the verified domain.
- Useful for whole-domain SEO monitoring.
- Includes HTTP and HTTPS variants.
- Includes relevant subdomains.
- Verification normally uses DNS.
- Strong default choice for site owners who control DNS.
URL-Prefix Property
A URL-prefix property covers the exact protocol and path prefix that you verify, making it useful when access needs to be restricted to a particular version or section.
- Can isolate a protocol or subdomain.
- Supports several verification methods.
- Useful for specific site sections.
- Does not automatically combine every domain variation.
- Can exist alongside a Domain property.
Understanding the Performance Report
Performance data is where SEOs connect Google Search visibility with the queries and landing pages that generated it.
Total Clicks
The number of times users clicked from the relevant Google Search surface to your site during the selected reporting period.
Impressions
How often a result from your property was shown or otherwise counted as an impression under Google's reporting rules.
Average CTR
Clicks divided by impressions. CTR analysis is useful for spotting pages that receive visibility but attract fewer clicks than expected.
Average Position
An aggregated average of the top position associated with your property in the reported search results. Treat it as directional rather than as a perfect rank tracker.
Use Dimensions and Filters Together
The real power of the Performance report appears when you move beyond the four headline metrics. Analyse queries, pages, countries, devices, search appearance and dates, then combine filters to isolate a specific SEO question.
Current Performance reporting also supports different time granularities, including hourly, daily, weekly and monthly views where available. The 24-hour view is especially useful for recent launches and short-term diagnosis, while longer periods are better for trend analysis.
Search, Discover, News and AI Performance
Additional performance reports can appear when Google has enough relevant data for that property or feature.
Google Search
The main Search results report provides the broadest organic-search data, including query and landing-page performance, filters and search-appearance breakdowns.
Discover & Google News
Eligible properties can receive separate reports for Google Discover and Google News. These reports only appear when the property has sufficient qualifying traffic.
Generative AI Performance
Google is testing and rolling out a dedicated report showing how sites perform in generative AI experiences in Google Search. Availability is not yet universal, so treat it as an emerging Search Console report rather than a guaranteed menu item.
Emerging reportHow to Use URL Inspection
URL Inspection is the fastest place to investigate one specific URL rather than interpreting a site-wide aggregate report.
Inspect Google's Indexed View and Test the Live URL
URL Inspection can show information about the version Google knows, including indexing status, discovery and crawl information, the declared and Google-selected canonical where available, and other indexing details. You can also run a live test to see whether Google can currently access and process the URL.
A successful live test means the page is technically available for crawling and processing; it does not guarantee that Google will add the page to the index or rank it.
Indexed vs Not Indexed Does Not Mean Good vs Bad
Many legitimate URLs should not be indexed. The key is whether your important canonical pages are indexable and whether excluded URLs are being excluded for the reason you intended.
Indexed Pages
These are URLs Google has added to its index. Being indexed does not guarantee impressions, rankings or traffic, but it is generally a prerequisite for normal organic visibility.
Not Indexed Pages
These URLs are outside the index for one of many reasons. Redirected URLs, duplicate alternatives, intentionally noindexed pages and true 404s may all be perfectly valid exclusions.
Diagnose the Reason
Do not attempt to “fix every exclusion”. Open the reason, examine example URLs and determine whether those URLs actually deserve to be indexed before changing anything.
What Google Search Console Indexing Statuses Mean
Use this section as a practical diagnostic library: identify the status, decide whether it is expected and only then choose a corrective action.
Crawled – Currently Not Indexed
Google crawled the URL but did not index itGoogle has fetched the page but has not added it to the index. The page may be indexed later, but repeatedly requesting indexing is not a substitute for improving the underlying page or site signals.
Discovered – Currently Not Indexed
Google knows the URL but has not crawled it yetGoogle discovered the URL but has not yet fetched it. This can occur on newer sites or larger sites where Google is prioritising other URLs for crawl.
Alternate Page With Proper Canonical Tag
Usually expectedGoogle sees this URL as an alternate version and recognises a canonical URL that should represent the content instead.
Duplicate Without User-Selected Canonical
Google identified duplicate contentGoogle considers the URL a duplicate of another page, but you did not explicitly identify which URL should be canonical.
Duplicate, Google Chose Different Canonical Than User
Google disagreed with your canonical preferenceYou declared one canonical URL, but Google's systems selected another URL as the representative version.
Page With Redirect
Usually expectedThe URL redirects elsewhere, so the redirecting URL itself is normally not eligible to remain indexed as a standalone page.
Redirect Error
Redirect could not be processed correctlyGoogle encountered a problem following the redirect. Causes can include loops, excessive chains, invalid destinations or other redirect-processing failures.
Not Found (404)
The requested URL returned a 404 responseGoogle requested the URL and your server correctly reported that the page does not exist.
Soft 404
The page behaves like a missing or empty pageGoogle believes the page effectively represents missing or very thin content even though the server may return a successful response instead of an actual 404.
Blocked by robots.txt
Googlebot is disallowed from crawling the URLA robots.txt directive prevents Google's crawler from fetching the page. Remember that blocking crawling and preventing indexing are not exactly the same thing.
Excluded by ‘noindex’ Tag
Google detected an instruction not to index the pageThe URL contains an eligible noindex directive and Google has excluded it from the index.
Server Error (5xx)
Googlebot could not retrieve the page successfullyThe server returned a 500-level response or otherwise failed while Google was trying to access the URL.
Blocked Due to Access Forbidden (403)
The server denied Google's requestGooglebot attempted to access the URL but the server returned a forbidden response.
Sitemaps and Temporary Removals
Both tools influence how URLs are discovered or temporarily surfaced, but neither should be confused with a guaranteed indexing command.
XML Sitemaps
Submit XML sitemaps so Google can discover important canonical URLs and so you can monitor whether Google was able to fetch and process those sitemap files.
- Include canonical indexable URLs.
- Remove redirected and intentionally noindexed URLs.
- Monitor last read and processing status.
- Investigate sitemap syntax or fetch errors.
- Use sitemap segmentation when diagnosis benefits from it.
Removals Tool
The Removals tool can temporarily hide eligible URLs from Google Search and also provides information related to outdated-content requests and SafeSearch-related reporting.
- Useful for urgent temporary search-result hiding.
- Not a permanent deletion mechanism by itself.
- Fix the underlying indexing condition separately.
- Use noindex, authentication or removal at source where appropriate.
- Do not use removals merely to “clean” ordinary GSC 404 reporting.
Core Web Vitals, HTTPS and Rich Results
These reports help diagnose user-experience and search-appearance issues that sit alongside traditional crawling and indexing.
Core Web Vitals
Search Console groups URLs using real-world Core Web Vitals data where sufficient data exists. The key metrics are LCP for loading, INP for responsiveness and CLS for visual stability.
Use the report to identify affected URL groups, then investigate individual templates with tools such as Google PageSpeed Insights.
HTTPS Report
The HTTPS report helps identify indexed URLs that Google cannot serve or evaluate successfully over HTTPS when a secure version is expected.
Treat HTTPS problems as technical infrastructure issues rather than trying to manipulate them through indexing requests.
Rich Result Enhancements
When Google detects supported structured data on the property, Search Console can expose enhancement reports showing valid items and issues for eligible rich-result types.
For URL-level validation, use the Google Rich Results Test.
Links, Crawl Stats, Settings and Permissions
These reports provide valuable diagnostic context, but they should not be mistaken for exhaustive databases of every crawl or backlink.
Links Report
Review samples of external links, top linking sites, top linked pages, internal links and common linking text. The report is useful for directional analysis but should not be treated as a complete live backlink database.
Crawl Stats
Inspect Google's crawling history, including request volume, response behaviour, host availability, file types and crawl-purpose information. This is particularly useful for diagnosing site-wide server or crawl issues.
Users & Permissions
Control who can access a property and at what permission level. Agencies and site owners should regularly audit access so former staff and suppliers do not retain unnecessary permissions.
Settings & Associations
Property settings contain ownership, crawling and association-related information. Search Console can also connect with supported Google products and services where appropriate.
Manual Actions and Security Issues
Most Search Console warnings are diagnostic. Manual actions and security issues deserve a different level of urgency because they can directly affect trust and visibility.
Do Not Ignore These Reports
A manual action means Google has determined that pages or the site violate relevant spam policies and has applied a manual measure. A security issue can indicate hacking, malware, phishing, unwanted software or other behaviour that may harm users.
Resolve the underlying cause first. Validation or reconsideration should come after the problem itself has genuinely been fixed.
Read the exact issue, identify affected pages or practices, correct the violation thoroughly and follow the reconsideration process where available.
Secure the site, identify the compromise, remove malicious content or code, patch the vulnerability and then use Google's review process where required.
Deleting URLs from Search Console reports does not resolve an underlying spam, hack or infrastructure problem.
Useful Google Search Console SEO Workflows
Search Console becomes much more valuable when every report is connected to a specific SEO decision.
Find Quick-Win Queries
Filter for queries already receiving substantial impressions and review their landing pages. Keywords sitting near stronger visibility can reveal opportunities for better topical coverage, internal links or result presentation.
Find CTR Opportunities
Identify pages with strong impressions but relatively weak click-through rates. Review search intent, titles, descriptions, competing results and search appearance before rewriting snippets blindly.
Diagnose Traffic Declines
Compare equivalent date ranges and identify whether the decline comes from fewer impressions, weaker positions, lower CTR, particular pages, devices, countries or query groups.
Spot Cannibalisation Signals
Filter a query and inspect which pages receive impressions for it. Multiple URLs are not automatically a problem, but unstable page/query relationships can indicate unclear intent or internal competition.
Check New Content
Use URL Inspection to confirm accessibility and indexing information, then monitor Performance data rather than repeatedly requesting indexing simply because traffic has not appeared immediately.
Guide Internal Linking
Find pages already associated with strategically important query clusters, then strengthen relevant internal paths from authoritative pages rather than adding links purely by URL count.
Audit Indexation
Compare your intended indexable URL set with Page Indexing reasons. Focus on valuable canonical URLs that are unexpectedly excluded rather than trying to force every discovered URL into Google's index.
Connect Technical Issues
When indexing drops, cross-check Page Indexing, Crawl Stats, sitemaps, robots directives, server behaviour and template changes instead of assuming the issue is purely content-related.
Automate Larger Analysis
For larger sites and recurring reporting, use the Google Search Console API to extract and process performance data outside the normal interface.
Search Console vs Analytics vs SEO Tools
These platforms answer different questions. Serious SEO analysis usually uses them together rather than treating one as a replacement for the others.
Google Search Console
Best for Google Search visibility, queries, landing pages, indexing, canonicals, crawling, sitemaps and Google-specific technical diagnostics.
Google Analytics
Best for understanding what happens after visitors arrive: sessions, engagement, events, key events, acquisition and broader user behaviour. Read our Google Analytics guide.
Third-Party SEO Platforms
Tools such as crawlers, rank trackers and backlink platforms add competitor data, broader link indexes, technical crawling and estimated keyword metrics that Search Console does not provide.
Common Google Search Console Mistakes
Most GSC mistakes come from interpreting a report as an instruction rather than understanding what the report is actually describing.
Trying to Index Every URL
Redirects, duplicates, filters, obsolete pages and intentionally excluded URLs do not all belong in Google's index. Focus on your intended canonical content set.
Repeatedly Requesting Indexing
Request Indexing is not a ranking or quality fix. If Google repeatedly declines to index a page, investigate why the page or site may not merit indexing instead of resubmitting it endlessly.
Treating Average Position as a Rank Tracker
Position is aggregated across queries, devices, locations and result contexts. Use it directionally and combine it with query/page-level analysis.
Redirecting Every 404
A genuine deleted page can return 404. Redirect only when a relevant replacement exists instead of sending every missing URL to the homepage.
Ignoring Canonical Conflicts
A canonical tag is only one signal. Internal links, redirects, sitemap entries and duplicated content should all reinforce the same preferred URL.
Overreacting to Short-Term Data
Recent data is useful for monitoring, but SEO conclusions should normally consider enough history to account for seasonality, reporting delay and ordinary daily volatility.
Common Questions About Google Search Console
Quick answers covering indexing, crawling, 404s, canonicals, performance and the practical limits of Search Console data.
01 What is Google Search Console used for?
Google Search Console is used to monitor Google Search performance, indexing, crawling, sitemaps, Core Web Vitals, structured-data enhancements, links and selected security or policy issues affecting a verified website.
02 What does Crawled – currently not indexed mean?
Google has crawled the URL but has not added it to the index. The URL may be indexed later. If an important page remains in this state, review content quality, duplication, canonicals, internal linking and other signals rather than repeatedly requesting indexing.
03 What does Discovered – currently not indexed mean?
Google knows the URL exists but has not yet crawled it. This can be normal for newer or lower-priority URLs. Persistent problems may justify reviewing crawl efficiency, internal linking and overall site quality.
04 Is Alternate page with proper canonical tag an error?
Usually not. It means Google recognises the URL as an alternate version of another canonical page. If the canonical is the one you intended, no fix is normally required.
05 Should I fix every 404 in Search Console?
No. A removed URL can legitimately return 404. Prioritise 404s that are still internally linked, included in XML sitemaps or represent content that should actually exist.
06 Does Request Indexing guarantee Google will index a page?
No. Requesting indexing asks Google to recrawl an eligible URL. A successful live inspection also does not guarantee that the page will ultimately be indexed or rank in Google Search.
07 Is Google Search Console accurate for keyword rankings?
Search Console provides first-party performance data, but average position is aggregated rather than a fixed rank-tracking measurement. For exact scheduled rank monitoring, use it alongside a dedicated rank tracker.
08 What is the difference between Search Console and Google Analytics?
Search Console focuses on how a site performs and is processed in Google Search. Google Analytics focuses primarily on user acquisition and behaviour after visitors reach the site. See our Google Analytics guide.
09 Does Search Console show every backlink?
No. The Links report provides useful linking information but should not be treated as a complete, real-time index of every external backlink pointing to a website.
10 Can Google Search Console help with an SEO audit?
Yes. Search Console is one of the most important data sources for a technical and organic-search audit because it exposes actual Google Search, indexing and crawl information. It should be combined with a site crawler, analytics and other SEO data. See our SEO audit guide.
Use Search Console to Understand What Google Is Actually Seeing
Google Search Console is most useful when its reports are interpreted together. Performance data tells you where visibility exists, Page Indexing shows how Google is handling URLs, URL Inspection diagnoses individual pages, Crawl Stats reveals larger crawling patterns and enhancement reports expose additional technical opportunities. The objective is not to make every Search Console warning disappear; it is to make sure important pages are discoverable, crawlable, canonical, indexable and genuinely useful enough to earn visibility.
