Redirects

Map old paths to new ones when reorganizing docs.

When you rename slugs or restructure sections, add redirects so bookmarks and external links keep working.

Console

Manage redirects in the site console under Redirects. Each rule maps a source path to a destination (another path on the site or an absolute URL) and an optional position for evaluation order.

After changing redirects, publish so the public host picks them up.

Docs-as-code (`site.yaml`)

Declare redirects in site.yaml. On git sync, when the redirects: key is present, Pinnate replaces the site’s redirect rules with that list.

List form:

redirects:
  - from: /old-path
    to: /start/introduction
    status: 301
  - from: /legacy
    to: https://example.com/docs

Map form:

redirects:
  /old-path: /start/introduction
  /legacy:
    to: /sites/overview
    status: 302

Omit redirects: to leave console-managed rules unchanged. Set redirects: [] (or false) to clear all redirects on sync.

Expanded SEO notes: SEO → Redirects.