How to Check Language Versions in Google’s Index: See What Has Actually Been Picked Up

The short answer

To check whether language versions are in Google’s index, review each URL individually, not just the site as a whole. Google removed the easy-to-read International Targeting report from Search Console, so you can no longer see in one place whether your French, Spanish, or German pages are set up correctly (GSC Wizard). Instead, combine the URL Inspection Tool, the Pages section in Search Console, and manual site: searches for each language folder or subdomain. The goal is straightforward: for every language version, you need to know whether Google has crawled it, whether it is indexed, and which URL Google selected as the canonical. Without these checks, your Spanish or German content may be live but completely absent from Google’s search results.

Key takeaways

• Google has removed the International Targeting report from Search Console. Geographic targeting signals now come from ccTLDs, hreflang, server location, and on-page content, with no manual override available (GSC Wizard).
• Hreflang tags often lack a reciprocal link. If page X points to page Y, page Y must also point back to page X. Otherwise, Google may ignore or misinterpret the annotation (Google Search Central).
• The URL Inspection Tool shows the exact index status, Google-selected canonical, and most recent crawl date for each URL, making it the most reliable check for individual language versions (Google Search Console Help).
• You can implement hreflang through the HTML head, HTTP headers, or an XML sitemap. Every URL must reference the complete set of alternative language versions (Wikipedia).
• 86 percent of Europeans believe everyone should speak at least one foreign language, underlining the commercial value of correctly indexed multilingual content (Eurobarometer via ECER).

Why is my site translated, but nobody can find the German or French version?

An online store may have Dutch, French, and German pages that look complete in the browser. All three language versions are polished, translated, and live. Yet Google Search Console may show that only the Dutch pages receive traffic. That gap between being live and being indexed is exactly where international small and mid-sized brands often get stuck.

A page loading correctly in a browser says nothing about its status in Google’s index. It may have a valid hreflang tag and still be skipped by Google. The canonical may point to the wrong page, the internal linking structure may make the language version difficult to reach, or Google may treat it as duplicate content compared with the Dutch original. Without active monitoring, you may not spot the issue until months later, when revenue from France or Germany consistently falls short of expectations.

Why are manual checks more important now that Google has removed the report?

Until recently, you could open one report in Search Console to see whether Google had accepted your country or language targeting, including a list of hreflang errors. That report no longer exists. Google now determines geographic relevance from a combination of signals: your domain type, such as a ccTLD or subfolder, your hreflang implementation, server location, and the language of your content (GSC Wizard). There is no longer a central dashboard that tells you, “this hreflang setup is wrong” or “this language version is not being targeted correctly.”

That means the responsibility has shifted to the website owner. You need to bring the separate signals together yourself: crawl status, canonical selection, internal links, and hreflang validation. For brands expanding internationally, this is far from a theoretical issue. If you manage three or four language versions without regularly checking whether Google has actually picked them up, you could be continually creating content that never appears in search results. If you are also evaluating an SEO tool that supports international sites, this comparison of SEO tools is a useful place to start.

How do you check whether all your language versions are in Google’s index?

This process works whether you manage three or twelve language versions. If you already have the tools ready, allow around ten to fifteen minutes per language version.

Step 1: Create a list of every language version URL

Collect every language and country variation along with its full URL, including subfolders such as /fr/ and /de/, or subdomains such as fr.example.com. Without a complete list, your checks will be random rather than systematic, and you are likely to miss the pages that matter most, including product pages and landing pages.

Step 2: Use the URL Inspection Tool for every language version

Paste each URL into the URL Inspection Tool in Search Console. It shows whether the page is indexed, when it was last crawled, and which canonical URL Google has actually selected (Google Search Console Help). The last point is critical. Your French page may be crawled successfully, but if Google chooses the Dutch version as canonical, the French page is unlikely to appear in French search results.

Step 3: Check hreflang reciprocal links

Confirm that every language version links back to every other relevant language version. If page Y does not link back to page X, Google may ignore or misinterpret the entire hreflang set (Google Search Central). This is one of the most common technical reasons why language versions exist but are not properly distinguished in search results.

Step 4: Make sure hreflang is implemented consistently across the site

Hreflang can be implemented in the HTML head, HTTP headers, or XML sitemap, but avoid mixing these methods within the same page set. Every URL must reference the full set of alternative versions, including itself (Wikipedia). A common mistake is for the Dutch page to reference French and German versions but not itself, leaving the entire setup open to misinterpretation.

Step 5: Run a manual site search for each language folder

Search Google for site:yourdomain.com/fr/ and compare the number of results with the actual number of French pages on your site. A significant gap, such as twenty live pages but only four indexed, is a clear sign of a broader indexing problem.

Step 6: Review the Pages section in Search Console by language segment

Filter the Pages report by URL pattern for each language folder, then review which pages are excluded and why. Reason codes such as “Duplicate, Google chose different canonical than user” often point directly to the hreflang or canonical issue identified in steps 2 and 3.

Step 7: Repeat the check regularly, not just once

Indexing is not a permanent one-time status. New content, site changes, or a migration can cause previously indexed language versions to drop out of Google’s index. Make this a recurring process, ideally monthly for your most important language markets.

Get started:

