Redirects

Redirects maps an old public path to published tinymash content or another local public path. It is intended for changed permalinks and imported sites.

Manage mappings under Redirects in the admin navigation. Each mapping has a source path, target, enabled state, and HTTP status: 301, 302, 307, or 308.

Choose a content target for a post or page. The mapping stores the entry identity and follows it if its URL changes. An internal-path target is fixed. External targets are not supported.

Content and application routes take priority. A redirect is checked only when the requested path would otherwise return not found. Incoming query strings are ignored. Reserved admin, media, asset, feed, Search, tag, and secret-link paths cannot be used to bypass their protected handling.

Use a permanent status only when the old address should be replaced for good. Check the destination before enabling a large imported set.

Static exports leave redirect handling on the live site and rewrite known references to live URLs.