18 SEO Issues When Migrating a Site to WP Engine

Moving a WordPress website to WP Engine can improve performance, security, caching, and scalability, but the migration can also create SEO problems if technical settings do not transfer correctly.

Moving the files and database is only part of the process. Redirects, canonicals, robots.txt, XML sitemaps, DNS, SSL, internal links, caching, indexing directives, and server configuration also need to remain correct.

Google treats a hosting change differently from a URL change. If your URLs stay the same, you are mainly changing infrastructure. If URLs change too, you need a proper URL mapping and redirect strategy.

At Search Miners, we help businesses identify technical SEO problems before and after website migrations through a comprehensive SEO Audit.

What Happens When You Migrate a WordPress Site to WP Engine?

A typical WP Engine migration moves your WordPress installation, database, themes, plugins, media, and configuration to a new hosting environment.

You then test the site on WP Engine before pointing your live domain to the new environment. WP Engine recommends adding the domain in its User Portal and updating DNS when you are ready to launch. You may also need to search and replace to update domain references.

The process sounds simple, but SEO adds another layer. Your migration must preserve the technical signals search engines already understand while the site moves to its new hosting environment.

These are some common issues that you can encounter when doing so:

1. Staging Sites Can Accidentally Create SEO Problems

One of the first things you should check during a WP Engine migration is the staging environment.

WP Engine automatically restricts search engine traffic to sites using its environment.wpengine.com domain. This helps prevent development and staging versions from appearing in search results.

That protection is useful.

But it creates an important migration checklist item.

Your production site must not retain development-only crawling or indexing restrictions after launch.

Google specifically warns website owners to remove noindex and robots.txt blocks that were only necessary during development or migration.

Check Before Launch

Review your robots.txt, meta robots tags, X-Robots-Tag headers, WordPress Search Engine Visibility settings, SEO plugin indexing settings, canonical URLs, and XML sitemap accessibility. 

Never assume these settings transferred correctly just because the pages look correct.

2. Robots.txt Can Change During the Migration

Your robots.txt file tells search engines which areas of the website they can crawl.

That makes it particularly important during a hosting migration.

WP Engine explains that non-production environments using its WP Engine subdomain are restricted from search engine crawling and indexing. It also recommends allowing the production site to use the appropriate robots.txt configuration once the site goes live.

A migration can therefore create two opposite problems.

You can accidentally block Google from the live website.

Or you can accidentally expose a staging environment to search engines.

Both situations create SEO risks.

What Should You Check?

Open:

https://example.com/robots.txt

Then confirm that:

• The file loads correctly
• Important website sections are not blocked
• Your XML sitemap is referenced correctly
• Development-only rules are gone
• WordPress admin areas remain appropriately restricted
• The production environment does not inherit staging restrictions

Google also recommends checking the robots.txt configuration on the new site before completing a site move.

3. Your Redirects May Not Move With the Website

Redirects deserve special attention during a WP Engine migration.

Your old website may contain hundreds or thousands of redirects created through .htaccess, WordPress plugins, server or Nginx rules, CMS settings, or WP Engine’s redirect tools. 

The problem is that these systems do not always transfer in the same way.

WP Engine specifically states that it does not use .htaccess. It also provides its own redirect rules and Nginx configuration options.

This creates an important migration question:

Where do your existing redirects live?

Suppose your old server contains:

/old-seo-page → /seo-services

through an .htaccess rule.

You move the site to WP Engine. If that rule does not get recreated using the appropriate WP Engine configuration, the old URL may stop redirecting. A visitor could receive a 404 instead. Google could also encounter the broken URL.

A Better Migration Process

Before moving the site, export your existing redirects.

Then categorize them:

Redirect type	What to check
301	Confirm destination still exists
302	Confirm the redirect is genuinely temporary
HTTP → HTTPS	Confirm the final URL is HTTPS
Old URL → New URL	Confirm the new page is relevant
Redirect chain	Replace with a direct redirect
Redirect loop	Fix before launch
Deleted page	Determine whether a relevant replacement exists

WP Engine currently supports 301 and 302 redirect rules through its User Portal and also provides options for managing larger redirect sets.

4. Redirect Chains Can Appear After Migration

A migration can introduce a redirect chain even when the original website did not have one.

For example:

old-page → intermediate-page → new-page

This often happens when a website has gone through multiple redesigns.

You may start with:

/old-page → /new-page

Then another migration adds:

/old-page → /new-page → /latest-page

The final setup now contains an unnecessary hop.

