- How do I install michael-rubel/laravel-seo-manager in a Laravel application?
- Install it with Composer using composer require michael-rubel/laravel-seo-manager. The package follows Spatie laravel-package-tools conventions, so its service provider and facade are auto-discovered. Publish the config file with vendor:publish and define your URL-to-tag mappings there. Then include the package's Blade renderer in the head section of your layout so the resolved meta tags are output before the page renders.
- Does laravel-seo-manager support Laravel 10, 11, and 12?
- Not confirmed. The package's declared PHP and Laravel constraints date from around 2022, and release 3.1.1 only widened a transitive dependency range without raising the framework ceiling. Test the install on your target Laravel version in an isolated branch before committing, since Composer conflicts and deprecated framework calls are likely. If it does not resolve, plan for a fork or an in-house reimplementation.
- How does laravel-seo-manager decide which SEO tags to apply to a page?
- It keys metadata by the current request URL path and resolves the matching tag set before the head is rendered. Each entry in the configuration maps a path to its title, meta description, canonical URL, Open Graph tags, Twitter tags, and robots directives. Pages with no matching pattern fall back to whatever default you define, which is why unmatched routes can silently produce generic titles and descriptions.
- Can I use laravel-seo-manager with Inertia.js or a Vue or React single-page app?
- It is a poor fit. The package is built for server-rendered Blade monoliths where the response is assembled in PHP and meta tags are resolved before render. With Inertia, Nuxt, Next, or any API-first setup, the head is composed client-side or by a separate rendering tier, so a Blade-facing renderer never runs. Use a client-side head manager or a dedicated SSR SEO solution instead.
- Should I back laravel-seo-manager metadata with a config file or a database table?
- Both storage approaches are supported, and the choice drives most of your integration cost. Config-file-backed meta is a deploy-time artifact and is trivial to set up, but every change requires a deploy. Database-backed meta needs a new table, a migration, an admin CRUD surface, and a cache invalidation story, so budget for that work up front.
- Is michael-rubel/laravel-seo-manager still actively maintained?
- It is low-activity rather than abandoned: the repository is not archived, and release 3.1.1 was a single-line dependency-range widening. There is no published support policy, no security response process, and no roadmap. Treat it as a fork candidate or reference architecture, and assume you will inherit effectively all maintenance including future Laravel upgrades.
- What happens to SEO metadata when a page slug changes?
- Because records are keyed by URL path, changing a slug silently orphans the old metadata entry and leaves the new path unmatched. Visitors then see blank or default titles and descriptions, which can hurt search snippets and click-through. Pair any slug change with a redirect and an update to the stored mapping, and consider auditing unmatched paths regularly.
- Does laravel-seo-manager include an admin UI for editing meta tags?
- No. The package is a thin rendering and lookup layer that registers a facade and a Blade-facing renderer, not a content management tool. To make URL-keyed metadata practical you must build your own CRUD surface over the stored tag sets plus seeding for existing pages. Plan for that admin UI as the real integration cost, not the library itself.
- How do I test the SEO tag output from laravel-seo-manager in Laravel?
- Write feature tests that hit representative routes and assert the rendered head contains the expected title, description, canonical, and social tags. Cover the fallback path for unmatched URLs, trailing slashes, locale prefixes, query strings, and wildcard patterns, since those are where URL matching tends to break. Also add a test that fails when a known path loses its mapping, so slug changes do not quietly degrade metadata.
- What are the alternatives to laravel-seo-manager?
- The package is roughly 200 lines of MIT-licensed code, so reimplementing the URL-to-tag pattern against your own model is a realistic option. Actively maintained packages such as romanzipp/laravel-seo or ralphjsmit/laravel-seo cover similar ground with current framework support. For a Blade monolith that only needs titles, descriptions, and social tags, forking the original and owning the constraints is often the lowest-risk path.