- How do I install lyssal/seo-bundle with Composer?
- Run composer require lyssal/seo-bundle from your project root. If you are not using Symfony Flex, register the bundle in your config/bundles.php file. After installation, review the bundle configuration and connect the SEO services to the templates where you render metadata. Clearing the cache afterwards ensures the new services and Twig helpers are picked up.
- How do I set page titles and meta descriptions with LyssalSeoBundle?
- LyssalSeoBundle centralizes page titles and meta descriptions through its service-based configuration, so you define the SEO metadata once instead of hardcoding tags in every template. You then output the values in Twig using the provided helpers. This keeps titles and descriptions consistent across your site and makes them easy to change from a single place.
- Does LyssalSeoBundle support Open Graph and Twitter Card tags?
- Yes. The bundle includes Open Graph and Twitter Card support alongside the standard meta tags. You configure the social metadata the same way as the rest of your SEO values, and the Twig helpers render the resulting tags. This lets social platforms pick up correct titles, descriptions and preview data from your pages.
- How do I add a canonical URL to a page?
- Canonical URLs are configurable in LyssalSeoBundle, so you set the canonical value for a page through the bundle's configuration rather than writing the link tag manually. The value is then rendered in the head of your document by the Twig helpers. This helps prevent duplicate-content issues when the same content is reachable from several URLs.
- How do I noindex a page using robots directives?
- The bundle provides flexible robots directives with noindex controls. You enable or adjust the directive for the relevant page through the SEO configuration, and the helper renders the appropriate robots meta tag. This is commonly used for staging environments, thank-you pages, internal search results and other pages that should stay out of search indexes.
- Which Symfony versions does lyssal/seo-bundle support?
- The supported Symfony versions are declared in the package's composer.json, so check that file or run composer require lyssal/seo-bundle and review the resolved constraints. If your application uses an older or newer Symfony release than the declared range, Composer will report the conflict and you can run composer why-not lyssal/seo-bundle for details. Always confirm the constraint before planning an upgrade.
- Can I use LyssalSeoBundle in a Laravel application?
- No. LyssalSeoBundle is a Symfony bundle that depends on Symfony's service container, bundle configuration and Twig integration, so it will not work as a drop-in Laravel package. Laravel projects should use a Laravel-specific SEO package or manage metadata manually in Blade views. If you are porting a Symfony site to Laravel, plan to replace this bundle rather than reuse it.
- How do I extend the SEO metadata logic with my own services?
- The bundle is built around extensible service-based configuration for custom SEO logic. You can decorate or override the relevant services in your application's service configuration to compute titles, descriptions or canonical values dynamically. This approach suits multi-domain sites, translated URLs or values derived from your entities, while the Twig helpers keep rendering consistent.
- How do I test the SEO output produced by LyssalSeoBundle?
- There is no documented dedicated test helper, so the practical approach is to render the Twig template in a functional or integration test and assert on the resulting HTML. Check for the expected title, description, canonical link and robots meta tag in the response. Testing the rendered output rather than internal services also verifies that your configuration is actually applied in templates.
- Is LyssalSeoBundle actively maintained, and what are the alternatives?
- Check the GitHub repository at github.com/Lyssal/seo-bundle for recent commits, releases and open issues before committing to it, since maintenance activity is the best indicator of future support. Alternatives include other Symfony SEO bundles or managing metadata directly in Twig with your own services. The main advantage of this bundle is that it centralizes meta tags, canonical URLs, robots directives and social tags in one configuration layer.