A website migration without a proper redirect strategy is an SEO disaster waiting to happen. When you move a HubSpot website between portals, change domains, or restructure your URL architecture, every existing URL that changes needs a 301 redirect pointing to its new location. Miss even a handful of high-traffic pages and you will watch your organic traffic drop within days.
This guide covers everything you need to know about implementing 301 redirects during a HubSpot migration, from the fundamentals of redirect types to advanced techniques for bulk redirects, chain detection, and post-migration monitoring.
Understanding Redirect Types and When to Use Them
Not all redirects are created equal, and using the wrong type during migration can cost you rankings. Here is how each redirect type behaves and when you should reach for it.
| Redirect Type | Signal to Search Engines | Link Equity Transfer | Index Behaviour | Use During Migration? |
|---|---|---|---|---|
| 301 (Permanent) | Page has permanently moved | Yes (90-99%) | Old URL removed, new URL indexed | Yes |
| 302 (Temporary) | Page is temporarily elsewhere | Minimal — retained on old URL | Old URL kept in index | Almost never |
| 308 (Permanent, POST) | Same as 301, preserves HTTP method | Yes | Same as 301 | Rarely relevant |
| Meta Refresh | Client-side redirect, not recommended | Partial at best | Inconsistent indexing | Never |
| JavaScript Redirect | Often invisible to crawlers | Unreliable | Crawlers may not follow | Never |
301 Redirects (Permanent)
A 301 redirect tells search engines that a page has permanently moved to a new URL. This is the redirect type you should use for virtually every URL change during a migration. When Google encounters a 301 redirect, it transfers the vast majority of the original page’s link equity to the new URL, eventually removes the old URL from its index, and updates internal link references over time. The key word is “permanent.” A 301 redirect tells Google this change is final, so the search engine invests in updating its records.
302 Redirects (Temporary)
A 302 redirect tells search engines the move is temporary and the original URL may come back. During a migration, you should almost never use 302 redirects. Google keeps the original URL in its index, does not fully pass link equity to the new URL, and periodically checks whether the original URL is back. The only scenario where a 302 makes sense during migration is if you are temporarily redirecting traffic while a page is under construction and you genuinely plan to reinstate the original URL.
308 Redirects and Other Types
HubSpot’s redirect tool creates standard 301 redirects. You will not typically encounter 308 (permanent redirect for POST requests) or other redirect codes in a CMS migration context. Stick with 301 for everything unless you have a very specific technical reason not to.
The 302 Disaster: 40% Blog Traffic Loss
A single misconfigured redirect rule accidentally applied 302 redirects to an entire blog section. Search engines refused to consolidate ranking signals, leaving old URLs in the index while new pages sat in limbo. It took over three months to recover organic blog traffic to pre-migration levels.
The Homepage Funnel: Rankings Wiped Overnight
A team redirected 200+ unique pages to the homepage because they could not find matching equivalents on the new site. Google treated every redirect as a soft 404. Rankings for all 200 pages dropped out of the top 100 within two weeks, and the homepage itself saw a ranking penalty from the redirect abuse.
Auditing Your Current URL Structure
Before you create a single redirect, you need a complete inventory of every URL on your current HubSpot site.
Crawl Your Existing Site
Use a tool like Screaming Frog, Sitemap.xml analysis, or Ahrefs Site Audit to crawl your current site and build a complete URL list. You want to capture every URL that could receive external traffic or carry link equity.
- ✓All published website pages and their URLs
- ✓All published blog posts and their URLs
- ✓Landing pages (including ones used in past campaigns that may still receive traffic)
- ✓System pages (thank you pages, preference centre, password-protected pages)
- ✓PDF and file download URLs hosted in HubSpot's file manager
- ✓Any existing redirects already in place
- ✗Internal draft pages (do not redirect — they were never indexed)
- ✗Staging or preview URLs (these are not public)
Identify High-Value URLs
Not every URL carries equal weight. Prioritise your redirect mapping by traffic impact and link equity.
Organic Traffic Pages
Pages that receive organic search traffic need redirects mapped to the most relevant equivalent on the new site. Any error here has an immediate traffic impact.
Backlink Magnets
Pages with external backlinks carry link equity that you want to preserve. Use Ahrefs or Semrush to identify these pages and map them carefully.
Internal Link Hubs
Pages frequently linked to from other content on your site. Broken internal references create redirect chains across your own site.
Conversion Pages
Landing pages and form pages that drive leads. Even if organic traffic is low, these carry direct business value from paid and email campaigns.
Export your Google Search Console performance data and your backlink data from Ahrefs or Semrush. Cross-reference these with your URL inventory. Any page with meaningful traffic or backlinks must have a carefully mapped redirect.
For a complete pre-migration SEO checklist, see our HubSpot website migration checklist.
Using HubSpot’s URL Redirect Tool
HubSpot provides a built-in URL redirect manager that handles most redirect needs during a portal migration.
Access the Redirect Tool
Navigate to Settings > Website > Domains & URLs > URL Redirects in your HubSpot portal. This is where you create, manage, and bulk-import redirects.
Enter the Original URL
Specify the old URL path relative to the domain (e.g., /old-page-slug). Use relative paths, not full URLs, when the domain stays the same.
Set the Redirect Destination
Enter the new destination URL. This can be a relative path on the same domain or a full URL if you are changing domains.
Choose Redirect Type and Match Style
Select Standard (301) for permanent redirects. Choose Flexible match to handle trailing slashes, capitalisation, and query parameters automatically.
Save and Verify
Save the redirect, then test by visiting the old URL in a browser. Confirm the address bar updates to the new URL and the page loads correctly.
Flexible vs. Exact Matching
HubSpot offers two matching modes that determine how strictly the redirect URL is matched.
- Only redirects the precise URL entered
/old-pageredirects, but/old-page?utm_source=emaildoes not- Trailing slash variants may not match
- Use when you need surgical precision
- Redirects regardless of trailing slashes and capitalisation
/old-page,/old-page/, and/Old-Page?ref=123all redirect- Catches URL variations from search engines and external links
- Best choice for migrations — use this by default
Redirect Limitations in HubSpot
HubSpot's redirect tool only works for URLs on domains connected to the portal. You cannot redirect URLs on domains you do not control, regex-based redirects are not supported natively, and there is a soft limit of approximately 10,000 redirects (varies by plan). Redirect rules are processed in order, so conflicts between rules can produce unexpected behaviour.
Bulk Redirect Uploads
For any migration involving more than a handful of URL changes, manual redirect creation is impractical. HubSpot supports bulk redirect uploads via CSV.
Preparing Your Redirect CSV
Create a CSV file with two columns: the source URL path and the destination URL path.
- ✓Use relative paths where possible (e.g.,
/blog/old-postrather thanhttps://yourdomain.com/blog/old-post) - ✓Remove any trailing whitespace from all cells
- ✓Ensure no duplicate source URLs exist in the file
- ✓Verify that every destination URL actually exists and returns a 200 status code
- ✗Do not include header rows that HubSpot might interpret as a redirect entry
- ✗Do not mix full URLs and relative paths in the same column
Upload Process
Import Your CSV
In the URL Redirects tool, select the "Import" or "Upload" option. Choose your CSV file and HubSpot will process the redirects in bulk.
Review the Import Summary
Check for any errors or skipped entries in the import report. Common issues include duplicate source URLs, malformed paths, and character encoding problems.
Spot-Check a Sample
Visit a random sample of old URLs and confirm they redirect correctly. Test across page types — website pages, blog posts, and landing pages.
Verify No Dead Ends
Confirm that no redirects accidentally point to 404 pages. A redirect to a nonexistent page is worse than no redirect at all — it wastes the crawl budget and frustrates users.
Version Control Your Redirect Map
Treat your redirect mapping spreadsheet as a critical project document. Keep it version-controlled and accessible to everyone involved in the migration. You will reference it repeatedly during QA, post-launch troubleshooting, and SEO monitoring.
Avoiding Redirect Chains and Loops
Redirect chains and loops are two of the most damaging redirect errors, and they are surprisingly easy to create during a migration.
What Is a Redirect Chain?
A redirect chain occurs when URL A redirects to URL B, which redirects to URL C. Instead of one hop, the user and search engine crawlers must follow multiple redirects to reach the final destination.
Each additional hop in the chain dilutes link equity and increases page load time. Google has stated that it will follow redirect chains, but after 5-10 hops it stops following and treats the URL as an error.
How Chains Form During Migration
Chains are most common when you are migrating a site that has been migrated before. The original redirects from the first migration still exist, and your new redirects create an additional hop.
The Double Migration Chain
In 2023, /about-us was redirected to /company/about. In the 2026 migration, /company/about moves to /about. Anyone visiting /about-us now follows a three-hop chain: /about-us → /company/about → /about. Link equity is diluted at every hop.
Preventing Chains
Before creating your new redirect map, export all existing redirects from the source portal. Cross-reference your new redirects against the existing ones and collapse any chains. Every redirect should go directly from the original URL to the final destination URL, with no intermediate hops.
/about-us→/company/about/company/about→/about- 2 hops, equity dilution at each step
/about-us→/about/company/about→/about- 1 hop each, maximum equity preserved
Redirect Loops
A redirect loop occurs when URL A redirects to URL B and URL B redirects back to URL A. The browser bounces back and forth until it gives up and shows an error. Loops can be hidden in longer chains where the loop is three or four hops deep.
Test every redirect after implementation. Automated tools like Screaming Frog can crawl your redirect map and flag chains and loops before you go live. A single undetected loop can make an entire section of your site inaccessible.
Testing Methodology
Thorough testing is the difference between a migration that preserves rankings and one that tanks them.
Pre-Launch Testing
- ✓Crawl the redirect map — Use Screaming Frog or a similar tool to follow every redirect and verify the final destination returns a 200 status code
- ✓Check for chains — Ensure no redirect requires more than one hop to reach the destination
- ✓Check for loops — Flag any circular redirect patterns
- ✓Verify high-priority pages — Manually check your top 20-50 most-trafficked pages to confirm correct redirect destinations
- ✓Test with query parameters — Verify that URLs with UTM parameters and other query strings redirect correctly
Post-Launch Testing
On launch day, immediately verify the following across all content types — pages, blog posts, and landing pages:
- ✓A sample of redirects across all content types works correctly
- ✓XML sitemap has been updated with new URLs and submitted to Google Search Console
- ✓Internal links across the site point to final destination URLs (not URLs requiring a redirect)
- ✓Canonical tags reference the correct new URLs
Ongoing Monitoring
For the first 30 days after launch, maintain continuous monitoring of redirect health.
30-Day Monitoring Dashboard
Track Google Search Console's coverage report for new crawl errors, 404 error reports in both HubSpot and Search Console, and redirect-related warnings. Any new 404 errors appearing after migration indicate URLs that need redirects you missed.
Monitoring Organic Traffic Post-Migration
Even a well-executed migration with perfect redirects will see some temporary fluctuation in organic traffic. The key is distinguishing normal volatility from a redirect-related problem.
Establish Your Baseline
Before migration, document your organic traffic metrics so you have a clear point of comparison.
Organic Sessions
Total organic sessions per week from Google Analytics. Record at least 4 weeks of data before migration to account for natural variance.
Landing Page Performance
Organic landing page performance for your top 50 pages. These are the first pages to check if traffic drops post-migration.
Keyword Rankings
Rankings for your target terms from Search Console or a rank tracking tool. Capture positions for at least your top 100 keywords.
Crawl Stats
Pages crawled per day and crawl errors from Google Search Console. A healthy baseline helps you spot post-migration crawl budget issues quickly.
What to Expect Post-Migration
A clean migration with proper redirects typically follows a predictable recovery timeline.
| Timeframe | Expected Behaviour | Action Required |
|---|---|---|
| Week 1-2 | 10-20% organic traffic fluctuation as Google processes redirects | Monitor daily, do not panic |
| Week 3-4 | Traffic stabilising, potentially still below pre-migration levels | Investigate if drop exceeds 30% |
| Week 5-8 | Full recovery, sometimes with improvements if new site architecture is better | Shift to monthly monitoring |
| Beyond 8 weeks | Traffic should meet or exceed pre-migration levels | Investigate persistent drops immediately |
If you see a drop of more than 30% that does not recover within two weeks, investigate immediately. Common causes: missing redirects for high-traffic pages, redirect chains diluting link equity, canonical tag issues, robots.txt accidentally blocking important pages, or XML sitemap not updated.
Recovery Actions
If organic traffic drops significantly, work through these steps in order:
Check Google Search Console
Review crawl errors and fix them immediately. New 404s and server errors indicate missed redirects or broken pages.
Verify Key Pages Are Indexed
Search site:yourdomain.com/page-slug for your most important pages to confirm they appear in Google's index.
Review Your Redirect Map
Look for missing entries, especially for pages that had high traffic or strong backlink profiles before migration.
Check for Accidental Noindex Tags
Migrated pages sometimes inherit noindex directives from staging environments. Verify the robots meta tag on every template.
Submit Updated Sitemap
Submit an updated sitemap through Search Console and request indexing for key pages to accelerate Google's processing.
For comprehensive post-migration SEO monitoring, a professional SEO audit can identify issues that manual checks might miss.
Common SEO Pitfalls During HubSpot Migration
Over hundreds of migrations, we have seen the same mistakes repeated. Here are the ones that cause the most damage.
Redirecting Everything to the Homepage
When teams cannot find a clear equivalent for an old page, they default to redirecting it to the homepage. Google recognises this as a "soft 404" and may treat the redirect as if the page simply disappeared. Worse, it signals to Google that your redirects are low quality. If a page has no equivalent on the new site, redirect to a closely related category page, or accept the 404 if the page had minimal traffic and backlinks.
Forgetting Blog Pagination and Tag Pages
HubSpot blogs generate pagination URLs (/blog/page/2, /blog/page/3) and tag listing pages (/blog/tag/hubspot). These pages often accumulate backlinks and traffic. If your new blog structure changes these URLs, you need redirects for them.
Ignoring File and Image URLs
PDFs, images, and downloadable files hosted in HubSpot's file manager have URLs that may be linked to from external sites. If you are changing domains or file structures, these URLs need redirects too.
Not Updating Internal Links
Redirects are a safety net for external links and search engines, but your own internal links should point directly to the final destination URLs. Every internal link that goes through a redirect is a wasted server round-trip and a tiny bit of lost link equity. After migration, crawl your site and update any internal links that still point to old URLs.
Removing Redirects Too Soon
Some teams remove redirects after a few months, assuming Google has updated its index. External backlinks pointing to old URLs will break the moment you remove the redirect. Google recommends keeping redirects in place for at least one year, and ideally indefinitely.
Our complete HubSpot-to-HubSpot migration guide covers these pitfalls in the broader context of a full portal migration.
Building Your Redirect Map: A Practical Framework
Here is a step-by-step framework for building a migration redirect map that protects your SEO.
Export All URLs
Crawl your current site and export every URL. Include pages, blog posts, landing pages, system pages, and file URLs. This is your complete URL inventory.
Export Existing Redirects
Pull all existing redirects from your current HubSpot portal. These will need to be updated to point to final destination URLs in the new structure.
Map Old URLs to New URLs
Create a spreadsheet with columns for: Old URL, New URL, Page type, Priority (based on traffic and backlinks), and Status (mapped, no equivalent, merged).
Handle URLs with No Equivalent
For pages that will not exist on the new site, decide: redirect to a closely related page, create a new page as a redirect target, or accept the 404 (only for pages with no traffic and no backlinks).
Collapse Existing Redirect Chains
For every URL that already has a redirect in the source portal, ensure your new redirect goes directly from the earliest URL in the chain to the final destination. No intermediate hops.
Implement and Test
Upload your redirect map to the destination portal, then run through the testing methodology described in this guide. Verify every redirect before go-live.
For teams dealing with large-scale migrations involving hundreds or thousands of URLs, Jetstack's migration services include automated redirect mapping and validation tools that catch errors before they impact your traffic.
FAQ
How many 301 redirects can I have in HubSpot?
HubSpot does not publish a hard limit, but portals typically support up to 10,000 URL redirects. For enterprise portals with larger needs, HubSpot’s support team can discuss limit increases. If you are approaching the limit, audit your existing redirects and remove any that point to pages that no longer receive traffic or have no external backlinks.
How long do 301 redirects take to be processed by Google?
Google typically processes 301 redirects within days to weeks, depending on how frequently Googlebot crawls your site. High-authority pages with regular crawl activity are processed faster. Low-traffic pages may take several weeks. You can accelerate the process by submitting an updated sitemap through Google Search Console.
Should I redirect HTTP URLs to HTTPS during migration?
Yes. If your old site had any HTTP URLs (or if external links reference HTTP versions), ensure your redirect map covers both HTTP and HTTPS variants. HubSpot enforces HTTPS by default, so any HTTP request to your domain should redirect to the HTTPS equivalent before any page-level redirect is applied.
Can I use wildcard or regex redirects in HubSpot?
HubSpot’s native redirect tool does not support regex patterns. Each redirect must be created individually or uploaded via CSV. If you need pattern-based redirects (e.g., redirecting an entire blog folder from /news/* to /blog/*), you will need to enumerate every URL individually or implement the pattern redirect at the DNS or CDN level.
What happens to my Google Search Console data after migration?
If your domain stays the same, your Search Console data continues accumulating in the same property. If you are changing domains, you need to use the Change of Address tool in Search Console to notify Google. Add and verify the new domain in Search Console, then submit the change of address request from the old property.
How do I handle URL parameters like UTM codes during redirects?
With HubSpot’s flexible match option enabled, redirects will work regardless of query parameters. The parameters are typically passed through to the destination URL. However, test this explicitly with your most common UTM parameter combinations to ensure they pass through correctly.