Findable Laravel Package

Product Decisions This Supports

• Build vs. buy for SEO tooling on Statamic sites. Whether to adopt a free, off-the-shelf add-on for meta tags, Open Graph, and sitemap controls instead of building custom fieldsets and templates.
• Roadmap sequencing for marketing/content sites. Helps decide if baseline SEO controls ship as a small add-on task this sprint or become a larger custom initiative next quarter.
• Dependency and vendor-risk reviews. Informs the "safe to depend on?" call for a low-adoption, stale package before it enters the stack.
• Content-ops ownership. Who edits meta data, how editors manage SEO fields in the CMS, and where governance lives for canonicals, redirects, and titles.
• Not a differentiator. Treat as commodity plumbing — decisions should hinge on maintenance cost and time-to-value, not feature depth.

When to Consider This Package

Consider it when:

• You run Statamic (Laravel-based CMS) and need basic on-page SEO controls fast.
• Budget or procurement is constrained; MIT license means no purchase cycle.
• The site is small-to-midsize with simple SEO needs (meta, OG, sitemap).
• You have PHP/Statamic capability to review, pin, and fork the code.

Look elsewhere when:

• Staleness is disqualifying. Last release January 2022 and only 13 stars: small user base, thin peer support, untested against recent Statamic/PHP versions.
• You need vendor support, an SLA, or clear long-term maintenance commitments.
• Requirements are advanced: structured data, hreflang/i18n, canonical logic, redirects, Core Web Vitals.
• Enterprise, multi-site, or compliance-sensitive contexts where dependency provenance matters.
• You are not on Statamic — this package is irrelevant outside that ecosystem.

Recommendation: Time-boxed spike, source review, and a fork-and-own plan before committing. If SEO is revenue-critical, prefer a maintained alternative or an in-house build.

How to Pitch It (Stakeholders)

Executives: A free, MIT-licensed SEO add-on for our Statamic CMS. Cheap to trial and quick to integrate, but it has a small community and no release since early 2022 — frame it as a low-cost build-vs-buy experiment, not a strategic platform bet. The risk is maintenance, not money.

Engineering: Thin add-on around CMS fields and templates. Review the source, pin the version, verify compatibility with our Statamic and PHP versions, and add tests around field output. Budget a few days to fork and own it if we adopt.

Product: Expect commodity SEO plumbing, not differentiation. Validate with SEO KPIs — indexation, click-through rate, organic traffic — and force a decision within one sprint: adopt, fork, or replace.