Operational Template
Locale SEO Brief Template
Every new locale should begin with one brief that locks audience, search intent, metadata, route scope, and QA expectations before publish.
Brief Identity
Start with ownership and market definition.
A locale brief should capture the locale code, region, product surface, release target date, and named owner before any writing starts.
This ensures the team is aligning on a market, not just a translation request.
- Locale code and language tag
- Regional market and target users
- Product surface and route scope
- Owner and reviewer
Search Intent
Plan keyword intent by route, not by page title alone.
Each route needs a primary keyword cluster, supporting semantic terms, audience definition, and expected CTA.
The brief should separate informational, navigational, documentation, and partnership intent clearly.
- Primary keyword cluster per route
- Supporting semantic terms
- Audience and CTA per route
- Internal linking targets
Metadata Pack
Lock the metadata before the page ships.
Every indexable route should leave the brief with a planned H1, title, meta description, canonical, alternate locale map, and schema language.
This avoids a last-minute scramble that leads to duplicated or weak metadata.
- H1 per route
- Title and description per route
- Canonical URL
- Alternate locale map and schema language
QA Gates
A locale does not publish without proof.
The brief should define the pre-publish checks for localized copy, metadata, hreflang, sitemap, locale manifest, and live verification.
Evidence links should point to preview URLs, screenshots, and release notes.
- Preview URL and QA notes
- Screenshots for affected routes
- Approval fields for content, SEO, QA, and product
- Explicit release decision
Next step
Read source markdown
Use the HTML page for browsing and the source markdown for locked reference and audit trails.
Related