Exceptionchecker Bundle Laravel Package

Product Decisions This Supports

• Error Handling & UX Recovery: Enables seamless redirection or graceful degradation for broken links (e.g., 404s) without disrupting user flow, improving retention and reducing bounce rates.
• Technical Debt Mitigation: Automates the cleanup of stale URLs (e.g., post-migration or content updates) by flagging them via GoneHttpException, reducing manual log parsing.
• Developer Productivity: Provides a self-service UI for non-technical stakeholders (e.g., content teams) to manage URL exclusions/wildcards without developer intervention.
• Compliance & Auditing: Logs broken links with timestamps, enabling historical tracking of URL changes (useful for SEO or legal compliance).
• Build vs. Buy: Avoids reinventing a URL validation/redirection system, leveraging Symfony’s ecosystem for low-maintenance integration.
• Roadmap Prioritization: Justifies investment in a "broken link monitor" feature for content-heavy platforms (e.g., blogs, e-commerce, or documentation sites).

When to Consider This Package

• Adopt if:

  • Your Symfony app relies on dynamic or frequently updated URLs (e.g., blogs, product pages, or API-driven content).
  • You lack a dedicated broken-link monitoring tool but need a lightweight, self-hosted solution.
  • Your team prioritizes developer efficiency over custom-built solutions (e.g., no time to maintain a separate cron job for URL checks).
  • You want to reduce Monolog noise by excluding known "false positive" errors (e.g., legacy URLs).
  • Your stakeholders need a non-technical way to manage URL redirects/exclusions (e.g., via a web form).

• Look elsewhere if:

  • You’re not using Symfony (package is framework-specific).
  • You need enterprise-grade features (e.g., Slack/email alerts, analytics, or third-party integrations like Google Search Console).
  • Your team prefers serverless/headless solutions (e.g., AWS Lambda + API Gateway for URL validation).
  • You require high scalability (package is archived with minimal adoption; may need customization).
  • Your primary goal is SEO crawling (consider dedicated tools like Screaming Frog or DeepCrawl).

How to Pitch It (Stakeholders)

For Executives: *"This package lets us automatically detect and fix broken links in our Symfony app—like a ‘netflix for URLs.’ Instead of users hitting dead ends or our team drowning in error logs, we can:

• Redirect broken links to a fallback page (e.g., homepage) or mark them as ‘gone’ for SEO.
• Empower content teams to manage fixes via a simple web form (no dev tickets needed).
• Cut manual work by 80%—no more parsing Monolog emails for stale URLs. Think of it as insurance for our digital assets: cheaper than reinventing the wheel, and it pays dividends in UX and SEO."

For Engineering: *"This is a Symfony listener bundle that:

• Catches 404s and checks if the URL is excluded/redirected (supports wildcards and case-insensitive matches).
• Integrates with Monolog to suppress false positives (e.g., /old-page.html → /new-page.html).
• Provides a CRUD UI for managing exceptions (great for non-devs to add/remove URLs).
• Throws GoneHttpException for deleted URLs (cleaner than 404s for SEO). Pros: MIT-licensed, lightweight, and avoids custom logic. Cons: Archived repo (but minimal risk for our use case).* Alternatives: Build a custom listener or use a SaaS tool like LinkChecker—but this gives us control with less overhead."*