Statamic Linkwise Laravel Package

Product Decisions This Supports

• Build vs. buy for link health / content auditing. This package gives you internal-link graph visibility (inbound/outbound coverage, orphaned entries, broken links) without a custom crawl-and-index subsystem. The PM decision is whether link health is a differentiator or table stakes — if table stakes, buy.
• Internationalization as a first-class product capability. The v1.3.0 per-locale filter on Overview stats is a genuine product-level unlock: until now, a multilingual site's headline numbers were blended across languages, which meant you could not answer "is the French site healthy?" without manual work. Per-locale scoping turns the Overview from a vanity dashboard into a per-market health check — relevant for roadmap decisions on localization investment, market launch readiness, and content parity across locales.
• Feature prioritization for content ops. Broken-link counts, orphaned entries, and inbound/outbound coverage map directly to backlog items: content refresh, internal-linking campaigns, redirect hygiene, and translation QA. Stats you can slice by locale let you rank work per market rather than by aggregate noise.
• Roadmap gating for multilingual launches. "All languages" staying unchanged preserves the global view for exec reporting; the new locale filter supports go/no-go per market. Together they cover both steering and operating views.
• Bug-fix confidence signal. The restoration of the per-language entry-count chips (broken since 1.2.0) is a reminder to treat minor-version UI regressions as a maintenance cost when judging the package against in-house ownership.

When to Consider This Package

Consider it when:

• Your product runs on Laravel/PHP and content lives in Eloquent models the package can index.
• You operate a content-heavy or editorial surface where internal linking, orphan pages, and broken links materially affect SEO, crawl budget, or user trust.
• You are multilingual and need per-locale health reporting — this release makes the Overview genuinely usable per market, which was previously a gap.
• You want link auditing inside the app (dashboards for editors/ops) rather than a separate SaaS crawl tool with its own auth, cost, and data-egress story.
• You need a cheap, fast baseline before committing to an enterprise SEO platform.

Look elsewhere when:

• You need real-time crawling of external sites, JS-rendered pages, or log-file/analytics-backed link discovery — this is an in-app content graph tool, not a crawler.
• You are not on Laravel, or content is not modeled in a way the package can index without heavy glue.
• You need enterprise SEO suite features: rank tracking, backlink profiles, SERP monitoring, historical trend warehouse.
• You require vendor-supported SLAs or a formal security review process — open-source maintenance risk is yours to absorb.
• Your multilingual need is machine translation or locale routing — this release improves reporting, not translation workflow.

How to Pitch It (Stakeholders)

For executives: We can get per-market visibility into content and link health without building an auditing system. The 1.3.0 release closes the multilingual reporting gap — we can now see entry counts, orphaned pages, broken links, and link coverage per language, not just as a global blend. That directly supports decisions about whether to keep investing in specific locales. Low cost, contained scope, no new vendor contract.

For engineering: It is a Laravel-native package, so it plugs into existing models and auth rather than introducing a separate service. This release is additive and non-breaking — "All languages" behaves exactly as before; the locale filter is opt-in, reusing the same filter component already shipped on the Links and Broken Links pages, so there is no new pattern to maintain. It also fixes a UI regression from 1.2.0 where per-language entry chips stopped rendering — worth flagging as evidence that minor upgrades need a visual smoke test. Integration effort is modest; the real cost is keeping the index fresh (scheduling) and validating that our content model maps cleanly.

For content/SEO teams: You get a per-locale dashboard for broken links, orphaned entries, and inbound/outbound coverage, plus the returned per-language entry counts — which makes it practical to run localization QA and internal-linking campaigns market by market instead of guessing from a single blended number.