Redirect Bundle Laravel Package

Product Decisions This Supports

• Domain Consolidation Strategy: Simplify multi-domain management by enforcing a canonical URL (e.g., john-doe.fr over www.johndoe.fr) to improve SEO, analytics tracking, and user experience.
• SEO & Performance Optimization: Eliminate duplicate content issues and consolidate link equity by redirecting non-preferred domains to a single, standardized URL.
• Cost Efficiency: Reduce hosting/maintenance costs by retiring unused domains (e.g., www variants) and redirecting traffic to a single domain.
• Roadmap for Internationalization: Support global expansion by managing country-code TLDs (e.g., .fr, .com) and their regional aliases (e.g., www.johndoe.fr → johndoe.fr).
• Build vs. Buy: Avoid custom development for domain redirects; leverage this lightweight, configurable bundle instead of building in-house solutions (e.g., Nginx/Apache rules or JavaScript redirects).
• Use Cases:
  • Merging domains post-acquisition.
  • Post-migration cleanup (e.g., after switching from http to https).
  • Enforcing brand consistency across marketing campaigns (e.g., johndoe.com vs. johndoe.co).

When to Consider This Package

• Adopt if:
  • Your Symfony app manages 3+ domains with overlapping content (e.g., www, non-www, or TLD variants like .com/.co).
  • You need server-side redirects (faster, SEO-friendly) over client-side solutions (e.g., JavaScript or meta refresh).
  • Your team lacks DevOps bandwidth to configure redirects via .htaccess/Nginx.
  • You prioritize maintainability over one-off solutions (e.g., hardcoded redirects in controllers).
• Look elsewhere if:
  • You’re not using Symfony (this bundle is framework-specific).
  • You need dynamic redirects (e.g., user-specific or A/B test paths)—this bundle uses static YAML config.
  • Your redirects require complex logic (e.g., path rewrites beyond domain consolidation).
  • You’re on PHP <5.3.2 or Symfony ≥3.0 (compatibility gap).
  • You need analytics tracking post-redirect (this bundle handles redirects only; pair with Google Tag Manager or similar).

How to Pitch It (Stakeholders)

For Executives: *"This bundle lets us consolidate our web presence by automatically redirecting users from outdated or duplicate domains (e.g., www.johndoe.fr) to our preferred canonical URL (johndoe.fr). It’s a no-code solution that:

• Saves costs by retiring unused domains.
• Boosts SEO by eliminating duplicate content.
• Reduces support tickets from users confused by multiple URLs.
• Ships in hours, not weeks, with zero DevOps overhead. Think of it as ‘set it and forget it’ for domain hygiene—like a traffic cop for the web."

For Engineering: *"This is a Symfony-specific, battle-tested way to handle domain redirects via YAML config. Key benefits:

• Lightweight: ~3 steps to install/configure (Composer + kernel + YAML).
• Flexible: Supports wildcards for TLDs (e.g., *.johndoe.fr) and nested aliases.
• Performance: Server-side 301 redirects (better than client-side hacks).
• Future-proof: Easy to extend for multi-region or A/B testing needs. Downside: Static config only—if you need dynamic rules, we’d need to layer in a service or event listener. But for 90% of use cases, this is a drop-in win."*