CrawlCheck

Findings · 2026-09-30 · By · 1 view

CrawlCheck in German, French, Spanish and Portuguese

The main pages and every scan report are now served under /de/, /fr/, /es/ and /pt/. What is translated, what stays English by design, and how each page declares its language.

crawlcheck.io serves its home, pricing, how-it-works, tools and notice pages, and every scan report, in German, French, Spanish and Portuguese under /de/, /fr/, /es/ and /pt/. The blog, guides, report JSON and machine-readable files stay in English, finding codes and crawler names are never translated, and there is no redirect by IP address or browser language. Each translated page declares its language, a canonical to itself and hreflang links to every alternate, with x-default pointing to English.

What is translated, and why
Home, pricing, how it works, tools, notice
DE / FR / ES / PT
translated
Why
the pages people decide on
Scan report
DE / FR / ES / PT
translated, including figure titles
Why
the product
Report JSON and machine-readable files
DE / FR / ES / PT
English; translated paths redirect to it
Why
read by software
Blog and guides
DE / FR / ES / PT
English
Why
written once, cited by URL
Finding codes, crawler names
DE / FR / ES / PT
never translated
Why
identifiers, not words
Language choice
DE / FR / ES / PT
URL prefix only
Why
no IP or browser-language redirect

crawlcheck.io now serves its main pages and every scan report in German, French, Spanish and Portuguese, at /de/, /fr/, /es/ and /pt/. This note says what is translated, what deliberately is not, and how each page tells search engines which version is which.

What is translated? #

Since 25 September 2026: the home page, pricing, how it works, the free tools page and the notice about the two unrelated sites with similar names. Since 26 September: every scan report, with translated section headings, finding titles, explanations and fix text, and the titles inside its figures. A scan started from a translated page lands on the translated report. The language switcher is in the footer of every translated page and of the English original.

SurfaceDE / FR / ES / PTWhy
Home, pricing, how it works, tools, noticetranslatedthe pages people decide on
Scan reporttranslated, including figure titlesthe product
Report JSON and machine-readable filesEnglish; translated paths redirect to itread by software
Blog and guidesEnglishwritten once, cited by URL
Finding codes, crawler namesnever translatedidentifiers, not words
Language choiceURL prefix onlyno IP or browser-language redirect

Why do some things stay English? #

Machine-readable output is read by software, and a second vocabulary would make every consumer's parser handle five. Finding codes and crawler names are identifiers, so GPTBot is GPTBot in every language. And there is no redirect by IP address or browser language: a German visitor who types the English URL gets the English page, and the page head tells engines which four alternates exist.

How does each page declare its language? #

Every translated page sets <html lang> to its language, a canonical to itself, and hreflang links to the English original, the other three languages and an x-default pointing to English. Internal links point at the translated version of a target where one exists and at the English page where it does not, and a request for a translation that does not exist is redirected to English rather than served half-translated. The translated URLs are in the sitemap. If you run a multilingual site, the hreflang audit guide covers the return-link and x-default errors this setup avoids.

What was hard, and what is next? #

Chart labels had to be translated and still fit their figures, and grade words in page titles needed their own handling. Each language was reviewed independently before it shipped, and the review found real errors, which is why it exists. The open question is whether the guides follow: a guide is cited by URL and a translated copy splits the citations, so the traffic to the translated pages will decide it. Everything else that changed that week is in the 29 September release notes; how to read a report in any language is in the report guide.

Live, as you read this: the corpus now holds 570,959 domains across 9,163 scans. The figures in this piece were measured on the date above; this line is not.

CrawlCheck’s dataset when this page loaded: 570,959 sites measured.

Share this finding:LinkedInXEmailFollow Emmanuel on LinkedIn

Questions this post answers

Which CrawlCheck pages are available in German, French, Spanish and Portuguese?

The home page, pricing, how it works, the free tools page, the not-affiliated notice and every scan report, under the /de/, /fr/, /es/ and /pt/ prefixes. The blog and guides stay in English.

Does crawlcheck.io redirect me based on my location or browser language?

No. Language is chosen only by the URL prefix, and a footer switcher links the alternates. hreflang links in the page head tell search engines which versions exist.

Why is the report JSON not translated?

It is read by software, so every consumer should parse one vocabulary. A request for a translated JSON path is redirected to the English JSON. Finding codes and crawler names are identifiers and are never translated.

Will the guides be translated?

Not decided. A guide is cited by URL and a translated copy would split citations; traffic to the translated pages will decide it.

Related findings

The main product

Found this on your own site? We fix it for $100.

Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.

Free browser extension

Check this on any site you open, without leaving the page.

CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.

Write for the library

Measured something yourself? Submit an article.

Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.

Submit an article

How it works · a reply within about a week

Spotted a mistake or a bug on this page? Report an error. Confirmed errors are fixed and logged on the corrections page.

Comments

Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain (how). Those appear at once, marked verified.

Writing about this? Facts, live figures and marks — every number on that page is dated and traceable to a scan.

All findings · The dataset · How the dataset works