# Localization Notes

## Purpose

English should remain the source language for product meaning, SEO direction, and reusable website copy. Future localized versions, including German, should stay close to the source meaning and avoid loose paraphrasing.

## Sections That Should Always Be Translated

- Home page headline, subheadline, and supporting copy
- Feature page titles, meta descriptions, H1s, intros, and FAQs
- FAQ answers
- Product summaries
- Use case sections
- SEO-facing explanatory copy that appears on public pages
- Pricing, support, privacy, and contact page copy
- CTA labels and helper text
- Error or empty-state text if exposed on the website

## Terms That Should Stay Consistent

- Petlytics
- iOS
- iPhone
- App Store
- Feature page slugs unless the site later supports localized URLs
- Any approved role names once product translations are finalized

## What Not to Auto-Translate Loosely

- Do not translate `family sharing` in a way that suggests Apple Family Sharing if the page means Petlytics shared access
- Do not blur the difference between `reminders` and `notifications`
- Do not translate AI-related wording in a way that suggests diagnosis, treatment, or clinical certainty
- Do not replace `timeline` with different words on each page; choose one approved translation and keep it consistent
- Do not switch between different translations of `shared care` without a glossary decision
- Do not improvise translations for role names such as owner, editor, executor, or viewer without product approval
- Do not turn concise product copy into broader claims during translation

## Glossary Candidates

- pet care
- feeding
- medication
- weight
- reminder
- notification
- timeline
- care history
- shared care
- family sharing
- multi-pet household
- pet sitter
- roles and permissions
- AI insight
- AI hint
- AI recommendation
- informational guidance
- owner
- editor
- executor
- viewer

## German Localization Notes

- Decide early whether the site should prefer `Haustierpflege` or `Tierpflege` and use one consistently
- Decide one translation for `timeline`, such as `Verlauf` or `Chronik`, and keep it stable across the site
- Translate `pet sitter` consistently; do not alternate between several informal variants
- Check whether role names should be translated functionally or kept closer to the English product vocabulary
- Keep meta titles and descriptions concise enough for search results after translation

## Process Notes

- Build a small approved glossary before translating landing pages
- Reuse the English content structure so localized pages stay aligned with the source
- Review translated FAQ entries for clarity and directness, not just literal accuracy
- Re-check internal links, structured data, and metadata after localization