TapCub is live — analytics, insights and live chat, free on one platform
Glossary

What is a dynamic URL? Static vs dynamic, SEO and analytics

A dynamic URL generates content from parameters in the query string. Static vs dynamic URLs, what Google recommends, how three filters become hundreds of URLs, and how to keep analytics readable.

Chen Yu Reviewed by Xu An Also called dynamic URLs Last updated Nov 15, 2026 Glossary

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 URLDynamic URL
Example/blog/crawl-budget/search?q=crawl+budget&page=2
How content is producedFixed file or fixed routeTemplate filled from a query at request time
Number of URLsOne per page you publishOne per parameter combination, possibly unlimited
ReadabilityWords that describe the pageKeys and values, sometimes ids or session tokens
SEO riskLowDuplicate and near-duplicate pages, wasted crawling
Typical usesArticles, product pages, landing pagesSite search, filters, sorting, pagination, tracking
AnalyticsOne row per pageOne 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.

  1. Combinations of values. Each parameter is either absent or one of 5 values: 6 options. 6 × 6 × 6 = 216 URLs, including the unfiltered page.
  2. Parameter order. If the site's links don't fix the order, ?color=black&size=42 and ?size=42&color=black are 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.
  3. 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=black and /shoes?size=42 count as /shoes.
  • Parse campaign parameters as source data, not as pages. utm_source, utm_medium and utm_campaign describe 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/42 and /shoes/42/black both 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:

  1. 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 /shoes in 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.
  2. 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.
  3. Search terms are kept. Site search parameters default to s, q and search and 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.
  4. Hashes stay out unless you route with them. By default the script drops # and everything after it. A hash router needs data-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

Was this explanation clear?

We use your answers to fix and expand this page.

Chen Yu

Technical Engineer

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

FAQ

Questions people ask

Short answers to the follow-up questions that come up most.

Still have a question?

Chat with the team behind TapCub — we usually reply within a few hours on business days.

Are dynamic URLs bad for SEO?

Not by themselves. Google crawls and indexes dynamic URLs. The risk is volume: filters, sorting and session ids can create thousands of URLs with the same content, which wastes crawling and splits signals. Fix parameter order, block or canonicalise combinations nobody searches for, and keep only useful filtered pages indexable.

What is the difference between a static and a dynamic URL?

A static URL points at one fixed page, such as /about. A dynamic URL fills a template from a query, such as /shoes?color=black, so one template can produce many URLs. A path like /shoes/black can still be dynamic underneath; the difference is how content is produced, not how the URL looks.

How do I find dynamic URLs on my site?

Look for addresses with ? and & in your site crawl, in the Search Console page indexing report and in server logs. Group them by path and parameter name to see which template produces the most variants. In analytics, a page report that folds query strings shows whether those variants receive real traffic at all.

See this number on your own site

Add one script tag for web and apps, and the first reports fill in within minutes.

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics