Product Decisions This Supports
- Build vs. buy vs. borrow for SEO surface area. This package is a candidate to supply the SEO plumbing (meta/Open Graph output, sitemaps, schema markup, redirects — confirm exact coverage before committing) on Statamic-powered properties, instead of an engineering build or a license for Statamic's first-party SEO Pro.
- Standardization across the site portfolio. Whether to pick one SEO addon for every Statamic property, or let each site/property owner choose. This package's tiny footprint (15 stars, 0 dependents) argues against making it the standard.
- Roadmap scoping and sequencing. Adopting an existing addon removes SEO work from the core content-platform backlog, freeing engineering capacity for revenue-facing features.
- Migration path. If any property still runs a legacy Statamic v2 Aardvark SEO setup, this is the cheapest continuity option — it converts a rewrite into an upgrade.
- Content-ops autonomy. Determines whether marketing can self-serve SEO metadata in the control panel or must file engineering tickets for every page.
- Dependency risk posture. The real decision here is "code we adopt and own" vs. "vendor we rely on." At 15 stars, 0 dependents, a single maintainer, and a
NOASSERTION license, this is not a vendor relationship — it's a fork candidate.
When to Consider This Package
Consider it when:
- The stack is Statamic 3/4/5 on Laravel — this is a Statamic addon, not a general Laravel package, so the lock-in is to Statamic's addon lifecycle and version cadence.
- The sites are small-to-medium content properties where basic on-page SEO is sufficient and nobody needs an enterprise SEO suite.
- You have in-house PHP capacity to read the source, pin versions, and fork if upstream goes quiet.
- Legal/procurement has cleared the license.
NOASSERTION is a hard gate — do not adopt until the actual license is identified and approved.
- You're replacing a legacy Aardvark SEO install and want continuity over a clean-room rewrite.
Look elsewhere when:
- License clarity, support SLAs, security-response commitments, or indemnification are required — none of those exist here.
- You need multi-site or multi-language SEO metadata at scale, content audits, automated structured data, or edge redirects.
- You already license Statamic SEO Pro and the feature delta is marginal; the switching cost likely exceeds the savings.
- Zero dependents and a recent-but-single-maintainer release history mean the API surface is unvalidated and documentation is likely thin. Treat that as real integration risk, not a footnote.
- The team is on plain Laravel without Statamic — this package does nothing for you.
Re-evaluation triggers: license resolved to a recognized OSI license, maintainer count increases, dependent count grows, or a security advisory lands.
How to Pitch It (Stakeholders)
To executives: This is a small, narrowly scoped addon that replaces a build task on our Statamic sites at essentially zero license cost. The trade-off is dependency risk: it has almost no adoption, one maintainer, and an unresolved license. Recommendation is a timeboxed pilot on one low-traffic property — not a platform commitment — with a pre-agreed fallback to SEO Pro or an in-house build. Cost of finding out is a few engineer-days; cost of standardizing prematurely is an unmaintained dependency in the revenue-adjacent SEO path.
To engineering: Composer-installable Statamic addon on Laravel — low integration cost. Ask: vendor and pin the package, read the source to confirm actual feature coverage, and assume we may own it. Budget explicit time for that review rather than treating install as done.
To marketing: They get editable SEO fields and generated metadata in the CMS without filing tickets. Caveat: capability set must be verified against what they assume before promises are made.
The ask: One property, one sprint, three exit criteria — license resolved, feature parity confirmed, no security flags — then a go/no-go on broader rollout.