Abnormal is hiring French- and Dutch-speaking SDRs and AEs in the Netherlands, Sweden and Japan, and has translated 71 pages into five languages. But each translated page tells search engines it is a copy of the English page: /fr/platform/email-security and /de/platform/email-security both point their canonical tag at the English URL, the German and Japanese homepages point at the English homepage, and titles and descriptions are still English. A French CISO searching in French is likely to be shown the English page, or nothing.
First action
Change the canonical template for localized routes.
How to measure it
Search clicks to /fr, /de, /es, /pt, /ja pages
- Now
- –
- Target
- 3x
- By
- 90 days
Steps
Fix the canonical template
Localized routes point to themselves on abnormal.ai.
Web Engineering Lead 1 day
Add hreflang in the head
Same alternates as the sitemap, x-default to English.
Web Engineering Lead 1 day
Translate titles and descriptions
All 355 localized pages.
International Marketing Lead 1 week
Validate
Crawl the five locales and test with Search Console.
Web Engineering Lead 2 days
Track by country
Impressions and clicks per locale.
Digital Marketing Lead weekly
Add Dutch
The ten pages Dutch SDRs link to most.
International Marketing Lead 1 month
Brief sales
Localized links for outreach in each region.
Senior Manager, Demand Generation Operations 1 day
Why it works
Give every localized page a self-referencing canonical on abnormal.ai, add matching hreflang links in the page head (the sitemap already lists them), and translate the title and meta description for all 355 pages. Then check Search Console by country, and add Dutch versions of the ten pages the new Dutch SDRs send most.
The translation work is already done; a template fix lets it earn local-language search traffic and gives the international sales team pages that look local in search results and link previews.
Ready to use
ChecklistLocalized SEO fix list
[ ] Canonical on each localized page points to itself [ ] Canonicals use abnormal.ai, not www [ ] hreflang en, fr, de, es, pt, ja, x-default in the head [ ] Translated <title> and meta description [ ] Translated Open Graph text [ ] Search Console checks per country [ ] Dutch versions of the top ten outreach pages
Risks and how to handle them
English pages lose some traffic
hreflang sends each searcher to their language, so total traffic grows.
Machine-translated metadata reads badly
Have regional sellers review the top 20 pages.
Evidence
- Your websiteLocalized site (checked October 21, 2026): 71 pages each under /fr, /de, /es, /pt and /ja, listed in the sitemap with hreflang alternates. On every localized page checked, the canonical tag points to the English page (for example /fr/platform/email-security and /de/platform/email-security both declare https://www.abnormal.ai/platform/email-security; /de and /ja declare https://www.abnormal.ai), and the <title> and meta description stay in English while the body is translated (French H1: "La plateforme de sécurité e-mail moderne pour l'ère de l'IA"). There are no Dutch, Swedish or other Nordic pages; customer stories and the blog are English only.Source
- HiringInternational hiring: Sales Development Representatives, Dutch Speaking (posted October 19, 2026) and French Speaking (September 18), each "Fluency in Dutch is a must" / French; Enterprise Account Executives in the Netherlands (October 5), Sweden and Japan; a Senior Channel Account Manager, Nordics ("our partner ecosystem is one of the fastest-growing engines"; recruit partners with "our Nordics distributor"); Customer Solutions Engineers in the UK and Ireland; a Portuguese-speaking Professional Services Consultant; AI Security Sales Executives in the UK and Australia (October 20).Source
- Your websiteEvery page checked declares its canonical on https://www.abnormal.ai/..., and that host answers with a 308 redirect to https://abnormal.ai/, which is the address the sitemap lists.Source
- Your websiteThe "Refer a Peer" page: "The strongest recommendation in security isn't a demo. It's a peer." A public page in the AI transformation section describes how marketing operations built an automated workflow to translate Japanese form submissions in Marketo, which previously waited "roughly a week" for a human translation service before reaching Salesforce.Source