Deadlink Bundle Laravel Package

Product Decisions This Supports

• SEO & Content Integrity: Proactively identify and fix broken links (404s, redirects, or invalid URLs) in CMS-driven or database-backed content (e.g., blog posts, product pages, or documentation) to preserve SEO rankings and user trust.
• Automated QA for Content Pipelines: Integrate into CI/CD pipelines to scan for broken links before content deployments (e.g., staging → production), reducing post-launch fire drills.
• Build vs. Buy: Avoid reinventing a custom solution for link validation, especially if the team lacks time/resources to build a scalable crawler with retries, rate-limiting, and event-driven alerts.
• Use Cases:
  • Headless CMS/Decoupled Architectures: Validate links in JSON/API responses (e.g., Strapi, Contentful) before rendering.
  • Legacy Migration: Audit thousands of URLs during system transitions (e.g., moving from WordPress to a custom PHP app).
  • Dynamic Content: Check links in user-generated content (e.g., forum posts, comments) or third-party integrations (e.g., embedded widgets).
  • Compliance: Meet accessibility/SEO audits (e.g., WCAG 2.1 Success Criterion 2.4.4) by ensuring all links are functional.

When to Consider This Package

• Adopt if:

  • Your Symfony app relies on database-stored content (Doctrine ORM/ODM) with URLs (e.g., blog posts, product descriptions).
  • You need event-driven alerts (e.g., Slack notifications, email digests) when broken links are found, not just a CLI report.
  • Your team can extend the bundle (e.g., add custom LinkSourceInterface for APIs, sitemaps, or external services).
  • You’re okay with maintenance risk: The package is unmaintained (last release 2014), but the core logic (HTTP checks + events) is simple to fork/modernize.
  • You prioritize speed over features: The bundle lacks retries, proxy support, or JavaScript-rendered link detection (e.g., SPAs).

• Look elsewhere if:

  • You need modern Symfony support (v6+): The bundle targets Symfony 2.x and may conflict with newer dependencies.
  • Your links are dynamic or JavaScript-rendered (e.g., React/Vue apps): Use a headless browser tool like Puppeteer or Laravel Crawler.
  • You require scalability: For large sites (>100K links), consider a dedicated service like Screaming Frog or Ahrefs API.
  • You need real-time monitoring: This is a batch tool; pair it with a service like LinkChecker for continuous scans.
  • Your stack isn’t Symfony/PHP: For Laravel, use spatie/laravel-crawler or deadlinkchecker/deadlinkchecker.

How to Pitch It (Stakeholders)

For Executives:

"This bundle automates the tedious task of finding broken links in our content—saving us hours of manual QA and protecting our SEO rankings. For example, if a marketing campaign links to a product page that 404s after a migration, we’ll catch it before users do. It’s a low-code, event-driven solution that integrates with our existing Symfony stack, with minimal dev lift. The trade-off? We’ll need to maintain it ourselves (but the core logic is simple), and it won’t handle JavaScript-heavy sites. For now, it’s a cost-effective way to plug a critical gap in our content pipeline."

For Engineers:

*"This is a lightweight Symfony bundle that lets us:

1. Scan for broken links in Doctrine entities (e.g., blog posts, products) via a CLI command (astina:deadlink:check).
2. React to failures via events (e.g., log to a dashboard, trigger a Slack alert, or auto-fix via a migration).
3. Extend it for custom sources (e.g., API responses, sitemaps) by implementing LinkSourceInterface.

Pros:

• No external dependencies (self-hosted).
• Event-driven architecture fits our Symfony event bus.
• Works for static content (no JS rendering needed).

Cons:

• Unmaintained: Last release was 2014, but the code is simple to fork/modernize (e.g., update Symfony 2 → 6 compatibility).
• No retries/proxies: We’d need to add those ourselves for robustness.
• No GUI: Output is CLI/log-based (but we can build a simple dashboard on top).

Recommendation: Use this for database-backed content, pair it with a modern crawler for JS-heavy sites, and plan to maintain/fork it. Alternatives like spatie/laravel-crawler exist for Laravel, but this fits our Symfony stack better."*