Next.jsметаданныеcanonical
Next.js Metadata API: canonical, hreflang and OG
One place for titles, alternates and social cards — without duplicate URLs in search.
7 min
App Router metadata via metadata or generateMetadata. Mistakes here create duplicate listings when Google sees the same page on multiple URLs.
Canonical and hreflang
- alternates.canonical points to the clean final URL
- alternates.languages links RU/EN with x-default
- Consistent trailing-slash policy sitewide
We centralize buildPageMetadata(locale, path, title, description) and use generateMetadata for dynamic blog and service routes.
Read also
- Full SEO stack checklist for 2026Metadata, indexing, schema, speed and content — a practical layer-by-layer checklist for Next.js sites.
- Free mockup before payment reduces project riskOne hero screen after brief — aligns on style before the main contract.
- Telegram bot for lead captureQualify in messenger, push to CRM with UTM deep links and after-hours auto-reply.
- SEO vs paid ads budget splitNew site: heavier on ads. Mature organic: shift spend but keep paid for predictability. Track CAC by channel.