How to Convert a Review CSV to a Google Merchant Center XML File (Founder-Friendly Technical Guide)

If you already have your reviews exported as a CSV, you’re halfway to getting product ratings into Google Shopping. The only catch? Google Merchant Center does not accept CSV files, only XML formatted exactly the way Google expects.

The problem is that XML feels “technical,” and Google’s documentation can be a little intimidating. This guide breaks down the process in plain English, showing you how to take your existing CSV and convert it into a Google-compliant XML file without needing to write code or hire a developer.

This is not an uploading guide (that’s Blog #1). This article focuses entirely on the conversion itself, the structure, the fields, the mapping, and the validation.

Who is this guide for?

•	Anyone searching for “convert CSV to Google Merchant Center XML”
•	Anyone needing to generate Google Product Ratings XML files from CSV
•	Anyone who has review CSV exports from Judge.me, Loox, Okendo or Stamped
•	Anyone who wants star ratings to appear on Google Shopping

Why Google Doesn’t Accept CSV Files for Product Ratings

CSV files store review data in a flat table format: Rows represent reviews, columns represent fields.

But Google Merchant Center needs relationship-aware formatting:

•	Each review must be wrapped inside a <review> block
•	Each <review> has “child elements” such as <rating>, <content>, <review_id>, etc.
•	Product identifiers must be nested inside <product_ids>
•	The entire collection must be wrapped in a <reviews> or <feed> element

In other words:

CSV = table XML = structured document

Google uses XML because it’s predictable, strict, and machine-readable, but that means you must convert.

What Google’s XML Format Looks Like (Simplified)

Here’s a simple version of what Google expects:

<reviews>
  <review>
    <review_id>12345</review_id>
    <reviewer_name>Sarah</reviewer_name>
    <review_timestamp>2025-11-10T12:45:00</review_timestamp>
    <content>Loved the quality!</content>
    <rating>5</rating>
    <product_ids>
      <sku>HOLO-STAR-01</sku>
    </product_ids>
  </review>
</reviews>

Every part of this XML corresponds to a column in your CSV.

Your job is simply to map the right CSV columns to the right XML fields.

Understanding the Required XML Fields

Here are the fields Google expects in a basic review entry, explained in founder-friendly language:

<review_id>

A unique identifier for each review. Can be your CSV’s ID column, timestamp + SKU, or any unique value.\

<reviewer_name>

The customer’s name. If your reviews are anonymous, use the placeholder your CSV provides.

<review_timestamp>

The date the review was created. Google prefers UTC timestamps in this format: YYYY-MM-DDThh:mm:ss

<content>

The body of the review — plain text. Avoid emojis or special characters that break XML.

<rating>

A number from 1 to 5.

<product_ids>

A nested block containing product identifiers. You must provide only one of these:

•	<sku>
•	<gtin>
•	<mpn>

The identifier must match exactly what’s in your Google product feed.

How to Map Your CSV Columns to Google’s XML Fields

Let’s say your CSV has these columns:

id,author,created_at,body,rating,sku

You might map them like this:

This mapping step is the most important part of the conversion.

The Most Common CSV Problems That Break XML

Before converting, here are the issues that usually cause XML rejection:

1. Missing ratings

A blank rating field results in a broken <rating> element.

2. Invalid rating values

Only numbers 1–5 are allowed.

3. Missing product identifiers

If SKU/GTIN isn’t provided, Google can’t match the review to a product.

4. Emojis or weird characters

XML hates 🚀🤩💖 unless properly encoded, best to remove them.

5. Broken timestamps

Formats like “Nov 10, 2025” won’t work, must be ISO/UTC.

6. Duplicated review IDs

Each <review_id> must be unique.

Fixing these in the CSV prevents XML frustration later.

The Easiest Way to Convert a CSV into XML (No Coding)

You technically can convert a CSV to XML manually or with scripts. But unless you’re comfortable writing and maintaining code, it’s not practical.

This is why dedicated converters exist.

With a tool like Review2XML, the process looks like this:

Step 1: Upload your CSV

Supports Judge.me, Loox, Okendo, Stamped, and custom CSVs.

Step 2: Map the columns

You choose which CSV column becomes:

•	review_id
•	reviewer_name
•	review_timestamp
•	content
•	rating
•	SKU/GTIN/MPN

Step 3: Validate the data

The tool checks for missing fields, bad ratings, and invalid timestamps.

Step 4: Download your XML

You’ll receive a fully compliant XML file ready for Google.

This removes all coding, formatting, and structural guesswork.

Manual Conversion, Scripts, and Tools Compared

Here’s a founder-friendly comparison of your options:

If your reviews already exist in a CSV, tools like Review2XML offer the cleanest, cheapest workflow.

Validation Checklist Before Uploading to Google Merchant Center

Before you upload your XML, run through this quick checklist:

•	✔ Every <review_id> is unique
•	✔ All <rating> values are between 1–5
•	✔ Every review includes a valid <product_ids> element
•	✔ All timestamps use YYYY-MM-DDThh:mm:ss
•	✔ No emojis or strange characters in <content>
•	✔ The XML opens and closes properly
•	✔ No missing tags or partial fields

If everything checks out, your XML is ready.

Final Thoughts

Converting a review CSV into a Google Merchant Center XML file doesn’t need to be technical or expensive. Once you understand Google’s structure and field requirements, the whole process becomes predictable:

•	Clean your CSV
•	Map your fields
•	Validate your data
•	Generate your XML
•	Upload to Google

If you prefer to skip the technical steps entirely, Review2XML can convert your CSV to a fully compliant XML file in seconds, no coding required.

Frequently Asked Questions

Can I convert a CSV from any review platform?

Yes, as long as the CSV has columns for reviewer name, rating (1–5), review text, review date, and a product identifier (SKU, GTIN, or MPN). Review2XML supports Judge.me, Loox, Yotpo, Okendo, Stamped, Junip, Reviews.io and Trustpilot exports natively.

What format does Google require for the review XML?

Google requires the Product Ratings feed format with specific XML elements: publisher, reviews, review, reviewer, review-id, ratings, products, product, product-ids. Dates must be in ISO 8601 format. See our feed specification guide for the full schema.

Do I need to know how to code to convert a CSV to XML?

No. Review2XML handles the entire conversion through a point-and-click interface — upload, map columns, download XML. No coding required.

What if my CSV has different column names than expected?

Review2XML has a manual column mapping step where you can match your CSV columns to the correct Google fields. This works for any CSV format.

How many reviews can I convert at once?

Review2XML can handle exports with thousands of reviews. The free plan lets you preview the first 3 rows. Paid plans starting at $6/month include unlimited conversions.