Evaluate multilingual site and international SEO strategy

[spizeck]

Goal

Evaluate whether Sea Saba should add first-class multilingual content, initially considering Dutch, French, and Spanish, and produce an implementation plan based on actual search/customer opportunity rather than translating the entire site by default.

This issue is primarily an audit and architecture decision. Do not bulk-translate or launch localized routes until the recommended scope and language priority are clear.

Questions to answer

1. Which languages are most likely to provide meaningful value for Sea Saba?
2. Which existing pages should be translated first?
3. What URL/i18n architecture best fits the current Next.js App Router site?
4. How should localized pages be represented to Google and other search/AI systems?
5. How will translations be maintained when English source content changes?
6. Which content should remain English-only initially?

Evidence

Where available, use real evidence such as:

• Google Search Console impressions/clicks by country and query
• current site analytics by geography/language
• existing customer/booking market data if available and appropriate
• current organic search demand

Do not infer that all three candidate languages deserve equal investment merely because they are widely spoken.

Initial candidates:

• Dutch
• French
• Spanish

The audit may recommend a staged order or recommend deferring one or more languages.

Architecture review

Inspect the current Next.js architecture and recommend a maintainable localization approach.

Evaluate:

• locale-prefixed routes such as /nl/, /fr/, /es/
• default English URL behavior
• App Router compatibility
• shared components/navigation/footer
• localized metadata
• localized structured data where appropriate
• localized breadcrumbs
• sitemap generation
• canonical URLs
• hreflang / language alternates, including x-default where appropriate
• language switcher behavior
• preserving deep links/anchors
• redirects and legacy URLs
• analytics attribution across locales
• accessibility and lang attributes
• avoiding duplicate-content/indexing problems

Do not use a client-side automatic-translation widget as the primary localization architecture.

Content scope

Recommend a Phase 1 based on customer value.

At minimum evaluate localization priority for:

• homepage
• Diving
• Dive Sites overview
• Plan Your Trip
• Courses
• Contact
• booking-related guidance / calls to action
• FAQ
• Visiting Yachts

Also classify lower-priority material such as individual dive-site descriptions, historical/editorial content, legal/privacy pages, and operational documentation.

Translation quality

Recommend how translations should be produced and reviewed.

The strategy should account for:

• Sea Saba terminology
• SDI/TDI terminology
• Saba place names
• dive terminology
• safety-critical wording
• booking/cancellation wording
• maintaining the Sea Saba brand voice
• avoiding invented or mistranslated operational claims

Machine/AI assistance may be useful, but customer-facing translations should have an appropriate review process, especially for safety, booking, and legal content.

Maintenance

Define how English content changes propagate into localization work.

Avoid an architecture where translated pages silently become stale.

Consider a lightweight way to identify:

• source content changed
• translation needs review
• translation version/date
• untranslated fallback behavior

SEO requirements for any future implementation

Any implementation plan should include:

• indexable server-rendered localized pages
• unique localized title/description metadata
• correct canonical URLs
• reciprocal hreflang
• sitemap language alternates where appropriate
• correct document language
• no automatic redirect solely from browser language that prevents users/search crawlers from choosing a locale
• no duplicate localized URLs for the same language/content
• Search Console verification plan after launch

Deliverable

Produce a concise architecture/audit document and, if implementation is recommended, create clearly scoped follow-up GitHub issues for staged delivery.

The report should recommend:

1. whether multilingual support is worth implementing now
2. language priority, supported by available evidence
3. Phase 1 page set
4. URL/routing architecture
5. SEO architecture
6. translation/review workflow
7. content-maintenance workflow
8. analytics/Search Console measurement plan
9. estimated implementation complexity and major risks
10. proposed follow-up implementation issues

Acceptance criteria

• Current repo architecture is inspected before recommending an approach.
• Dutch, French, and Spanish are evaluated rather than automatically approved.
• Recommendations distinguish evidence from assumptions.
• Proposed architecture follows modern international SEO practices.
• Phase 1 avoids translating low-value content unnecessarily.
• Translation freshness/maintenance is addressed.
• No production localization changes are made as part of the audit unless they are trivial documentation/tooling prerequisites and explicitly justified.
• Any follow-up issues are independently reviewable and staged.
• Do not merge implementation work automatically.