Weave Code
Seo Helper Laravel Package
arcanedev/seo-helper
Laravel package for managing SEO metadata with a clean API. Set page titles, meta descriptions, keywords, canonical URLs, robots directives, Open Graph, and Twitter Card tags, with Blade helpers for easy integration.
:mag: SEO Helper is a package that provides tools and helpers for SEO (Search Engine Optimization).
Frequently asked questions about Seo Helper
- How do I install arcanedev/seo-helper in a Laravel app?
- Install it with Composer using composer require arcanedev/seo-helper. Laravel package auto-discovery should register the service provider; publish the optional config if you need to change defaults. After installation, verify package discovery, facade aliases, config caching, and Blade rendering in a non-production spike.
- Which Laravel and PHP versions does arcanedev/seo-helper support?
- The latest recorded release is 2024-03-21, so do not assume support for the current or next Laravel and PHP versions. Check the package's composer constraints and Packagist metadata, then run composer why-not against your application's dependency set. A CI matrix across your supported PHP and Laravel versions is the safest way to confirm compatibility.
- How do I set page titles and meta descriptions with SEO Helper in Blade?
- Use the package's facade or Blade helpers to set page titles, meta descriptions, keywords, canonical URLs, robots directives, Open Graph, and Twitter Card tags per request. For maintainability, wrap those calls in your own Blade component or SeoPresenter service rather than calling the facade directly throughout views. Confirm the final HTML output and verify escaping for dynamic values.
- Does arcanedev/seo-helper support canonical URLs, robots directives, Open Graph, and Twitter Card tags?
- Yes, the package is presented as supporting page titles, meta descriptions, keywords, canonical URLs, robots directives, Open Graph, and Twitter Card tags. Those are rendering helpers, not proof that every SEO requirement is covered. Validate the exact output and options for your installed version.
- Does arcanedev/seo-helper handle JSON-LD, hreflang, sitemaps, or multilingual SEO?
- The package is not described as a full SEO platform and should not be assumed to provide JSON-LD, hreflang, sitemap generation, redirects, or multilingual metadata without explicit verification. Its documented scope is metadata and tag rendering for server-rendered pages. If you need those broader capabilities, evaluate them as separate requirements or choose a different tool.
- How should I handle escaping for user-supplied SEO metadata?
- Output escaping for user-supplied meta values must be verified before production use. Test quotes, ampersands, angle brackets, and attribute contexts in the rendered HTML, especially for CMS-entered titles and descriptions. If the package's behavior is unclear, sanitize values in your own wrapper and add HTML-output tests.
- How do I configure or override arcanedev/seo-helper tag rendering?
- Publish the optional config if you need to adjust defaults, then baseline it in version control. Before relying on overrides, confirm which parts of tag rendering and configuration are intentionally overridable in your supported version. Keep an internal wrapper or Blade component so templates depend on your API, not the package facade, and test config caching after changes.
- Can I use arcanedev/seo-helper with Inertia, an SPA, or an API-first Laravel app?
- The package fits Laravel monoliths and server-rendered Blade pages best. For Inertia, SPA, API-first, or headless frontends, it is insufficient on its own unless SEO tags are injected server-side or through SSR. Confirm that crawlers receive the correct metadata in the initial HTML response.
- How do I test SEO tags and production cache behavior when using arcanedev/seo-helper?
- Add feature or HTML-output tests that render representative pages and assert critical tags such as title, description, canonical, robots, Open Graph, and Twitter tags. Run those tests under production-like cache settings, including config caching and package discovery, because local development can hide issues. Snapshot tests are useful for catching silent SEO regressions, but review diffs carefully.
- Is arcanedev/seo-helper maintained, and what should I do if it is abandoned?
- The package is small, MIT-licensed, has one primary maintainer, and its latest recorded release is 2024-03-21, so abandonment and compatibility are real risks. Pin the version, review releases and security advisories quarterly, assign an internal owner, and keep a fallback Blade partial or an actively maintained alternative ready. An internal wrapper limits the blast radius if you need to replace it.
Weaver
How can I help you explore Laravel packages today?