Prepare WordPress SEO before moving to Shopify

Quick verdict

A WordPress to Shopify SEO migration should not start with the Shopify theme.

It should start with the old WordPress site.

That site contains the evidence you need to protect: URLs, rankings, backlinks, redirects, metadata, blog posts, internal links, images, schema, noindex rules, canonical tags, page-builder content, analytics benchmarks and years of small editorial decisions.

If that evidence is not exported before the move, the Shopify build team has to guess what mattered.

Guessing is where migration damage starts.

Before design, theme selection or app decisions, decide what must be preserved, what should be rebuilt, what can be merged and what should not move at all.

If the platform decision is still open, read Shopify vs WordPress before committing to the move. If the move is already approved, use the WordPress to Shopify SEO migration guide to connect URL mapping, tracking, indexation and post-launch monitoring.

Why WordPress migrations go wrong

Most WordPress to Shopify SEO losses are not caused by Shopify itself.

They happen because the old WordPress site is treated as clutter instead of evidence.

Common failure patterns:

• high-performing blog posts are removed because they look outdated
• old category/tag/archive URLs are ignored until after launch
• metadata from Rank Math or Yoast is not exported
• Elementor pages are rebuilt visually but lose text, headings or internal links
• redirect rules from plugins or server config are missed
• media URLs and embedded images break
• noindex/canonical rules are not reviewed
• WordPress content is forced into Shopify without deciding what role it should play
• GA4/Search Console benchmarks are not saved before launch

The migration is safer when every old URL gets a decision before the new site goes live.

What to export before Shopify work begins

Before Shopify build decisions, collect:

If this feels like too much work, that is the point: migrations fail when this work is skipped.

WordPress tools are evidence sources, not future strategy

Rank Math, Yoast, Elementor and similar tools can be very useful before a migration.

But they are bridge systems.

Their role is to show what exists today so the new Shopify site can be rebuilt deliberately.

Do not assume:

• Rank Math titles become Shopify titles automatically
• Yoast schema settings transfer cleanly
• Elementor layouts become Shopify sections
• WordPress redirects become Shopify redirects
• WordPress categories become Shopify collections
• WordPress tags should become Shopify tags

Each item needs a migration decision.

The point is not to recreate WordPress inside Shopify. The important work is preserving search value while rebuilding the ecommerce architecture in the right Shopify shape.

Separate real assets from WordPress clutter

A mature WordPress site usually contains both valuable pages and years of clutter.

Do not migrate everything equally.

Classify URLs into five groups:

Examples:

• a high-traffic buying guide might be rebuilt as a Shopify guide
• a WooCommerce product category might become a Shopify collection
• an old comparison post might redirect into a stronger resource
• thin tag archives might be retired or redirected carefully
• media attachment pages usually should not become new Shopify pages

The mistake is treating migration as copy-and-paste. It is really a content and URL triage process.

Map WordPress content to Shopify roles

WordPress and Shopify do not think about content the same way.

Use this map:

Do not let Shopify’s available fields decide the content strategy. Decide the role first, then choose the Shopify destination.

Watch Elementor and page-builder pages carefully

Elementor and other page builders create one of the biggest hidden migration risks.

A page might look simple in the browser but contain:

• important copy inside widgets
• hidden mobile/desktop variants
• accordions or tabs with crawlable text
• embedded forms
• internal links inside sections
• custom schema or scripts
• image galleries
• calls to action
• shortcodes

When those pages are rebuilt in Shopify, visual similarity is not enough.

For each important Elementor/page-builder page, capture:

• rendered text
• headings
• internal links
• images
• CTAs
• forms
• schema output
• analytics events
• current organic traffic
• intended Shopify destination

Then rebuild the page based on what it does, not just how it looks.

Redirects are not a launch-day admin task

Redirects are the migration control system.

For each old WordPress URL, record:

• old URL
• current status code
• organic clicks/impressions
• backlinks
• revenue or enquiries if known
• content type
• proposed Shopify destination
• redirect priority
• owner
• test status

