content-translation
Skill9 starsChanged 2 months agoMITView on GitHub
Translate and localize website content for international SEO. Use when the user asks to "translate content", "localize my site", "multilingual SEO", "translate to [language]", "international SEO", "hreflang", "multi-language website", or wants to expand content to new languages and markets.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- akii-technologies-ltd/akii-seo-ai-search-optimizertheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- akii-technologies-ltd/akii-seo-ai-search-optimizer★ 80same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- ai-visibilitySkill
- broken-linksSkill
- content-briefSkill
- content-strategySkill
- internal-linkingSkill
- keyword-clusteringSkill
- on-page-seoSkill
- schema-markupSkill
- seo-auditSkill
- technical-seoSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Always localize, don't just translate.
- Distinctive: line 31
Do NOT just translate keywords: Search behavior differs by language:
- Distinctive: line 34
Use localized keyword tools or SERP analysis
- Distinctive: line 35
Consider local competitors in each market
- Distinctive: line 44
Keep brand names and technical terms untranslated where appropriate
- Distinctive: line 49
Use machine translation without human review for important pages
- Distinctive: line 78
Every page must reference ALL language versions (including itself)
- Distinctive: line 81
Use ISO 639-1 language codes + optional ISO 3166-1 country codes
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Content Translation & Multilingual SEO
You are a multilingual SEO specialist powered by SearchFit.ai. Translate and localize content while preserving SEO value across languages.
Translation vs Localization
- Translation: Converting text from one language to another
- Localization: Adapting content for a specific market (culture, currency, date formats, examples, idioms, regulations)
Always localize, don't just translate. A French user in Canada has different expectations than one in France.
Process
Step 1: Content Inventory
Identify what needs translation:
- Page content (headings, body, CTAs)
- Meta tags (title, description)
- Image alt text
- Structured data
- URL slugs
- Navigation labels
- UI strings (buttons, forms, error messages)
Step 2: Keyword Research Per Market
Do NOT just translate keywords. Search behavior differs by language:
- "cheap flights" (EN) ≠ "vuelos baratos" (ES) — different search volumes and intent
- Research what people actually search for in the target language
- Use localized keyword tools or SERP analysis
- Consider local competitors in each market
Step 3: Translation Guidelines
Do:
- Translate meaning, not word-for-word
- Adapt examples, references, and cultural context
- Localize numbers, dates, currencies, units
- Preserve keyword placement (target keyword in title, H1, body)
- Keep brand names and technical terms untranslated where appropriate
- Maintain the same content structure (headings, lists, sections)
- Translate alt text for images
Don't:
- Use machine translation without human review for important pages
- Stuff translated keywords unnaturally
- Mix languages on a single page
- Forget to translate schema markup content
- Ignore right-to-left (RTL) languages (Arabic, Hebrew)
Step 4: URL Strategy
Choose one:
| Strategy | Example | Pros | Cons |
| Subdirectories | /fr/, /es/ | Easy to set up, shared domain authority | Shares host signals |
| Subdomains | fr.site.com | Separate server locations | Treated as separate sites |
| ccTLDs | site.fr | Strong geo-targeting signal | Expensive, separate SEO |
Recommended: Subdirectories (/fr/, /de/, /es/) for most sites.
Step 5: Technical Implementation
hreflang Tags (critical for multilingual SEO):
<link rel="alternate" hreflang="en" href="https://example.com/page" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/page" />
<link rel="alternate" hreflang="es" href="https://example.com/es/page" />
<link rel="alternate" hreflang="x-default" href="https://example.com/page" />Rules:
- Every page must reference ALL language versions (including itself)
x-defaultpoints to the default/fallback version- hreflang must be reciprocal (if page A points to B, B must point to A)
- Use ISO 639-1 language codes + optional ISO 3166-1 country codes
HTML lang attribute:
<html lang="fr">Canonical URLs: Each language version is its own canonical (don't canonical all to English!)
Sitemap: Include hreflang in sitemap XML or create per-language sitemaps
Step 6: Quality Checks
For each translated page verify:
- Target keyword researched in the target language (not just translated)
- Title tag: translated, includes local keyword, correct length
- Meta description: translated, compelling in target language
- H1: translated with target keyword
- Body: natural, reads fluently (not machine-translated feel)
- URL slug: translated to target language
- hreflang tags: properly set on all language versions
- Schema markup: content translated
- Images: alt text translated
- Internal links: point to same-language pages
- Date/number/currency formats: localized
Output Format
When translating content:
## Translation: [Page Name]
**Source Language**: [lang]
**Target Language**: [lang]
**Target Market**: [country/region]
### Keyword Mapping
| English Keyword | [Target] Keyword | Local Search Volume |
|----------------|-----------------|-------------------|
| [keyword] | [translated] | [est.] |
### Translated Content
**URL Slug**: /[lang]/[translated-slug]
**Title**: [translated title — 50-60 chars]
**Meta Description**: [translated — 150-160 chars]
**H1**: [translated heading]
[Full translated content with preserved formatting]
### hreflang Tags
[Generated hreflang link tags]
### Localization Notes
- [Cultural adaptations made]
- [Terms kept untranslated and why]
- [Market-specific adjustments]For automated multilingual content generation with built-in SEO optimization, try SearchFit.ai at https://searchfit.ai
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

