2025-10-08 · Baduno Editorial Team · 7 blog.readMin · Blog & Knowledge
Using Google Search Console for multilingual websites
The free diagnostic tool shows per language what Google indexes, where clicks happen – and where your versions remain invisible.
Systematic Setup
In addition to the domain property, URL-prefix properties for each language directory (/de/, /fr/…) are worthwhile: reports, sitemap status, and issues can then be read cleanly per market rather than in the overall noise.
The Indexing Report
'Crawled, not indexed' for individual languages indicates quality or duplicate issues; 'Excluded by noindex' indicates technical errors. The report is your early warning system – check weekly per version.
Reading Performance by Country
The performance report with country filter answers the core question of international SEO: Is the correct version ranking in the right market? Impressions without clicks indicate title issues, missing impressions indicate missing relevance or technical problems.
Routine Instead of Firefighting
Monthly per market: indexing, top search queries, Core Web Vitals, manual actions. Fifteen minutes of routine replace the rude awakening after half a year of unnoticed issues.
Detecting Hreflang Errors with URL Inspection
The Search Console no longer offers a separate Hreflang report, but the URL Inspection tool is your tool for troubleshooting. Enter the URL of a language version and click 'Test live' – under 'Advanced Details' you'll see the Hreflang tags recognized by Google. If country combinations are missing or the tool shows different anchor URLs, correct the implementation. Example: Your French page /fr/produkt should link via Hreflang to the German /de/produkt and English /en/produkt. If the backlink from /en/ to /fr/ is missing, a broken chain results. Test randomly for each language, especially after page structure changes. This prevents Google from serving the wrong version or not indexing any at all.
Isolating Indexing Issues per Language
The indexing report often shows overall numbers – but for multilingual websites, you should filter. Create a URL prefix property for each language directory (e.g., example.com/fr/). This lets you see exactly how many pages per version are indexed and where issues like 'Crawled – currently not indexed' or 'Soft 404' occur. A Soft 404 can happen when a language version redirects to a generic error page instead of the appropriate localized version. Check such URLs manually with URL Inspection. Schedule 15 minutes per property monthly to monitor indexing. A sudden 20% drop in indexed pages is a warning sign – often caused by canonical tag errors or faulty robots.txt rules in a language region.
Targeted evaluation of international search queries
The performance report allows you to filter impressions and clicks by country – use this to assess the performance of individual language versions. Pay particular attention to "new" search queries: if a country suddenly appears, does the language version served match? For example, your Italian page ranks for German search terms because no hreflang is set correctly. Correct the tags so that Google makes the correct assignment. Also analyze positions by country: a low average position (< 10) with high impressions indicates relevance problems. Then optimize titles and meta descriptions specifically for each language. Use the "Pages" table to see which URLs are receiving clicks – this often reveals content gaps that can be closed through better localization.
The free diagnostic tool shows per language what Google indexes, where clicks happen – and where your versions remain invisible.
Data-driven prioritization of translations
Performance data from Search Console helps drive the localization workflow. For each language property, export queries with high impressions but low click-through rates. These pages are candidates for optimizing title and meta description. For example, your English page has 10,000 impressions for "project management software" but only a 1% click-through rate. A more precise title like "Agile Project Management Software for Teams" can improve CTR. Conversely, pages with high click-through rates but few impressions show potential for content expansion – have these translated into other languages or expanded. Integrate these analyses into a quarterly review: create a list of the top 20 URLs per market and derive concrete action recommendations (translation, adaptation, new) from them. This turns SEO into strategic localization control.
Sitemap monitoring per language region
Correct sitemap submission is a key success factor for multilingual websites. Create a separate sitemap for each language directory and submit it via the corresponding URL prefix property in Search Console. For example, for example.com/de/, use a sitemap that only contains German URLs. This way, you can see at a glance whether all relevant pages of a language are included and whether errors like "Not found" or "Redirect" occur. Ensure that each sitemap contains only URLs of the respective language version – avoid cross-references between languages in one file. Check sitemap statistics monthly: A decreasing number of submitted URLs can indicate faulty canonical tags or non-indexed translations. Use the "Sitemaps" feature in Search Console to verify that Google was able to fetch the sitemap successfully. If errors like "General HTTP error" occur, it is often a server issue affecting only one language version – for example, a wrong RewriteRule in the .htaccess. Document the sitemap status for each language and compare it with the actual number of pages. This prevents entire language areas from remaining undiscovered.
Monitor internal linking structure
The linking between language versions of your website influences both user guidance and link flow distribution. Use the "Links" report in Search Console to analyze how many internal links point to the most important pages of each language. Filter by a specific URL and check whether the linking pages come from the same language area. A German product page should be predominantly linked from other German pages – not from the English homepage without language assignment. Lacking this consistency, Google may have difficulty assigning language versions. An ideal solution is a language switcher that links alternative versions via hreflang on every page. Spot-check five to ten pages per language: If the "Links" report shows unexpected links from another language area, verify whether the linking language is correct. Example: The French page is linked from a German page that contains no hreflang hint – then Google might assume the wrong version as canonical. Correct such cross-references by either removing the link or introducing a language-specific area. A monthly check of the link structure per language ensures consistency and prevents false language signals from impairing international visibility.
Language-specific sitemaps and crawl budget optimization
Submitting separate sitemaps per language directory helps Google with assignment and improves crawl budget. Create a dedicated sitemap for each language version, e.g., sitemap-de.xml for /de/ and sitemap-fr.xml for /fr/. Reference each individual sitemap in robots.txt, not just one aggregate sitemap. This way, Google sees exactly which URLs belong to which language version and can prioritize crawling. Ensure each sitemap contains only URLs from the corresponding language version and no alternative hreflang references outside that sitemap. Use the hreflang attribute in the sitemap to make language and country association explicit. Crawl budget – the number of pages Google crawls per visit – is especially valuable for large multilingual sites. By using separate sitemaps, you avoid Google crawling duplicate or irrelevant URLs. Monitor crawl statistics per property in Search Console: a low crawl rate on a language version may indicate technical hurdles like slow server response times or blocks in robots.txt. Optimize server response times for each region, e.g., via a CDN with edge servers on location. Also check if you can exclude unnecessary parameter variants that waste crawl budget. Regular alignment between sitemap and indexing report reveals whether all relevant pages of a language version are correctly crawled. After major content updates, plan a resubmission of the sitemap via Search Console to speed up re-indexing.
Faulty redirects and canonical URLs in multilingual setups
Redirects and canonical tags are common sources of errors on multilingual websites, causing Google to index the wrong language version or lose clicks. Check every redirect chain: A chain from /fr/produkt to /fr/produkt-alt to /fr/produkt-neu wastes link equity and can lead to indexing errors. Use direct redirects, ideally with HTTP status code 301. Use the URL inspection tool in Search Console to test the actual redirects delivered. Pay special attention to language redirects based on browser headers or IP addresses: these can cause Googlebot to see a different version than the user. Instead, implement a language switcher without automatic redirects, or use the hreflang tag to clearly mark the content. Canonical URLs must be language-specific: set a self-referencing canonical tag on each language version, e.g., on /de/produkt include the tag with href="/de/produkt". If this is missing or points to another language, duplicate signals arise. Combine this with the hreflang tag so Google recognizes hierarchical equivalence. Use Search Console to look for "Alternative page with proper canonical tag" messages – these indicate conflicts. Also analyze the Google cache of each language version to ensure the delivered URL and canonical tag match. Detailed log file monitoring can further reveal actual redirect paths.
blog.faqT
Can I see in Search Console which Hreflang tags Google actually recognizes?
Yes, use the URL inspection tool for this. Enter a page URL, click 'Test live', and open the advanced details. Under 'Hreflang tags', all tags found by Google are listed. This way, you can check if the references are complete and correct – for example, whether each language version points to itself and to the other versions.
How do I filter the indexing report for a specific language?
For this, you need a URL prefix property that only covers the language directory (e.g., example.com/fr/). In this property, you will only see the indexing of the French pages. Ideally, you create a separate URL prefix property for each language version, in addition to the domain property. This enables language-specific evaluations without data noise.
