HubSpot flexible pattern URL redirects are designed for URL changes that follow a repeatable structure. Instead of creating a separate redirect for every old page, you define a source pattern and a destination pattern so matching URLs can be handled as a group.
They are useful during content migrations, blog restructuring, folder changes and URL standardisation. However, a pattern redirect is only safe when the relationship between the old and new URLs is predictable. If the mapping is unclear, individual redirects are usually better than trying to force an irregular set of pages into one rule.
The right approach is to treat redirects as part of a URL migration plan, not as a quick technical fix. Define the business and content change first, choose the redirect type, test representative URLs, and then monitor the results. This reduces broken links, redirect chains, incorrect page destinations and avoidable search visibility problems.
What is a flexible pattern URL redirect in HubSpot?
A flexible pattern URL redirect maps a repeatable group of old URLs to a corresponding group of new URLs. The source URL contains variable parts, and the destination uses those captured parts where appropriate. This allows one rule to represent many URL relationships.
For example, a site may move pages from an old folder to a new folder while keeping the rest of each path consistent. A pattern can express that structural change without requiring a manually maintained redirect for every page.
A pattern redirect is appropriate when the URL relationship is predictable, testable and valid for every URL that the rule can match.
This is different from a standard redirect, which maps one source URL to one destination URL. Flexible patterns reduce repetitive configuration, but they also increase the impact of a mistake. A poorly designed rule can send many unrelated URLs to the wrong destinations.
When should you use a pattern redirect?
Use a flexible pattern when a large set of URLs shares the same structural change. Common examples include:
- Moving pages from one consistent folder to another.
- Removing or adding a predictable path segment.
- Changing a date-based URL structure where the remaining path can be mapped reliably.
- Moving a group of content into a new information architecture.
- Migrating from another content management system with a consistent legacy URL format.
Do not use a pattern simply because there are many URLs. Volume is not enough. The source URLs must have a meaningful relationship with their destinations, and the rule must not match pages that should remain unchanged.
Use individual redirects when the old URLs are irregular, when destinations differ by page, or when a pattern would require exceptions. A smaller set of precise redirects is safer than a broad rule that creates incorrect matches.
Consistent structure
The same path transformation applies across the full group, and the variable part can be carried into the destination.
Irregular mapping
Pages have different destinations, exceptions or content relationships that cannot be represented by one repeatable rule.
How to plan the redirect before configuring HubSpot
Start with the intended URL state rather than the HubSpot form. A redirect is a technical expression of a content and architecture decision. Write down what is changing, which URLs are in scope, and what should happen to URLs that do not match the main pattern.
- Inventory the old structure. Identify the folders, path segments, URL parameters and page types affected by the change.
- Define the new structure. Confirm the final destination format before creating redirects. Avoid redirecting to an interim URL that may change again.
- Separate included and excluded URLs. List pages that should follow the pattern and pages that require a different destination or no redirect.
- Choose the redirect status. Use a permanent redirect for a lasting move. A temporary redirect is appropriate only when the change is genuinely temporary or being tested.
- Prepare test cases. Select normal examples, edge cases, paths with different lengths and URLs that should not match.
This preparation creates a simple decision sequence: define the final state, prove the mapping, configure the rule, test the rule, then monitor the live result.
How to create a flexible pattern redirect in HubSpot
HubSpot interface labels and available options can change by account configuration and product updates, so use the current redirect settings in your portal as the source of truth. The underlying workflow is generally the same.
1. Open the URL redirect tool
Sign in with a role that can manage website settings, then open the HubSpot settings area and locate the URL redirect tool under the website, domains or URL management settings. Review existing redirects before adding a new one. An existing rule may already match the source path, or a new rule may overlap with one already in place.
2. Start a new redirect and select the pattern option
Create a new redirect and choose the flexible pattern or equivalent pattern-based option when it is available. The form should provide fields for the original URL pattern and the destination URL pattern.
3. Define the original URL pattern carefully
Enter the old path structure using the variable syntax supported by HubSpot. Treat each variable as a captured part of the original URL. Keep the pattern as narrow as the migration requires. A rule that matches only the intended folder is easier to reason about than one that begins at the site root and relies on assumptions.
Check whether the rule applies to the path only or to additional URL elements such as query strings. Do not assume that parameters, trailing slashes, language folders or case differences will behave the same way unless you have verified them in the current HubSpot implementation.
4. Define the destination pattern
Build the destination from the final URL structure. Reuse captured variables only when the corresponding value remains valid in the new location. A source segment should not be carried forward merely because it is available. For example, an old date segment may need to be removed if the new architecture no longer uses dates.
Review the destination as a human would. It should resolve to the correct page, represent the same or intentionally changed content, and avoid sending multiple unrelated pages to a generic destination.
5. Select the appropriate status
For a permanent URL move, select a permanent redirect. Use a temporary redirect only when the original URL is expected to return or when you are deliberately running a short-term test. The status should reflect the intended business state of the URL, not simply the easiest option in the interface.
6. Save and test before expanding the change
Test several URLs immediately after saving the rule. Include a typical URL, a URL with a different variable value, the deepest expected path, an excluded path and a URL that should not match. Confirm that the response reaches the final destination directly and does not create a loop or chain.
Testing one successful example proves only that one URL works. Testing boundaries proves whether the rule is safe for the wider URL set.
Redirect testing and migration checks
Redirect testing should cover more than whether a browser eventually displays a page. Check the complete path from the old URL to the final destination.
- Confirm the old URL returns the intended permanent or temporary status.
- Confirm the destination URL is correct for the specific source URL.
- Check for redirect chains where one redirect leads to another redirect.
- Check for loops where URLs point back to themselves or cycle between destinations.
- Verify that the destination page is relevant and accessible.
- Review internal links, canonical references and XML sitemap entries after the migration.
- Monitor not-found errors and unexpected traffic changes after launch.
A redirect should not be treated as a substitute for updating internal links. If the website still links to old URLs, visitors and crawlers continue to encounter unnecessary redirects. Update navigation, content links, templates and campaign references so the new URL structure becomes the normal operating state.
Common failure modes and how to avoid them
Overly broad matching
A pattern that begins too high in the URL hierarchy may capture pages outside the intended migration. Limit the source path to the smallest stable structure that represents the change.
Overlapping rules
Multiple rules may appear reasonable in isolation but produce confusing results together. Review existing redirects and document which rule owns each affected URL group. If precedence matters, test the actual order and outcome in HubSpot rather than relying on assumptions.
Incorrect variable reuse
A captured value may be syntactically valid but semantically wrong for the destination. A product identifier, article slug or date should only be reused when it still identifies the correct destination after the move.
Redirecting everything to a general page
Sending many old pages to a homepage or broad category page can create a poor user experience and weak content mapping. Redirect to the closest relevant final page. If no meaningful destination exists, decide deliberately whether the old URL should return a not-found response instead.
Leaving temporary rules in place indefinitely
Temporary redirects should have an owner and a review date. Without that ownership, they become permanent operational clutter and make future migrations harder to understand.
A redirect rule should have an owner, a documented reason and a defined final state.
A practical operating model for HubSpot redirects
For ongoing website management, maintain a redirect register outside the redirect interface. Record the source pattern, destination pattern, status, owner, creation date, reason and review date. This gives marketing, content and technical teams a shared reference when URL changes happen later.
- The source pattern describes only the intended URL group.
- The destination is the final approved URL structure.
- Variable values are reused only where they remain meaningful.
- Exceptions and exclusions have been identified.
- Representative URLs have been tested.
- Internal links and sitemap references have a plan for updating.
- An owner is responsible for monitoring and future changes.
When the redirect rules affect a broader CRM, content or website operating model, the technical configuration should be coordinated with the teams that own those processes. HubSpot consulting can help align URL structure, content operations, automation and reporting when a migration is part of a larger systems change. For related architecture and implementation work, see HubSpot consulting services and CRM consulting.
Example: moving a structured resource library
Imagine a business moving a resource library from an old folder to a new one while keeping each resource slug unchanged. A flexible pattern may be suitable because the path transformation is consistent. The team would first confirm that every resource follows the same structure, identify exceptions such as landing pages and downloads, test several representative URLs, and then update internal links to the new folder.
If some resources need new slugs, some are being retired and others are being merged, the migration is no longer a simple pattern change. Those URLs should be mapped individually or handled through a combination of a narrow pattern and explicit exception rules.
The practical lesson is simple: use flexible redirects for repeatable relationships, not for convenience. The quality of the migration depends on the quality of the mapping decision before the rule is saved.
Frequently asked questions
What is a flexible pattern URL redirect in HubSpot?
It is a redirect rule that maps a group of old URLs to a group of new URLs using a repeatable path structure and supported variable syntax, rather than mapping every URL individually.
When should I use a HubSpot pattern redirect instead of individual redirects?
Use a pattern redirect when the same URL transformation applies consistently across the full group. Use individual redirects when destinations vary, exceptions are common or the source URLs are irregular.
Should a HubSpot URL migration use a 301 or 302 redirect?
Use a permanent redirect for a lasting URL move. Use a temporary redirect only when the change is genuinely temporary or is being tested for a limited period.
How should I test a flexible pattern redirect?
Test typical URLs, different variable values, boundary cases, excluded URLs and paths that should not match. Confirm the status, destination, absence of loops or chains, and relevance of the final page.
Can a flexible redirect replace updating internal links?
No. Redirects handle requests for old URLs, but internal links should still be updated so users and crawlers use the final URL directly and the website remains easier to maintain.
Need a safer HubSpot URL migration?
Review the URL structure, ownership and redirect logic before implementation so your HubSpot migration creates a cleaner and more reliable website system.
