A HubSpot CMS migration that ignores SEO is a migration that destroys organic traffic. It happens more often than anyone in the industry wants to admit: a team moves their website pages to a new HubSpot portal, skips the redirect mapping, and watches months or years of search engine equity evaporate within weeks.
This checklist exists to prevent that outcome. Every step in this guide is designed to preserve the organic traffic you have worked to build, while giving you a clean, well-organized website in the destination portal. Whether you are migrating between HubSpot portals, moving from HubSpot CMS to another platform, or consolidating multiple HubSpot websites into one, the SEO principles are identical.
Pre-Migration: The URL Audit
Before touching a single page, you need a complete picture of what exists and what matters.
Crawl the Existing Site
Use a site crawler like Screaming Frog, Sitemap.xml, or Ahrefs Site Audit to generate a complete inventory of every URL on the current HubSpot website.
- ✓Website pages — all published pages and their full URL paths
- ✓Landing pages — including legacy campaign pages that may still receive traffic
- ✓Blog posts and blog listing pages (including pagination URLs)
- ✓System pages — 404, password prompt, subscription preferences
- ✓PDF and file URLs hosted in HubSpot's file manager
- ✓Image URLs referenced in content and templates
Export this to a spreadsheet. This becomes your master URL inventory.
Identify High-Value Pages
Not every page carries the same SEO weight. Use Google Analytics and Google Search Console to identify the pages that matter most.
Top Organic Traffic Pages
These are your priority. Any redirect error on these pages has an immediate traffic impact. Export Search Console performance data sorted by clicks.
Pages with Backlinks
Use Ahrefs, Moz, or SEMrush to find pages that external sites link to. These carry link equity that must be preserved through accurate 301 redirects.
Keyword-Ranking Pages
Cross-reference your keyword targets with the pages that rank for them. These pages need perfect redirect mapping to preserve position.
Zero-Traffic, Zero-Backlink Pages
These are candidates for retirement. Not every page needs to migrate. Letting these 404 is acceptable if they carry no external value.
Document the Current URL Structure
Map the URL hierarchy of the current site. Note the patterns used for different content types.
| Content Type | Common URL Pattern | Example | Check For |
|---|---|---|---|
| Blog posts | /blog/post-slug | /blog/hubspot-tips | Pagination, tag pages, author pages |
| Blog (alternate) | /resources/blog/post-slug | /resources/blog/migration-guide | Subdirectory depth changes |
| Landing pages | /offers/ebook-name | /offers/crm-guide-2026 | Campaign-specific UTM parameters |
| Landing pages (alternate) | /lp/campaign-name | /lp/spring-promo | Paid ad destination URLs |
| Website pages | /page-slug | /about, /pricing | Nested paths like /company/about |
| Subdomain blogs | blog.company.com | blog.company.com/post | Requires DNS-level redirects |
Understanding the current structure is essential for planning the destination URL structure and identifying which URLs will change.
Redirect Strategy: The 301 Redirect Map
A 301 redirect tells search engines that a page has permanently moved to a new URL. It transfers approximately 90-99% of the original page’s link equity to the destination URL. Every URL that changes during migration needs a 301 redirect.
Building the Redirect Map
Create a spreadsheet with three columns mapping every URL change.
| Old URL | New URL | Priority |
|---|---|---|
| /blog/hubspot-tips | /resources/blog/hubspot-tips | High |
| /pricing | /products/pricing | Medium |
| /old-landing-page | (retired — redirect to closest equivalent) | Low |
Map One-to-One Redirects
Each old URL should point to the most relevant new URL. Avoid redirecting everything to the homepage — search engines treat this as a soft 404 and you will lose rankings for every affected page.
Preserve URL Slugs Where Possible
If the old URL was /blog/migration-guide and the new URL can be /blog/migration-guide, no redirect is needed. Fewer redirects means fewer potential failure points.
Handle Retired Pages
If a page is not migrating, redirect it to the closest topically relevant page that is migrating. Never redirect retired pages to the homepage unless they are genuinely homepage-level content.
Test Trailing Slash Variants
HubSpot handles trailing slashes differently depending on configuration. Test both /page and /page/ to ensure redirects work for both variants.
Chain and Loop Prevention
Redirect chains occur when URL A redirects to URL B, which redirects to URL C. Each hop dilutes link equity and increases page load time. Redirect loops (A → B → A) create infinite loops and completely break page access. Before implementing your redirect map, export existing redirects from the source portal and collapse all chains into single-hop redirects.
Subdomain Redirects
If your migration involves a subdomain change (e.g., moving from blog.company.com to company.com/blog), you need DNS-level or server-level redirects in addition to HubSpot’s URL redirect tool. HubSpot’s built-in redirects only work within the same domain.
Implementing Redirects in HubSpot
HubSpot provides a built-in URL redirect tool under Settings > Website > Domains & URLs > URL Redirects. This tool handles redirects for pages hosted on HubSpot CMS.
Individual Redirects
For small migration projects (under 100 URLs), adding redirects one at a time through the HubSpot UI is straightforward. Enter the original URL path, the redirect destination, and confirm the redirect type is 301 (permanent).
Bulk Redirect Upload
For larger migrations, HubSpot supports CSV upload for redirects. Format your CSV with two columns: the original URL and the redirect target. Upload through the URL Redirects settings page.
Redirects are path-based, not full-URL based — you enter /old-path, not https://domain.com/old-path. Query parameters are not preserved by default. HubSpot redirects only apply to domains connected to that portal, so cross-domain redirects require external handling.
Flexible Redirects
HubSpot’s flexible redirect option lets you create pattern-based redirects using a wildcard. For example, redirecting /blog/old-category/:slug to /blog/new-category/:slug handles an entire category change with a single rule. Use these sparingly and test thoroughly, as overly broad patterns can create unintended redirects.
Meta Data Migration
SEO is not just about URLs. The meta data associated with each page directly affects click-through rates from search results.
| Meta Element | Where to Find in HubSpot | Migration Method | Impact if Missed |
|---|---|---|---|
| Title Tags | Page editor > Settings > SEO title | Export via API or manual copy | Rankings drop, CTR drops |
| Meta Descriptions | Page editor > Settings > Meta description | Export via API or manual copy | CTR drops in SERPs |
| Canonical Tags | Auto-generated or custom override | Verify after migration | Duplicate content issues |
| Open Graph Tags | Page editor > Social section | Manual transfer | Broken social sharing previews |
| Structured Data | Template-level JSON-LD markup | Recreate in destination templates | Rich snippet loss in SERPs |
Title Tags
Export every page’s title tag from the source portal and apply them to the corresponding pages in the destination portal. HubSpot stores the SEO title separately from the page title — ensure you are mapping the SEO title, not just the page heading.
Meta Descriptions
Similarly, export and reapply meta descriptions. These appear in search result snippets and influence click-through rates. HubSpot allows meta descriptions at the page level in the page editor’s Settings tab.
Canonical Tags
Verify that canonical tags on migrated pages point to the correct new URLs. HubSpot automatically generates canonical tags based on the published URL, but if you have custom canonical overrides in the source portal, those need to be manually transferred.
Open Graph titles, descriptions, and images for social sharing need to be migrated from the Social section of each page's settings. If the source site uses structured data (JSON-LD schema markup) in templates or modules, ensure this is recreated in the destination portal. Common types include Organization, FAQ, Article, and BreadcrumbList schemas.
Blog Migration: Special Considerations
Blog content has additional SEO considerations beyond standard website pages.
Blog URL Structure
HubSpot blogs can be configured with different URL structures. If the URL structure changes during migration, every blog post URL needs a redirect.
Standard Blog Path
domain.com/blog/post-slug — The most common default HubSpot blog URL structure.
Category-Based Path
domain.com/blog/category/post-slug — Adds a category subfolder, increasing redirect complexity.
Custom Path
domain.com/resources/insights/post-slug — Custom structures require careful one-to-one mapping.
If you are migrating hundreds of posts with a URL structure change, this is the single largest redirect mapping exercise in the project.
Author Pages and Tag Pages
HubSpot generates author pages (/blog/author/name) and tag pages (/blog/tag/topic) automatically. If these pages have been indexed by search engines, they need redirects too. Many teams overlook these because they are auto-generated rather than manually created.
- ✓Redirect blog author pages to new author page URLs
- ✓Redirect blog tag listing pages to new tag URLs
- ✓Update RSS feed URL in any external syndication services
- ✓Verify new blog listing page generates proper pagination URLs
- ✗Do not redirect old pagination URLs (e.g.,
/blog/page/2) — these are dynamic and will regenerate
Testing Redirects Before Go-Live
Never assume redirects work because they look correct in a spreadsheet. Test every redirect.
Manual Spot-Checking
For high-priority pages, manually enter the old URL in a browser and verify you land on the correct new page. Check that the browser address bar shows the new URL (not a temporary redirect that preserves the old URL).
Automated Redirect Verification
For large redirect sets, use a tool like Screaming Frog’s list mode or a simple script to test every redirect in your map.
- ✓200 response on the final destination (the page loads correctly)
- ✓301 response on the redirect (not 302, which is temporary)
- ✓No redirect chains (single hop from old URL to new URL)
- ✓No redirect loops (infinite redirects)
- ✓No 404s on the destination URL (the page actually exists)
- ✓Mobile testing — verify redirects on mobile devices and user agents
We have seen teams implement 500+ redirects and skip testing entirely. Invariably, a formatting error in the CSV upload causes dozens of broken redirects that are not caught until organic traffic drops two weeks later. Testing is not optional.
Post-Migration SEO Monitoring
The work does not end at go-live. SEO impact from a migration takes two to eight weeks to fully manifest, and monitoring during this period is critical.
Google Search Console Validation
Submit the New Sitemap
If your sitemap URL has changed, submit the new one in Google Search Console and remove the old one. Do this within 24 hours of go-live.
Request Indexing for Key Pages
Use the URL Inspection tool to request indexing for high-priority pages that have new URLs. This accelerates Google's processing.
Monitor the Coverage Report Daily
Check daily for new 404 errors, crawl anomalies, and redirect issues. Every new 404 indicates a missing redirect that needs to be added.
Inspect Key Pages
Use the URL Inspection tool for key pages to verify Google is seeing the correct URL, canonical, and indexing status.
Monitor for 404 Errors
A spike in 404 errors in the first week after migration is normal — not every URL can be anticipated in advance. What matters is that you catch and fix them quickly. Prioritise fixes based on the traffic and backlink profile of the affected pages.
Track Organic Traffic
Compare organic traffic week-over-week and month-over-month in Google Analytics. It is normal to see a temporary dip in the first two to four weeks as search engines process the redirects and re-evaluate the content. If the dip exceeds 30% or does not recover within six weeks, investigate.
Monitor Keyword Rankings and Backlinks
Track rankings for your target keywords daily during the first month post-migration. Tools like Ahrefs, SEMrush, or Google Search Console’s Performance report show ranking changes. Minor fluctuations are expected; significant drops indicate a redirect or technical SEO issue.
Check that your high-value backlinks are now pointing to (or properly redirecting to) the correct pages on the new site. Use Ahrefs or Moz to compare backlink profiles before and after migration. Broken backlinks represent lost authority that can take months to rebuild.
Common SEO Mistakes During HubSpot Migrations
These are the errors we see most frequently when reviewing post-migration sites.
- Redirecting everything to the homepage (soft 404)
- Missing blog author and tag page redirects
- Ignoring image and file URLs from file manager
- Not updating internal links after migration
- Skipping the testing phase entirely
- Map each page to the most topically relevant equivalent
- Include auto-generated blog pages in redirect map
- Redirect file manager URLs or keep files at same paths
- Crawl post-migration and update all internal links
- Test every redirect before go-live — no exceptions
Working With Jetstack on CMS Migrations
Jetstack’s implementation services include comprehensive CMS migration support with an SEO-first methodology. Our process includes automated URL auditing, redirect map generation, meta data extraction, and post-migration monitoring dashboards.
End-to-End Migration Support
For the broader portal migration context, including data and workflow migration alongside CMS, see our complete HubSpot-to-HubSpot migration guide. For a technical deep dive on moving CMS pages specifically, our guide to migrating HubSpot CMS pages between portals covers the template and module layer.
Ready to migrate your HubSpot website without risking your SEO? Contact our team to discuss your project.
Frequently Asked Questions
How long do 301 redirects take to be recognized by Google?
Google typically discovers and processes 301 redirects within a few days of crawling the redirected URL. However, the full impact on rankings can take two to eight weeks as Google re-evaluates the content at the new URL. High-authority pages are crawled more frequently and tend to be processed faster.
Should I use 301 or 302 redirects during a HubSpot migration?
Use 301 (permanent) redirects for any URL that has permanently changed. 302 (temporary) redirects tell search engines to keep the original URL in the index, which defeats the purpose of a migration. The only scenario for 302 redirects is during a testing phase where you plan to revert the change.
How many redirects can HubSpot handle?
HubSpot does not publish a hard limit on the number of URL redirects, but performance can degrade with extremely large redirect lists (10,000+). For most migrations, the redirect volume is well within HubSpot’s capabilities. If you need to manage a very large redirect set, consider consolidating pattern-based redirects using HubSpot’s flexible redirect feature.
Will my Google Ads and social media links break after migration?
Any link pointing to an old URL will follow the 301 redirect to the new URL. This means Google Ads, social media posts, email links, and any other external references will continue to work. However, you should update the links in active ad campaigns and social profiles to point directly to the new URLs to avoid redirect latency.
What happens to HubSpot tracking URLs and UTM parameters after migration?
HubSpot tracking URLs and UTM parameters are typically preserved through 301 redirects, but this depends on your redirect configuration. Test a sample of tracking URLs with UTM parameters to verify they pass through correctly. If parameters are being stripped, you may need to adjust your redirect rules.
Can I undo a redirect if something goes wrong?
Yes. HubSpot URL redirects can be deleted at any time through the URL Redirects settings page. Removing a redirect restores the original URL path behavior. However, if search engines have already processed the redirect and updated their index, it may take several weeks for the original URL to be re-indexed.