How do I resolve conflicting redirects in HubSpot?

Definition: HubSpot redirect priority is the numeric order used to choose between rules matching the same incoming URL. As of October 2026, HubSpot documents that the matching redirect with the lowest value applies.

Key facts

• HubSpot's redirect management documentation gives an example where priority 1 takes precedence over priority 100.
• HubSpot's flexible redirect documentation describes rules that match URL patterns and carry matched parts into destination URLs.
• The URL redirects API guide documents a separate setting, isOnlyAfterNotFound, that controls whether an existing live page prevents a redirect.

How is the winning redirect selected?

HubSpot's management guide places the controls under Content > Domains & URLs > URL Redirects. For an editable rule, Actions > Edit > More options exposes Priority. Clearing Assign lowest priority allows a custom value; new redirects receive the lowest priority by default.

Resolving an overlap means assigning the intended rule a smaller numeric value than competing matching rules. The documentation does not specify a tie-breaker for equal values, so distinct values make the intended order explicit. Update URL redirect saves the change.

Which matching settings need checking?

A query string is the part of a URL containing parameters after ?, as described in HubSpot's flexible pattern guide. Its parameter-based example requires Match query strings under More options.

The API guide identifies the matching controls:

• isMatchFullUrl includes the domain when matching the incoming URL.
• isMatchQueryString includes the query string in the path match.
• isProtocolAgnostic matches both HTTP and HTTPS.
• isTrailingSlashOptional allows a trailing slash to be ignored.

The same guide states that isOnlyAfterNotFound: false lets the redirect take precedence over an existing page.

How can a flexible pattern overlap another rule?

HubSpot's flexible pattern example moves a blog to a subdomain while retaining everything after /posts/. It uses these values in Original URL and Redirect to, respectively:

http://www.example.com/posts/*rest-of-url
http://blog.example.com/posts/{rest-of-url}

Here, *rest-of-url captures the remainder, and {rest-of-url} inserts it into the destination. Because this rule covers multiple URLs, a conflict review includes patterns covering the affected path alongside individual URL rules. The original pattern and destination template serve different purposes: the original determines matching, while the destination determines where a matching request goes.

Related terms

• HTTP redirects
• How do I create a HubSpot URL redirect?
• How do I create a pattern-based URL redirect in HubSpot?
• How do I control query strings in HubSpot redirects?

FAQ

Can I edit an automatically created redirect?

HubSpot's management documentation says system redirects appear when a published page, blog, or blog post URL changes. You can find them through Display > System redirects; these rules cannot be edited.

What if the priority change appears ineffective?

The same documentation allows up to 48 hours for redirect propagation and recommends clearing your browser cache when behavior differs from expectations.

Does a live page always prevent redirection?

The API documentation says isOnlyAfterNotFound: false gives the redirect precedence over an existing page. You can check this setting when a published page and a redirect share an incoming URL.

Sources

1. HubSpot, "Create and manage URL redirects", 21 May 2026
2. HubSpot, "Set up a flexible pattern URL redirect", 10 February 2026
3. HubSpot Developers, "URL redirects API", 13 April 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer