Quick answer
NOTABIS flags a URL for url-query-review when the full URL is longer than 2,000 characters or contains more than five query parameters. These are review thresholds chosen for crawlability diagnostics, not universal SEO limits. Keep important URLs understandable, remove unnecessary parameters, and use canonicalisation or routing rules for intentional variants.
What the issue means
Query parameters carry state such as filters, sorting, tracking, or session data:
/products?category=shoes&sort=price&utm_source=newsletter
Parameters can create many URL variants for the same content, split internal links, and make debugging harder. A long or parameterised URL is not automatically wrong; an important question is whether each variant has a distinct purpose and a stable canonical strategy.
Why it matters for SEO
Search engines can crawl parameterised URLs, but large variant sets may consume crawl activity and make duplicate or canonical relationships harder to interpret. Tracking parameters usually do not create new content and should not be allowed to spread through internal links. There is no single character count that guarantees indexing or rankings.
How NOTABIS detects it
The url-query-review rule is page-scoped. NOTABIS measures the URL string and parses its query component; it records a low-severity review when the total URL length exceeds 2,000 characters or the query contains more than five ampersand-separated parameters. It does not determine whether parameters are useful, duplicate content, sensitive, or safe to remove.
How to check it yourself
List the parameters in the browser address bar, server logs, analytics links, and internal HTML. Group variants by content and intent, then request representative URLs to compare status, canonical, robots directives, and page output. Check whether redirects or framework routing reorder, drop, or duplicate parameters.
How to fix it
Remove tracking parameters from internal navigation where they are not needed, keep filter and sort controls consistent, and avoid putting session identifiers in public URLs. For variants that should consolidate, emit a correct canonical and link internally to the clean URL. For variants that should not be crawled, use a deliberate crawl and index strategy rather than deleting state users need.
/products/shoes
/products/shoes?sort=price
Test analytics, pagination, caching, and sharing after changing parameter handling. Re-crawl representative variants and confirm that the final canonical and content match the intended design.
When this is intentional or does not need fixing
Search, filters, pagination, localisation, and authenticated workflows may require parameters. A long signed URL can be a security or application requirement; do not truncate it blindly. Review whether the page is public and indexable before changing routing or blocking a parameter pattern.
Related issues
Read duplicate content, missing canonical URLs, canonical and noindex conflicts, and deep crawl pages.
Run a NOTABIS audit
NOTABIS lists URLs that cross its length or parameter-count review thresholds so you can inspect their purpose and canonical strategy in context.