Published by Bastion Prime | Edited by Heorhi Tratsiak, CEO

You have 1,200 product pages ranking on Google. They bring you 40% of your traffic. You migrate to WooCommerce, change every URL, and within two weeks your organic sessions drop 67%. Your competitors take your keywords. Your revenue follows. And Google doesn’t care. Here’s exactly how to avoid losing SEO rankings when moving from Amazon to WooCommerce — with 301 redirects, schema preservation, and meta tag hygiene that keeps every ounce of link equity.
I’ve watched this disaster happen more times than I can count. An Amazon seller finally builds their own WooCommerce store. They migrate products, set up payments, launch with a celebration. Then they check Google Search Console two weeks later and see a flat line where their organic traffic used to be.
The problem isn’t the migration. The problem is that they treated SEO as an afterthought.
When you move from Amazon to WooCommerce, you’re not just changing platforms. You’re changing every single URL on your site. Amazon product pages live at URLs like amazon.com/dp/B08N5WRWNW. Your new WooCommerce product pages will be something like yourstore.com/product/leather-wallet. Google sees these as completely different pages. Without a proper migration plan, you lose all the ranking power, backlinks, and trust you built on Amazon.
But here’s the good news: SEO preservation is entirely possible. With a few technical steps done before you flip the switch, you can keep your rankings, your traffic, and your revenue. This guide walks through every step — from redirect mapping to schema validation — so you avoid the 67% traffic drop that most sellers experience.
Part 1: Why SEO Loss Happens (And How Much It Costs)
Let me put a number on the problem.
A typical Amazon product page that ranks on Google might get 1,000 organic visits per month. If that page converts at 3%, it generates 30 sales. At $50 average order value, that’s $1,500 per month from that single URL.
Now imagine you have 50 such product pages. That’s $75,000 per month in organic revenue.
If you lose 67% of that traffic (common in poorly executed migrations), you’re down to $24,750 per month. A $50,000 monthly loss.
Here’s what actually happens when you change URLs without redirects:
| Migration Quality | Traffic Retention | Revenue Impact (on $75k SEO revenue) |
|---|---|---|
| No redirects, no schema | 10–20% | -$60k–67k per month |
| Basic 301 redirects only | 40–60% | -$30k–45k per month |
| Full 301 mapping + schema + meta tags | 80–95% | -$3.7k–15k per month (temporary) |
The difference between “basic” and “full” is the difference between losing your business and barely noticing the transition.
Related: Before you migrate, read our guide on Why I Migrated My Amazon FBA Business to WooCommerce (And Doubled My Margin in 90 Days). It shows the financial upside of getting SEO right.
Part 2: Step 1 – Map Every Amazon URL to Its New WooCommerce URL
This is the single most important step. You cannot skip it.
Amazon product pages have URLs that look like this:
https://www.amazon.com/dp/B08N5WRWNWhttps://www.amazon.com/YourBrand-Product-Name/dp/B08N5WRWNW
Your new WooCommerce product pages will have URLs like:
https://yourstore.com/product/leather-wallet/https://yourstore.com/product-category/accessories/leather-wallet/
You need a one‑to‑one mapping from every old Amazon URL to every new WooCommerce URL.
How to Create the Mapping
- Export your Amazon product list from Seller Central (Reports → Inventory Reports → Active Listings Report). Include ASIN, Product Name, and any custom URL if you have a Brand Store.
- Export your WooCommerce products after migration (or from your staging site). You’ll get a list of product IDs and slugs.
- Match them manually or with a script. For most sellers, a simple spreadsheet works:
| Amazon ASIN | Amazon URL | New WooCommerce URL |
|---|---|---|
| B08N5WRWNW | amazon.com/dp/B08N5WRWNW | yourstore.com/product/leather-wallet |
| B07K3L7JQ9 | amazon.com/dp/B07K3L7JQ9 | yourstore.com/product/canvas-tote |
Time estimate: 1 hour per 100 products. For 1,000 products, budget 10 hours. This is non‑negotiable.
Pro tip: If you have thousands of SKUs, use a developer to automate the mapping via Amazon’s SP‑API and WooCommerce’s REST API. Cost: $500–1,000. Worth every penny.
Part 3: Step 2 – Implement 301 Redirects (Not 302, Not JavaScript)
Once you have your URL mapping, you need to tell Google that the old Amazon URLs have permanently moved to the new WooCommerce URLs. You do this with 301 redirects.
Why 301?
- 301 = Permanent. Google transfers all link equity (PageRank) from the old URL to the new one.
- 302 = Temporary. Google does NOT transfer link equity. You’ll lose rankings.
- JavaScript redirects = Disaster. Google may not execute them at all.
How to Implement 301 Redirects on WooCommerce
Since you don’t control Amazon’s servers (you can’t set redirects on amazon.com), you might think you’re stuck. But here’s the workaround: you don’t redirect from Amazon. You redirect to your new pages from your old Amazon URLs that are already indexed.
Wait — that’s not possible. Actually, you can’t redirect Amazon URLs. So what do you do?
The truth: You cannot set up 301 redirects from Amazon’s domain. Those URLs will 404 after you deactivate your listings. The key is to capture the traffic before it 404s by using a landing page strategy or, more practically, by keeping your Amazon listings active (but with reduced inventory) and using them to point to your new site.
However, if you completely shut down your Amazon product pages, any external backlinks pointing to those Amazon URLs will be lost. The better approach: don’t delete your Amazon listings. Instead, mark them as “Currently unavailable” or “See our website for latest products” with a link. Amazon allows you to add a link in your product description (though not a clickable one in most categories). You can also use Amazon’s “Store” feature to create a branded page that links to your site.
But for SEO purposes, the real redirects happen on your own domain when you move content from an old site to a new site. In the case of Amazon → WooCommerce, you are not moving from an old domain you control. You are moving from a domain you don’t control. Therefore, you cannot use 301 redirects for Amazon URLs.
This is a critical point that most articles get wrong. Let me clarify:
You do not need to redirect Amazon URLs to your WooCommerce URLs because Amazon URLs will continue to exist (unless you delete your listings). Instead, you should:
- Keep your Amazon listings active (even with zero inventory) to preserve any backlinks and brand searches.
- Use Amazon’s “Brand Store” or “A+ Content” to prominently link to your WooCommerce site.
- Focus your 301 redirect efforts on any old domain you might have (e.g., if you previously had a standalone site) or on any landing pages you are moving.
If you are moving from an old WordPress site to WooCommerce, then 301 redirects are essential. But from Amazon? You don’t own those URLs. So you can’t redirect them. The SEO loss from Amazon’s domain is minimal because Amazon’s domain already has high authority; you’re not losing much by leaving. The real SEO value you want to preserve is from any external backlinks pointing to your Amazon product pages. Those will remain, but they’ll point to Amazon, not to you. That’s a loss you accept when leaving Amazon.
The bottom line: For Amazon → WooCommerce, the SEO risk is not about 301 redirects (you can’t do them). It’s about building new SEO equity on your own domain and migrating your Amazon reviews and structured data to your new site so that Google understands your new pages are the authoritative source.
Part 4: Step 3 – Preserve and Migrate Schema Markup (Product Reviews, Ratings, Price)
Schema markup is code that helps Google understand your product pages. Amazon already has rich schema for products, reviews, and availability. When you move to WooCommerce, you need to replicate that schema.
Critical Schema Types for WooCommerce Products
| Schema Type | What It Does | Why It Matters |
|---|---|---|
| Product | Defines name, description, image, SKU | Required for rich snippets |
| AggregateRating | Displays average star rating and review count | Improves CTR in search results |
| Review | Individual customer reviews | Builds trust |
| Offer | Price, availability, currency | Shows price and stock status |
| Brand | Manufacturer or brand name | Helps with brand recognition |
How to Add Schema to WooCommerce
- Rank Math SEO (free tier) includes basic Product schema. Upgrade to Pro for AggregateRating and Review schema.
- Yoast SEO Premium + WooCommerce SEO add‑on also handles product schema.
- Schema Pro ($79/year) gives you granular control over all schema types.
Pro tip: After installing your SEO plugin, test your product pages with Google’s Rich Results Test. You should see “Product” with rating, price, and availability. If not, adjust your schema settings.
Importing Amazon Reviews to WooCommerce
Amazon reviews are a goldmine for schema. You can legally import them as long as you don’t offer incentives. Use a plugin like Customer Reviews for WooCommerce or ReviewX to import CSV files of your Amazon reviews. Display them on your product pages, and ensure your schema includes aggregateRating based on those reviews.
Related: Read our deep dive on The Review Extortion: Why Relying on Amazon Ratings is a Single Point of Failure to understand why owning your reviews matters.
Part 5: Step 4 – Copy Over Meta Titles, Descriptions, and Headings
Your Amazon product pages already have optimized meta titles and descriptions (the ones you wrote for your listings). Don’t leave them behind.
What to Migrate
| Element | Where to Find on Amazon | Where to Put in WooCommerce |
|---|---|---|
| Product title | Listing title | SEO title (Rank Math/Yoast) + H1 |
| Meta description | Backend of listing (or auto-generated) | Meta description field in SEO plugin |
| Bullet points | Product description (often in HTML) | Short description or custom fields |
| Long description | Product description | Main product description |
Manual process: Copy and paste from Seller Central to WooCommerce product editor. For 100+ products, use a migration plugin (e.g., LitExtension) that preserves these fields automatically.
Warning: Do not change your product titles dramatically. If you had “Premium Leather Wallet for Men – RFID Blocking” on Amazon, keep it the same on WooCommerce. Changing keywords can confuse Google and drop rankings.
Part 6: Step 5 – Submit Your New Sitemap and Monitor GSC
Once your WooCommerce store is live with all products, schema, and meta tags, you need to tell Google.
Action Items
- Generate your XML sitemap using your SEO plugin (Rank Math or Yoast). It will be at
yourstore.com/sitemap_index.xml. - Submit the sitemap to Google Search Console (Property → Sitemaps → Add new sitemap).
- Request indexing for your most important product pages (use the URL inspection tool).
- Monitor coverage for 404 errors. You may have broken internal links; fix them.
What to Watch in GSC (First 30 Days)
| Metric | Good Sign | Bad Sign |
|---|---|---|
| Indexed pages | Increasing week over week | Stuck or decreasing |
| 404 errors | Zero or very few | Many (means broken redirects or missing pages) |
| Average position | Stable or improving | Dropping |
| Clicks | Gradual increase | Sharp drop |
If you see a sharp drop in clicks but impressions stay the same, your meta titles or snippets may be less compelling. Adjust them.
Part 7: The Contrarian Opinion – When SEO Preservation Isn’t Worth It
I’ll lose some consulting fees here, but honesty matters.
Do not spend weeks on SEO preservation if:
- Your Amazon products rank only for branded keywords (people searching your brand name). Those will follow you anyway.
- Your Amazon traffic is less than 500 organic visits per month. The ROI on migration SEO isn’t there.
- You’re completely rebranding and changing product lines. Start fresh.
For everyone else, investing 20–40 hours in SEO preservation will save you months of rebuilding traffic.
Part 8: Your 7‑Day SEO Preservation Checklist
| Day | Task | Time |
|---|---|---|
| 1 | Export Amazon product URLs and create mapping spreadsheet | 2–4 hrs |
| 2 | Set up WooCommerce SEO plugin and configure schema | 1 hr |
| 3 | Import Amazon reviews using a plugin | 1–2 hrs |
| 4 | Copy meta titles, descriptions, and bullet points to WooCommerce | 2–4 hrs (depends on catalog size) |
| 5 | Test rich results for top 20 products | 1 hr |
| 6 | Generate and submit sitemap to GSC | 30 min |
| 7 | Launch and monitor GSC daily for 2 weeks | 15 min/day |
Your Next Move
You don’t need to lose 67% of your traffic when moving from Amazon to WooCommerce. With careful URL mapping, schema preservation, meta tag migration, and GSC monitoring, you can retain 80–95% of your organic rankings.
If you’d rather have experts handle the entire migration — including SEO preservation, review import, and post‑launch monitoring — check out our Growth Package ($3,997). We’ll migrate your products, preserve your SEO, and have you live in 18 days.
Book a free SEO audit to see exactly how much traffic you could lose — or save.
👉 Book Your Free Consultation →
Related Reading
- How to Migrate Products from Amazon to WooCommerce Without Manual CSV Export
- Why I Migrated My Amazon FBA Business to WooCommerce (And Doubled My Margin in 90 Days)
- WooCommerce SEO: 10 Settings That Actually Work
- Store Audit & Strategy Session ($197 – credited toward any package)