Weave Code
Alt Seo Laravel Package
alt-design/alt-seo
Alt SEO is a Laravel package for managing SEO metadata on your models and pages. It helps set titles, meta descriptions, Open Graph tags, and canonical URLs so your site stays search-engine friendly with minimal configuration.
alt-design/alt-seo is a Laravel package that brings flexible, configurable SEO management to your application. It helps you generate and maintain meta tags, titles, and canonical URLs for your pages without scattering logic across views.
- Configurable meta tags (title, description, Open Graph, Twitter Cards)
- Simple facade/helper API for setting SEO data per request
- Blade directives for clean template integration
- Sensible defaults with per-model overrides
- Publishable config for full customization
Ideal for developers who want lightweight, no-bloat SEO tooling that fits naturally into Laravel conventions.
Frequently asked questions about Alt Seo
- Does alt-design/alt-seo work in a plain Laravel app without Statamic?
- No. alt-design/alt-seo is a Statamic addon maintained by Alt Design, a Statamic-focused agency, so it targets Laravel applications where Statamic provides the content layer. It registers a service provider through Laravel package auto-discovery and publishes config, but the actual tags are rendered from Antlers or Blade partials fed by Statamic entry fields and blueprints. Without Statamic there are no entries or blueprint fields to drive it, so you need a different package for a plain Laravel or API-only app.
- How do I install alt-design/alt-seo in a Laravel project?
- Install with composer require alt-design/alt-seo, then publish the package config and wire the addon's fieldset into the blueprints for the collections you want to manage. Finally include the tag-rendering partial in the head of your layout template so titles, descriptions, canonical and social tags are output. Before installing, confirm the release tags actually exist on Packagist, because the published release metadata appears unverified.
- Which Laravel, PHP and Statamic versions does this SEO addon support?
- The integration assessment assumes Laravel 10, 11 or 12 with Statamic 4 or 5, but the package's own compatibility matrix has not been validated against current releases. Treat the supported PHP and Statamic ranges as unconfirmed until you check the composer.json constraints on Packagist or ask the maintainer directly. Pin exact versions in your composer.json and test an upgrade on a branch before rolling it out.
- Can I override the title, meta description and canonical URL per entry?
- The addon is built around page-level SEO metadata, so titles, meta descriptions and canonical URLs are edited per entry in the control panel and rendered by the shared head partial. Template-level overrides are the usual pattern for landing pages and paginated or filtered URLs. Before rollout, produce a field-by-field mapping between your existing head markup and the addon's blueprint fields, and confirm blueprint changes are additive so existing entry data is not orphaned.
- Does it output Open Graph, Twitter cards and JSON-LD structured data?
- The package is documented as handling titles, meta descriptions, canonical URLs, Open Graph and Twitter tags. JSON-LD or broader structured-data output is not clearly documented, so treat it as an open question for the maintainer. Validate the real output with the Rich Results Test and the Facebook and X/Twitter debuggers rather than trusting the README.
- How does it handle multi-site and multi-locale Statamic setups?
- Multi-site and multi-locale behavior is not described in the available materials, so treat it as unverified. Statamic multisite stores per-site entry data and derives localized URLs, which is exactly where canonical and hreflang output tends to break. Confirm per-site and per-locale rendering in staging before committing, especially if you rely on hreflang for international SEO.
- Does this addon generate sitemaps and robots.txt?
- The addon focuses on page-level head metadata such as titles, descriptions, canonicals and social tags, and sitemap or robots.txt generation is not confirmed. Pick one source of truth for each artifact, whether that is Statamic core, another addon or this package, and never run two in parallel. Duplicate or conflicting tags are the most common cause of SEO regressions after an addon migration.
- Does it work with Statamic static caching, Live Preview and static site generation?
- Compatibility with static caching, Live Preview and static site generation is not documented, so verify it in a staging environment that mirrors production caching. The main risk is a silent render failure producing permanently cached bad markup that crawlers pick up. Add a post-deploy check that asserts the presence of canonical, Open Graph and robots tags on a sample of pages.
- Is there a test suite, and how should I validate SEO output after upgrades?
- No test suite is visible in the repository, so upgrades must be validated by output diffing rather than by trust. Capture a pre-migration baseline with a crawler such as Screaming Frog plus Search Console and social debugger snapshots, then compare after each change so regressions are attributable. Consider adding CI assertions on the rendered head markup for your key templates.
- What are the alternatives, and is this addon actively maintained?
- Alternatives include other Statamic SEO addons and hand-rolled Antlers head partials, which give full control but no editorial UI. This package is agency-maintained with modest community signals (around 12 GitHub stars and 0 dependents), so plan on being largely self-supporting, though the MIT license gives you fork rights if it is abandoned. Check the actual commit history and release tags on Packagist before adoption, since the listed release date appears anomalous.
Weaver
How can I help you explore Laravel packages today?