# How to Migrate from WordPress to HubSpot CMS Without Losing SEO Rankings in 2026 ## Table of Contents - [Introduction](#introduction) - [Why CMS Migrations Lose SEO Rankings](#why-cms-migrations-lose-seo-rankings) - [Phase 1: Pre-Migration SEO Audit](#phase-1-pre-migration-seo-audit) - [Phase 2: URL Architecture Planning](#phase-2-url-architecture-planning) - [Phase 3: Content Migration to HubSpot CMS](#phase-3-content-migration-to-hubspot-cms) - [Phase 4: SEO Configuration in HubSpot CMS](#phase-4-seo-configuration-in-hubspot-cms) - [Phase 5: Implementing 301 Redirects](#phase-5-implementing-301-redirects) - [Phase 6: Launch and Post-Migration Monitoring](#phase-6-launch-and-post-migration-monitoring) - [Most Common Mistakes in WordPress → HubSpot Migrations](#most-common-mistakes-in-wordpress--hubspot-migrations) - [Frequently Asked Questions](#frequently-asked-questions) - [Conclusion](#conclusion) - [References](#references) --- ## Introduction Migrating a website from WordPress to HubSpot CMS is a strategic decision that more and more B2B companies are making in 2026, driven by the need to integrate their website with the HubSpot CRM and take advantage of the content personalisation and revenue attribution capabilities the platform offers. However, a poorly executed migration can result in significant losses in organic rankings, traffic and leads. The fear of losing SEO is, rightly, one of the main barriers to CMS migrations. Google takes weeks or months to fully process changes to a website, and during that period it is normal to observe fluctuations in rankings. The difference between a successful migration (which maintains or improves SEO) and a disastrous one (which causes drops of 30–50% in organic traffic) lies in planning and technical execution. This guide covers the complete process of migrating from WordPress to HubSpot CMS from an SEO perspective: from the pre-migration audit to post-launch monitoring, including URL planning, content migration, SEO configuration in HubSpot and redirect implementation. It is based on Emovere's experience across more than 40 WordPress-to-HubSpot CMS migration projects. --- ## Why CMS Migrations Lose SEO Rankings Before diving into the migration process, it is important to understand why CMS migrations can cause ranking losses. The most frequent causes are: **URL changes without redirects:** If site URLs change during migration (for example, from `/blog/article-1/` to `/article-1`) without 301 redirects, Google loses track of the pages and backlinks point to non-existent URLs. This can result in losses of domain authority and rankings. **Loss of SEO metadata:** Page titles, meta descriptions, image alt texts and structured data (schema markup) must be migrated alongside the content. If these metadata elements are lost during migration, pages lose important SEO signals. **Changes to internal linking structure:** Internal linking is a relevant SEO factor. If internal links break or are modified during migration, the distribution of the site's internal PageRank changes, which can affect the rankings of individual pages. **Performance degradation:** If the new HubSpot CMS site has worse Core Web Vitals than the original WordPress site, Google may penalise the rankings of affected pages. **Content changes:** Modifying page content during migration (even with the intention of improving it) can cause ranking fluctuations. The ideal approach is to migrate content exactly as it is and make content optimisations in a later phase. **Indexation problems:** If the HubSpot CMS site is not correctly configured for indexation (XML sitemap, robots.txt, canonical tags) before launch, Google may take longer to index the migrated pages. --- ## Phase 1: Pre-Migration SEO Audit ### Complete WordPress Site Inventory The first step of any migration is to create a complete inventory of the WordPress site: all indexed URLs, their SEO metadata, their backlinks and their performance metrics. This inventory is the baseline against which the success of the migration will be measured. The recommended tools for the inventory are: **Screaming Frog SEO Spider:** Crawls all URLs on the WordPress site and exports a complete list with URL, title, meta description, H1, response code, canonical, hreflang and other SEO metadata. It is the most comprehensive tool for technical inventory. **Google Search Console:** Exports the URLs indexed by Google, search performance data (impressions, clicks, average position by URL and keyword) and indexation errors. This data is essential for prioritising which pages are most important for SEO. **Ahrefs / SEMrush:** Exports the site's backlink profile (which external URLs link to which pages on the site) and the keywords each page ranks for. This information is critical for ensuring that pages with the most backlinks and best rankings are migrated correctly. ### Page Categorisation Once the inventory is complete, pages must be categorised according to their SEO importance: **Critical pages (Tier 1):** The 20–50 pages with the most organic traffic, the most backlinks or the best rankings for strategic keywords. These pages must be migrated with maximum attention to detail and verified individually after migration. **Important pages (Tier 2):** Pages with moderate organic traffic or medium-quality backlinks. These must be migrated correctly but can be verified more quickly. **Low-value pages (Tier 3):** Pages with little or no organic traffic, without relevant backlinks and with low-quality content. These pages can be migrated, redirected to more relevant pages, or simply not migrated (if the content adds no value). **Pages to delete:** Duplicate pages, thin-content pages (fewer than 300 words with no added value), empty WordPress category pages and WordPress tag pages that have no organic traffic. These pages can be removed during migration, with 301 redirects to the most relevant pages. --- ## Phase 2: URL Architecture Planning ### Principles for URL Planning in HubSpot CMS URL architecture is one of the most important SEO factors and one of the hardest to change after migration. The basic principles for good URL architecture are: - **Short, descriptive URLs:** URLs should be short, descriptive and contain the page's primary keyword. - **Clear hierarchical structure:** The folder structure of URLs should reflect the content hierarchy of the site. - **No URL parameters:** URLs should be clean, without query string parameters (`?id=123&cat=5`). - **No dates in blog URLs:** Blog article URLs should not include the publication date, as this makes it difficult to update content without changing the URL. ### Decision: Keep or Change URLs The most important decision in URL architecture planning is whether to keep the existing WordPress URLs or change them in HubSpot CMS. **Keep URLs (recommended in most cases):** If WordPress URLs are already short, descriptive and without dates, the safest approach is to keep them exactly the same in HubSpot CMS. This eliminates the need for 301 redirects and ensures that existing backlinks continue to point to valid URLs. **Change URLs (only if necessary):** If WordPress URLs have structural problems (dates in blog URLs, query string parameters, very long slugs), it may make sense to change them during migration. However, this change must be made with correct 301 redirects for each URL that changes. ### URL Mapping: WordPress → HubSpot CMS URL mapping is a document that relates each WordPress URL to its equivalent in HubSpot CMS. This document is the basis for implementing 301 redirects and must be completed before starting content migration. The recommended format for URL mapping is a spreadsheet with the following columns: | WordPress URL (source) | HubSpot URL (destination) | Type | Priority | Status | |---|---|---|---|---| | /blog/article-1/ | /blog/article-1 | 301 | Tier 1 | Pending | | /services/consulting/ | /services/consulting | Keep | Tier 1 | Pending | | /about-us/ | /company | 301 | Tier 2 | Pending | | /tag/hubspot/ | /blog (redirect) | 301 | Tier 3 | Pending | --- ## Phase 3: Content Migration to HubSpot CMS ### Content Migration Tools HubSpot does not offer a native content import tool from WordPress, so content migration must be done manually or through third-party tools. **HubSpot Import Tool (for blogs):** HubSpot offers a blog article import tool in CSV format. The CSV must include the fields: title, article body (HTML), meta description, article URL, publication date, author and categories. This tool is suitable for blog migrations with many articles (more than 50). **Manual migration (for site pages):** Site pages (homepage, service pages, contact pages) must be migrated manually, recreating the design in the HubSpot editor and copying the content. This process is more labour-intensive but allows content to be reviewed and improved during migration. **Custom migration scripts:** For sites with large volumes of content (more than 500 pages), it may be necessary to develop custom scripts that use the WordPress API to export content and the HubSpot API to import it. This approach requires technical knowledge but allows much of the process to be automated. ### SEO Metadata Migration Migrating SEO metadata is as important as migrating content. For each migrated page, it is necessary to verify and configure in HubSpot CMS: - **Page title (SEO title):** Must be identical to that of the WordPress site, unless there are specific reasons to change it. - **Meta description:** Must be identical to that of the WordPress site. - **Canonical URL:** HubSpot CMS automatically manages canonical tags, but it is necessary to verify that they point to the correct URL. - **Image alt text:** Must be migrated along with the images. - **Structured data (schema markup):** HubSpot CMS automatically implements basic schema markup (Article, BreadcrumbList, WebSite), but if the WordPress site had custom schema markup (FAQ, HowTo, Product), it must be implemented manually in HubSpot. ### Image Migration WordPress site images must be uploaded to the HubSpot File Manager before migrating content. The recommended process is: 1. Export all images from the WordPress site (from the `wp-content/uploads/` directory). 2. Upload images to the HubSpot File Manager, maintaining the folder structure. 3. Update image references in the migrated content to point to the new HubSpot File Manager URLs. An important point to note is that image URLs change during migration (from `domain.com/wp-content/uploads/2023/01/image.jpg` to `f.hubspotusercontent.com/...`). This does not affect the SEO of pages, but it can affect backlinks that point directly to site images. --- ## Phase 4: SEO Configuration in HubSpot CMS ### XML Sitemap Configuration HubSpot CMS automatically generates an XML sitemap for the site, accessible at `/sitemap.xml`. The sitemap includes all published pages on the site, with last modification dates and indexation priorities. To verify that the sitemap is correctly configured: 1. Access `https://yourdomain.com/sitemap.xml` and verify that it includes all important pages on the site. 2. Submit the sitemap to Google Search Console (Sitemaps → Add new sitemap). 3. Verify that there are no errors in the sitemap (URLs with 404 errors, URLs blocked by robots.txt). ### Robots.txt Configuration HubSpot CMS allows the `robots.txt` file to be customised from the portal settings (Settings → Website → Pages → Robots.txt). HubSpot's default `robots.txt` allows indexation of all pages on the site, but it may be necessary to add specific rules to block indexation of staging pages, test pages or sections of the site that should not be indexed. ### Hreflang Tags for Multilingual Sites If the WordPress site had content in multiple languages with hreflang tags, it is necessary to configure hreflang tags in HubSpot CMS after migration. HubSpot Content Hub automatically manages hreflang tags for content with language variants created on the platform. ### Structured Data Verification HubSpot CMS automatically implements the following types of structured data: - **WebSite:** On the homepage, with the site search field. - **Article:** On blog articles, with author, publication date and image fields. - **BreadcrumbList:** On pages with breadcrumbs enabled. To verify that structured data is correctly implemented, Google's Rich Results Test tool (search.google.com/test/rich-results) can be used on migrated pages. --- ## Phase 5: Implementing 301 Redirects ### Redirects in HubSpot CMS HubSpot CMS includes an integrated redirect management tool (Settings → Website → Pages → URL Redirects). This tool allows individual 301 redirects to be created or imported in bulk from a CSV file. To import redirects in bulk: 1. Prepare a CSV file with two columns: source URL and destination URL. 2. In HubSpot, go to Settings → Website → Pages → URL Redirects → Import. 3. Upload the CSV file and verify that the redirects have been created correctly. ### Redirect Verification After implementing redirects, it is necessary to verify that they work correctly. The recommended tools are: **Screaming Frog SEO Spider:** Can crawl the WordPress site (before launch, using the exported URL file) and verify that all URLs redirect correctly to their HubSpot CMS equivalents. **Redirect Checker (httpstatus.io):** Allows individual redirects to be verified, showing the complete redirect chain and the final response code. **Google Search Console:** After launch, Search Console shows coverage errors (URLs with 404 errors, URLs blocked by robots.txt) that may indicate missing or incorrect redirects. ### Redirect Chains A common mistake in migrations is creating redirect chains (A → B → C) instead of direct redirects (A → C). Redirect chains are less efficient (each additional hop adds latency) and can cause PageRank loss. If the WordPress site already had existing redirects, it is necessary to "flatten" the redirect chains when creating new redirects in HubSpot CMS. --- ## Phase 6: Launch and Post-Migration Monitoring ### Launch Checklist Before making the DNS change and launching the site on HubSpot CMS, verify: - [ ] All Tier 1 pages are migrated and individually verified - [ ] All SEO metadata (titles, meta descriptions, alt texts) is migrated - [ ] The XML sitemap is generated and accessible - [ ] The robots.txt is correctly configured - [ ] All 301 redirects are implemented and verified - [ ] Structured data is correctly implemented - [ ] Core Web Vitals of the new site are equal to or better than those of the WordPress site - [ ] The SSL certificate is active on the custom domain - [ ] Google Analytics and Google Search Console are configured on the new site - [ ] The HubSpot tracking code is active on all pages ### Post-Launch Monitoring During the first 4–8 weeks after launch, it is necessary to actively monitor the site's SEO performance to detect and correct problems quickly. **Metrics to monitor:** - **Organic traffic (Google Analytics):** Compare organic traffic week by week with the equivalent period from the previous year. A drop of 10–15% in the first weeks is normal; a drop of more than 20% requires investigation. - **Indexation coverage (Google Search Console):** Verify that Google is correctly indexing the pages of the new site and that there are no coverage errors. - **Search performance (Google Search Console):** Monitor impressions, clicks and average position for the most important keywords. - **404 errors (Google Search Console):** Verify that there are no URLs with 404 errors that should have redirects. - **Core Web Vitals (Google Search Console):** Verify that the Core Web Vitals of the new site are in the "Good" range. --- ## Most Common Mistakes in WordPress → HubSpot Migrations Based on our experience across more than 40 migration projects, these are the most frequent mistakes and how to avoid them: **Mistake 1: Launching without complete redirects.** The most costly mistake in SEO terms. Solution: complete the URL mapping before starting migration and verify all redirects before launch. **Mistake 2: Changing content during migration.** Modifying page content during migration makes it impossible to know whether ranking fluctuations are due to the migration or to content changes. Solution: migrate content exactly as it is and make content optimisations in a later phase. **Mistake 3: Not migrating low-traffic pages.** Although low-traffic pages do not generate much direct traffic, they may have quality backlinks that contribute to domain authority. Solution: migrate all pages with backlinks, regardless of their traffic. **Mistake 4: Ignoring WordPress category and tag pages.** WordPress category and tag pages can have their own organic traffic. Solution: check in Google Search Console whether these pages have traffic and, if they do, create equivalent pages in HubSpot or redirect them to relevant pages. **Mistake 5: Not verifying performance before launch.** If the new HubSpot CMS site has worse Core Web Vitals than the WordPress site, the launch may cause ranking losses. Solution: run performance tests on the staging site before launch and optimise until the same or better results than the WordPress site are achieved. --- ## Frequently Asked Questions **How long does it take Google to recover rankings after a migration from WordPress to HubSpot CMS?** The ranking recovery time after a well-executed migration is generally 4 to 12 weeks. During the first 2–4 weeks, it is normal to observe ranking fluctuations while Google processes the site's changes. From week 4–6, rankings should stabilise and, in most cases, return to pre-migration levels or even improve if the new site has better technical performance. If after 12 weeks rankings have not recovered, it is a sign that there are pending technical issues to resolve (missing redirects, indexation problems, performance degradation). **Is it necessary to migrate all blog articles, including the oldest ones?** Not necessarily. Very old articles (more than 3–4 years old) with little or no organic traffic and without relevant backlinks may not be worth the migration effort. However, before deciding not to migrate an article, it is necessary to verify in Google Search Console and Ahrefs/SEMrush that it has no organic traffic or quality backlinks. Articles that are decided not to migrate must have 301 redirects to the blog homepage or to related articles, to avoid 404 errors. **Can I do the migration in phases, migrating the blog first and then the rest of the site?** Yes, it is possible to do the migration in phases, but it requires careful planning to avoid indexation and user experience problems. The most common way to do a phased migration is to keep the main domain on WordPress and move the blog to a HubSpot subdomain (for example, `blog.domain.com`), or vice versa. However, this approach has SEO implications: backlinks to the blog on the main domain are not automatically transferred to the subdomain. The alternative is to do the complete migration in a single phase, which minimises the risk of inconsistencies. **What happens with WordPress plugins that generate dynamic content (calculators, configurators, etc.)?** WordPress plugins that generate dynamic content (price calculators, product configurators, comparison tools, etc.) do not have a direct equivalent in HubSpot CMS. To migrate this type of functionality, there are three options: (1) recreate the functionality using custom HubSpot modules with JavaScript, (2) keep the functionality in WordPress and embed it in HubSpot via an iframe, or (3) use a third-party tool (such as Typeform, Outgrow or a custom development solution) that integrates with HubSpot. The choice depends on the complexity of the functionality and the available budget. **Does migration to HubSpot CMS affect the performance of lead generation forms?** Migration to HubSpot CMS should not negatively affect the performance of lead generation forms; in fact, in most cases it improves it. Native HubSpot forms are optimised for conversion, integrate directly with the CRM without additional plugins, and allow automatic follow-up workflows to be configured. However, during the transition period (the first weeks after launch), it is important to closely monitor form conversion rates to detect any technical issues (forms that do not submit, validation errors, loading problems). --- ## Conclusion Migrating from WordPress to HubSpot CMS without losing SEO rankings is perfectly possible when following a structured process: pre-migration audit, URL planning, content and metadata migration, SEO configuration in HubSpot, redirect implementation and post-launch monitoring. Migration projects that fail from an SEO perspective are, almost without exception, those done in a hurry, without a prior audit and without a complete URL mapping and redirect plan. The success of a migration is not measured only in maintaining existing rankings: a well-executed migration is also an opportunity to improve content architecture, optimise SEO metadata and improve the site's technical performance. Many of the migration projects we have carried out at Emovere have resulted in improvements of 15–30% in organic traffic in the 6 months following launch, thanks to the technical and content improvements implemented during the process. If you are planning a migration from WordPress to HubSpot CMS, the Emovere team can accompany you throughout the entire process, from the initial audit to post-launch monitoring. --- ## References [1] Google Search Central — Site Move with URL Changes. https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes [2] HubSpot Developer Documentation — URL Redirects. https://developers.hubspot.com/docs/cms/building-blocks/url-redirects [3] Screaming Frog — SEO Spider Tool. https://www.screamingfrog.co.uk/seo-spider/ [4] Google Search Console Help — Sitemaps. https://support.google.com/webmasters/answer/7451001 [5] Ahrefs — Site Audit Tool. https://ahrefs.com/site-audit