SEO & Redirects
The work you would otherwise defer until the week before launch.
Per-page SEO
Every page and post has an SEO group: title, description, Open Graph image, Twitter card, canonical URL, and a no-index toggle. Sensible values are derived from the page's own content when the fields are left empty, so an editor who ignores the group entirely still ships valid metadata.
| Output | How |
|---|---|
| Meta, OG and Twitter tags | Per page and post, from the SEO group |
| Canonical URLs | Derived from `DOMAIN` and the page slug |
| sitemap.xml | Generated at build from published documents |
| robots.txt | Generated, with preview routes excluded |
| JSON-LD | Organization, WebPage and Article structured data |
Redirects
Redirects are Sanity documents — source, destination, and 301 or 302. At build time, they become Nitro route rules for server rendering and Apache rules for static hosting, so the same CMS entry works whichever way you deploy.
Editors manage them. Nobody edits a config file to retire a URL.