Using Google Search Console to Monitor Your Multilingual Store

Most Shopify merchants check Google Search Console once, see green checkmarks, and assume their multilingual store is fine. It isn't — and the proof is hiding in plain sight inside three reports most people never open.

Using Search Console for a multilingual store is fundamentally different from using it for a single-language site. You're dealing with multiple URL variants, hreflang tags that must be perfectly symmetrical across every language, and separate click and impression data per locale — each of which can silently underperform for months without a single error alert. This guide walks you through the exact setup, the reports that matter, and the specific thresholds that should trigger action.

How Shopify Markets Affects Your Search Console Setup

Before you open a single report, you need to understand a critical structural difference that changes how Search Console works for your store.

Shopify Markets (native multilingual) serves translated content on subfolder URLs: yourstore.com/fr/ for French, yourstore.com/de/ for German, and so on. These all live under one root domain. Shopify also injects hreflang tags automatically for every published locale.

Legacy third-party translation apps (the kind that use JavaScript overlays or separate domains/subdomains) produce a completely different structure. Some duplicate content onto subdomains like fr.yourstore.com, others use query parameters like ?lang=fr, and many don't generate valid hreflang at all.

Why this matters for Search Console:

• With Shopify Markets + a native translation app like StoreLingo, all your language variants are discoverable under one Search Console property. You can filter performance by URL prefix (/fr/, /de/) to isolate each locale's data.
• With subdomain setups, you need separate Search Console properties per subdomain and must manually cross-reference hreflang errors across them.
• JavaScript overlay apps often make Google see only the default-language content, meaning your translated pages may never be indexed at all — and Search Console's Coverage report is where you'll catch that.

If you haven't decided on your URL structure yet, the choice between subfolders and subdomains has real SEO consequences worth understanding before you migrate.

Setting Up Search Console Correctly for Multiple Languages

Add the Right Property Type

For a Shopify Markets store on a single domain, add a Domain property in Search Console (e.g., yourstore.com). This captures all subfolders, all protocols, and all subdomains in one view — no fragmented data.

If you're using subdomains per language, add each subdomain as a separate URL-prefix property (https://fr.yourstore.com/) and verify each one individually.

Submit Sitemaps for Every Locale

Shopify automatically generates a sitemap at yourstore.com/sitemap.xml that includes sitemap index files for products, pages, collections, and blogs. When you publish a new language through Shopify Markets, those URLs should appear in the relevant sitemaps within 24–48 hours.

Submit your sitemap to Search Console and then check Indexing → Sitemaps to confirm:

• The sitemap was fetched successfully (not returning a 4xx or 5xx)
• The number of "Discovered URLs" is climbing as expected after you publish new language content
• There are no sitemaps throwing errors for specific locales

A common problem: if you add a language in Shopify but forget to publish it, those URLs won't appear in the sitemap and won't get indexed. The Sitemaps report makes this immediately visible.

The Three Search Console Reports That Actually Matter

1. Search Performance — Filtered by Language Subfolder

Go to Search Results → Performance and add a Page filter using the URL prefix for each locale (e.g., /fr/). This gives you impression, click, CTR, and average position data for that specific language.

Thresholds that should trigger investigation:

• A language subfolder showing fewer than 10 impressions per week after 6+ weeks of being indexed is a signal that Google isn't treating those pages as serving a real audience — check your hreflang, check that the language is actually published, and verify the content isn't near-duplicate of your default.
• A CTR drop of more than 3 percentage points versus your default-language equivalent for the same product category suggests your translated meta titles and descriptions aren't compelling in that language. Generic machine-translated titles like "Red Shoes — Buy Online" perform far worse than copy that reflects how speakers of that language actually search.
• Average position worse than position 20 for a language that represents a significant portion of your target market means Google is indexing the pages but not trusting them — usually a content quality issue or a hreflang misconfiguration that's sending confusing signals.

2. Indexing → Pages (Coverage)

This report shows which URLs Google has indexed, which it couldn't, and why. For multilingual stores, focus on:

"Duplicate without user-selected canonical" — This error frequently appears when translated pages are too thin or share too much boilerplate with the default language. Google chooses the canonical itself, usually picking your English URL, which means your French or German page never ranks. The fix is improving the uniqueness and depth of translated content — especially product descriptions and SEO meta fields.

"Crawled — currently not indexed" — Google fetched the page but decided not to index it. For translated pages, this often means the content quality threshold wasn't met. If you translated a 40-word product description, Google may simply not consider it worth indexing.

"Page with redirect" — If your previous translation setup used a JavaScript overlay that redirected users by language, old URLs may still be in Google's index pointing to 301s. These need to be cleaned up.

Aim to keep your "not indexed" count below 5% of your total submitted URLs. Above that, you have a systemic issue rather than isolated edge cases.

