Weave Code
Laravel Meta Laravel Package
f9webltd/laravel-meta
f9webltd/laravel-meta provides a simple way to manage SEO meta tags in Laravel. Attach metadata to Eloquent models, define reusable defaults and templates, and render dynamic titles, descriptions, Open Graph and Twitter tags for cleaner, more consistent pages.
Laravel Meta Tags - Render meta tags within your Laravel application
Frequently asked questions about Laravel Meta
- How do I install f9webltd/laravel-meta in a Laravel application?
- Install it with Composer using composer require f9webltd/laravel-meta. The package follows standard Laravel package conventions, so it registers a service provider automatically and its configuration file can be published with the vendor:publish command. After that you can define defaults and render meta tags in your Blade templates.
- Which Laravel and PHP versions does laravel-meta 4.x support?
- Version 4.0.0 requires PHP ^8.2 and Laravel ^11.0, ^12.0, or ^13.0. The release is a compatibility-focused major version that adds Laravel 13 support and drops legacy framework and PHP versions. The package intends to track Laravel's official support policy going forward, so the constraint window should stay aligned with supported Laravel releases.
- How do I attach meta tags to an Eloquent model with laravel-meta?
- The package is designed to attach metadata directly to Eloquent models, so SEO values live alongside the records they describe instead of being hardcoded in views. You add the package's meta behaviour to the model and define the fields or accessors that supply the title, description, and related tags. Rendering then pulls those values dynamically for each model instance.
- Can I define default meta tags and reusable templates?
- Yes. The package supports defining reusable defaults and templates, which is useful for consistent site-wide titles, descriptions, and fallbacks. Defaults can be set in configuration, while templates let you compose values per page or per model. This reduces duplication and keeps meta output consistent across a large Laravel application.
- How do I render meta tags in Blade templates?
- Meta tags are rendered through the package's Blade/helper API wherever your layout outputs head content. You typically place a single render call in your main layout so every page gets consistent output. Because the package is a utility library, it sits alongside your application code rather than changing your application structure.
- Does laravel-meta support Open Graph and Twitter card tags?
- Yes, the package renders dynamic titles, descriptions, Open Graph tags, and Twitter tags. That means you can maintain one source of metadata per page or model and output it in multiple formats for search engines and social platforms. Keeping these in one place avoids mismatched values between standard and social meta tags.
- How do I upgrade from laravel-meta 3.x to 4.x?
- Version 4.0.0 is a major release, so treat it as a normal major upgrade: review the changelog and diff, update your Composer constraint, then run your test suite. The release notes describe the change as support-policy alignment and removal of legacy PHP and Laravel support rather than a rewrite, but you should still smoke-test rendered meta tags in staging. Confirm whether any config, Blade directive, or API changes affect your usage before deploying.
- Can I use laravel-meta on Laravel 10 or PHP 8.1?
- No, 4.x requires PHP 8.2 or higher and Laravel 11, 12, or 13. Applications still on Laravel 10 or PHP 8.1 must either remain on the 3.x line or complete their PHP and Laravel upgrades first. The recommended order is to upgrade PHP to 8.2+, then Laravel to 11+, and only then adopt laravel-meta 4.x.
- How should I test meta tag output in my Laravel application?
- Add feature tests that request your key pages and assert the expected title, description, Open Graph, and Twitter tags appear in the response. Also test the fallback behaviour when a model has no metadata, since defaults and templates are the main source of regressions. Because the package only affects rendered metadata, failures are contained to head output rather than core application behaviour.
- Is f9webltd/laravel-meta actively maintained, and what are the alternatives?
- The package is community maintained with a small maintainer footprint, which is normal for a narrow utility library but does represent a single point of failure for production templates. Its 4.0.0 release shows active maintenance aligned with Laravel's support policy, though you should check issue responsiveness and release cadence before standardising on it. Alternatives include dedicated SEO packages such as spatie/laravel-sitemap-adjacent tooling or simply rendering meta tags manually in your Blade layout.
Weaver
How can I help you explore Laravel packages today?