Weave Code
Seo Pro Laravel Package
statamic/seo-pro
SEO Pro is a comprehensive SEO addon for Statamic. It adds an intuitive SEO fieldtype for meta titles and descriptions, Open Graph and Twitter Card tags, XML sitemaps, redirects, canonical URLs, and social image support, helping you improve search visibility without leaving the control panel.
Statamic SEO Pro is an addon for the Statamic CMS that gives editors control over on-page SEO without leaving the control panel. Add the SEO fieldtype to entries and terms to manage meta titles, descriptions, canonical URLs, robots directives, and social sharing images, with sensible fallbacks.
- Meta tags for titles, descriptions, Open Graph, and Twitter Cards
- Sitemap generation and canonical URL support
- Robots controls including noindex/nofollow
- Social previews with custom sharing images
- Works with Antlers and Blade templates
Frequently asked questions about Seo Pro
- Can I use statamic/seo-pro in a plain Laravel app without Statamic?
- No. SEO Pro is a first-party, license-gated addon for the Statamic CMS rather than a general-purpose Laravel package. Its blueprint fieldsets, control-panel SEO report, head-rendering tag, and sitemap and redirect routes only exist inside a Statamic runtime. If you are not on Statamic, or are evaluating a move to headless WordPress or Next.js, this package is not a fit. You can still install it in a Laravel app's Composer file, but nothing useful will happen without Statamic.
- Which Statamic versions does SEO Pro support, and how do upgrades work?
- Each addon major tracks a Statamic major, so SEO Pro 7.x only runs on the matching Statamic release line. Check the Composer constraint in the addon's composer.json against the Statamic version in your lockfile before requiring it. Version mismatches are the single most common install failure reported by teams. Write the supported matrix into your runbook, because every Statamic upgrade becomes a compatibility review item for as long as you rely on the addon.
- How do I install statamic/seo-pro?
- The install is composer require statamic/seo-pro, adding your license key to the environment, and publishing the config file. Statamic auto-discovers addons, so there is no service provider to register manually. The real work is post-install: importing the shipped SEO fieldset into your collection blueprints and rendering the head tag once in your layout. Test on a staging site first, since license and version issues surface immediately at boot.
- How does SEO Pro licensing work, and what happens when the license lapses?
- SEO Pro is a commercial, license-gated addon, so each site needs a valid key supplied through the environment or config. The documented behavior at expiry is the part worth confirming in writing before purchase: does it degrade only the SEO report, block control-panel editing, or merely stop updates? Model the answer in your risk register and assign an owner for renewal and procurement budget. Assuming expiry is harmless is a common and avoidable surprise.
- How do I add SEO fields to entries and terms?
- Import the SEO fieldset that ships with the addon into the blueprints of the collections and taxonomies you want editors to control. The data persists in the entry's seo field, and a site, collection, then entry cascade supplies fallback defaults. In practice that means definitions live in one place and editors only override what they need. Before importing, check whether any existing blueprint already uses a seo or seo_pro handle, because collisions produce confusing fallback behavior rather than clear errors.
- How do I output SEO meta tags in Antlers and Blade templates?
- Render the addon's head tag once inside the head of your layout, and it outputs the title, meta description, canonical URL, robots directives, Open Graph, and Twitter Card tags. In Blade you use the same underlying tag rather than hand-writing meta elements. The important step is removing any hand-written title and meta tags, otherwise you get duplicates that confuse crawlers. Custom routes, error pages, and controller-rendered views have no implicit cascade and will silently render defaults, so handle those explicitly.
- Does SEO Pro generate XML sitemaps and redirects?
- Yes. The addon registers routes for XML sitemap generation and for redirects, both driven by configuration and the SEO data on your entries. Canonical URL support and robots directives such as noindex and nofollow are configured per entry through the same fieldtype. Watch the interaction with static or full-page caching: a cached response can keep serving a 200 for a URL you just redirected, so plan the ordering and invalidation. Verify the generated sitemap includes every collection and locale you expect.
- Does SEO Pro work with headless or API-driven front ends?
- The SEO values are stored on the entry, but they do not automatically arrive in the shape a separate front end needs for title, Open Graph, and canonical tags. You are responsible for exposing that field through your API and mapping it into the right head tags in Next.js, Nuxt, or whatever renders the page. Decide up front who owns that mapping so it does not become an afterthought. For server-rendered Statamic views the addon handles this for you.
- Do I need a queue worker and a Chrome binary for SEO Pro?
- SEO report scoring runs through Laravel queues, and its cost scales with entries multiplied by SEO fields and locales, so keep it off the save path and ensure a worker is actually running. Social preview image generation additionally relies on Browsershot and Puppeteer, which means the worker host needs a Chrome or Chromium binary available. Missing the binary produces failed preview jobs rather than obvious errors, so test it in staging before launch. Note that errors during deferred report generation were previously not recorded at all, so a sudden spike after upgrading is usually a correctness fix.
- Should I buy SEO Pro or build my own SEO fields?
- Buy it if you are committed to Statamic and want the standard feature set: an editor-facing fieldtype, sensible fallback cascade, head tag, sitemap, redirects, and social previews. Hand-rolling those is real work, and the addon's config-declared architecture is upgrade-friendly because it does not invade your code. The calculus changes if you need bespoke scoring rules, custom cascade classes, or sitemap URL logic beyond what is exposed, since those push you toward forking and defeat the buy decision. Validate that your content model fits the shipped fieldset before signing.
Weaver
How can I help you explore Laravel packages today?