Aardvark Seo Laravel Package

Product Decisions This Supports

• Build vs. buy for SEO fundamentals. Informs whether we hand-roll meta/OG/robots/sitemap/redirect logic in Antlers templates and a custom fieldset, or adopt an existing Statamic addon and redirect engineering hours to differentiated features.
• Roadmap scoping for a content platform. Maps directly to a discrete "SEO baseline" epic: meta titles/descriptions, canonical URLs, Open Graph/Twitter cards, XML sitemaps, redirects, and editor-facing SERP/social previews. Useful for estimating what a v1 SEO milestone actually requires versus what can be deferred.
• Agency and multi-site standardization. If we run several Statamic builds, a shared SEO fieldset and conventions reduce per-project QA and drift. This is the strongest PM argument: consistency across sites is worth more than any single feature.
• Content operations and editor enablement. Character-count guardrails and previews let content teams self-serve SEO basics, reducing dependency on specialists and shortening the publish cycle.
• CMS migration/consolidation gating. If we are moving to Statamic or evaluating it, "SEO parity" is often a launch blocker. This package is a datapoint on whether parity is achievable without custom work.
• Supply-chain and procurement risk decisions. The license reads NOASSERTION and the listed repository does not obviously match the vendor namespace. That is a legal/provenance question that should be resolved before it appears in a roadmap commitment, not after.
• Contribute vs. fork vs. replace. Low star count and zero listed dependents (weak proxies for an addon, but still signals) mean we should decide up front whether gaps are fixed upstream, forked internally, or worked around in our own layer.

When to Consider This Package

Consider it when:

• We are committed to Statamic and need SEO primitives quickly, with a team small enough that a bespoke implementation is a real cost.
• Editors, not engineers, own metadata and redirects, and need guardrails plus previews.
• Requirements are the common 80%: meta/OG tags, sitemaps, redirects, canonicals — not algorithmic SEO consulting.
• We are willing to audit the source, pin a version or commit, and carry a fork if the maintainer goes quiet.
• We want a configurable starting point we can extend rather than a black box.

Look elsewhere when:

• The stack is not Statamic/Laravel — there is no portable value here.
• Legal cannot accept an unresolved NOASSERTION license; do not adopt until clarified in writing.
• We need enterprise SEO capabilities: automated audits, rank tracking, hreflang and multi-domain internationalization, or integration with a commercial SEO suite.
• We require a vendor SLA, security disclosure process, or long-term support contract. Fifteen stars and zero dependents is a community-support profile, not a vendor-support profile.
• The site is headless/API-first and SEO rendering lives outside Statamic templates, which reduces the addon to a field-definition convenience.
• A well-maintained alternative or Statamic's native SEO capabilities already cover the requirement with less added surface area.

Recommendation: treat it as a pilot candidate on one non-critical property, with a written exit plan (pin, fork, or replace with internal partials), rather than a platform-wide standard.

How to Pitch It (Stakeholders)

For executives. This is a small, low-cost addon that gets SEO hygiene — titles, descriptions, social previews, sitemaps, redirects — into a Statamic site faster than building it ourselves. The value is speed and consistency across sites, not a competitive SEO advantage. The caveats are maturity and licensing: a small community, an unclear license declaration, and a repository that does not obviously match the vendor name. Frame the ask as a time-boxed pilot with a documented exit plan, not a strategic dependency. Expected benefit: reduced engineering hours per site launch and fewer SEO defects found late in QA.

For engineering. Evaluate the integration surface before committing: how fields are exposed in Antlers, what configuration is required, how upgrades are handled, and whether the redirect and sitemap behavior is predictable under caching. Treat the license (NOASSERTION) and the repo/vendor naming mismatch as blockers to resolve with legal and a source review. If adopted, pin a commit, vendor the code, and isolate our usage behind our own templates so a replacement is a contained change.

For product and content teams. It shortens the path to a usable SEO baseline and gives editors direct control with sensible guardrails, which removes a recurring dependency on specialists for routine metadata work. It does not replace an SEO strategy, keyword research, or performance work — those remain separate roadmap items with separate owners.

Bottom line: a reasonable tactical build-vs-buy shortcut for Statamic SEO basics, contingent on license clarity and a willingness to own the dependency. Do not anchor the platform roadmap to it until those two conditions are met.