How to Import Reviews Between Apps Without Losing SEO

Why does switching review apps hurt SEO at all?

Because your star ratings in Google are not stored by Google. They are read, on each crawl, from structured data your review app prints into the page. Switch apps carelessly and that markup disappears for a window of hours or days, and the rich result disappears with it.

The social proof on the page is the other casualty. A buyer who lands on a product page with no reviews where there used to be forty assumes the worst, and that is a conversion loss the moment the old widget stops rendering and before the new one is populated.

• Star snippets vanish when the review markup stops being printed.
• Product pages look abandoned when the widget is empty mid-switch.
• Deep links to individual reviews break if review URLs change.
• Crawl budget gets spent on empty pages if you import slowly.

How do I get my reviews out of the old app?

Most review apps support exporting your reviews as a CSV file, usually from a settings or data-export screen, and some send the file by email rather than downloading it in the browser. Export first, before you touch anything else, and keep the original file untouched as a backup.

Open the CSV and confirm it actually contains what you need: the review body, rating, author name, date, and crucially a product identifier such as the handle, SKU, or product ID. Reviews and photos sometimes export separately, so check whether image URLs came across or whether media needs a second export.

How do I keep each review attached to the right product?

This is where migrations quietly go wrong. The old app and the new app rarely identify products the same way: one keys on the Shopify product ID, another on the handle, another on a SKU you set years ago. If the mapping column does not line up, your reviews import as orphans or land on the wrong product.

Before importing, reconcile the product identifier in your export against the field the new app expects. Build a small lookup if you have to. A few hours spent matching identifiers here saves you from the far worse job of un-mixing thousands of misattributed reviews later.

• Decide the single key both apps agree on (handle, SKU, or product ID).
• Spot-check ten products by hand before importing the full file.
• Hold back deleted or merged products so reviews do not orphan.
• Keep author and date intact so review recency is not reset.

Why should I run both apps at once for a few days?

A brief overlap during the switch is what stops product pages going blank. Install and populate the new app while the old one is still rendering, verify the new reviews are showing correctly, and only then remove the old widget. The cost is a short period of paying for two apps, which is far cheaper than a week of empty product pages.

During the overlap, watch for double-rendered reviews and for two sets of structured data on the same page. You want exactly one source of review markup live at any moment, so plan the cutover so the old markup comes out as the new markup goes in, not before and not long after.

How do I keep my star snippets through the move?

Preserving the review structured data through the move is what protects your star snippets. After import, view the source of a populated product page and confirm the new app is printing valid AggregateRating and Review markup, then run a couple of pages through a structured-data test to be sure Google can still read the ratings.

There is a deeper version of this that most apps never reach. Many review apps were built for the on-page shopper and stop there: the reviews look right to a human but sit inside a widget a crawler or an AI answer engine cannot read. Getting your existing reviews readable, corroborated, and citable in search and AI answers is the gap BetterReviews is built to close, and a migration is the natural moment to fix it rather than carry the same blind spot into the new app.

Do I need redirects, and which URLs change?

You need redirects only if URLs actually change, so check two things. First, whether the new app gives individual reviews their own URLs and whether those differ from the old ones. Second, whether anything links to review pages, such as email campaigns or a dedicated reviews page.

If review URLs change, add 301 redirects from the old paths to the new so existing links and any indexed review pages keep their value. Most migrations leave the product URLs themselves untouched, which is the case that matters most for rankings, so in practice the redirect work is small and targeted.

What does a safe migration look like end to end?

Export to CSV and back up the file. Reconcile the product mapping and spot-check it. Install the new app and import into it while the old one still renders. Verify reviews and structured data on real pages. Remove the old widget so only one set of markup is live. Add redirects for any changed review URLs, then monitor Search Console for a week.

The through-line is order. Each step protects the next, and the only irreversible mistakes (orphaned reviews, lost markup, blank pages) come from skipping the overlap or rushing the mapping. Move deliberately and the buyer never notices the switch happened.