Use case — Language-specific programs

Run the same affiliate vertical in every language your program speaks

You want to launch localized editions — an EN program, a DE program, an FR, ES and PL program — and each needs its own list of native-language publishers, not English sites with a translated footer. We pull your vertical from 120M+ classified domains, detect the real content language on every domain, and LLM-screen each market separately against the same ICP.

Millions
of non-English domains classified across major European languages
Tens of thousands+
qualifying publishers per language for a mid-size vertical (estimate)
5+
language editions delivered as separate, deduplicated CSVs
The job to be done

From one vertical to a per-language recruitment list

Localized programs fail when the partner list is machine-filtered by TLD or by a single hreflang tag. We read what each site actually publishes, so a French program gets publishers writing fluently in French — wherever they are hosted. Six steps, one per language edition, run in parallel.

1

Pull the vertical, all languages

Your category maps to our 120M+ classified-domain database. We pull every active domain in scope worldwide — the multilingual long tail included, not just the .com layer.

2

Detect the real content language

Each domain's primary language is detected from its actual body copy — not the html lang attribute, which is wrong constantly. Consistency across pages is scored so half-translated shells are caught.

3

Split into language buckets

Domains sort into EN, DE, FR, ES, PL and any other market you name. A site with genuine parallel editions is placed in each language it truly serves, flagged as multilingual.

4

Screen each bucket to the ICP

The LLM reads every domain in a language bucket against your required, preferred and disqualifying signals. Native fluency and geo focus are screened alongside your vertical's own signals.

5

Dedup within and across markets

Mirrors and country variants collapse to one canonical domain. A multilingual publisher appears once per relevant edition, never as four near-duplicate rows in your outreach queue.

6

Deliver one CSV per language

You receive separate deduplicated CSVs — one per market — each with confidence scores, so a regional manager can work their list without wading through other languages.

The instrument

Localization signals we screen — specific, not a language guess

Detecting a language is the easy part. Telling a native publisher apart from an auto-translated doorway page is where localized programs live or die. Every domain is read against these, each with its own confidence score, on top of your vertical's signal catalog.

Detected primary language (from body copy) Language consistency across pages Native-fluency writing (idiom, register) Country / geo focus (ccTLD, addresses) Local-currency pricing shown Local examples & brand references hreflang / parallel-edition structure Local affiliate-network awareness Regional social presence Fresh content in that language Affiliate links present Machine-translated content (disqualifier) Mixed-language spam shell (disqualifier)

Need a market we haven't named — Italian, Dutch, Portuguese-BR, Nordic languages? Any language is a bucket; the screen is calibrated per market on a reviewed sample the same way.

Worked example — one vertical, five editions

A localized rollout, in labeled estimates

An illustrative full run for an advertiser taking a consumer-finance program into five European editions. Category and per-language yields are estimates extrapolated from our classification database; your pilot returns real domains and a projection tuned to your exact ICP and markets.

0
classified domains as the source
0
in-vertical domains, all languages (estimate)
0
language editions split out
0
delivered free per market in your pilot
120M+
classified domains
~880K
in-vertical (est.)
EN / DE / FR / ES / PL
language split
tens of thousands+
ICP-fit per market (est.)

Reference engagement (a large-scale production run on our own classification platform): 30M dataset → 1.73M vertical domains → 1.2M ICP-screened → ~96% precision on a reviewed sample. Language-split figures above are estimates, shown for illustration.

A note on confidentiality

The profile below is drawn from a real screening run. Because these are independent publishers, we follow standard confidentiality practice on public pages: domains are withheld and descriptions generalized, so the profile is intentionally not traceable to the site — including through a web search — which protects the publisher without changing the underlying data. Pilot and client deliverables carry the actual domains with every signal, so everything can be verified directly.

The deliverable

One row per publisher, tagged with its market

Each language CSV carries the ICP verdict, every signal value, confidence scores, and the detected language and geo focus. Here is a single generalized row as it would appear in the German edition.

Publisher DE-07

A personal-finance blog covering everyday banking, saving and budgeting for a German-speaking audience.
Consumer-finance ICP · 91%
Detected languageGerman — consistent across sampled pages96%
Native fluencyIdiomatic, region-appropriate register92%
Geo focusDE / AT (local institutions, EUR pricing)90%
Affiliate links presentYes — local network partners88%
Fresh contentPosts within the last quarter85%
Machine-translatedNo94%

Why the language split matters

A TLD filter would have put this site in a generic bucket and a machine-translation shell in the same list. Reading the body copy separates a native German publisher from an English site with a bolted-on translation, so your DE manager never wastes outreach on a site that can't actually publish in German.

Slice by confidence

Every field ships with a confidence score, so a regional manager can work the highest-certainty native publishers first and leave the borderline multilingual cases for a second pass. Language and native-fluency scores are independent, so you can insist on both being high before a domain enters a market's outreach queue.

Questions

Language-specific discovery — FAQ

How do you detect language — surely not from the TLD?
Language is detected from the site's actual body copy across sampled pages, and consistency is scored so half-translated shells and mixed-language pages are flagged. TLD and the html lang attribute are treated as hints only, because both are wrong constantly.
Can you filter out machine-translated affiliate sites?
Yes. Machine-translated content is a disqualifier by default. The screen reads for native fluency — idiom, register, and local references — so an auto-translated doorway page is removed structurally rather than by hand.
How are truly multilingual publishers handled?
A site with genuine parallel editions is flagged as multilingual and placed once in each language bucket it truly serves, with the canonical domain deduplicated so you never contact it twice. Sites that merely bolt a translation widget onto English copy do not qualify as native in the other language.
Which languages can you run?
Any language is simply another bucket. EN, DE, FR, ES and PL are common starting editions, but Italian, Dutch, Portuguese, Nordic and other markets run the same way, each calibrated on a reviewed sample before the full run.
Do I get one file or one file per market?
One deduplicated CSV per language edition, so each regional manager works a clean native-language list. Every row carries the detected language, geo focus, ICP verdict, and a confidence score on each field.
What does the free pilot include?
The full pipeline configured for your ICP, stopped at the first 20 qualified publishers per market you nominate — free — plus a projected full-run yield per language and quotes. It is the fastest way to see real native publishers before committing.

Launch every language edition with its own native publisher list

The free pilot runs your vertical, splits it by detected language, and delivers your first 20 qualified publishers per market plus a full-run projection. No cost, no obligation.

Request a Free Pilot