- How do I install digitaldream/laravel-seo-tools in a Laravel app?
- Run composer require digitaldream/laravel-seo-tools and let Laravel package auto-discovery register the service provider. Publish the config and migrations with php artisan vendor:publish, run php artisan migrate, add the package trait to the models whose SEO you want to manage, then drop the render component into your base Blade layout. A working spike is typically half a day to two days depending on how many content types you wire up.
- Which Laravel and PHP versions does laravel-seo-tools support?
- The last release was April 2024, so its declared constraints may stop short of Laravel 11 or 12 and PHP 8.3. Run composer why-not digitaldream/laravel-seo-tools against your target version and read the composer.json illuminate/support and php requirements before committing. If the constraints block your stack, you will need to fork and widen them yourself.
- How do I attach SEO metadata to an Eloquent model?
- The package stores SEO fields in a polymorphic table and links them to models through a trait, so you add the trait to any content model such as Post, Page or Product. Each record holds title, description, canonical, robots and Open Graph/Twitter values that an editor can change from the dashboard. Confirm what the component emits when a model has no SEO row, since you want a sensible configured default rather than an empty title.
- How do I render the SEO tags in my Blade layout?
- Place the package's render component or directive inside the head section of your base layout so it outputs title, meta description, canonical, robots and Open Graph/Twitter tags from the model's SEO record. Server-rendered tags are the entire point, because crawlers and social scrapers read them straight from the HTML response. Test the rendered output with a real crawler or social debugger before launch.
- Are the packaged admin routes protected, and can I change the prefix or guard?
- Packaged CRUD dashboards are often registered under plain web middleware, which would expose editorial controls to any authenticated user unless you wrap them. Read the service provider and route file, then apply your own admin middleware, change the route prefix, or mount the routes behind your existing admin guard. Verify this before deploying, because it is the most common security gap in packages like this.
- Does laravel-seo-tools work with Inertia, Vue, React or a headless front end?
- Poorly. The package's value is emitting meta tags into server-rendered HTML, so in an Inertia or headless setup where head tags are managed client-side you only get the persistence half. For a headless app, query the package's model directly through an API or choose an API-first SEO solution instead. Adopt it only for classic Blade-rendered Laravel monoliths.
- Is it safe to let non-technical editors paste HTML into meta fields?
- That is a stored-XSS vector if the Blade component renders editor-supplied values with unescaped output. Keep escaping enabled for meta content, sanitize anything you allow, and restrict who can reach the editor routes. The source is small enough to audit in under an hour, so read the component's Blade file during your spike.
- Will the SEO lookup slow down my pages or cause N+1 queries?
- Potentially yes, because a per-model polymorphic lookup on every render becomes an N+1 and a latency tax on high-traffic pages unless you eager-load the relation. Eager-load the SEO relation in your controllers or cache the resolved metadata in your cache store. There is no documented cache-invalidation hook, so plan a model observer or a small fork to clear the cache on save.
- Does it handle sitemaps, robots.txt, redirects, JSON-LD and hreflang?
- The package advertises meta tags, Open Graph, Twitter cards, sitemaps, robots.txt and redirects, which covers the usual editor-facing surface. Structured data, hreflang and multi-locale metadata variants are likely out of scope and will be separate work. Confirm each feature exists in the version you install rather than assuming from the description.
- Is laravel-seo-tools production-ready and actively maintained?
- It has roughly 154 stars, zero dependents, a single maintainer and a last release in April 2024, so it is effectively unproven at scale. Treat it as adopt-with-a-fork-plan: audit the source, confirm your Laravel and PHP matrix, and be ready to maintain it in a private VCS. If your team already runs Filament or Nova, reusing the migration and model with a native admin resource is often the stronger alternative.