• Put every language version URL into one spreadsheet, with columns for index status, canonical, and latest crawl date.
• Check at least your ten most important pages in each language with the URL Inspection Tool this week.
• Compare the number of site: results for every language folder with the number of pages that are actually live.
• Schedule this review every quarter, not only after a website change.

Which signals matter beyond index status alone?

Index status is the starting point, not the finish line. A page can be indexed and still attract almost no traffic because Google has included it in the index without seeing it as the best match for local search intent. Review impressions and clicks by language segment in the Performance section of Search Console as well. A French page with hundreds of impressions but almost no clicks suggests a ranking issue, not an indexing issue.

Another useful signal is the ratio of crawled to indexed pages by language. If Google crawls your German pages but consistently chooses not to index them, the cause is often content that is too thin or too similar to the source language. This is a common outcome when automated translation is published without local adaptation. Google explicitly recommends making language and region-specific pages clear not only technically through hreflang, but also through locally relevant content (Bounteous).

Third, consider server location and ccTLD signals. A brand serving content from a Dutch data centre under a generic .com domain with language-based subfolders lacks one geographic signal that ccTLDs can provide. This is not a dealbreaker, but it can influence how Google assesses relevance by country, especially now that manual targeting overrides are no longer available.

Which mistakes repeatedly stop language versions from being picked up?

Imagine a small business with twelve employees expanding its online store into France, Spain, and Germany. The marketing manager translates its hundred most important product pages, publishes them under /fr/, /es/, and /de/, and assumes Google will automatically pick them up within a few weeks. Three months later, a manual site: search reveals that only thirty of the hundred French pages are indexed. The reason: the hreflang tags pointed from Dutch to French, but not back again, so Google largely ignored the annotations.

This example reflects the most common issues:

• Missing reciprocal links in the hreflang set, causing Google to see the configuration as unreliable.
• Canonical conflicts, where a translated page accidentally points to the source language as its canonical, preventing Google from indexing the translation as the main version.
• Thin or machine-translated content that is not sufficiently distinct from the source page to be treated as unique and valuable.
• No internal links from the main navigation to language versions, meaning Google may discover them through the sitemap but treat them as low priority.
• A one-off audit instead of an ongoing process, meaning issues are only discovered once the revenue impact is already visible.

Businesses that publish in multiple languages are more likely to face these problems than companies with one language version, simply because the number of variables, including hreflang, canonicals, internal links, and content quality, multiplies with every additional language. A tool that optimizes GEO and SEO together and adapts using real Search Console data can flag these issues sooner than a quarterly review, because monitoring is continuous rather than occasional.

Get started:

• Whenever you launch a new language version, check that hreflang tags are reciprocal immediately, rather than waiting until the next language is published.
• Compare content length and uniqueness in every language against the source version. A literal machine translation is a risk factor.
• Make each language version accessible through the main navigation, not only through the sitemap.
• For every site change or migration, document the impact on existing hreflang configurations.

Frequently asked questions

How long does it take for a new language version to appear in Google’s index?

It varies widely, but owners of active websites often see results within a few days to a few weeks, depending on crawl budget and site size. If indexing is slow or missing after more than a month, review your hreflang and canonical configuration.

What is the difference between a crawled and indexed language version?

Crawled means Googlebot has visited the page and read its content. Indexed means Google has added the page to the database used to generate search results. A page can be crawled without ever being indexed, for example when its canonical points to a different URL.

Which tools can automate checks for language versions in Google’s index?

Alongside manual checks with the URL Inspection Tool and site: searches, some platforms continuously monitor Search Console data and flag anomalies by language segment. This is useful for brands that publish in multiple languages and do not want to manually review hundreds of URLs every month.

Does every language version need its own ccTLD to be indexed properly?

No. Subfolders such as /fr/ and subdomains such as fr.example.com can work just as well, provided your hreflang implementation is correct and the content is genuinely relevant to the local audience. A ccTLD is one of several signals Google considers, not a requirement (GSC Wizard).

What does it mean when Google chooses a different canonical from the translated page itself?

It means Google does not consider the translated URL to be the primary version to show, usually because there is too much overlap with the source page or because of a technical configuration issue. Fix it by ensuring the translated page’s canonical tag points to itself and making the content sufficiently distinct from the original.

Conclusion

Checking language versions in Google’s index is not a one-time task. It is an ongoing process, especially now that Google has removed the clear International Targeting report and site owners must piece the signals together themselves. Combining the URL Inspection Tool, hreflang validation for reciprocal links, and regular site: searches gives you a realistic view of what Google has actually picked up, rather than what you assume is live. For brands publishing in three, five, or eight languages, the risk rises quickly. Every new language adds technical variables that can each explain why part of your content remains invisible.

If you do not want to check every language version manually each month, but would rather build this into the way your content is published and improved using real Search Console data, book a no-obligation consultation to discuss what this could look like for your international site.

About the company

Launchmind is the AI colleague that writes, checks, and publishes SEO content on your own blog every day, in eight languages, then adapts using real Search Console data. The platform is built for marketing managers, entrepreneurs, and CMOs at small, mid-sized, and scale-up businesses who know content works but do not have the time to create and maintain it consistently themselves.