A redirect is weak if it sends a valuable old URL to the homepage just because there is no obvious replacement.

For example:

• old /category/running-shoes/ should usually map to a relevant Shopify collection
• old /blog/best-running-shoes-for-flat-feet/ might map to a rebuilt guide
• old /product/nike-model-x/ should map to the closest live product or successor
• old tag archives might map to a collection, guide or no direct replacement depending on value

Use Shopify redirect mapping when the URL list is ready.

Metadata and schema need rebuilding, not copying blindly

Export WordPress metadata, but do not blindly copy it into Shopify.

Old titles and descriptions may have been written for a different site structure.

Review:

• title tags
• meta descriptions
• canonical rules
• noindex settings
• social titles/descriptions
• schema type/output
• breadcrumbs
• product data
• FAQ/HowTo markup if present

Then rebuild based on the new Shopify page role.

A WordPress guide title might still work. A WooCommerce category title may need to become a stronger Shopify collection title. A plugin-generated schema setup may need to be replaced by cleaner Shopify/theme/app output.

The export protects evidence. It does not replace judgement.

Internal links are easy to break and hard to notice

WordPress content often contains years of internal links.

During migration, these links can break, redirect, or point to weaker destinations.

Before launch, crawl old internal links and decide:

• which links should point to Shopify collections
• which should point to Shopify products
• which should point to rebuilt guides
• which should be removed
• which should be updated inside migrated posts

Do not rely only on redirects. Internal links should be updated to final Shopify URLs where possible.

This matters because internal links tell users and search engines which pages are important.

Analytics and Search Console must survive the move

A migration without measurement is guesswork.

Before launch, save:

• GA4 landing-page reports
• organic revenue/conversion data where available
• Search Console pages/queries
• top product and collection pages
• top blog and guide pages
• current event/conversion setup
• paid media pixel setup if relevant

After launch, track:

• organic clicks/impressions by old versus new destination
• indexed Shopify URLs
• redirect errors
• crawl errors
• revenue/conversion tracking
• collection performance
• product performance
• blog/guide performance

If tracking breaks during the move, a measurement loss can look like an SEO loss. Use Shopify migration analytics tracking QA before judging performance.

A safer WordPress to Shopify preparation sequence

Step 1: crawl the old WordPress site

Capture all public URLs, metadata, headings, canonicals, indexability, internal links and status codes.

Step 2: export search and revenue evidence

Pull Search Console, GA4 and backlink data before launch pressure begins.

Step 3: export plugin and builder evidence

Document Rank Math/Yoast metadata, redirects, noindex rules, schema settings and Elementor/page-builder pages.

Step 4: classify every URL

Protect, rebuild, merge, redirect or retire.

Step 5: design Shopify destinations

Map products, collections, pages, blogs and resources based on their new role.

Step 6: write redirect rules

Do not wait until launch day. The redirect map should be tested before go-live.

Step 7: rebuild important content manually

Especially guides, landing pages, Elementor pages and commercial content.

Step 8: test crawl, index and tracking signals

Use staging/live QA before launch decisions become irreversible.

Step 9: monitor the first 14 days closely

Search Console and analytics will show whether mapping, redirects and tracking are behaving as expected.

What not to do

Do not:

• migrate only the pages that look important visually
• delete old WordPress posts without checking traffic/backlinks
• assume blog content has no commercial value
• redirect everything to the homepage
• trust automated import tools without crawl QA
• copy metadata without reviewing page intent
• ignore tag/category/archive URLs
• forget old redirect plugin rules
• treat Elementor output as simple text
• judge migration success before tracking is verified

Minimum viable migration control sheet

At minimum, build a sheet with these columns:

This sheet matters more than the theme preview.

Where to go next

• Export plugin metadata with WordPress SEO settings before Shopify migration.
• Use the implementation runbook: WordPress to Shopify SEO migration.
• Compare the SEO tradeoff first: Shopify vs WordPress.
• Compare the platform decision: Shopify vs WordPress.
• If WooCommerce is involved, use WooCommerce to Shopify.
• Build the redirect system with Shopify redirect mapping.