- How do I install lyssal/seo in a Laravel application?
- Install it with Composer using composer require lyssal/seo. The package is framework-agnostic, so there is no Laravel-specific service provider documented in the provided overview; you can call its fluent builders from controllers, view composers, or middleware. Check the repository README for any optional integration steps before wiring it into your app.
- What SEO metadata can I manage with lyssal/seo?
- It provides fluent builders for page titles, meta descriptions, canonical URLs, and social sharing tags, including Open Graph and Twitter Cards. It also includes helpers for sitemaps and robots.txt. The package focuses on on-page SEO metadata and keeps that concern separate from your templates and controllers.
- Does lyssal/seo support Open Graph and Twitter Card tags?
- Yes. The package explicitly supports Open Graph and Twitter Card social sharing tags through its fluent API. You define the values once and let the package render the appropriate meta tags, with automatic output escaping by default.
- Is lyssal/seo Laravel-specific or framework-agnostic?
- It is framework-agnostic and PSR-compliant, so it can be used in Laravel as well as other PHP applications. In Laravel you would typically install it via Composer and invoke the builders from your controllers, middleware, or view layer. There is no documented Laravel-only API in the provided overview.
- How do I set a page title and meta description with lyssal/seo?
- Use the package's fluent builders to define the title and meta description, then render the resulting metadata in your layout. The exact method names are not included in the provided overview, so check the README for the builder syntax. The goal is to keep title and description definitions out of your templates and controllers.
- Does lyssal/seo escape meta tag output automatically?
- Yes, the overview states that it provides sensible defaults with automatic output escaping. This helps prevent malformed tags or injection issues when titles, descriptions, and social values contain special characters. You should still review any raw HTML you pass into the builders.
- Can lyssal/seo generate sitemaps and robots.txt?
- It includes helpers for sitemaps and robots.txt in addition to meta tags. The overview does not specify the exact output format or API, so consult the repository documentation for usage details. These helpers can keep common SEO files consistent with the rest of your metadata setup.
- Which Laravel versions are supported by lyssal/seo?
- The package is framework-agnostic, so Laravel version support is not tied to a specific Laravel release in the provided context. Compatibility will depend on the package's PHP version constraints and your application's PHP runtime. Check the composer.json requirements before installing it in an older Laravel project.
- How should I test SEO metadata in a Laravel app using lyssal/seo?
- Because the package builds metadata through a fluent API, you can assert the generated title, description, canonical URL, and social tags in your application tests. Keep the metadata construction in a testable service, controller, or view composer rather than embedding it directly in Blade templates. The overview does not document package-specific test helpers, so use your normal Laravel HTTP or unit assertions.
- Is lyssal/seo production-ready compared with other Laravel SEO options?
- It is lightweight and offers sensible defaults like automatic escaping, but the provided overview does not include test coverage, release history, or security audit details. Review the repository for maintenance activity and compare it with Laravel-specific SEO packages or manual meta tag management. Pin a version and add tests before using it in production.