3. Search Results — Hreflang Validation (via URL Inspection)

Important update: Google deprecated the standalone International Targeting report in Search Console in early 2024. It no longer exists in the current interface. Don't rely on guides that tell you to find it under "Legacy Tools."

The current way to diagnose hreflang issues is:

1. Use the URL Inspection tool on a specific page URL to see how Google last crawled it and whether it detected hreflang annotations.
2. Use the Page indexing report to look for hreflang-related errors, which now surface as page-level issues rather than a dedicated report.
3. For systematic hreflang validation, use a third-party crawler (Screaming Frog, Sitebulb, or Ahrefs Site Audit) alongside Search Console. These tools will crawl all your language variants and flag hreflang tags that are missing reciprocal confirmations — the single most common cause of hreflang failure.

A hreflang tag only works when both sides confirm each other. Your French page must point to your English page, and your English page must point back to the French page. If you have more than 50 pages with broken reciprocal hreflang in a catalog of 500+ products, that's a systematic problem, not isolated errors — and it requires a process fix, not manual correction.

StoreLingo handles hreflang injection automatically when you publish translations through Shopify Markets, which eliminates most of these reciprocal-link errors at the source. But you still need to verify via Search Console + a crawler that the tags are rendering correctly in production.

Diagnosing Language Cannibalization Accurately

A common piece of advice says "if two language versions rank for the same query, your hreflang is broken." This is an oversimplification that leads merchants to chase phantom problems.

When it's not a problem: If a French-speaking user in France searches an English-language brand term or product name, Google may legitimately surface both your English and French pages — especially if the French translation hasn't yet accumulated ranking signals. This is normal during the early indexing phase.

When it is a problem: Cannibalization is real when:

• Both the English and French versions of a translated, French-language query appear in the same SERP for French users
• Your Search Performance report shows your French subfolder pages have lower impressions than the English equivalents for French-language queries (filter by country: France, then compare queries)
• The URL Inspection tool shows Google has indexed the French URL but the canonical it's returning is the English URL

In that third case, Google has overridden your intended canonical, which is a content quality signal — not just a technical hreflang issue.

Building a Monthly Monitoring Routine

Set a recurring task (30 minutes, once a month) with this checklist:

• Coverage report: Check that "valid indexed" URLs are growing proportionally with the languages you've published. Flag any spike in "not indexed" or "duplicate" errors.
• Performance by locale: Pull clicks and impressions per subfolder. Flag any locale where impressions have dropped more than 20% week-over-week for two consecutive weeks.
• New queries per language: Sort by impressions, filter to each language subfolder, and look for high-impression / zero-click queries. These are keywords where you rank but your title or description isn't earning the click — a translation quality issue, not a ranking issue.
• URL Inspection spot-checks: Pick 3–5 recently translated product pages and run them through URL Inspection to confirm Google has fetched the current version (check "last crawl date") and that hreflang is being detected.

If you're using StoreLingo's change-detection feature to keep translations current as your catalog evolves, also cross-check that updated product pages have been re-crawled after translation — the URL Inspection "Request Indexing" button is useful for prioritizing this.

Add StoreLingo on the Shopify App Store →

For a deeper look at how translated meta titles and descriptions directly affect the CTR numbers you're monitoring in Search Console, see Why Translated Meta Titles and Descriptions Make or Break Multilingual SEO. If you're finding hreflang errors that Shopify's automatic tags aren't resolving, Hreflang on Shopify: The Complete Guide to International SEO Tags covers the edge cases in detail. And if your coverage report is surfacing duplicate content warnings, Does Multilingual Content Cause Duplicate Content Penalties? explains exactly when Google treats it as a problem and when it doesn't.

---

FAQ

Does Google Search Console have a dedicated multilingual or International Targeting report? Google deprecated the International Targeting report in early 2024, so it no longer appears in Search Console. Hreflang monitoring now requires a combination of the URL Inspection tool, the Page indexing report, and a third-party crawler to systematically validate reciprocal hreflang tags across your full catalog.

How can I connect Search Console data to revenue by language to see which locales are actually worth investing in? Beyond GA4 integration, Search Console's own URL-level click and impression data is underused here: export performance filtered by each language subfolder as a CSV, then map those URLs to your Shopify sales data by locale to calculate revenue-per-click by language. For ongoing reporting, the free Looker Studio connector for Search Console lets you build a dashboard that plots clicks, impressions, and CTR per subfolder alongside GA4 conversion data — far more actionable than checking each tool separately.

My translated pages are getting crawled but not indexed — what's the most likely cause? The most common cause is thin content: if your translated product descriptions are under 100 words, or your meta fields weren't translated (leaving them in the default language), Google often judges the page as not meaningfully different from the original and excludes it from the index. Translating the full page — including SEO title, meta description, and product description body — and ensuring the content is substantive enough to stand on its own is the fix.