Skip to main content

Separate Cache for Query Parameters

Updated over 3 weeks ago

By default, FlyingPress does not cache URLs with query parameters. These are bypassed to avoid caching unnecessary or duplicate content.

However, if a query parameter changes the visible content, you can tell FlyingPress to treat it as unique and generate a separate cached version.

How it works

Once you add a query parameter to this setting:

  • FlyingPress will cache URLs with that parameter separately.

  • Each variation will get its own cached HTML file.

Example:

  • /products/ → cached

  • /products/?filter=red → bypassed by default

  • Add filter/products/?filter=red is now cached separately

When to use it

Use this only when the parameter actually changes the page content.

Examples (safe to cache):

  • /products/?filter=red — filtered product list

  • /blog/?page=2 — paginated content

  • /deals/?sort=price — sorted listings

Avoid caching:

  • Tracking or marketing params (utm_source, fbclid, ref)

  • Temporary/session-based values

FlyingPress already ignores many common tracking parameters automatically.
See: Ignored query parameters

Did this answer your question?