- Does gwd/seo-meta-nova-field work with Nova 4 or Nova 5?
- Not out of the box. The last release is from September 2020 and targets the Nova 3 era, whose custom fields use Vue 2 and an older asset pipeline. Nova 4 and Nova 5 moved custom fields to Vue 3 with a new build process, so the compiled component will not render without a rebuild. On Nova 4 or 5, treat this as a small fork project rather than a drop-in Composer install.
- How do I install gwd/seo-meta-nova-field in a Laravel Nova resource?
- Nominal installation is a Composer require, publishing the compiled assets, and registering the field class in the fields method of your Nova resource. Because the package is unmaintained and targets Nova 3, the safer path is to fork or vendor it into a private repository and add it as a path or VCS repository. Then confirm the field class autoloads and the Vue component is published to Nova's asset directory before relying on it.
- Does this package output meta tags on the front end or only edit them in Nova?
- It only solves the admin input problem. The package provides a Nova field that renders grouped SEO inputs and hydrates or fills a resource attribute; it does not emit meta tags, generate sitemaps, or handle Open Graph image uploads. Rendering canonical, robots, OG, and Twitter tags in your Blade or API layer remains your responsibility.
- What Laravel and PHP versions does gwd/seo-meta-nova-field support?
- The repository has a single release dated 15 September 2020, which places it in the Nova 3 and Laravel 6 to 8 era. There is no evidence it has been validated against PHP 8.1 or current Laravel releases, and there are no dependents or reported tests to confirm otherwise. Check the composer.json constraints before assuming compatibility, and plan to verify it on your exact stack.
- Where does the field store SEO metadata — one JSON column or separate columns?
- The package does not document an opinionated schema in the overview; it hydrates a resource attribute from the grouped inputs. Whether that maps to a single JSON column or discrete columns depends on how you configure the field and your model casts. Confirm the fill and resolve behavior against your schema, because a mismatch can silently write nothing.
- Is it compatible with nova-translatable or spatie/laravel-translatable?
- There is no stated compatibility with nova-translatable or spatie/laravel-translatable, and the package predates much of the current Nova localization tooling. Multi-locale sites would need to verify how the field resolves and fills per-locale values, which likely requires changes to the field class. Assume you will own that integration work if you adopt it.
- Does it validate meta title and description length or escape output?
- No model-layer validation or output escaping is described. The field is an editing surface, so SERP length limits, character validation, and escaping belong in your form requests, model rules, and templates. Do not assume the package sanitizes values before you render them.
- Is gwd/seo-meta-nova-field maintained, and what are the alternatives?
- Treat it as unmaintained source code: one release, no visible maintenance cadence, no reported test suite, around 24 stars, and zero dependents. Alternatives include building a small custom Nova field yourself, using a maintained SEO package for the domain layer alongside a simple JSON field, or forking this one under MIT. The license removes the legal blocker to forking but not the engineering cost.
- Can I use it with Nova 4 by rebuilding the Vue component?
- Yes, that is the realistic path. You would port the Vue 2 component to Vue 3, update it for Nova 4's asset build, and check the field class for deprecated resolve, fill, and withMeta signatures. Add a round-trip test that fills, saves, and resolves the attribute so a silent hydrate or fill mismatch cannot wipe metadata unnoticed.
- How do I verify the field actually saves SEO metadata instead of silently wiping it?
- Write a minimal test that sets values through the field, saves the model, and re-resolves the attribute to assert the round trip. The highest-severity failure mode is a hydrate or fill mismatch on a newer Nova, where the field renders but writes nothing and editors erase metadata on save without an error. Also verify the provenance of the package, since the gwd vendor name and the AndreasGJ repository owner differ.