Definition
A GET parameter (or query-string parameter) is a key–value pair appended to a URL after a question mark, with multiple pairs separated by ampersands, e.g. /casinos/?sort=rating&payment=crypto. The web server and the page's scripts read these values to change what is shown — filtering a list, sorting results, setting a language, carrying a tracking tag — without needing a different path for every combination.
GET parameters are visible, shareable and cacheable, which makes them convenient but also creates SEO and privacy exposure. Every distinct combination of parameters is technically a different URL, so a page with several filter and sort options can generate thousands of crawlable URLs that all show substantially the same content, and any parameter that carries user data is exposed in the URL, in server logs, and in analytics.
In context
On iGaming affiliate and operator sites, GET parameters are the usual cause of index bloat: faceted-filter combinations on casino and game lists, sort orders, pagination, session identifiers and tracking tags multiply the URL space far beyond the number of real content pages. The standard handling is to decide which parameterised URLs have genuine search value (usually very few) and, for the rest, canonical each variant to the clean base URL, noindex combinations that should not be indexed at all, disallow tracking and session parameters in robots.txt, and configure the analytics platform to consolidate or ignore parameters that only carry tracking data.
Security and privacy rules also apply. Parameters must never carry passwords, tokens or personal data, because URLs are logged, cached, shared and sent in referrer headers.
Tracking parameters (UTMs, click IDs) should be read by the page and then stripped from the visible URL so they are not indexed and not propagated. Handled well, GET parameters are a clean way to build flexible interfaces; handled carelessly, they are one of the most common sources of both crawl waste and accidental data exposure on large sites.
Worked example
An affiliate's casino list has five filters and three sort orders, generating about 6,000 crawlable parameter URLs for one underlying list. It canonicals them all to /casinos/, noindexes the filter combinations, and disallows ?sort= in robots.txt.
Indexed URL count drops sharply and crawl budget concentrates on the reviews.
Related terms
Frequently asked questions
Browse the full iGaming & affiliate glossary — hundreds of EN/RU terms with examples.
← Back to glossary