Lingua Detective vs Google Cloud Translation detectLanguage: whole-site verdicts, not a text-blob score
Verdict: Google Cloud Translation's detectLanguage is a reliable, well-documented way to detect the language of a piece of text you already have in hand, and it covers 100+ languages on Google's own infrastructure. It was never built to tell you whether a *website* is actually serving the right language on every page — that takes crawling, rendering, and a verdict per URL, which is what Lingua Detective does instead. Pick based on the job: detecting a string vs. auditing a site.
| Google Cloud Translation detectLanguage | Lingua Detective | |
|---|---|---|
| What it is | Managed API that detects the language of a text string | Site crawler + language-verdict engine for multilingual sites |
| Setup | GCP account, billing, API key or service account | None — first 20 pages free, no account or card |
| Pricing | ~$20 per 1M characters | $0.015 → $0.006/page in bulk, or $0.002/call via pay-per-call API |
| Privacy / offline | Text is sent to Google's servers for processing | Offline detection engine — page text never leaves to a third party |
| Output | Language code + confidence for a text blob | Per-page pass/fail verdict across the whole site, with optional AI arbitration |
| Best for | Detecting the language of arbitrary strings inside your own app | Auditing whether a live multilingual site is actually correct, page by page |
Pick Google Cloud Translation detectLanguage if…
- You need to detect the language of arbitrary text inside your own app in real time — user input, chat messages, support tickets.
- You're already on GCP and want detection billed alongside Translate, NLP, and your other Google Cloud usage.
- You need enterprise SLAs and official support behind every call.
- Your use case is a single string at a time, not whether an entire website is correct end to end.
- You're comfortable sending the text itself to Google's servers for processing.
Pick Lingua Detective if…
- You want to know which *pages* of a live site are wrong, not just the language of a string you already extracted.
- You don't want to open a GCP project, attach a credit card, or manage API keys for an audit you might run once a quarter.
- Keeping page text out of third-party hands matters to you or your client.
- Your site is JS-rendered, and you need real Chromium rendering to see what a visitor actually sees before detecting anything.
- You want a report with a verdict per page, not a set of language codes you still have to interpret and map back to URLs.
Pricing math
Auditing a 500-page multilingual site:
- detectLanguage: you first need your own crawler and renderer to pull representative text off each page, then send it to the API. At roughly 1,500 characters per page after stripping nav and footer boilerplate, that's 500 × 1,500 = 750,000 characters, about $15 at ~$20 per million characters — and that only covers the API calls, not the crawler, the renderer, or the logic that turns an
frvs.enresult into a pass/fail verdict. - Lingua Detective: 500 pages = 200 pages × $0.015 + 300 pages × $0.010 = $3 + $3 = $6, crawling, rendering, and verdicts included. Add spider crawling at +$0.005/page (+$2.50) if you want Lingua Detective to discover the URLs itself instead of supplying them.
FAQ
Q: Does detectLanguage tell me which pages of my site are wrong?
No — it only returns a language code for text you send it; you'd still build the crawling and page mapping yourself.
Q: Is Lingua Detective's offline engine as accurate as Google's API?
For clear-cut text, comparable. Ambiguous or mixed-language pages get an optional AI arbitration pass before a verdict ships.
Q: Do I need a GCP account or credit card to try Lingua Detective?
No — the first 20 pages are free, no account or card required.