Google Merchant Center for Miami Stores: Bilingual English and Spanish Feeds

A store in Miami sells to a market where language is part of the product data. The U.S. Census Bureau’s QuickFacts, using American Community Survey 5-year estimates for 2020-2024, reports that 75.3% of Miami-Dade residents aged 5 or older speak a language other than English at home. That figure covers all languages, not only Spanish, but it explains why an English-only feed can leave part of your market unreached.

This guide covers how Google handles language in Merchant Center, how to add a Spanish feed next to your English one, what changes between the two and the mistakes that cause errors. If you want specialists to build it, see our Google Merchant Center agency page.

Why does language matter for Google Shopping?

Google matches products to searches with the words in your product data: title, description and attributes. A product titled Women’s linen dress is a strong match for an English search and a weak one for a search in Spanish. Google’s help center says the language of your data source determines the language of your product data, and that when titles, descriptions and variants do not match that language, products may perform worse. If most of the data does not match, products may be disapproved.

Currency follows the same logic. Google says prices should be in the currency of the target country, and otherwise its currency conversion applies. For a Miami store that means USD in both feeds, so a shopper who switches language never sees a different price for the same product. Keep the two versions of each page in step, and treat a language switch as a change of text only, never of offer.

What does Google require when you add Spanish?

Google’s supported languages page lists English and Spanish, and says some countries support targeting in several languages. We found no sentence that names Spanish for the United States specifically, so treat the steps below as the logical reading of the general rules and test them on a small batch first. The requirements are clear:

• Same language everywhere. Landing pages must be in the same language as the product data, and so must the elements of the landing page and checkout that help shoppers navigate and buy.
• Currency. The United States uses USD.
• Same IDs. Google’s specification says to use the same ID for the same product across countries or languages.
• Accurate data. Titles up to 150 characters, descriptions up to 5,000, no promotional text, and prices and availability that match the page.

How do you set up a bilingual feed?

1. Keep your English primary data source as it is, with its language and United States target set.
2. Create a second primary data source for the Spanish version, with Spanish as the language and the United States as the target country.
3. Build Spanish product pages and checkout elements for the products in that source. Start with the best sellers if the full catalog is not ready.
4. Reuse the same product IDs, prices, availability, identifiers and shipping settings, so both versions describe one product.
5. Write Spanish titles and descriptions for the Spanish source instead of pasting machine output.
6. Upload a small batch, check Needs attention for the Incorrect language issue and then scale.

Google recommends submitting all your products in a single primary data source, but language is set per data source, so a second language needs its own. Fetch both files on the same schedule from the same product source, so a price change reaches both within one refresh. Watch the Performance page after launch, because Google does not describe how two language versions of one product interact.

Before a product goes into the Spanish source, check its page against Google’s landing page requirements:

• The title, description and navigation are in Spanish.
• The price is clear, in USD and equal to the feed.
• A working buy or add to basket button is visible.
• Availability is stated on the page and matches the feed.
• Delivery, returns and contact information can be found in Spanish.

What changes between the two feeds?

This map is an Avafa working tool. It separates what must stay identical from what must be rewritten:

How do you write Spanish titles that match searches?

Do not translate word for word. Start from the product type in the words Spanish-speaking shoppers use, then add brand, model and the attributes that distinguish the product, such as color or size. Check wording against real searches before you commit: Search Console queries, if you already rank in Spanish, and Google’s own suggestions as you type. Keep the title at 150 characters or less and leave out promotional text such as free shipping.

Read each title once as a customer. If it sounds like software wrote it, rewrite it. A machine-translated title that reads badly matches nothing and weakens trust when shoppers land on the page.

Which mistakes cause errors in bilingual feeds?

• A Spanish feed that links to English pages, which Google treats as a language mismatch.
• A Spanish page whose checkout or key elements are still in English.
• Spanish titles on products whose pages, options or variants are not available in Spanish.
• Prices or stock updated in one feed and not the other, which creates price mismatches.
• A site that blocks US IP addresses or redirects visitors by language or location. Google’s page on language inconsistency says blocking US IP addresses stops its crawler reaching your site, so check what the crawler sees.
• Sizes, units or product names that change meaning between languages.

If Google flags the issue, fix the language across the feed, landing pages and checkout, resubmit and request a review. Google says a new crawl after the request usually takes 24 to 48 hours. The product-level fix path is in our guide to products disapproved in Merchant Center.

How do you measure whether the Spanish feed works?

1. Record the baseline: impressions and clicks for the products you will translate first.
2. Launch in batches and note the date of each batch.
3. Check Needs attention after each batch for language, price and landing page issues.
4. Compare each product group on the Performance page with its own earlier weeks, not with the whole catalog.
5. Keep the titles that earn impressions and rewrite those that do not.

What else should Miami stores check?

• Shopify catalogs. Shopify’s help page says product options and variants must be in English to sync through the Google & YouTube app, so check this first. See our Shopify and Merchant Center guide.
• Delivery promises. The official Atlantic hurricane season runs from June 1 to November 30, according to the National Hurricane Center. Review handling and transit times in Merchant Center when storms can disrupt carriers.
• Holiday overlap. Use our Black Friday 2026 Merchant Center checklist so sale prices reach both feeds together.
• Physical stores. Link your Business Profile and read about local inventory ads and free local listings.

How we work at Avafa

We audit the English feed first, plan which products go Spanish first, write the titles with you and set up one refresh for both sources. We work remotely and do not have an office in Miami. To have this built for your store, talk to our agency specialized in Google Merchant Center.

Frequently asked questions

Do I need a Spanish version of my website?

Yes for the products you send in Spanish. Google says landing pages must match the language of the product data, including navigation and checkout elements.

Does the Spanish feed need different product IDs?

No. Google’s specification says to use the same ID for the same product across countries or languages.

Will the two feeds compete with each other?

Google does not describe this case. Keep IDs, prices and availability identical and watch the Performance page for changes after launch.

Can the Spanish feed update automatically?

Yes, if it is generated from the same source as the English one and fetched on a schedule, so prices and stock update together.

What does the Incorrect language issue mean?

A product is written in a language different from the feed, or the checkout is not in the feed language. Google’s detection is automatic and sometimes wrong, and you can request a review.

How do I fix many language issues at once?

Filter Needs attention by the issue, download the CSV, correct the products and upload the file again.

Should I start with the whole catalog?

No. Start with the products that have the best pages and the most demand, confirm they process cleanly and extend from there.