- Is rz/seo-bundle a Laravel package?
- No. The repository rzproject/SeoBundle is a Symfony bundle, even though it is catalogued alongside Laravel and PHP packages. It bootstraps through Symfony bundles.php, an Extension and Configuration pair, compiler passes, and a Twig extension, which Laravel does not register. Treat it as a reference implementation or specification, not a Laravel dependency.
- Can I install rz/seo-bundle in Laravel with Composer?
- Composer may fetch the source, but it will not become a working Laravel SEO package. There is no Laravel service provider, middleware, Blade integration contract, or config publishing flow in the package; it expects a Symfony kernel. Requiring it as-is is not feasible, so use a Laravel-native alternative or rebuild the interface internally.
- What features does rz/seo-bundle offer for SEO metadata?
- The advertised feature set includes fluent builders for page titles, meta descriptions, and canonical URLs; Open Graph and Twitter Card tag generation; configurable sitemap and robots output; and pluggable renderers. The technical evaluation confirms the domain is well understood and low complexity, but also identifies the implementation as Symfony-specific. Verify any Blade or structured-data claims directly against the source before relying on them.
- Which Laravel versions support rz/seo-bundle?
- None are officially supported. The package is an archived Symfony bundle with no compatibility work for Laravel 10, 11, or 12 and no PHP 8.3 or 8.4 maintenance. Do not plan a Laravel upgrade path around it because there is no upstream maintainer to patch compatibility issues.
- How is rz/seo-bundle configured?
- In Symfony it is configured through the bundle Extension and Configuration classes and registered in bundles.php. It does not follow Laravel conventions such as config/seo.php, publishable config files, or a service provider. For a Laravel build, define your own config array and bind an internal SeoManager contract instead.
- Is rz/seo-bundle maintained and safe for production?
- No, it is archived with zero stars, zero dependents, and a score of 0.015. There is no security response, CVE triage, or upstream patching, so any vulnerability becomes your responsibility. License compatibility, test coverage, last-commit date, and possible outbound HTTP calls must be established before it enters a dependency tree, and those unknowns block a security review.
- What are the best alternatives to rz/seo-bundle for Laravel?
- Use a maintained Laravel-native SEO package or build a small internal SeoManager with methods such as setTitle, setDescription, setCanonical, addStructuredData, and render. Generate sitemaps with a Laravel command or job that introspects routes, and keep robots output configurable. Evaluate alternatives on Laravel 10, 11, and 12 support, test coverage, license, release cadence, and security response.
- Does rz/seo-bundle generate sitemaps and robots directives?
- The package advertises configurable sitemap and robots output as part of its SEO surface. The technical evaluation confirms sitemap and robots handling is part of the domain but warns the plumbing is Symfony-specific. If you rebuild it in Laravel, test URL normalization, pagination-aware canonicals, hreflang, per-locale metadata, and attribute escaping.
- Should I fork rz/seo-bundle and port it to Laravel?
- Forking is technically possible, but the estimate is two to three weeks including tests, and you would own the package permanently with no upstream to rebase against. Reading it as a reference and rebuilding behind an internal contract is usually one to two weeks and gives you control over interfaces and tests. Fork only if there is a specific behavior that is genuinely hard to reproduce.
- How should I test SEO metadata in a Laravel rebuild?
- Unit test the SeoManager methods and rendered output, then feature test routes to assert title, description, canonical, Open Graph, Twitter Card, and robots tags. Add tests for URL normalization, pagination-aware canonicals, locale and hreflang handling, escaping, and sitemap command output. If any code is lifted, pin the PHP version used in CI and run PHPStan or Larastan as part of the review.