Manage TYPO3 Redirects: Fix 404s, Improve SEO, Avoid Errors

In TYPO3, go to Site Management → Redirects, add the old URL (source) and new URL (target), and use a 301 redirect for permanent changes to preserve SEO value.

TYPO3 redirects are rules that automatically send users and search engines from one URL to another using the built-in Redirects module (EXT:redirects) in Site Management → Redirects. They are used when URLs change, content is moved, or pages are removed.

They help fix 404 errors, preserve SEO value (link equity), and ensure users reach the correct page.

You can manage redirects in the TYPO3 backend under:

Site Management → Redirects (or Sites → Redirects, depending on version).

This module lets you create, edit, and manage redirects without coding.

Access:

• Admins: Full access by default
• Editors: Require permission for the Redirects module and sys_redirect table

Ensure permissions are correctly set so your team can manage redirects efficiently.

Types of Redirects in TYPO3 (With SEO Impact)

Choosing the right redirect type is critical for both SEO and user experience.

301 (Moved Permanently)

• Permanent redirect; passes SEO value
• Use: URL changes, deleted pages, migrations
• Avoid: temporary changes

302 (Found / Temporary)

• Temporary redirect; original URL often stays indexed
• Use: short-term changes, campaigns
• Avoid: permanent updates

303 (See Other)

• Redirect after form submission (POST → GET)
• Use: thank-you or confirmation pages
• Avoid: SEO-related redirects

307 (Temporary Redirect)

• Like 302 but preserves HTTP method
• Use: technical/temporary cases
• Avoid: SEO redirects (old URL remains indexed)

308 (Permanent Redirect)

• Like 301 but preserves HTTP method
• Use: advanced cases only
• Rarely needed for typical sites

Which Redirect Should You Use? (Quick Guide)

Default rule: Use 301 redirects for most TYPO3 website changes.

When Should You Use TYPO3 Redirects? (Key Use Cases)

Use redirects whenever a URL changes or content is removed:

• URL / slug changes: Redirect old URLs to new ones
• Deleted or moved pages: Point to the closest relevant page
• Domain / protocol changes: HTTP → HTTPS, www ↔ non-www

Broken or legacy URLs: Fix outdated links from campaigns or bookmarks

• Blog URL update:
  /blog/old-title → /blog/new-seo-title (301)
• Deleted product:
  /product/old-item → /category/relevant-products (301)
• HTTP → HTTPS:
  http: //example.com → https: //example.com (301)
• Domain migration:
  old-domain.com/* → new-domain.com/* (301)

Follow these steps in Site Management → Redirects:

1. Open Redirects Module
2. Add New Redirect
3. Enter Source & Target
   1. Source: /old-page
   2. Target: /new-page
   3. Use relative URLs for internal pages
4. Select Status Code
   1. Use 301 for most cases
   2. Use 302/307 only if temporary
5. Set Options (Optional)
   1. Choose correct site/domain
   2. Force SSL (HTTP → HTTPS)
   3. Keep GET parameters
   4. Use priority if needed
6. Save, Clear Cache & Test
   1. Save changes
   2. Clear cache
   3. Test redirect (should return 301)

Common Mistakes to Avoid

• Incorrect source path (typos or missing slash)
• Wrong site/domain selected
• Trailing slash mismatch (/page vs /page/)
• Not clearing cache after saving

• Redirect loop (A → B → A)
  Occurs when redirects point back to each other.
  Fix: Ensure a direct one-way redirect (A → B) and remove conflicting rules.
• Redirect not working
  Often caused by incorrect path, wrong site configuration, or regex issues.
  Fix:
  • Check exact source path (including leading slash)
  • Verify correct site/domain selection
  • Validate regex syntax if used
• 404 still showing after redirect
  Usually due to caching or incorrect matching.
  Fix:
  • Clear TYPO3 cache
  • Check redirect priority and order
  • Confirm correct source URL match
• Wrong status code (302/307 instead of 301)
  Prevents proper SEO value transfer.
  Fix: Use 301 (Moved Permanently) for permanent URL changes

• Redirects
  Send users from an old URL to a new one (e.g., after URL changes).
• Routing
  Defines how TYPO3 generates and resolves URLs internally.
• URL rewriting (server-level)
  Managed via .htaccess (Apache) or Nginx config for low-level URL handling.

When to use what:

• Use TYPO3 redirects for content-level URL changes
• Use routing for URL structure and generation
• Use server-level rewrites for global or performance-critical rules

TYPO3 uses the scheduler to automatically automate tasks, including the handling of redirects. If you set up the scheduler, TYPO3 will manage redirects for you.

• To do this, go to Admin Tools > Scheduler in the backend.

Configure automatic redirects

In your config.yaml file, you need to make some settings to ensure that the redirects are handled automatically:

• autoCreateRedirects: set this to true to create redirects when a page URL changes automatically.

• autoUpdateSlugs: Set this to true to ensure that URLs are automatically updated when a slug is changed.
• redirectTTL: This defines how long the redirects remain active (you can set the desired time).
• httpStatusCode: Set this to 301 for permanent redirects.

Once set up, TYPO3 will automatically take care of redirects when URLs change, saving you time and effort.

To keep your redirects clean, fast, and SEO-friendly, follow these core practices:

Use 301 for Permanent Changes

Always use 301 (Moved Permanently) for URL changes to pass link equity and update search engine indexing correctly. Use 302 only for short-term cases.

Avoid Redirect Chains

Redirect chains (A → B → C) slow down load time and dilute SEO value. Always redirect directly from the old URL to the final destination.

Clean Up Regularly

Remove outdated or unused redirects to keep your setup efficient and reduce errors or conflicts.

Test Every Redirect

After setup, verify that the redirect works correctly and returns the right status code (301).

Monitor with Google Search Console

Track indexing, detect redirect issues, and fix errors before they impact rankings.

Redirects aren’t just technical, they’re essential for SEO and user experience. Done right, they prevent 404 errors, preserve rankings, and guide users to the right content.

If you’re updating URLs, fixing broken links, or planning a migration, set up redirects properly and keep them clean. A well-managed redirect strategy protects both traffic and performance.

Need help? A TYPO3 Agency can ensure your redirects are accurate, efficient, and SEO-safe.