The plan in one line: publish the rule engine, the reply desk and the migration path as content, on one domain, in English with German and French where buyers search locally. Every page should be something incumbents cannot copy without changing their legal posture or owning data they lack.
It follows from Search: the read: the EU legal, agency-ops and reply clusters have no sequencer in them (The keyword landscape). And Julian cannot cold email German prospects (Go-to-market plan), so search carries more of the DACH funnel than it would for a US vendor.
Ship fewer than 100 pages in the first quarter. The ruleset and its checker are the flagship. Comparison and migration pages are the traffic. Reply playbooks are the moat.
Clusters to own
| Cluster | Example queries | Language | Flagship asset | Why it is winnable |
|---|---|---|---|---|
| EU law per country | "is cold email legal in France", "Kaltakquise per E-Mail erlaubt", "prospection B2B RGPD" | Local, plus English for every country | /law/<country> pages generated from the versioned ruleset | Owned by Lexware, HubSpot DE, Overloop and GDPR consultancies; no sequencer (The keyword landscape) |
| Agency operations | "cold email tool for agencies", "multi-client reply management" | English | Agency-ops guides plus a per-client cost calculator | Mailshake and EmailBison blogs and Smartlead feature pages; no neutral owner (Lead-gen agencies) |
| Reply handling | "how to respond to not interested", "prospect GDPR access request" | English; DE/FR for legal ones | Reply-situation library (about 150 pages) | No competitor covers the inbox side (Glossaries, template and prompt libraries) |
| Deliverability diagnostics | "Microsoft basic auth SMTP", "GMX WEB.DE spam folder" | English and German | Microsoft readiness checker; DACH mailbox-provider guides | Only 11x has a provider-specific tool, and nobody covers Outlook or DACH providers (Free tools as SEO and lead magnets, Microsoft rules: Outlook.com and Microsoft 365 limits) |
| Migration | "migrate from Smartlead", "EmailBison alternative" | English | Migration guides tied to importers | EmailBison has no alternatives page; Woodpecker's agency panel users chose an EU tool once already (EmailBison: SEO teardown, Woodpecker: search teardown) |
Leave "cold email software" alone for a year: it is a self-ranking contest among vendors with thousands of URLs.
For German recipients the answer to "is cold email legal?" is mostly no: §7(2) Nr. 2 UWG needs prior consent, B2B included (Germany). Write that. A page that says "block" where the law says block makes the rest of the site credible. Never headline "GDPR-compliant cold email" as a blanket claim (GDPR and ePrivacy).
Free tools, in build order
| # | Tool | Input → output | Ship by | Why first |
|---|---|---|---|---|
| 1 | EU legality checker | Recipient country, address type (generic or named), B2B or B2C, existing relationship, sender country → allow / warn / block, legal basis, required notice and footer text, source links | 6 Nov 2026 | It runs on the per-recipient rule engine from The wedge, so the tool is the product demo. Nobody ships one |
| 2 | Microsoft readiness checker | Domain or MX → which mailboxes rely on Basic SMTP AUTH, what changes when it goes default-off at the end of December 2026, what to switch to | 20 Nov 2026 | A dated deadline with search demand before it and support demand after (Microsoft-first outbound) |
| 3 | Reply classifier | Pasted reply → category (interested, not now, OOO with return date, referral, unsubscribe, legal objection), next step, suggested answer | 11 Dec 2026 | It shows the The reply desk in ten seconds to the agency operator, not to a student |
| 4 | List country checker | CSV of company domains → share of the list lawfully emailable per country, run in the browser | Jan 2027 | The agency question behind every client brief (Go-to-market plan). Process the file client-side and keep nothing |
| 5 | Art. 14 notice generator | Sender, source, purpose, language → a localised notice paragraph for step one | Feb 2027 | KASPR was fined €240,000 partly over missing and English-only notices (Data sourcing law) |
SPF/DKIM/DMARC and blacklist checks belong inside onboarding; 14 of 15 tool vendors already ship them.
Rules for every tool page: the verdict is free and ungated; ask for an email only for a PDF audit or a monitoring alert. Put 1,200–1,800 words of explanation under the tool, written from your own data, with FAQPage and WebApplication markup. Expose each tool through the API and MCP server too (AEO playbook: being the answer).
Programmatic plays that are defensible
Google's spam policies target pages made at scale with little value. Each family below answers one query completely from data the entrant maintains.
| Family | Pages (year one) | Built from | Guardrail |
|---|---|---|---|
| Country rule pages | ~33 countries in English; DE, AT, CH in German; FR, BE, LU in French | The versioned ruleset with a source and confidence per row (EU/EEA country matrix) | One page per country, not per sender-recipient pair. Add a pair page only where a court or regulator has ruled on it |
| Reply situations | ~150 | The classifier's taxonomy plus reviewed answer templates | A human-written answer and timing per page; ship each as an n8n/Make template and Claude skill too |
| Integration pages ("reply desk for Smartlead agencies") | ~15 | Working integrations only | No page for an integration that does not exist |
| Benchmarks by country and provider | Quarterly report, then ~20 pages | Design partners' anonymised exports (Reply benchmarks) | Publish a cell only above a minimum sample, and state the method on every page |
| EU agency directory | 20 at launch, opt-in | Partner programme profiles with a GDPR-posture field | Agencies write and approve their own profiles. No rating markup |
Do not build people pages, "[industry] email list" pages, technology lookups, a generic glossary or AI-written "strategy for
Comparison pages that are honest
| Page | Angle |
|---|---|
| Smartlead vs Instantly for agencies running 20+ clients | Per-client cost with dated prices, one concession to each side, what neither does (multi-client replies, recipient-country rules) |
| EmailBison vs Smartlead | Isolation, flat pricing, API surface |
| EmailBison alternatives | The incumbent has no page for this query |
| Smartlead review, from an integration partner | Credible because you sell an overlay on it, not against it |
| Woodpecker alternative for agencies | EU buyers who already chose a European tool |
| "Instantly, Smartlead und die DSGVO" (German) | The legal angle, in the language the legal query is searched in (Comparison and alternatives pages) |
House rules: disclose that you are a vendor and an integration partner; date every price and re-check quarterly; concede something real to each rival; source every claim; no AggregateRating without the reviews on the page. Instantly's, EmailBison's and Amplemarket's pages read as credible because they do most of this.
Site architecture
| Path | What lives there | Note |
|---|---|---|
/ + /de/ + /fr/ | Marketing pages | Locale prefixes only where the body is translated |
/law/, /de/recht/, /fr/droit/ | Ruleset hub and country pages | Changelog and a downloadable JSON/CSV of the ruleset |
/tools/ | Free tools | Results pages noindex, as [[seo-hunter|Hunter]] does |
/replies/, /compare/, /migrate/, /benchmarks/ | Libraries, comparisons, migrations, data reports | Dataset markup on benchmarks, as Smartlead uses |
/help/ | Help centre, indexable | Intercom or Help Scout behind the main domain; Woodpecker moved to a subfolder |
/trust/ | DPA, subprocessors, data location, AVV in German | Procurement document for EU buyers (Subdomain strategy) |
docs., app., api., mcp., status. | Product surfaces | Mintlify docs with llms-full and OpenAPI; wildcard certificates; staging behind auth |
One domain, not six: the Forge splits authority across six blogs (Salesforge and the Forge: SEO teardown). Pick a brand that cannot collide with an adverb or a consumer product, as Instantly's and PlusVibe's do (Affiliate and review-site SEO). Give tenant hosts opaque IDs under a wildcard certificate, so certificate logs do not publish the customer list as EmailBison's do.
i18n done properly. lemlist, Clay and Salesforge all serve English bodies under lang="de" or lang="fr" URLs. Do the opposite:
- Publish a locale URL only when a native speaker has reviewed its body.
- Self-referencing canonicals per locale, reciprocal
hreflangplusx-default, and alangattribute that matches the text. - Localise what people search locally: law, reply handling, the Microsoft and DACH-provider guides, the top 20 help articles, EUR pricing. Keep comparison and product pages in English, as Dutch, French and Spanish buyers search (The keyword landscape). Use the searched terms: Kaltakquise, Abmahnung, prospection, RGPD.
The 90-day calendar
Aligned with The first 90 days (12 October 2026 to 10 January 2027). Pages are written by people with data: 8–12 pieces a month plus tools.
| Weeks | Dates | Ship | Pages |
|---|---|---|---|
| 1–2 | 12–25 Oct | Robots and sitemaps, generated llms.txt and pricing.md, Search Console and Bing, rank tracker (40 queries, EN/DE/FR), AI prompt baseline, one month of Ahrefs or Semrush for DE/FR/NL/ES volumes | 5 |
| 3–4 | 26 Oct–8 Nov | Ruleset v1 public; /law/ hub and 10 country pages (UK, IE, FR, DE, AT, NL, BE, SE, ES, IT); DE pages in German; legality checker by the 6 November gate | 14 |
| 5–6 | 9–22 Nov | Microsoft readiness checker plus two guides; "Smartlead vs Instantly for agencies"; "EmailBison alternatives" | 6 |
| 7–8 | 23 Nov–6 Dec | 30 reply playbooks; integration pages for Smartlead, Instantly, EmailBison; first weekly "EU Agency Office Hours" transcript (Content engines) | 35 |
| 9–10 | 7–20 Dec | Reply classifier with the desk launch on 11 December; migration guides from Smartlead, Instantly, Woodpecker; FR country pages; the German DSGVO comparison | 8 |
| 11–13 | 21 Dec–10 Jan | Remaining country pages in English; 50 help articles for multi-client setup; first review of what ranked; brief the Q1 benchmark | ~70 total, plus help |
Q1 2027: reply library to 150, tools 4 and 5, the first benchmark, and the agency directory when the partner programme opens in March.
Measurement
| Layer | Metric | Source | Check |
|---|---|---|---|
| Visibility | Impressions and clicks per cluster (path regex), per locale | Search Console, Bing Webmaster Tools | Weekly |
| Position | 40 fixed queries × EN/DE/FR | Rank tracker | Weekly |
| Tools | Runs, result-to-signup rate, alerts subscribed | Product analytics | Weekly |
| Pipeline | Pilot requests with an organic or tool first touch; "how did you hear" with search and AI options | CRM | Monthly |
| AI answers | Named, cited, position across a fixed prompt panel | See AEO playbook: being the answer | Monthly |
Day-90 targets (my estimates, not benchmarks): every country page indexed; five pilot requests with a tool or law page as first touch; top-10 positions for three migration or comparison queries. If nothing in German ranks by day 90, check indexation and hreflang before writing more.
No absolute volumes exist for the German, French or Dutch legal terms (The keyword landscape). The paid keyword data bought in week one is there to resize this calendar.
What this means for an entrant
- Publish the ruleset before the product is finished. It is the flagship page, the first free tool and the source the AEO work points to (EU/EEA country matrix).
- Treat migration and comparison pages as the traffic plan. The incumbents do not write them about themselves.
- Build the reply library as product. Each playbook is also a classifier label, a template and an importable workflow for the The reply desk.
- Get i18n right once. Real translations with hreflang, on the clusters searched locally, beat three locales of English duplicates.
- Measure by cluster and prune by quarter. The site should get smaller where pages earn nothing.