Technical SEO & GSC Glossary

The average ranking of your top URL for a given search query across all Google Search appearances in the chosen timeframe. When multiple URLs from your site rank for a query, GSC counts the highest-ranking URL for each impression.

Because it is an average across varying personalized, geographic, and device search results, average position can fluctuate even when rank is stable in one region. A position of 1–10 typically indicates page 1 of organic desktop results.

The authoritative version of a duplicate or near-duplicate set of web pages that Google designates as representative to be indexed and served to searchers.

Specified in code via <link rel="canonical" href="..."> or HTTP Link headers. Google uses canonical declarations as a strong hint, but evaluates many signals (redirects, internal links, sitemap entries, page content) to determine the Google-selected canonical.

The total number of URLs that Googlebot can and wants to crawl on a site during a given period. It is the intersection of Crawl Capacity (host limit) and Crawl Demand (content value and freshness).

Generally not a constraint for small-to-medium sites (<10,000 pages). It becomes a primary architectural concern for large e-commerce platforms, dynamic faceted navigation, or sites with frequent publishing cadences.

The maximum simultaneous crawl rate Googlebot will apply to a host without degrading the site’s server performance or causing HTTP 5xx errors.

Calculated dynamically based on server response latency, error rates, and host limits configured in Search Console or detected automatically during crawling.

How much Google wants to crawl your site, driven by popularity, freshness, and the perceived value of re-crawling URLs to detect content updates.

Even if a server has massive crawl capacity, Googlebot will not crawl if crawl demand is low due to stagnant content or low site popularity.

A Search Console status indicating that Googlebot successfully fetched and crawled the page, but Google chose not to add it to the search index.

Typically signals perceived low content quality, thin content, near-duplicate text, or low crawl demand/priority compared to other site pages. Does not indicate an HTTP or server error.

A public dataset of real-world user experience metrics collected from opted-in Chrome users across millions of origins on the web.

Powers the Core Web Vitals report in Google Search Console. Provides 75th-percentile field data for LCP, INP, and CLS across 28-day rolling collection windows.

Google found the URL (via sitemaps, internal links, or external referrals), but has not yet crawled or scheduled it for immediate crawling.

Often occurs on new websites or large sites where crawl capacity is constrained, or where Googlebot prioritizes more established URLs on the host. If chronic, check internal linking depth and server response times.

The URL that Google’s indexation pipeline chose as canonical after evaluating all algorithmic signals, regardless of the user-declared canonical.

Viewable via the URL Inspection Tool. If Google-selected canonical differs from User-declared canonical, inspect internal links, sitemap entries, and content similarity.

Recorded whenever a search result URL appears on the current search results page that a user is viewing, regardless of whether the result was scrolled into the user’s viewport.

For paginated search results, an impression is only logged if the user navigates to the page containing your link. For carousel or image search results, impression logging rules have specialized criteria.

A Core Web Vital metric measuring overall site responsiveness by tracking the latency of all user interactions (clicks, taps, key presses) throughout a page lifecycle.

Replaced First Input Delay (FID) as an official Core Web Vital in March 2024. A good INP score is 200 milliseconds or lower at the 75th percentile of page visits.

A Core Web Vital metric that measures perceived loading speed by recording the render time of the largest image or text block visible within the initial viewport.

A good LCP score is 2.5 seconds or less at the 75th percentile of page loads. Common culprits include unoptimized hero images, slow server response times (TTFB), and render-blocking JavaScript.

A penalty issued by a human reviewer at Google when a site is found not to comply with Google Search Essentials (e.g. unnatural links, pure spam, cloaking).

Visible in the Security & Manual Actions tab. Manual actions depress rankings or remove affected URLs from search results until a reconsideration request is submitted and accepted.

The regular expression syntax engine used by Google Search Console filters and BigQuery, designed by Google for predictable, linear-time evaluation without catastrophic backtracking.

Unlike PCRE, RE2 deliberately does not support lookarounds (?=...), backreferences (\1), or possessive quantifiers. Supports case-insensitive matches using the flag (?i).

A Google Search presentation that goes beyond the standard blue link and description snippet, such as recipes, reviews, FAQ accordions, and product cards.

Enabled by implementing structured data schema (JSON-LD) following Schema.org standards and Google Search Central feature guides.

A filter dimension in the Performance report that categorizes impressions and clicks by the specific rich result, visual enhancement, or experience type displayed in search.

Examples include Merchant Listings, Product Snippets, Good Page Experience, Videos, and Translated Results.

A page that returns a successful HTTP 200 OK status code to crawlers, but displays content indicating to users that the page does not exist, has an empty state, or is missing.

Googlebot flags these as errors because serving 200 for missing pages wastes crawl budget and confuses indexation. Fix by serving authentic HTTP 404/410 status codes or redirecting to relevant content.

An automated REST API provided by Google to query the indexing status, crawl metadata, canonical choices, and rich result validations of individual URLs programmatically.

Subject to a daily quota (typically 2,000 calls per day per property). Best used for auditing critical conversion templates, verifying automated deployments, and debugging index anomalies.

Google’s server-side rendering pipeline based on an evergreen Chromium engine that executes JavaScript, fetches DOM subresources, and builds the rendered DOM for indexing.

Rendering may be deferred until computing resources are available. Pages requiring excessive API calls, long timeouts (>5s), or user interaction to render content risk incomplete indexing.