Weave Code
Simple Seo Bundle Laravel Package
ibrows/simple-seo-bundle
A lightweight Symfony bundle for basic SEO management, helping you define page titles, meta descriptions, and related metadata through simple configuration. Easy to install and integrate into existing Symfony applications.
At a glance
Frequently asked questions about Simple Seo Bundle
- Is ibrows/simple-seo-bundle a Laravel package?
- No. It is a Symfony bundle with Composer type symfony-bundle, built around Symfony bundle registration, dependency injection, Doctrine mapping, and Twig rendering. Laravel's service container and bootstrap do not provide equivalent integration points, so you should not treat it as a Laravel package.
- Can I install ibrows/simple-seo-bundle in a Laravel app with Composer?
- You may be able to add the Composer package, but it will not integrate with Laravel out of the box. Its services, configuration, and Twig extension are wired for Symfony, so Laravel will not register or use them automatically. The technical evaluation recommends not adopting it for a Laravel target because it contributes no runtime value and can add unused Symfony dependencies.
- Which Laravel and PHP versions does ibrows/simple-seo-bundle support?
- It does not list Laravel support because it is a Symfony bundle. The evaluation flags a likely Symfony 2.x-era PHP and Doctrine floor, which may conflict with PHP 8.x and supported framework versions. You must inspect its composer.json constraints before considering any use, and a composer require against a modern lockfile may fail to resolve.
- What SEO features does ibrows/simple-seo-bundle provide?
- It provides lightweight handling for SEO metadata such as page titles, meta descriptions, and related tags. The bundle is designed for simple configuration and template-friendly rendering rather than a full SEO suite. It is a minimal tool for the essentials, not a complete content SEO platform.
- How do I render page titles and meta descriptions with this bundle in Twig?
- The bundle is described as providing template-friendly helpers and a Twig extension for rendering SEO tags. In a Symfony app you would configure metadata and call those helpers from your Twig templates. In Laravel, Blade does not use Symfony's Twig extension wiring, so there is no direct equivalent without reimplementation.
- Does ibrows/simple-seo-bundle support canonical tags, hreflang, Open Graph, or slug redirects?
- The overview only confirms basic metadata such as titles, meta descriptions, and related tags. The technical evaluation explicitly lists canonical, hreflang, Open Graph, and redirect-on-slug-change as scope questions to verify before any decision. Do not assume advanced SEO features are included.
- Is ibrows/simple-seo-bundle maintained and safe for production?
- The evaluation reports zero stars, zero dependents, no visible CI, no test suite, and no release or security disclosure path. That means there is little evidence of production use or ongoing ownership. Runtime blast radius is small because it mainly reads strings and renders tags, but adopting it creates an owner-less dependency risk.
- What are good Laravel alternatives to a Symfony SEO bundle?
- For Laravel-native SEO metadata, the evaluation suggests benchmarking maintained options such as spatie/laravel-seo and artesaos/seotools. Compare them against your actual requirements for titles, descriptions, canonical URLs, Open Graph, and sitemap or redirect behavior. A maintained Laravel package is usually a better fit than adapting a Symfony bundle.
- How would I build simple SEO metadata natively in Laravel instead?
- The evaluation recommends a small native SeoMeta module: a metadata record keyed by route or URL holding title, description, keywords, and canonical, plus a renderer that emits title and meta tags in deterministic order with fallbacks. That is roughly 50 to 150 lines of logic and one database table. You would then add admin CRUD and Blade components only as needed, avoiding Symfony-specific configuration and Doctrine wiring.
- Can I fork ibrows/simple-seo-bundle or use it as a reference design?
- The MIT license makes forking legally straightforward, but the evaluation warns that a fork turns an unmaintained OSS dependency into an internal product without an owning team. A better use is as a reference design for a native implementation. Capture the decision explicitly as evaluated and chose to build, rather than treating it as package adoption.
Weaver
How can I help you explore Laravel packages today?