Seo Bundle Laravel Package

Product Decisions This Supports

• Social sharing & acquisition strategy: Automatic og:* and twitter:* fallbacks (title, description, URL, image) mean every page ships shareable previews by default — directly supporting decisions about organic reach, referral traffic, and campaign link performance without per-page metadata work.
• Build vs. buy: A drop-in bundle that handles Open Graph, Twitter cards, canonical URLs, and image resolution removes the need to hand-roll meta tag management. Adopt rather than build, freeing engineering to focus on differentiating features.
• Roadmap sequencing of "polish" work: Fallback logic and relative-path resolution are classic "last-mile quality" items that often sit in the backlog. This release delivers them for free, so we can deprioritize metadata hardening on the roadmap.
• Internationalization / CDN and asset strategy: ImageUrlResolver resolving relative paths like /images/logo.jpg to absolute URLs supports decisions about CDN-hosted or subdirectory-deployed assets — social crawlers require absolute URLs, and this closes that gap without app-level changes.
• Extensibility decisions: ImageUrlResolverInterface gives us a customization seam (e.g., tenant-specific asset domains, signed URLs, S3/CloudFront rewriting) — useful when evaluating multi-tenant or white-label architectures.
• Use cases unlocked: Product launch pages, blog/article syndication, marketing landing pages, e-commerce product cards — anywhere link previews drive click-through.

When to Consider This Package

Adopt when:

• The product relies on social/SEO discoverability (marketing sites, content platforms, e-commerce, SaaS landing pages).
• Engineering currently hand-writes meta tags in Blade templates or duplicates Open Graph/Twitter logic across views.
• Pages frequently set a canonical title/description and want social tags to inherit sensibly rather than be repeated.
• Assets are served from relative paths or a CDN and social crawlers are failing to render previews.
• You need a customization seam for image URLs (multi-tenant, white-label, signed URLs) — the new interface covers this.

Look elsewhere when:

• The product is fully authenticated/internal with no public-facing shareable pages.
• You need a broader SEO suite (sitemaps, structured data/JSON-LD, hreflang, robots directives) — verify coverage before committing; this release is scoped to meta/social tags.
• You require a highly opinionated schema/structured-data layer or integration with an external SEO platform.
• You have strict dependency governance and cannot absorb a new Composer dependency (though the release is backward-compatible, so upgrade risk is low).

How to Pitch It (Stakeholders)

For executives: SeoBundle v2.2.0 closes two high-friction gaps — broken social previews from relative images, and missing metadata when pages only define a canonical title/description. The result is reliable link previews across social platforms with zero extra work from content or engineering teams. It is fully backward-compatible, so there is no migration cost or delivery risk; upgrading is a single composer update.

For engineering: The release adds an ImageUrlResolver service (with a swappable ImageUrlResolverInterface) that converts relative image paths to absolute URLs, plus sensible fallbacks: og:url → canonical URL, and og:title/og:description/twitter:title/twitter:description → the page's title/description. SeoManager now accepts an optional resolver via constructor injection, so existing behavior is preserved and customization is opt-in. No removals, no deprecations, full BC. Action: upgrade and, if we need tenant- or CDN-specific asset domains, bind a custom ImageUrlResolverInterface implementation.

Recommendation: Upgrade now (low risk, immediate quality gain) and add a ticket to evaluate a custom ImageUrlResolverInterface if/when we introduce multi-tenant asset domains.