Shopify Markets translation checklist.

1. Check market and language setup

Start with the basics before reviewing content. Translation QA only makes sense if you know which languages and markets are live.

• Confirm which languages are published.
• Confirm which markets are active and customer-facing.
• Check the primary language for each storefront experience.
• Open each localized storefront URL and confirm it resolves correctly.
• Check that the language selector, country selector, or market routing works as expected.

This setup step helps you prioritize. A missing translation in a live German market is more urgent than a missing translation in a draft or hidden language.

2. Check catalog content

Your catalog is usually the largest translation surface in a Shopify store. Check more than product titles.

• Product titles and descriptions.
• Product SEO titles and meta descriptions.
• Product option names and values, such as size, color, material, or finish.
• Collection titles, descriptions, handles, and SEO fields.
• Variant-related display text that appears in selectors or product details.

3. Check storefront and support content

Shoppers do not only read product pages. They also rely on navigation, policies, content pages, and theme interface text.

• Menus, navigation labels, and footer links.
• Pages such as About, Contact, size guides, shipping information, and returns.
• Blog posts, article titles, excerpts, and content blocks.
• Policy pages such as refund, privacy, shipping, terms, and legal notices.
• Theme text such as buttons, labels, badges, cart messages, empty states, and announcement bars.

These areas affect trust. A mostly translated product page with an untranslated return policy can still make the store feel unfinished.

4. Check metafields and metaobjects

Many Shopify stores use custom data to power storefront content. This is where translation checks often fail if the audit only looks at visible pages.

• Product specifications stored in metafields.
• Ingredients, care instructions, warnings, dimensions, and technical details.
• Reusable content blocks stored as metaobjects.
• Badges, icons, callouts, and landing page modules controlled by custom fields.

If custom data appears on the storefront, include it in your translation QA process.

5. Repeat the check after updates

Translation QA is not only a launch task. Stores change too often for a one-time review to stay accurate.

• Run a scan after adding many new products.
• Run a scan after changing product descriptions, policy pages, or theme sections.
• Run a scan before launching a new market or campaign.
• Review new critical issues first, especially those visible in active markets.
• Keep an exportable fix list so translation work can be assigned or reviewed in batches.

DSK Translation Check is built for this repeatable QA loop. It turns the checklist into a read-only scan and gives you a fix queue for missing, stale, blank, and copied translations.