Google recommends sending the old URL directly to the final destination and avoiding redirect chains that add unnecessary hops. 

During a WP Engine migration, crawl the site after launch and look specifically for URLs that redirect more than once.

5. Canonical URLs Can Point to the Wrong Environment

Canonical tags tell search engines which URL represents the preferred version of a page. During a migration, canonical URLs can accidentally retain staging or old-domain references.

Imagine the live page is:

https://example.com/seo-audit

But its canonical tag says:

https://example.wpengine.com/seo-audit

That creates an obvious SEO problem.

Google may receive conflicting signals about which URL should appear in search results.

Check canonical tags on key pages, including the homepage, service pages, blog posts, category pages, product pages, location pages, and high-traffic landing pages. 

Google specifically recommends checking rel=”canonical” annotations after redirects become active during a site move and making sure the new URLs appear in the canonical tags.

6. Internal Links Can Still Point to the Old Environment

A WordPress migration can leave old URLs inside your content.

For example, a blog post may contain:

https://old-domain.com/technical-seo

while the new website uses:

https://example.com/technical-seo

Visitors may still reach the destination if a redirect exists. But you should not rely on redirects for your own internal links. Update internal links so they point directly to the current URLs.

Search and replace may be necessary after migration to ensure domain references use the intended domain.

Search your database and crawl the website for references to the old domain, WP Engine staging domain, HTTP versions, old URL paths, image URLs, PDF URLs, and internal anchors.

This becomes particularly important for large WordPress websites with years of published content.

7. DNS Changes Can Cause Temporary SEO Problems

When you make a website live on WP Engine, you need to point your domain’s DNS to the new hosting environment. This step determines where visitors go when they request your domain. Taking a site live involves adding the domain to the WP Engine User Portal and pointing DNS to WP Engine.

A DNS mistake can produce:

• Downtime
• 404 errors
• SSL problems
• Incorrect server responses
• Inconsistent access between users
• Crawling problems

Before changing DNS, confirm that the WP Engine environment works correctly using the intended domain configuration.

Then test the website from multiple networks and locations after the DNS change.

Do not judge the migration solely from your own browser.

8. SSL and HTTPS Need to Be Checked

HTTPS is not something you should treat as an afterthought during migration.

If your website already uses HTTPS, confirm that the new WP Engine environment serves the correct certificate and redirects HTTP traffic appropriately.

WP Engine says its Advanced Network applies SSL and CDN automatically once the domain is correctly configured with the network.

But your SEO check should go further.

Test:

http://example.com

http://www.example.com

https://example.com

https://www.example.com

You should know exactly which version is your preferred URL and confirm that the other versions resolve appropriately.

Also check for mixed-content issues involving images, CSS, JavaScript, fonts, and embedded media.

A page can technically load while still containing references to insecure resources.

9. XML Sitemaps Can Break or Become Outdated

Your XML sitemap should contain the URLs you actually want Google to crawl and index.

A migration can change your sitemap location, URLs, domain references, canonical URLs, last modification dates, and included page types.

Update sitemaps during site moves and submit the new sitemap through Search Console. After migrating to WP Engine, open the sitemap manually.

For example:

https://example.com/sitemap_index.xml

Then check several URLs inside it.

Ask:

• Does the sitemap load?
• Does it use the correct domain?
• Can it contain HTTPS URLs?
• Do the URLs return 200 responses?
• Are redirected URLs excluded?
• Are noindex pages excluded?
• Are important pages missing?

A sitemap can load successfully while still containing the wrong URLs.

10. WP Engine Caching Can Affect What You See After Migration

WP Engine uses extensive caching, including server-level caching and CDN caching. Its current documentation explains that cached content may remain visible after changes until the relevant caches are cleared.

This creates an unusual migration problem. You may make an SEO change and believe it did not work because you are still seeing an older cached version.

For example, you may update canonical tags, robots directives, page content, redirects, or structured data, but your browser or CDN may continue serving an older version.

Purge caches when updates are not appearing as expected. After migration, test important SEO elements in a fresh session and confirm the actual server response rather than relying only on what you see in the browser.

11. Performance Can Change After Migration

One reason companies choose WP Engine involves website performance.

WP Engine’s current Advanced Network uses Cloudflare infrastructure, CDN delivery, and other performance features. WP Engine states that its Advanced Network can improve performance by up to 25%, although actual results vary by website and configuration.

Do not assume that moving to a faster host automatically makes every page faster.

Your WordPress site’s performance still depends on its theme, plugins, images, JavaScript, CSS, third-party scripts, database queries, fonts, page structure, and cache configuration.

