WordPress migrations are content migrations too
WordPress sites often contain ecommerce pages, blog posts, guides, landing pages, categories, tags, media URLs and SEO plugin settings. A Shopify migration needs to decide what moves, what redirects and what should be rebuilt.
Export SEO settings before the old site changes
Titles, meta descriptions, canonicals, noindex rules, redirects, schema settings and plugin data should be exported before plugins are removed, staging replaces production or the old site is frozen.
Internal links need deliberate rebuilding
WordPress content often contains years of links to products, categories and related guides. Those links should point directly to the new Shopify structure, not through redirect chains.
Preserve content that supports commerce
Guides, comparisons and educational posts can support collection rankings and customer trust. Do not remove them just because they are not product pages.
A WordPress-to-Shopify migration is not a copy of the old site
The mistake is thinking the migration is finished when the content has been imported and the redirects have been uploaded.
WordPress and Shopify organise a store differently. WordPress may have pages, posts, categories, tags, WooCommerce products, product categories, page-builder landing pages, plugin-generated schema, redirect rules and custom templates. Shopify has products, collections, pages, blogs, redirects, themes, apps and a more fixed commerce structure.
That means a safe migration is not a copy-and-paste exercise. It is a translation.
A valuable WordPress asset may become a Shopify collection. A WooCommerce category may need to become a collection with stronger buying guidance. A blog post may need to become a guide that supports a collection. A page-builder landing page may need to be rebuilt manually because the visible content does not exist cleanly in the database export.
The job is to move the search value, not the mess.
Export the WordPress evidence first. If that has not happened yet, start with WordPress SEO settings before Shopify migration.
Decide what the old site is actually worth
Before building Shopify destinations, separate the old WordPress site into assets and clutter.
Assets are pages that support search visibility, sales, trust, links or customer decisions. Clutter is everything that exists because WordPress, plugins or old campaigns created it over time.
Typical assets:
- product pages with organic traffic or revenue;
- WooCommerce product categories with search demand;
- buying guides that assist collection or product discovery;
- comparison pages with backlinks or high-intent traffic;
- service, support or warranty pages customers need;
- old campaign pages with links or branded demand.
Typical clutter:
- thin tag archives;
- duplicate blog categories;
- media attachment pages;
- old search result URLs;
- outdated landing pages;
- plugin-generated pages with no traffic or links;
- filtered URLs that never should have been indexable.
Do not migrate everything with the same level of care. A migration that protects junk with the same priority as revenue pages usually protects neither well.
Map WordPress content types to Shopify roles
A clean Shopify migration starts by deciding what each old content type should become.
| WordPress / WooCommerce asset | Possible Shopify destination | Main risk |
|---|---|---|
| WooCommerce product | Shopify product | Variants, descriptions, media, reviews and schema can change |
| WooCommerce category | Shopify collection | Category may become a thin grid unless rebuilt as a search landing page |
| Blog post | Shopify blog article or page | Internal links and media often break |
| WordPress page | Shopify page, guide or collection support content | Page-builder content may be lost |
| Elementor landing page | Rebuilt Shopify page/template section | Rendered copy may not export cleanly |
| Tag archive | Usually consolidate, redirect or retire | Preserving weak archives creates index bloat |
| Media attachment URL | Usually retire or redirect only if valuable | These often have little user value but may have links |
| Old redirect source | New redirect decision | Historical link equity can be lost if ignored |
This mapping stage matters more than the visual design. If the page roles are wrong, a beautiful Shopify launch can still lose organic visibility.
Build the Shopify structure from search assets, not menu labels
Do not start by recreating the old navigation.
Start with the pages that need to rank or convert:
- priority collections;
- important products;
- evergreen buying guides;
- brand or support pages;
- migration-preserved landing pages;
- pages with backlinks;
- pages that drive organic revenue.
Then ask what Shopify structure supports those assets.
A common example:
A WooCommerce store may have one broad product category, several tag pages and a handful of product filters. In Shopify, that might need to become:
- one parent collection;
- two or three child collections if search demand exists;
- no indexable tag pages;
- carefully controlled filter URLs;
- supporting buying-guide content;
- internal links from relevant products and guides.
If you simply redirect everything into one broad collection, the Shopify version may be cleaner but weaker for search.
Rewrite the redirect map as a decision log
Redirect mapping is where many migrations pretend to be safer than they are.
A spreadsheet with old URL and new URL columns is not enough. You need to know why the destination was chosen.
Add these columns:
- old URL;
- old content type;
- old traffic/backlink/revenue evidence;
- new Shopify URL;
- destination type;
- decision reason;
- redirect status;
- QA result;
- owner;
- notes.
Use decisions such as:
- rebuild as Shopify product;
- rebuild as Shopify collection;
- move as Shopify page;
- move as Shopify blog article;
- merge into stronger guide;
- redirect to closest commercial page;
- redirect to closest informational page;
- retire because no value exists;
- investigate before launch.
Never use the homepage as a lazy destination for valuable old URLs. If the old URL had specific intent, the redirect should preserve that intent as closely as possible.
Rebuild metadata only after the destination is known
Do not copy every WordPress title and description into Shopify.
Metadata should follow the new page role.
Examples:
- A WooCommerce product category becoming a Shopify collection may need a stronger commercial title than it had in WordPress.
- A WordPress buying guide becoming a Shopify blog article may keep its informational angle but need better internal links to collections.
- A page-builder landing page being merged into a collection support section may not need the same standalone title at all.
- A weak tag archive that redirects away should not have its metadata preserved.
Use the WordPress metadata export as a reference point, not as a copying task.
Check page-builder and hidden-content risk manually
Elementor and other builders can make WordPress migrations look complete when they are not.
A page may have visible content that does not transfer cleanly through a normal export. The Shopify page then launches with the headline and a thin body, while the content that used to support rankings is missing.
Manually check:
- top organic pages;
- top revenue support pages;
- Elementor landing pages;
- pages with accordions, tabs, FAQs or custom widgets;
- product pages with custom tabs;
- category pages with intro and below-grid copy;
- pages using shortcodes or plugin blocks.
For P1 pages, compare the old rendered page against the new Shopify page before launch.
Protect internal links, not just redirects
Redirects help users and search engines move from old URLs to new ones. Internal links tell them which new pages matter.
After migration, update internal links so they point directly to Shopify URLs rather than relying on redirects.
Check:
- navigation;
- footer links;
- collection descriptions;
- product descriptions;
- blog posts;
- buying guides;
- resource pages;
- image links;
- old campaign pages;
- breadcrumbs if custom.
A Shopify store can have a perfect redirect map and still underperform if the new internal linking makes important collections hard to reach.
Test the Shopify build before launch
Do not wait until the domain points to Shopify to check SEO basics.
Before launch, test:
- important products exist and are indexable;
- important collections exist and have useful content;
- metadata is present on priority pages;
- canonical output is sensible;
- no staging noindex setting is accidentally carried across;
- redirects are ready and importable;
- internal links point to final Shopify URLs where possible;
- structured data does not conflict with visible content;
- old blog and guide content has not become thinner;
- tracking events and checkout conversion tracking are ready;
- sitemap and robots behaviour is understood.
The migration sheet only matters if the live store matches it.
Launch-day checks
On launch day, check the pages that carry the most risk first.
Start with:
- homepage;
- top collections;
- top products;
- top old organic URLs;
- backlink targets;
- blog/guides with organic traffic;
- old WooCommerce category URLs;
- redirect samples by page type;
- robots.txt and sitemap;
- Search Console inspection for priority URLs;
- analytics and purchase tracking;
- checkout and payment flow.
Do not spend the first hour checking low-value URLs while high-value redirects are untested.
First 14 days after launch
The first two weeks are for diagnosis, not panic.
Track:
- old URL redirect errors;
- 404s from important old URLs;
- Search Console crawl and indexing messages;
- sitemap processing;
- top collection clicks and impressions;
- top product clicks and impressions;
- branded queries;
- organic landing page sessions;
- revenue tracking consistency;
- pages with sudden loss of impressions;
- pages with traffic but poor conversion.
Some fluctuation is normal after a migration. A pattern of important pages disappearing, redirecting poorly or losing internal links is not normal.
Common implementation mistakes
Avoid these:
- treating all old URLs as equal;
- redirecting many old pages to the homepage;
- rebuilding the visual design before mapping SEO assets;
- losing Elementor/page-builder content;
- copying plugin metadata without checking page role;
- preserving weak WordPress archives because they are easy to export;
- changing Shopify handles after launch without redirects;
- relying on redirects instead of updating internal links;
- launching before analytics and Search Console are ready;
- waiting a month before checking traffic-loss patterns.
What to use with this guide
Use the Shopify redirect mapping guide for the URL decision log.
Use the Shopify migration QA checklist for launch checks.
Use the migration crawl and indexing checks for sitemap, robots, canonical and indexation review.
Use the traffic drop after migration guide if the move has already launched and visibility has fallen.
Quick answer
Protect search equity during a Shopify migration by turning the old site into an evidence map before URLs, templates or tracking change.
What you will do
- Know which old URLs must be protected.
- Build redirects before launch pressure starts.
- Keep metadata, analytics and Search Console evidence available after the move.
- Reduce the risk of avoidable traffic loss.
What to check first
- Crawler export for the old site and Shopify staging site.
- Google Search Console page, query and indexing exports.
- GA4 annotations and landing-page reports.
- Shopify URL redirects.
- Redirect Mapping Sheet, Migration QA Checklist and Post-Migration Monitoring Sheet.
Work through it in this order
- Crawl the current site and export all indexable URLs.
- Export Search Console pages and queries for at least the last 16 months where available.
- Tag each old URL as protect, merge, replace, retire or investigate.
- Map protected URLs to the closest Shopify destination before launch.
- Copy or improve critical titles, descriptions, headings, content blocks and internal links.
- Test redirects, canonicals, sitemap output, robots rules and tracking on staging.
- Monitor Search Console, analytics and 404 logs for four weeks after launch.
Real-world notes
- The most common failure is redirecting old category URLs to the homepage because the Shopify collection structure was not ready.
- Traffic drops often look like ranking problems when the real issue is missing tracking, missing redirects or changed internal links.
- Blog URLs are easy to ignore during ecommerce migrations, but they often carry internal links and long-tail traffic.
Final checks
- Old URL crawl saved.
- Search Console export saved.
- Top landing pages mapped.
- Redirects uploaded and tested.
- Metadata for priority pages reviewed.
- Analytics and conversion tracking checked.
- Post-launch monitoring owner assigned.
Watch-outs
- If the old site has faceted URLs indexed, decide which should become Shopify collections and which should be retired.
- If products are discontinued during migration, redirect only where the replacement is genuinely useful.
- If the domain changes as well as the platform, follow a stricter site-move process and expect a longer stabilisation period.
Download the Migration Risk Kit or request an audit if organic revenue, product count or URL complexity is high.
Field questions
What SEO settings should be exported before moving from WordPress to Shopify?
Export title tags, meta descriptions, canonical settings, noindex rules, redirects, sitemap URLs, schema settings, top landing pages, Search Console data and internal link data.
Can WordPress blog posts move to Shopify?
Yes, but the content structure, URLs, internal links, metadata and redirects need planning. Some complex content models may be better rebuilt or kept separately.
Should Rank Math settings be used during migration?
Rank Math or another WordPress SEO plugin can be useful for exporting metadata and reviewing SEO settings before migration. It is a bridge tool, not a Shopify SEO tool.
