Skip to main content
FilaRank redirect manager with 404 capture and one-click 301 creation in Filament
HandleRedirects is registered on the web stack automatically. Set FILARANK_AUTO_REDIRECTS=false (or redirects.auto_register_middleware) to opt out. If you already append it in bootstrap/app.php, remove the duplicate so 404s are not logged twice:
Publish and run the redirect migration (the installer does this for you), then register the plugin on your panel:
The middleware serves matching redirects (with normalisation, chain-following A→B→C, and loop protection) and logs every 404. Logged 404s appear on the SEO Health page with a one-click Create redirect link that pre-fills the source path. Rules are cached for an hour and the cache is busted automatically on create/edit/delete.

Auto-redirects on slug change

Slug changes on published records create a 301 automatically. Reverting a slug clears the reverse rule, so renaming back and forth can’t leave a redirect loop behind.
Override HasSeo::isSeoPublished() if your model uses a different published flag than published_at or a status of published / live / public. Pair redirects with Internal Linking and Keyword Cannibalization reports on the same SEO Health dashboard to fix crawl and ranking issues in one place.
Last modified on October 10, 2026