Weave Code
Statamic Peak Seo Laravel Package
studio1902/statamic-peak-seo
An SEO addon for Statamic, built for the Peak starter kit. It helps you manage meta tags, Open Graph data, sitemaps, and other search-engine essentials so your content is easier to discover, index, and share.
Belongs to the Statamic Peak Starter Kit and contains all SEO fieldsets and partials.
Frequently asked questions about Statamic Peak Seo
- What is studio1902/statamic-peak-seo used for?
- It is a Statamic companion package for the Peak starter kit that provides SEO fieldsets and Antlers partials. It helps model SEO content and render meta tags, Open Graph data, and related search-engine markup. It is not a standalone Laravel SEO engine, crawler, or redirect manager.
- Is statamic-peak-seo a general Laravel SEO package or Statamic-only?
- It is Statamic-only in practice, even though Statamic runs on Laravel. The package is built around YAML fieldsets and Antlers partials for Peak, not a general Laravel service layer or database package. Non-Statamic Laravel apps or Blade, Inertia, and Livewire front ends get little value from it.
- How do I install statamic-peak-seo in a Laravel Statamic project?
- Install it with Composer in a Laravel project that already uses Statamic and the Peak starter kit. Then publish or import the package fieldsets, include the SEO partial in your base layout, and configure defaults. Check the README for exact publish tags and partial names because the package is convention-driven.
- Does statamic-peak-seo work with any Statamic site or only the Peak starter kit?
- It is designed for the Peak starter kit and assumes Peak conventions such as field handles, asset containers, layout partial names, and likely Tailwind or Glide image transforms. It can be adapted to an existing Statamic site by copying fieldsets and partials, but you must reconcile handles and migrate content. It is a poor fit for non-Peak or non-Statamic stacks.
- Which Laravel, PHP, and Statamic versions does statamic-peak-seo support?
- The supplied context does not list explicit Composer constraints, so inspect composer.json and the README before installing. Pin Statamic and PHP majors in your project and test against the exact versions you deploy. Statamic and Antlers major-version drift is the main long-term compatibility risk.
- Does statamic-peak-seo generate sitemaps, robots.txt, or redirects?
- The blurb mentions sitemaps and search-engine essentials, but the package is primarily an SEO fieldset and template layer. Verify in the repository whether sitemap generation, robots.txt, noindex, hreflang, and redirects are actually implemented or delegated to Statamic or another addon. Do not assume it is a full SEO engine.
- How do I add the SEO fields to my Statamic collection blueprints?
- Import or copy the package SEO fieldsets into your collection or blueprint YAML and expose the fields editors need, such as meta title and description. For existing sites, map your current SEO field handles to the package handles before migrating content. Then render the fields through the provided Antlers partials or your own adapted templates.
- Can I use statamic-peak-seo with headless Statamic, Inertia, or Livewire?
- It is a poor fit for headless or API-first Statamic because its main value is Antlers partial rendering inside a Peak theme. Inertia, Livewire, or separate front ends would need the SEO fields but a rewritten presentation layer. Treat it as a theme component, not an API dependency.
- Is the meta tag and JSON-LD output from statamic-peak-seo escaped and CSP-safe?
- The package renders SEO values through Antlers templates, so you must review every output context for correct escaping. Meta titles, descriptions, canonical URLs, Open Graph values, and JSON-LD need careful handling to avoid broken markup or XSS. Confirm CSP compatibility and test rendered HTML before production.
- What are the maintenance, security, and license risks of using statamic-peak-seo?
- Adoption is low, with roughly 14 stars and a single maintainer, so community scrutiny and independent testing are limited. Review tags, changelog, CI, and release authenticity before relying on it, and note that GPL-3.0 can trigger copyleft obligations if you redistribute a derivative theme or product. For internal use it is usually acceptable, but legal review is needed for distributed products.
Weaver
How can I help you explore Laravel packages today?