Quick answer
A dynamic URL is an address whose page is generated from a query at request time, with the query carried in parameters after a ?. Dynamic URLs don't hurt SEO by themselves; the problem is parameter combinations exploding into duplicate pages, in search and in analytics reports alike.
Formula: URLs per template = (values per parameter + 1) ^ number of parameters, multiplied further when parameter order isn't fixed
What is a dynamic URL?
A dynamic URL is a web address whose content is generated from a query when the page is requested, usually from a database, and which carries that query in URL parameters after a ?. https://shop.example/shoes?color=black&size=42&sort=price is dynamic: the same template at /shoes returns a different list for every combination of color, size and sort. A static URL such as https://shop.example/about points at one fixed piece of content.
Dynamic URLs are normal. Every search results page, filtered product list and paginated archive uses them. The trouble starts when parameters multiply. This is the thesis of this page: a dynamic URL doesn't hurt SEO by itself; the problem is parameter combinations exploding into large numbers of duplicate pages. Web analytics has the same problem, so parameters must be folded together or one page splits into hundreds of rows.
Note that not every URL with a ? is dynamic in this sense. A tracking parameter such as utm_source doesn't change the content at all. A quick test: remove the parameter; if the page is identical, it's a tracking parameter, not a content parameter.
Static vs dynamic URLs
| Static URL | Dynamic URL | |
|---|---|---|
| Example | /blog/crawl-budget | /search?q=crawl+budget&page=2 |
| How content is produced | Fixed file or fixed route | Template filled from a query at request time |
| Number of URLs | One per page you publish | One per parameter combination, possibly unlimited |
| Readability | Words that describe the page | Keys and values, sometimes ids or session tokens |
| SEO risk | Low | Duplicate and near-duplicate pages, wasted crawling |
| Typical uses | Articles, product pages, landing pages | Site search, filters, sorting, pagination, tracking |
| Analytics | One row per page | One row per combination unless parameters are folded |
A "static-looking" URL can still be dynamic underneath: /shoes/black/42 may be the same filter rewritten into the path. Rewriting changes how the URL looks, not how many combinations exist.
How search engines treat dynamic URLs
Google's documentation is direct about the trade-off. Its URL structure guide recommends standard key=value pairs joined with &, and advises avoiding session IDs in URLs, using cookies instead. It also warns that "overly complex URLs, especially those containing multiple parameters, can cause problems for crawlers", because additive filters create many URLs with largely the same content, so Googlebot may use more bandwidth than needed or fail to index all of a site's content.
Its faceted navigation guidance names two costs: overcrawling, because a crawler can't know a filtered URL is useless without fetching it, and slower discovery, because time spent on filtered URLs is time not spent on new pages. The options it gives:
- If filtered URLs don't need to appear in Search: block them with robots.txt, and keep individual item pages and an unfiltered listing crawlable. Or put filters in a URL fragment (
#color=black), which Google generally ignores for crawling and indexing. - If some filtered URLs should be indexed: use
&as the separator, keep filter order consistent, prevent duplicate filters, and return a 404 for combinations with no results instead of redirecting to a generic page. rel="canonical"on filtered URLs pointing to the unfiltered version may reduce crawling of the duplicates over time, though Google says it's less effective than blocking. Canonicalisation in general is described in Google's guide to consolidating duplicate URLs.
Google retired the Search Console URL Parameters tool in 2022, saying only about 1% of the parameter configurations set in it were useful for crawling. There is no setting to tell Google which parameters to ignore; the site's own links, canonicals and robots rules have to do that work. Crawl capacity spent on parameter variants is the subject of crawl budget.
Worked example: how three filters become hundreds of URLs
Sample data: a category page /shoes has three filter parameters, color, size and brand, each with 5 values. Any filter can be left out.
- Combinations of values. Each parameter is either absent or one of 5 values: 6 options. 6 × 6 × 6 = 216 URLs, including the unfiltered page.
- Parameter order. If the site's links don't fix the order,
?color=black&size=42and?size=42&color=blackare different URLs with the same content. Counting orderings: 1 (no filter) + 3 × 5 (one filter) + 3 × 25 × 2 (two filters, 2 orders) + 125 × 6 (three filters, 6 orders) = 1 + 15 + 150 + 750 = 916 URLs. - Across the site. With 40 categories built the same way: 40 × 216 = 8,640 URLs with fixed order, or 40 × 916 = 36,640 without it.
Fixing the parameter order alone removes 36,640 − 8,640 = 28,000 duplicate URLs, about 76%, without changing a single page. Blocking or canonicalising filter combinations that nobody searches for removes most of the rest. Add a sort parameter with 3 values and every number above grows again, by up to 4 times.
The same 916 variants hit your analytics. If the reporting tool treats each query string as a separate page, the /shoes row splits into up to 916 rows, each with a handful of pageviews, and the page that matters vanishes from the top-pages list.
Dynamic URLs in web analytics
- Fold content parameters into the page path for page reports, so
/shoes?color=blackand/shoes?size=42count as/shoes. - Parse campaign parameters as source data, not as pages.
utm_source,utm_mediumandutm_campaigndescribe where the visit came from; see UTM. - Keep the parameters you need as properties. Site search terms (
q,s,search) and filter choices are useful, but as a search-term report or an event property, not as page rows. - Strip identifiers. Session ids, email addresses and tokens in URLs leak into reports and referrers. Remove them at the source.
Common misconceptions
- "Google can't index dynamic URLs." It can and does. The problem is volume and duplication, not the
?. - "Rewriting to static-looking URLs fixes SEO." It changes the format. If
/shoes/black/42and/shoes/42/blackboth exist, you still have duplicates. - "Canonical tags stop crawling." They are a hint about which URL to index; Google may still crawl the variants, and says blocking is more effective for crawl load.
- "UTM parameters create duplicate content." They can create duplicate URLs if internal links carry them. Use UTM tags only on links from outside your site.
Dynamic URLs in TapCub
Taking the /shoes example into TapCub:
- One row, not 916. When the collector records a page for page statistics, it drops the query string and a trailing
/, and keeps the path up to 512 characters. All 916 variants appear as/shoesin Web analytics › Pages, so the category's real traffic stays visible. A route that only changes?tab=still sends a pageview, because the URL changed, but it's filed under the same path. - Campaign tags go to sources. UTM values are stored as source fields, not as part of the page path, and appear in the UTM tab of Web analytics › Sources split into source, medium, campaign, term and content.
- Search terms are kept. Site search parameters default to
s,qandsearchand can be edited in Web analytics › Configuration › Web settings; the term is stored on the pageview and shows up as an on-site search term in Web analytics › Sources, not as a page. - Hashes stay out unless you route with them. By default the script drops
#and everything after it. A hash router needsdata-hash="true"on the script tag, and then a URL containing#/folds the hash into the path.
If you need the filter values themselves, send them as event properties rather than expecting the page report to keep the query string. TapCub doesn't change how search engines crawl your parameters; robots rules and canonicals stay on your site.
Sources
- Google Search Central, URL structure best practices for Google Search.
- Google for Developers, Managing crawling of faceted navigation URLs.
- Google Search Central, How to specify a canonical with rel="canonical" and other methods.
- Google Search Central Blog, Spring cleaning: the URL Parameters tool (March 2022).
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Technical Engineer
Focuses on tracking code, SDKs, and API integrations, with practical guidance on implementation checks and troubleshooting.