30 lines
1.6 KiB
Markdown
30 lines
1.6 KiB
Markdown
# Localized SEO hreflang Strategy TODO
|
|
|
|
## Goal
|
|
Establish a consistent canonical and hreflang setup for the marketing site so search engines can index German and English content without duplicate-content penalties.
|
|
|
|
## Status (Stand 17.02.2026)
|
|
- **Discovery:** Not started.
|
|
- **Implementation:** Not started.
|
|
- **Validation:** Not started.
|
|
|
|
## Discovery
|
|
- [ ] Audit current route map and localized content coverage (marketing pages, blog, checkout flow).
|
|
- [ ] Decide on URL strategy (session-based locale vs. language-prefixed routes) and document migration implications.
|
|
- [ ] Identify required updates to `MarketingLayout`, sitemap generation, and Inertia responses for localized alternates.
|
|
|
|
## Implementation
|
|
- [ ] Ensure canonical URLs and hreflang tags are generated per locale with reciprocal references.
|
|
- [ ] Expose locale-specific URLs in navigation, Open Graph tags, and any structured data.
|
|
- [ ] Update translation files and config to support the chosen URL strategy.
|
|
|
|
## Validation
|
|
- [ ] Add automated checks (feature test or Playwright) verifying hreflang/canonical tags for both locales.
|
|
- [ ] Validate via Search Console-style inspection or lighthouse to confirm alternate links render correctly.
|
|
- [ ] Update docs (PRP + marketing playbooks) with the final hreflang strategy and operational guidance.
|
|
|
|
## Open Questions
|
|
- Should blog posts use language-specific slugs or shared identifiers with query parameters?
|
|
- How will we handle locale fallbacks for missing translations when hreflang is enforced?
|
|
- Do we need localized sitemap indexes per language or a unified sitemap with hreflang annotations?
|