Skip to the content
searchboar.

Crawling and indexing

URL parameter: Meaning, examples and limitations

A URL parameter is a named value in a URL’s query string, commonly written after a question mark. Parameters can select content, apply filters or record campaign information, so their meaning must be understood before they are removed, cached or canonicalized.

At a glance

  • Some parameters change the document; others only record context.
  • Parameter combinations can multiply crawlable addresses.
  • Removing every query string can break useful behavior.
On this page
One address branches into filter and tracking parameter cards.
A URL parameter is a named value in a URL’s query string, commonly written after a question mark.

Where is the parameter?

In /products?color=blue&sort=price, color and sort are parameter names with values. The application decides what those values do. A path component and a fragment are different URL parts.

Parameter order, repeated values and empty values can have application-specific meanings. Do not assume two addresses return identical content just because their visible paths match. Google's URL guidance explains why simple, consistent structures help crawling.

Example: filtering versus campaign tracking

A shop might use color=blue to show blue products and utm_source=newsletter to record how a visitor arrived. The first may change the displayed selection; the second commonly describes acquisition. UTM parameters and product filters should therefore not be treated as interchangeable.

A canonical decision depends on the page's intended content. A useful standalone category and a temporary filter combination may deserve different treatment. Review faceted navigation before creating indexable pages for every combination.

Why do parameters affect caching?

A cache needs a rule for deciding which requests can reuse one response. Ignoring a content-changing parameter can return the wrong result. Including every irrelevant tracking value can reduce reuse by creating many copies of the same public page.

The correct policy follows the application's actual contract. Test representative values and combinations, including errors. Never drop parameters that control authentication, authorization or user-specific behavior merely to improve cache hit rates.

What should be reviewed for SEO?

Inspect generated links, the canonical URL, redirects and the sitemap together. Unbounded combinations can create a crawl trap. Use a small set of deliberate, useful destinations where appropriate and make the underlying behavior consistent. Parameter cleanup is not a blanket rule that shorter-looking addresses always rank better.

Sources

  1. Google: URL parameter