Establish a performance baseline before migration and compare these metrics after the move:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)
• Total page weight
• Number of requests

12. Plugin Changes Can Create SEO Problems

A WordPress migration can also expose plugin compatibility issues.

WP Engine maintains a list of disallowed plugins and has specific platform configurations that differ from other hosting environments. Review theme and plugin versions during the migration process.

This matters because SEO functionality often depends on plugins.

For example, a plugin may control:

• XML sitemaps
• Canonical tags
• Schema markup
• Redirects
• Breadcrumbs
• Meta titles
• Meta descriptions
• Robots directives

If the plugin changes during migration, these elements can change with it. Do not compare only whether the homepage looks identical. Compare the HTML output and SEO configuration of important templates.

13. .htaccess Rules May Need to Be Recreated

This is one of the most important WP Engine-specific migration issues.

Many WordPress websites running on traditional Apache hosting rely on .htaccess for server rules.

WP Engine states that its platform does not use .htaccess. Instead, it provides other methods for implementing server behavior, including redirect and Nginx configuration options.

That means you should inventory important .htaccess rules before moving.

These could include 301 redirects, HTTPS redirects, security rules, rewrite rules, URL normalization, cache rules, and access restrictions.

Do not simply upload the old .htaccess file and assume WP Engine will use it.

Translate the required rules into the appropriate WP Engine configuration.

14. Search Console Should Be Part of Your Migration Plan

Google recommends using Search Console during site moves.

Before the migration, record your baseline. 

Monitor organic clicks, impressions, CTR, average position, indexed pages, top landing pages, top queries, Core Web Vitals, and crawl and indexing issues.

You can also review site engagement metrics to understand how visitors interact with your content. 

Then compare the same information after the migration.

Google notes that ranking fluctuations can occur while it recrawls and reindexes a migrated website. For medium-sized websites, the process can take weeks or longer.

Do not panic because rankings move slightly during the first few days.

Instead, look for persistent technical problems.

A temporary fluctuation is different from losing 30% of indexed URLs because the new website contains a noindex directive.

15. Search Console Can Reveal Migration Problems

After launch, check Google Search Console for unusual changes.

Pay particular attention to not indexed pages, pages with redirects, not found errors, server errors, crawled but currently not indexed pages, duplicate pages, alternate pages with a proper canonical, and sitemap errors.

You should also inspect important URLs individually using URL Inspection.

Choose pages that historically generated significant organic traffic.

If those pages are not indexed correctly, investigate immediately.

16. WP Engine Environment Settings May Not Copy Automatically

Another easy-to-miss issue involves WP Engine environment-level configuration.

WP Engine states that when copying environments, certain settings do not automatically transfer. These include redirect rules, custom cache exclusions, SSL certificates, and Nginx rules.

This matters if your migration or deployment process involves copying one WP Engine environment to another.

Your WordPress files and database can look correct while platform-level settings remain different.

That is why your migration checklist should include both:

WordPress configuration

and

WP Engine environment configuration.

Do not assume that copying the website means copying every hosting rule.

17. Do a Full Crawl Before You Switch DNS

One of the safest approaches is to crawl the existing website before migration.

Export important URLs with at least the URL, status code, title, meta description, canonical, indexability, H1, internal links, word count, images, redirects, and organic traffic.

Then crawl the WP Engine version before launch.

Compare the results. You want to identify differences before Google discovers them.

SEO element	Before migration	After migration
Homepage status	200	200
Canonical	Correct	Correct
Robots	Index	Index
Sitemap	Working	Working
Important URLs	200	200
Redirects	Working	Working
Internal links	Current domain	Current domain
HTTPS	Active	Active
Images	Loading	Loading
Schema	Present	Present
Analytics	Tracking	Tracking

This gives your team a technical baseline rather than relying on visual inspection.

18. Do Not Combine Too Many SEO Changes With the Migration

Google recommends changing one thing at a time where possible.

For example, if you are moving to WP Engine, changing the domain, redesigning the website, changing URL structures, rewriting content, and changing your information architecture simultaneously, it becomes much harder to identify the cause of a ranking change.

Consider this migration:

Hosting migration + domain change + redesign + URL change + content rewrite

If organic traffic drops, which change caused it? You may not know.

A cleaner approach is:

Step 1: Move hosting.

Step 2: Verify the site.

Step 3: Monitor organic performance.

Step 4: Make other major changes separately where practical.

This does not always work for large projects, but separating major variables makes SEO troubleshooting much easier.

WP Engine Migration SEO Checklist

Before launching your WordPress website on WP Engine, review this checklist.

Before Migration	During Migration	After Launch
Crawl the existing website	Test the WP Engine environment	Point DNS to WP Engine
Export important URLs	Confirm the correct domain configuration	Purge relevant caches
Record organic traffic and ranking data	Check SSL	Crawl the live website
Export existing redirects	Check robots.txt	Test redirects
Review .htaccess rules	Check noindex directives	Check Search Console
Check robots.txt	Check canonical tags	Submit the sitemap
Check canonical tags	Recreate required redirects	Inspect important URLs
Check XML sitemaps	Check internal links	Monitor organic clicks
Record Core Web Vitals	Check XML sitemaps	Monitor impressions
Back up the website	Test important pages	Monitor indexing
Review plugins and themes	Test images and PDFs	Monitor server errors
	Check structured data	Check Core Web Vitals
	Confirm analytics tracking	Compare rankings with the pre-migration baseline

What Are the Biggest SEO Risks When Moving to WP Engine?

If you want to prioritize your checks, start with these.

SEO issue	Importance
noindex left on production	Can prevent pages from appearing in Google
Incorrect robots.txt	Can block crawling
Missing redirects	Can create broken URLs and lost traffic
Redirect chains	Add unnecessary latency
Incorrect canonicals	Can confuse Google’s preferred URL selection
Broken internal links	Create unnecessary redirects and crawl inefficiency
Old staging URLs	Can create duplicate or incorrect references
Broken sitemap	Makes URL discovery harder
DNS errors	Can cause downtime or incorrect responses
SSL problems	Can disrupt HTTPS access
Cache issues	Can make old content or SEO settings appear live
Missing .htaccess rules	Can remove important redirects and rewrites
Plugin changes	Can alter SEO elements
Poor post-launch monitoring	Delays detection of migration problems

How Long Does SEO Take to Recover After a Migration?

SEO recovery after a migration has no fixed timeline. If URLs and technical signals stay consistent, disruption may be minimal, but URL changes can take Google several weeks or longer to process. Focus first on indexing, redirects, canonicals, sitemaps, and crawl errors rather than judging rankings in the first few days.

Should You Migrate Your WordPress Site to WP Engine?

WP Engine can provide a strong WordPress hosting environment, but your SEO results depend on how you execute the migration.

Treat a hosting migration as a technical SEO project, not just a server move. Preserve the signals Google already understands and test the new environment before switching the domain.

The key rule is simple: do not launch first and audit later. Test redirects, canonicals, indexing, sitemaps, and other critical SEO settings while the old website is still live so you can fix issues before they affect organic performance.

Improve Your Website’s SEO Before and After a WP Engine Migration

Search Miners can audit your website before and after migration to identify technical SEO issues involving crawling, indexing, redirects, canonicalization, internal linking, and performance.

If you are planning to move your WordPress website to WP Engine, contact Search Miners to identify potential SEO risks before they affect your organic performance.

People Also Ask

Does moving a WordPress site to WP Engine affect SEO?

Changing hosting providers does not automatically hurt SEO. If your URLs and important SEO settings stay the same, Google can process the hosting change without treating it as a URL migration.

Does WP Engine improve SEO?

WP Engine can support website performance through features such as caching, CDN delivery, and SSL. However, hosting alone does not guarantee higher rankings.

Does WP Engine use .htaccess?

No. WP Engine does not use .htaccess, so you should recreate important redirects and server rules using WP Engine’s supported configuration.

Can a WP Engine staging site get indexed by Google?

WP Engine restricts search engine traffic to its environment.wpengine.com staging domains. You should still check your production site for any leftover noindex or crawling restrictions after launch.

Do I need 301 redirects when moving to WP Engine?

Not if you are only changing hosting and keeping the same URLs. If your URLs change, use 301 redirects to send old URLs to their relevant new destinations.

What should I check after migrating to WP Engine?

Check your robots.txt, canonicals, redirects, internal links, XML sitemap, SSL, DNS, structured data, and page performance. Also review Google Search Console for indexing or crawling issues.

Can a migration cause a temporary drop in rankings?

Yes. Google may need time to recrawl and reindex the website after a migration, which can cause temporary ranking changes.

How do I prevent SEO problems during a WP Engine migration?

Crawl your website before the migration and document important SEO settings and URLs. Test the WP Engine site before launch, then monitor redirects, indexing, sitemaps, and Search Console after the switch.