skills.rest
marcogonzalo
marcogonzaloCOMMUNITY
Explore all skills by this author →
Website𝕏@MarcoGonzaloGitHub

veta-multilanguage-views

Fix locale routing and SEO metadata for next-intl marketing views.

1|Updated Nov 26, 2025
Search Tags:#i18n#sitemap#seo#next-intl#canonical urls#language toggle#marketing routes
One-click install
npx skills add https://github.com/marcogonzalo/studio-manager --skill veta-multilanguage-views
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: veta-multilanguage-views
Source: https://github.com/marcogonzalo/studio-manager/tree/main/.agents/skills/veta-multilanguage-views
Command: npx skills add https://github.com/marcogonzalo/studio-manager --skill veta-multilanguage-views

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves broken multilingual navigation and inconsistent SEO metadata by ensuring every marketing route has correct locale-aware slugs, canonical URLs, and discoverability controls.

Core Features & Use Cases

  • Correct translated slugs & language switching: Ensures navigation between EN/ES lands on the canonical URL for each locale (including default-locale “as-needed” behavior without redundant prefixes).
  • Production-ready SEO metadata: Implements canonical, hreflang/language alternates, and Open Graph URL consistency per marketing page using localized paths.
  • Sitemap and robots hygiene: Updates sitemap inclusion for indexable routes only and excludes dev-only routes so they are not indexed.
  • Real-world use case: When a marketing page like “Pricing” uses translated slugs and the user switches from /en/pricing to Spanish, the toggle must route them to /precios (not an incorrect prefixed default-locale variant), while canonical metadata and sitemap stay consistent.

Quick Start

Update src/i18n/routing.ts, wire the home page into the shared marketing layout, then implement per-page generateMetadata for the marketing routes and update src/app/sitemap.ts plus the language toggle to navigate to canonical localized URLs.

Frequently Asked Questions about veta-multilanguage-views

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix canonical URLs and hreflang metadata for next-intl marketing routes?▼

To fix canonical URLs and hreflang metadata for next-intl marketing routes, implement per-page generateMetadata functions that define canonical, language alternates, and Open Graph URLs using localized paths. This ensures search engines index the correct locale-specific pages.

Why does my next-intl language toggle route to the wrong URL when switching locales?▼

Your next-intl language toggle routes incorrectly because it lacks deterministic destination resolution. You must configure the toggle to resolve translated slugs to canonical localized paths, switching from `/en/pricing` to `/precios` rather than an incorrect prefixed variant.

How do I generate a multilingual sitemap with next-intl while excluding development routes?▼

Generate a multilingual sitemap with next-intl by updating `src/app/sitemap.ts` to output index-only routes for both EN and ES locales. Configure the generation logic to exclude dev-only routes so they remain undiscoverable by search engines.

Does next-intl support as-needed default locale prefixing for SEO?▼

Yes, next-intl supports as-needed default locale prefixing for SEO. You must configure source-of-truth locale routing in `src/i18n/routing.ts` to implement this behavior, removing redundant prefixes from the default locale URLs while keeping others intact.

What is the best way to handle translated slugs in a Next.js bilingual marketing site?▼

The best way to handle translated slugs in a Next.js bilingual marketing site is configuring source-of-truth locale routing with deterministic language switching. This maps translated paths accurately between EN and ES, maintaining canonical URL consistency across navigation.

Related Skills

Explore More Software Engineering Skills→
marcogonzalomarcogonzalo
1

veta-marketing-i18n-content

Validate ES and EN marketing page localization, routing, and SEO metadata.

Community
Advanced
serankingseranking
116

seo-hreflang

Validate hreflang signals across HTML, sitemaps, and cross-domain targets.

Official
Advanced
BoristokaBoristoka

seo

Implement technical SEO best practices in Next.js applications.

Community
Intermediate
eKoh951eKoh951

next-intl-app-router

Integrate next-intl locale routing and translations into Next.js App Router.

Community
Advanced