Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Filament Redirects Laravel Package

van-ons/filament-redirects

Filament plugin for managing URL redirects directly from your admin panel. Create, edit, and organize 301/302 redirects, track hits, and handle old or changed URLs without editing server config. Integrates as a Filament resource for quick setup.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Dynamic redirect strategy: v2.4.0 adds captured-group substitution in match redirect destinations. This supports product decisions around pattern-based redirects such as mapping legacy URL segments to equivalent new paths without creating one rule per URL. It reduces manual redirect maintenance during site migrations, rebrands, category restructures, and locale/path changes.
  • Self-serve redirect operations: The improved redirect list and form readability lowers the barrier for marketing, content, and support teams to manage redirects safely. This affects decisions about whether to keep redirect changes in engineering backlog or move them to an admin workflow.
  • Build vs. buy/adopt: If the product needs Laravel-native redirect CRUD plus pattern matching, this package can replace custom middleware or ad hoc database tables. The new captured-group feature strengthens the case for adopting rather than building a bespoke dynamic redirect system.
  • Roadmap input: This release supports prioritizing SEO hygiene, 404 reduction, and migration safety. It also opens use cases for campaign URLs, localized paths, and product/category URL changes where destination paths must preserve dynamic segments.
  • Risk profile: The release notes indicate feature additions and UI readability improvements, with no stated breaking changes or deprecations. Product can treat v2.4.0 as a low-friction capability upgrade, subject to normal regression testing.

When to Consider This Package

Consider this package when:

  • The product is a Laravel application and the team wants redirect management close to the application rather than in a separate CDN or SaaS tool.
  • Marketing, content, or operations teams need a readable admin interface to manage redirects without engineering involvement for every change.
  • The roadmap includes URL migrations, content restructuring, rebrands, multilingual path changes, or frequent campaign redirects.
  • Pattern-based redirects with captured groups are useful—for example, preserving slugs, category paths, or locale segments in destination URLs.
  • The team wants to avoid custom redirect middleware, bespoke admin screens, and manual one-off rules.
  • Redirect volume and complexity are moderate enough for an application-level package.

Look elsewhere or plan additional tooling when:

  • Redirects must run at the edge/CDN layer for very high traffic, global latency, or strict availability requirements.
  • The product needs advanced rule engines, A/B redirect testing, complex conditional logic, or enterprise-grade analytics.
  • The organization requires audited change management, approval workflows, or compliance controls not evident in this release.
  • The application is not Laravel/PHP or the team standardizes redirect infrastructure outside the app.
  • Redirect volume is extremely high and database-backed lookup performance becomes a concern without additional caching or architecture.

How to Pitch It (Stakeholders)

For executives: v2.4.0 makes the redirect system more usable and more capable. The readability improvements reduce dependence on engineering for routine redirect changes, while captured-group destinations let teams preserve URL structure automatically during migrations and restructuring. This lowers SEO and revenue risk from broken links and reduces the cost of launching URL changes.

For engineering: This is a Laravel-native way to avoid custom redirect middleware and one-off admin tooling. The new captured-group support removes repetitive rule creation for pattern-based redirects, and the UI improvements reduce support burden. No breaking changes are indicated in the release notes, so adoption can be scoped as a feature upgrade with normal testing.

For marketing/content operations: The redirect list and form are easier to read, and dynamic destinations mean fewer manual rules when paths change. That makes self-serve redirect management more practical for campaigns, content moves, and site migrations, while keeping engineering focused on higher-value work.

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
socialdept/atp-orm
cboxdk/laravel-assistant-client
socialdept/atp-resolver
socialdept/tenant-domains
tautvydasr/blade-class-names
socialdept/color-scales
maherelgamil/controller
coleus/widgets
coleus/table
coleus/users
coleus/music
coleus/health
coleus/calendar
coleus/notes
coleus/support
coleus/settings
coleus/apps
seampact/laravel
emmyconceptng/laravel-ng-postcode
jjsquady/round-robin