Weave Code
Seo Bundle Laravel Package
nucleos/seo-bundle
Nucleos SEO Bundle is a PHP package for adding SEO metadata to your site, offering configurable titles, descriptions, and related settings to help pages render search-friendly metadata. It integrates cleanly into Symfony applications and keeps SEO configuration simple and reusable.
nucleos/seo-bundle adds flexible SEO metadata management to Symfony applications. It lets you define and render page titles, meta descriptions, keywords, canonical URLs, robots directives, and Open Graph tags from configuration, controllers, or Twig templates, keeping metadata consistent across routes.
- Route- and controller-level SEO configuration
- Twig helpers for meta tags and Open Graph
- Canonical URL and robots handling
- Extensible, service-oriented architecture
- Native Symfony bundle integration
Frequently asked questions about Seo Bundle
- Is nucleos/seo-bundle a Laravel package?
- No. It is a Symfony bundle that depends on symfony/http-kernel, symfony/dependency-injection, symfony/event-dispatcher, symfony/config and Twig, and it plugs into Symfony's bundle, compiler-pass and event-subscriber model. There is no Laravel service provider, facade, publishable config or Eloquent bridge. For a Laravel codebase it is a reference architecture rather than an installable dependency.
- Can I install nucleos/seo-bundle in a Laravel application with Composer?
- Composer will likely resolve it, but installing it gains you nothing usable in Laravel. Nothing registers the bundle, no routes or commands are exposed, and the Twig renderers and Doctrine mappings assume Symfony idioms. Treat any attempt at direct integration as a reimplementation project, not a package install.
- What features does nucleos/seo-bundle actually provide?
- It provides XML sitemap generation through a registry of URL and section providers, first-class robots.txt handling, and SEO metadata attached to domain entities rather than hardcoded in templates. Meta, OpenGraph and Twitter card output is rendered through Twig templates and kernel listeners, with canonical URL support. The design is clean and reusable, which is why it is worth studying even outside Symfony.
- Which Laravel versions does nucleos/seo-bundle support?
- None officially. Its major versions track Symfony's release cadence, which is unrelated to Laravel's, so there is no compatibility guarantee and no reason to expect one. Any Laravel compatibility you achieve would be something you built and maintained yourself.
- How do I generate an XML sitemap in Laravel if this bundle is Symfony-only?
- You either use a Laravel-native package or port the pattern. A faithful port means a SitemapSection interface plus a container-resolved registry, each section yielding URLs in chunks, driven by a scheduled php artisan sitemap:generate command that writes into storage. That mirrors the bundle's provider-registry idea while replacing Symfony tagged services with Laravel tagged bindings.
- What are the Laravel alternatives to nucleos/seo-bundle for sitemaps and meta tags?
- For sitemaps, spatie/laravel-sitemap is the common Laravel-native choice, and for meta, canonical and OpenGraph rendering packages such as artesaos/seotools or ralphjsmit/laravel-seo cover similar ground. Verify current maintenance and Laravel version constraints before committing, since that ecosystem moves quickly. Benchmarking these first is cheaper than spending engineering days on a Symfony port.
- How would I port nucleos/seo-bundle's SEO metadata model to Laravel?
- Start with a seo_metadata polymorphic table keyed by model_type and model_id, plus a SeoMetadata value object holding title, description, canonical, robots directives, OpenGraph and Twitter fields. Replace the Twig renderers with Blade components or partials for the title tag, canonical link and social cards. Wire sitemap regeneration into an artisan command and the Laravel scheduler instead of a Symfony console command.
- Does nucleos/seo-bundle support JSON-LD structured data?
- Its coverage of structured data is weaker than its meta tag, canonical and OpenGraph support, so do not assume parity with dedicated schema packages. If rich results matter, plan to add JSON-LD emission yourself, either in the ported Blade components or as separate schema objects. Validate output against Google's Rich Results test before shipping.
- Is nucleos/seo-bundle actively maintained and safe for production?
- Adoption signals are thin: around two GitHub stars, no dependents and effectively a single maintainer. There is recent release activity, but the listed last release date is future-dated relative to today, so verify the tag, changelog and Composer metadata before trusting the maintenance signal. It is MIT licensed, so you can fork, but a fork needs an owner and a security patch review SLA.
- How do I handle sitemaps with more than 50,000 URLs?
- That threshold changes the design regardless of which package you use, because the sitemap protocol caps a single file at 50,000 URLs and 50MB uncompressed. Emit a sitemap index that points at sharded child sitemaps, and have each section provider stream or chunk results rather than loading everything into memory. In Laravel, generate shards in queued jobs and write them to storage, then serve the index from a lightweight route.
Weaver
How can I help you explore Laravel packages today?