Weave Code
Redirect Bundle Laravel Package
kunstmaan/redirect-bundle
KunstmaanRedirectBundle is a Symfony bundle for managing URL redirects from an admin interface. Create and maintain redirects to handle moved content, avoid broken links, and preserve SEO when URLs change.
KunstmaanRedirectBundle is a Symfony bundle for managing URL redirects directly from your application's backend. It provides a database-backed way to define and maintain redirects, so legacy or changed URLs can be sent to their new destinations without editing server configuration or routing files.
- Admin interface for creating, editing, and deleting redirects
- Supports 301 (permanent) and 302 (temporary) redirects
- Configurable source paths and target URLs stored in the database
- Integrates with the Kunstmaan admin bundle ecosystem
- Keeps redirect management in application code, versionable with your project
Frequently asked questions about Redirect Bundle
- Can I use kunstmaan/redirect-bundle in a Laravel application?
- No. kunstmaan/redirect-bundle is a Symfony bundle, not a Laravel package, and it expects Symfony bundle registration, routing, Doctrine, and admin conventions. Dropping it into Laravel would introduce a parallel framework paradigm and require significant adapter work. Treat it as a behavior reference, not a production dependency for Laravel.
- How do I install kunstmaan/redirect-bundle with Composer?
- You can install it with Composer, but it is designed for Symfony applications that register bundles and use Symfony routing and Doctrine. In a Laravel app, Composer may resolve the package, yet it will not wire into Laravel middleware, routing, or Eloquent automatically. For Laravel, do not install it as a redirect solution; build or choose a Laravel-native implementation instead.
- Does kunstmaan/redirect-bundle support Laravel 10 or Laravel 11?
- No. The package is a Symfony bundle with a last release in 2014, so modern Laravel versions are not supported. Its PHP and Symfony constraints are likely incompatible with current Laravel dependency graphs. Assume incompatibility until a time-boxed spike proves otherwise.
- What does kunstmaan/redirect-bundle actually do for redirects?
- It adds redirect management to Symfony applications, letting administrators create, edit, and delete URL redirects from an admin interface. It tracks hit counts and can return 301 or 302 responses for moved or removed pages to help preserve SEO. Those features are useful requirements, but the implementation is not Laravel-native.
- How does kunstmaan/redirect-bundle handle 301 and 302 redirects?
- The bundle lets administrators define redirects with response types so moved pages can use 301 and temporary moves can use 302. Correct status-code choice matters for SEO and traffic preservation. In Laravel, implement the same behavior with middleware that reads cached redirect rules and returns the appropriate status and Location header.
- Is kunstmaan/redirect-bundle safe for production SEO redirects?
- It carries high technical risk for production use because the last release was 2014 and it has virtually no community support. Redirect failures can cause redirect loops, stale rules, wrong status codes, or silent 404s that affect SEO and revenue. For business-critical redirects, use a maintained Laravel-native solution with caching, auditing, and tests.
- How do I track redirect hit counts in Laravel without this bundle?
- Create a redirects table with source path, target URL, status code, active flag, and hit count, then increment the count in middleware when a redirect matches. Cache the active redirect map to avoid a database lookup on every request, and flush that cache when redirects change. Add audit metadata so SEO-sensitive changes are traceable.
- What are the best alternatives to kunstmaan/redirect-bundle for Laravel?
- The lowest-risk alternative is a native Laravel module: a redirect model and migration, middleware for matching, cached lookup rules, and a simple admin CRUD surface. You can also evaluate maintained Laravel redirect packages, but verify Laravel version support, test coverage, release cadence, and cache behavior. Avoid adopting an abandoned Symfony bundle just for basic redirect management.
- How should I test redirects in a Laravel application?
- Write feature tests that request each source path and assert the expected status code and Location header, including 301 versus 302 behavior. Cover active and inactive redirects, cache invalidation, loop detection, and missing-target fallbacks. Run these tests in CI so redirect changes cannot silently break SEO or customer journeys.
- Is kunstmaan/redirect-bundle still maintained?
- No. Its last release was 2014-04-17, with 1 star and 0 dependents reported, which signals abandonment and no upstream community support. Adopting it directly would create internal technical debt for dependency upgrades, security patching, and compatibility testing. If you must use it in a legacy Symfony estate, assign an internal owner and budget for a fork.
Weaver
How can I help you explore Laravel packages today?