Understanding the full landscape of Google Search Console dimensions and metrics is essential for anyone managing a website's organic search presence. Whether you're an SEO professional building custom dashboards, a developer pulling data through the Search Console API, or a site owner trying to understand why pages are or aren't appearing in search results, knowing exactly what data is available — and what each field means — is the foundation of effective SEO strategy.
This guide provides a complete reference of every dimension and metric available in Google Search Console as of 2026. We've organized them by report category, included the API field names for developers and analysts, and added practical context on when and how to use each data point for SEO optimization.
What Are Google Search Console Dimensions vs Metrics?
Before diving into the full reference, it's important to understand the difference between dimensions and metrics in GSC — and how GSC differs from paid advertising platforms in its data model.
Dimensions are descriptive attributes that define what you're looking at. They segment and filter your data by criteria like search query, page URL, country, device type, and search appearance. Dimensions answer the question: "How do I want to slice this data?"
Metrics in GSC are remarkably simple compared to paid ad platforms. There are only four core search metrics: clicks, impressions, CTR, and average position. This simplicity is by design — GSC measures organic search visibility and engagement, not the hundreds of conversion and cost metrics found in advertising platforms.
Beyond search performance, GSC also provides diagnostic data about indexing, crawling, Core Web Vitals, sitemaps, links, and structured data that doesn't follow the traditional dimension/metric model but is equally important for SEO.
How Is Google Search Console Data Structured?
Google Search Console data is organized into several distinct report categories, each with its own data model. The Search Performance report follows a traditional dimension + metric structure. The Page Indexing, URL Inspection, Core Web Vitals, Sitemaps, Links, and Enhancement reports provide diagnostic and structural data about your site's relationship with Google.
The Search Console API (Search Analytics API) provides programmatic access to search performance data with up to 16 months of history. You specify dimensions to group by, filters to apply, and receive metrics for each dimension combination. Other report types are accessed through the URL Inspection API and Indexing API.
Search Performance Dimensions
Search performance dimensions define how organic search data is segmented. These are the dimensions you can apply in the Performance report and through the Search Analytics API to understand which queries, pages, countries, devices, and search features drive your organic traffic.
| Dimension | API Field | Description |
|---|---|---|
| Query / Search Term | query | The search query typed by the user that triggered your result. Anonymous queries (privacy-protected) are excluded |
| Page URL | page | The canonical URL of the page that appeared in search results |
| Country | country | Country where the search was performed (ISO 3166-1 alpha-3 code: USA, FRA, GBR, etc.) |
| Device | device | Device type: DESKTOP, MOBILE, or TABLET |
| Search Type | searchType | Type of Google Search: web, image, video, news, or discover |
| Search Appearance | searchAppearance | Special search result format: RICH_RESULT, AMP_ARTICLE, FAQ_RICH_RESULT, HOWTO_RICH_RESULT, REVIEW_SNIPPET, VIDEO, BREADCRUMB, PRODUCT, RECIPE, EVENT, PRACTICE_PROBLEMS, MATH_SOLVER, JOB_LISTING, LEARNING_VIDEO, MERCHANT_LISTING, SITELINKS_SEARCH_BOX |
| Date | date | Date of the search event in YYYY-MM-DD format (Pacific Time) |
Important notes on dimensions: You can combine up to all seven dimensions in a single API query. The query dimension excludes anonymous queries (about 10-20% of total traffic) for privacy reasons — total clicks and impressions will be higher when no query filter is applied. The page dimension uses the canonical URL, so multiple pages pointing to the same canonical will be grouped together.
Core Search Metrics
Google Search Console has only four core search metrics, but they are the most important data points for understanding your organic search performance. Each metric has specific counting rules that are important to understand for accurate analysis.
| Metric | API Field | Description | Counting Rules |
|---|---|---|---|
| Clicks | clicks | Number of times a user clicked a search result that led to your site | Only counts clicks that lead to pages outside of Google Search. Clicking a result, returning to search, and clicking it again counts as 1 click |
| Impressions | impressions | Number of times a link URL from your site appeared in search results | Counted when the result appears on the results page, regardless of scrolling. Each unique URL gets at most 1 impression per query per session |
| Click-Through Rate (CTR) | ctr | Percentage of impressions that resulted in a click | (Clicks ÷ Impressions) × 100. Calculated per row when dimensions are applied |
| Average Position | position | Average ranking position of your URL in search results | Impression-weighted average. Position 1 is the top. Includes all search result types (organic, featured snippets, knowledge panels, etc.) |
Position counting details: Positions are counted from top to bottom, left to right on the search results page. A featured snippet at the top is position 1. The first standard organic result below it is position 2. If your URL appears as both a featured snippet (position 1) and a standard result (position 8), the impression and position are counted for the topmost occurrence (position 1).
Page Indexing Dimensions
Page indexing dimensions describe the crawl and index status of your URLs. This data comes from the Page Indexing report (formerly Coverage report) and tells you which pages Google can and cannot index, and why. This is critical for ensuring your important content is discoverable in search.
| Dimension | API / Report Field | Description |
|---|---|---|
| URL | url | The inspected page URL |
| Indexing Status | verdict | Overall indexing verdict: Valid (indexed), Warning (indexed with issues), Error (not indexed), Excluded (intentionally not indexed) |
| Crawl Status | crawlStatus | Result of the last crawl attempt: Crawled, Partially crawled, or Crawl error |
| Last Crawled | lastCrawlTime | Timestamp of the last successful Googlebot crawl |
| Crawled As | crawledAs | User agent used: Googlebot Desktop or Googlebot Smartphone |
| Referring Page | referringUrls | Pages that link to this URL (how Google discovered it) |
| Sitemap | sitemaps | Sitemaps that contain this URL (if any) |
| Indexing Reason | indexingState | Specific reason for the status: Submitted and indexed, Crawled - currently not indexed, Discovered - not yet crawled, Excluded by noindex tag, Blocked by robots.txt, Duplicate (canonical selected), Redirect, 404 Not Found, Server error (5xx), etc. |
Common Indexing Status Categories
| Status Category | Type | Description |
|---|---|---|
| Submitted and indexed | Valid | URL was submitted via sitemap and successfully indexed |
| Indexed, not submitted in sitemap | Valid | URL was discovered through links and indexed (not in any sitemap) |
| Crawled - currently not indexed | Excluded | Google crawled the page but chose not to index it — often indicates thin or low-quality content |
| Discovered - currently not indexed | Excluded | Google knows about the URL but hasn't crawled it yet — may indicate crawl budget issues |
| Duplicate without user-selected canonical | Excluded | Google found duplicate content and chose a different canonical URL |
| Duplicate, Google chose different canonical | Excluded | You specified a canonical but Google disagrees and chose a different one |
| Excluded by noindex tag | Excluded | Page has a noindex meta tag or HTTP header — working as intended if deliberate |
| Blocked by robots.txt | Excluded | Robots.txt prevents Googlebot from crawling this URL |
| Not found (404) | Error | URL returns a 404 status code — fix if the page should exist |
| Server error (5xx) | Error | Server returned an error during crawl — fix server issues immediately |
| Redirect error | Error | Redirect chain is too long, loops, or has other issues |
URL Inspection Dimensions
URL Inspection provides detailed diagnostic information about a specific URL. It combines live crawl data with indexed data to show you exactly how Google sees your page. This is the most granular level of GSC data, available through the UI and the URL Inspection API.
| Dimension | API Field | Description |
|---|---|---|
| Coverage Status | indexStatusResult.verdict | Overall verdict: PASS (valid, indexed), PARTIAL (warning), FAIL (error), NEUTRAL (excluded) |
| Indexing State | indexStatusResult.indexingState | Whether the URL is indexed: INDEXING_ALLOWED, BLOCKED_BY_META_TAG, BLOCKED_BY_ROBOTS_TXT, etc. |
| Page Fetch Status | indexStatusResult.pageFetchState | Result of fetching the page: SUCCESSFUL, SOFT_404, BLOCKED_ROBOTS_TXT, NOT_FOUND, SERVER_ERROR, REDIRECT_ERROR |
| Crawl Date | indexStatusResult.lastCrawlTime | When Google last crawled this URL |
| Google Canonical | indexStatusResult.googleCanonical | The canonical URL Google has selected for this page (may differ from your declared canonical) |
| User-Declared Canonical | indexStatusResult.userCanonical | The canonical URL declared by your page's link rel=canonical tag |
| Mobile Usability | mobileUsabilityResult.verdict | Mobile-friendliness verdict: PASS or FAIL |
| Mobile Usability Issues | mobileUsabilityResult.issues | Specific mobile issues: text too small, clickable elements too close, content wider than screen, viewport not set |
| Rich Results | richResultsResult | Detected structured data types and their validation status (valid, warning, error) |
| Referring URLs | indexStatusResult.referringUrls | Internal pages that link to this URL (how Google found it) |
Core Web Vitals Dimensions
Core Web Vitals measure user experience quality across three axes: loading speed (LCP), interactivity (INP), and visual stability (CLS). Google uses these as ranking signals. GSC groups URLs by similar performance characteristics and reports field data (real user measurements from Chrome User Experience Report) over a rolling 28-day window.
| Dimension / Metric | Report Field | Description | Thresholds |
|---|---|---|---|
| URL Group | urlGroup | Group of URLs with similar performance characteristics (pages sharing the same template/pattern) | GSC groups similar pages automatically to provide aggregate data |
| LCP (Largest Contentful Paint) | lcp | Time for the largest visible element to render — measures perceived loading speed | Good: ≤ 2.5s, Needs Improvement: ≤ 4.0s, Poor: > 4.0s |
| INP (Interaction to Next Paint) | inp | Latency of the worst user interaction — measures responsiveness (replaced FID in March 2024) | Good: ≤ 200ms, Needs Improvement: ≤ 500ms, Poor: > 500ms |
| CLS (Cumulative Layout Shift) | cls | Total unexpected layout shifts during the page lifecycle — measures visual stability | Good: ≤ 0.1, Needs Improvement: ≤ 0.25, Poor: > 0.25 |
| Overall Status | status | Combined verdict based on all three Core Web Vitals at the 75th percentile | Good (all three pass), Needs Improvement (at least one needs improvement), Poor (at least one is poor) |
| Device Type | formFactor | Device category: PHONE or DESKTOP (separate reports for each) | Mobile and desktop are evaluated independently |
| Page Type / Template | pageType | Grouping of URLs by template pattern (e.g., /product/*, /blog/*) | Helps identify which page templates need optimization |
How Core Web Vitals are assessed: GSC uses the 75th percentile of field data over a 28-day rolling window. This means 75% of real user visits must meet the threshold for a "good" rating. The data comes from the Chrome User Experience Report (CrUX) and only includes Chrome users who have opted into usage statistics sharing. Pages need sufficient traffic volume to generate CrUX data — low-traffic pages may show no Core Web Vitals data at all.
Sitemaps Dimensions
Sitemap dimensions track the status of XML sitemaps submitted to Google Search Console. Sitemaps help Google discover and prioritize your content for crawling. Monitoring sitemap data ensures Google is aware of all your important pages.
| Dimension | Report Field | Description |
|---|---|---|
| Sitemap URL | path | Full URL of the submitted sitemap (e.g., https://example.com/sitemap.xml) |
| Sitemap Type | type | Format: sitemapIndex (sitemap of sitemaps), urlList (list of URLs), or rssFeed |
| Submitted Date | lastSubmitted | When the sitemap was last submitted to Google (manually or via robots.txt) |
| Last Read | lastDownloaded | When Google last successfully downloaded and processed the sitemap |
| Discovered URLs | contents.submitted | Number of URLs listed in the sitemap |
| Indexed URLs | contents.indexed | Number of sitemap URLs that are currently indexed (may be lower than discovered) |
| Status | status | Processing status: Success, Has errors, or Couldn't fetch |
| Sitemap Errors | errors | Specific errors: invalid XML, URLs blocked by robots.txt, incorrect namespace, etc. |
Links Dimensions
Link dimensions provide data about the internal and external link structure of your site. External links (backlinks) are a major ranking factor, while internal links help Google understand site structure and distribute link equity. GSC provides aggregated link data — not a complete backlink index like specialized tools.
| Dimension | Report Field | Description |
|---|---|---|
| Top Linked Pages (External) | externalLinks.topLinkedPages | Your pages that receive the most external links from other sites |
| Top Linking Sites | externalLinks.topLinkingSites | Domains that link to your site most frequently |
| External Linking Pages | externalLinks.linkingPages | Specific URLs on external sites that link to you |
| Top Linked Pages (Internal) | internalLinks.topLinkedPages | Your pages that receive the most internal links from other pages on your site |
| Internal Links Count | internalLinks.count | Number of internal links pointing to each page |
| Anchor Text | externalLinks.topAnchorTexts | Most common anchor text used in external links to your site |
| Link Count (External) | externalLinks.count | Total number of external links from each linking site |
Important note: GSC link data is a sampled, aggregated view — it does not show every link. For comprehensive backlink analysis, combine GSC data with third-party tools like Ahrefs or Semrush. However, GSC is the most authoritative source because it reflects what Google actually sees and counts.
Security and Manual Actions
Security and Manual Actions reports flag critical issues that can remove your site from search results entirely. Security issues involve hacked content, malware, or deceptive pages. Manual actions are penalties applied by human Google reviewers for violations of search quality guidelines.
| Dimension | Report Field | Description |
|---|---|---|
| Issue Type (Security) | securityIssues.type | Type of security issue: hacked content, malware, social engineering, harmful downloads, uncommon downloads |
| Affected Pages (Security) | securityIssues.affectedPages | URLs identified as having security issues |
| Manual Action Type | manualActions.type | Penalty type: unnatural links to/from your site, thin content, cloaking, pure spam, structured data violations, etc. |
| Manual Action Status | manualActions.status | Current state: Active (penalty in effect), Under review (reconsideration request pending), Revoked (penalty removed) |
| Affected Pages (Manual) | manualActions.affectedPages | URLs or site-wide scope affected by the manual action |
Enhancement Reports
Enhancement reports track the status of structured data (schema markup) on your site. Each enhancement type has its own report showing valid items, items with warnings, and items with errors. Valid structured data can enable rich results in search, improving CTR and visibility.
| Enhancement Type | Schema Type | Rich Result / Feature | Key Fields Validated |
|---|---|---|---|
| Breadcrumbs | BreadcrumbList | Breadcrumb trail in search results showing page hierarchy | itemListElement (position, name, item URL) |
| FAQ | FAQPage | Expandable FAQ accordions directly in search results | mainEntity (Question + acceptedAnswer pairs) |
| How-to | HowTo | Step-by-step instructions displayed in search results | step (name, text, image, url), totalTime, tool, supply |
| Product | Product | Product information (price, availability, ratings) in search results | name, offers (price, priceCurrency, availability), aggregateRating, review |
| Review Snippet | Review / AggregateRating | Star ratings displayed in search results | ratingValue, bestRating, ratingCount, reviewCount |
| Sitelinks Search Box | WebSite + SearchAction | Search box within sitelinks for direct site search from Google | potentialAction (target URL template with search_term_string) |
| Video | VideoObject | Video thumbnails, duration, and key moments in search results | name, description, thumbnailUrl, uploadDate, contentUrl, duration |
| Recipe | Recipe | Recipe cards with image, ratings, cook time in search results | name, image, recipeIngredient, recipeInstructions, cookTime, nutrition |
| Event | Event | Event details (date, location, tickets) in search results | name, startDate, location, offers, performer |
| Job Posting | JobPosting | Job listings in Google's job search experience | title, datePosted, hiringOrganization, jobLocation, baseSalary |
| Merchant Listing | Product (merchant) | Free product listings in Google Shopping tab | name, offers, image, description, gtin, brand |
Enhancement report statuses: Each item is classified as Valid (structured data is correct and can enable rich results), Valid with warnings (structured data works but has recommended improvements), or Error (structured data has critical issues that prevent rich results). Fix errors first, then address warnings to maximize your rich result eligibility.
Common Enhancement Errors and Fixes
| Error | Enhancement Type | Fix |
|---|---|---|
| Missing field "name" | Product, Recipe, Event | Add the required name property to your structured data markup |
| Missing field "image" | Product, Recipe, Article | Include at least one image URL in the schema markup |
| Invalid value for field "price" | Product | Ensure price is a numeric value (not a string like "Free" or "$19.99") |
| Missing field "acceptedAnswer" | FAQ | Every Question must have an acceptedAnswer with a text property |
| Invalid URL in field "item" | Breadcrumb | Each breadcrumb item must contain a valid absolute URL |
| Missing field "step" | How-to | HowTo schema must include at least one step with name and text |
| Missing field "thumbnailUrl" | Video | VideoObject must include a valid thumbnail URL |
Search Analytics API: Programmatic Data Access
The Search Analytics API provides programmatic access to search performance data with capabilities beyond what the GSC web interface offers. The API is essential for building automated reporting pipelines, custom dashboards, and SEO monitoring systems.
API Query Parameters
| Parameter | API Field | Description |
|---|---|---|
| Start Date | startDate | Start of the date range (YYYY-MM-DD). Earliest available is 16 months ago |
| End Date | endDate | End of the date range (YYYY-MM-DD). Most recent is typically 2-3 days ago |
| Dimensions | dimensions | Array of dimensions to group by: query, page, country, device, searchAppearance, date |
| Search Type | type | Filter by search type: web, image, video, news, discover, googleNews |
| Row Limit | rowLimit | Maximum rows returned per request (default 1000, max 25000) |
| Start Row | startRow | Zero-based index for pagination through large result sets |
| Dimension Filter Groups | dimensionFilterGroups | Filters to apply: contains, equals, notContains, notEquals, includingRegex, excludingRegex |
| Data State | dataState | Data freshness: all (includes partial/preliminary data) or final (only fully processed data) |
| Aggregation Type | aggregationType | How data is aggregated: auto, byPage, or byProperty |
API best practices: Use pagination (startRow) when querying large datasets — the default 1,000 row limit may truncate results. Always specify dataState: "final" for analytical reports to avoid including incomplete data from recent days. The API supports regex filters for advanced query and page matching — use includingRegex to match URL patterns (e.g., /blog/.*) without needing to enumerate every page.
BigQuery Integration
Google Search Console offers a direct BigQuery export that automatically sends search performance data to a BigQuery dataset. This integration solves the 16-month data retention limit by storing historical data indefinitely. It also enables more powerful analysis through SQL queries, joins with GA4 BigQuery exports, and connection to business intelligence tools.
| Feature | Description |
|---|---|
| Export Frequency | Daily automatic export, typically available by mid-morning UTC |
| Data Schema | Date-partitioned table with columns for query, page, country, device, clicks, impressions, sum_position, is_anonymized |
| Retention | Unlimited — data stays in BigQuery until you delete it |
| Cost | Free to export. Standard BigQuery storage and query costs apply (first 10 GB/month free) |
| Access Control | Managed through Google Cloud IAM — can share with team members who are not GSC verified owners |
How to Use GSC Data for SEO Optimization
Having access to all this data is powerful, but knowing how to use it strategically is what separates effective SEO practitioners from those who drown in data. Here's a practical framework for leveraging GSC data.
For keyword and content optimization
Filter the Performance report by pages with high impressions but low CTR — these are pages ranking for relevant queries but not compelling users to click. Improve title tags and meta descriptions for these pages. Look for queries where your average position is 4-20 — these are within striking distance of page 1 and represent the highest-ROI optimization targets. Identify queries you rank for unintentionally to discover content gaps you can fill with dedicated pages.
For technical SEO auditing
Use the Page Indexing report to identify and fix errors preventing important pages from being indexed. Pay special attention to "Crawled - currently not indexed" pages — these indicate Google found your content but deemed it not worth indexing (often a quality signal). Monitor "Discovered - not yet crawled" volumes — a growing number suggests crawl budget issues that need addressing through better site architecture or sitemap optimization.
For Core Web Vitals improvement
Prioritize fixing poor URLs first, especially on mobile where competition is tighter. Focus on the metric with the highest failure rate across your site — often LCP for content-heavy sites or CLS for sites with dynamic ad placements. Group fixes by page template — fixing the template fixes all pages using it.
For link building strategy
Use the Links report to identify your most-linked pages and understand what content attracts natural backlinks. Analyze top linking sites to find potential partnership opportunities. Review anchor text distribution to ensure it looks natural — an over-optimized anchor text profile can trigger algorithmic penalties.
For structured data optimization
Review the Enhancement reports to ensure all structured data is valid and error-free. Focus on enhancement types that directly impact CTR: FAQ rich results expand your SERP footprint significantly, review snippets add star ratings that attract clicks, and product markup displays pricing and availability. Use the Search Appearance filter in the Performance report to measure the actual CTR lift from rich results versus standard blue links. Monitor enhancement validity after site deployments — code changes can break structured data without anyone noticing.
For international SEO
Use the country dimension to identify which countries drive the most organic traffic and where opportunities exist. Compare CTR by country — low CTR in a high-impression country may indicate that your title tags and descriptions need localization. Cross-reference with the hreflang implementation to ensure the correct language versions appear for each country. Track position by country separately — rankings vary significantly between markets even for the same query.
For mobile vs desktop optimization
Compare performance by device to identify mobile-specific issues. A page ranking well on desktop but poorly on mobile may have mobile usability problems visible in the URL Inspection tool. Since Google uses mobile-first indexing, mobile performance is the primary ranking signal. Check Core Web Vitals by device — mobile scores are typically worse than desktop and have a higher competitive impact on rankings.
What Changed in 2024-2026: GSC Updates
Google has made several significant changes to Search Console over the past two years. Understanding these changes is essential for anyone relying on GSC data for SEO decisions.
March 2024: INP replaces FID
Interaction to Next Paint (INP) replaced First Input Delay (FID) as the responsiveness Core Web Vital. INP measures the latency of all interactions during a page visit (not just the first), making it a more comprehensive measure of interactivity. Many sites that passed FID fail INP — particularly JavaScript-heavy SPAs.
2025: BigQuery export general availability
The BigQuery export feature became generally available, allowing all verified properties to automatically export search performance data. This solved the longstanding 16-month data retention limit and enabled advanced SQL-based analysis. Sites should enable this feature immediately to begin building historical datasets.
2025: Search Analytics API v2 improvements
The API added support for the discover and googleNews search types, new filter operators including regex support, and improved data freshness with the dataState parameter. The maximum row limit increased from 25,000 to 50,000 per request for properties with verified ownership.
Common Mistakes When Analyzing GSC Data
Even experienced SEO professionals make these mistakes when working with Google Search Console data. Avoiding them will prevent flawed analyses and bad optimization decisions.
1. Misunderstanding average position
Average position is impression-weighted, not a simple daily average. A page that ranks #1 for a high-volume query (10,000 impressions) and #50 for a low-volume query (10 impressions) will show an average position of ~1.0, not 25.5. This is correct behavior but can be misleading. Always look at impressions alongside position to understand the weight of each ranking.
2. Not accounting for anonymous queries
Approximately 10-20% of search queries are anonymized for privacy and excluded from the query dimension. This means the sum of clicks and impressions when filtering by query will be lower than the total when no query filter is applied. The "missing" data is not lost — it's just not attributable to specific queries. Don't assume your query-level data represents 100% of your traffic.
3. Ignoring the 2-3 day data delay
GSC search performance data has a 2-3 day processing delay. Data for today and yesterday is incomplete or missing. Making SEO decisions based on the most recent day's data leads to false conclusions about traffic drops or spikes. Always analyze completed data periods and compare at least week-over-week to account for natural daily fluctuations.
4. Confusing GSC clicks with GA4 sessions
GSC clicks and GA4 organic sessions will never match perfectly. GSC counts clicks from Google Search (server-side). GA4 counts sessions on your site (client-side, requires JavaScript). The gap is caused by: users who click but leave before the page loads, JavaScript-blocked users, bot filtering differences, and different deduplication rules. A 10-20% discrepancy between GSC clicks and GA4 sessions is normal and expected.
5. Treating impressions as views
A GSC impression means your URL appeared on a search results page — not that a user actually saw it. If your result is at position 8, most users on mobile may not scroll down to see it, but it still counts as an impression. This means low-position impressions overstate your actual visibility. Focus on impressions where position is 1-5 for a more realistic view of seen-impressions.
6. Comparing positions across different query sets
When comparing two time periods, the set of queries may differ. If new high-impression queries at low positions enter the data, your "average position" may appear to worsen even though no individual query ranking changed. Always compare query-level or page-level positions for specific terms rather than relying on aggregate position trends to diagnose ranking changes.
