308 Permanent Redirect

308 Permanent Redirect in TYPO3

308 Permanent Redirect is similar to a 301 but ensures the request method doesn’t change. In TYPO3, this is used when you need a permanent redirect but want to retain the exact request type (GET, POST). Use 308 when you’re moving pages permanently but want to ensure that users’ requests stay consistent.

Key Tips for 308 Permanent Redirect in TYPO3:

• Use for permanent moves where the request method needs consistency.
• It is typically used in structured setups or complex integrations.

A 308 Permanent Redirect reports that a resource has moved permanently. Like the well-known 301, it transfers link equity and ranking to the new address. The difference: with 308 the request method must be preserved, so a POST stays a POST. This matters above all for interfaces and forms.

For classic websites 301 remains the standard because all systems know it. 308 is mainly used where the behaviour of requests has to be preserved exactly, for example with API endpoints, webhooks or form actions. Modern browsers and search engines understand both codes reliably.

In TYPO3 you create permanent redirects in the “Redirects” module. Make sure to avoid chains: if an address leads to the target through several redirects, visitors lose time and search engines lose patience. After a relaunch, therefore check regularly that all old URLs point directly to the new ones.

Always test new redirects in the browser and with a crawler before you put them live. A quick check of the status codes shows whether the desired method really is preserved and whether parameters such as tracking details are passed on correctly. This saves you laborious troubleshooting later in live operation.

When switching a domain to HTTPS or moving whole directories, one clean rule is better than many individual cases. A single, well-tested redirect rule saves maintenance effort and reduces the risk of individual pages being forgotten.

In short: Fix TYPO3 308 Error: Permanent Redirect Issues Explained.