SEO and metadata — Nexis documentation

Metadata is part of the route contract

Each published route needs an accurate title, description, canonical URL, and social representation. Layouts may provide inheritance while child pages override their own fields.

Generate from one inventory

Sitemap, robots, RSS, Atom, breadcrumbs, and feed links should come from the same published route inventory rather than hand-maintained divergent lists.

Only describe visible truth

Escape JSON-LD safely, reject unsafe canonical protocols, and add structured data only when it represents content that the user can actually see.

PRACTICAL LABS

Run this capability.

Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.

Make route metadata specific

TSX

export const seo = {
  title: 'Workbench articles',
  description: 'Public documentation for operating Nexis applications.',
  canonical: 'https://docs.example.com/articles/',
}

OUTPUT: The route emits a title, description, and canonical URL in its head.
BOUNDARY: Use a real absolute production origin; structured data must describe visible content.
PROVE IT: Validate the route head plus sitemap.xml, robots.txt, feed.xml, and atom.xml.

VERIFICATION

Prove the contract.

Audit every route title, description, canonical, Open Graph card, JSON-LD output, sitemap entry, robots rule, and feed URL.