- How do I install the gioppy/statamic-metatags addon in a Statamic 3 project?
- Install it with Composer by running composer require gioppy/statamic-metatags from your project root. Because it is a Statamic 3 addon, it must be installed in a Statamic 3 site rather than a plain Laravel app. After installation, follow the repository README for any publish or configuration steps, then confirm the addon appears in the Statamic control panel.
- What is the difference between global defaults and per-entry meta tag overrides?
- Global defaults let you define a consistent baseline for title, description, canonical, robots, and social tags across your site. Per-entry overrides let editors replace those values on individual entries when a page needs different metadata. The addon resolves these in the control panel so collections stay consistent without hardcoding tags in templates.
- How do I output meta tags in Antlers templates?
- The addon is designed to output title, description, canonical, robots, Open Graph, and Twitter tags from your Antlers templates. You typically add its Antlers tags or variables to your layout head section so every page renders the resolved metadata. Check the README for the exact tag names and syntax for your version.
- Which SEO meta tags does gioppy/statamic-metatags support?
- It covers the common SEO set: title, description, canonical URL, robots directives, Open Graph tags, and Twitter card tags. The package describes itself as able to manage and customize any meta tag, so you can add others beyond the built-in set. Exact supported fields are documented in the repository README.
- Is this addon compatible with Statamic 4 or Statamic 5?
- The package is described as an addon for Statamic 3, so you should not assume compatibility with Statamic 4 or 5. Check the Composer constraints in the repository and the latest releases before upgrading Statamic. If no compatible release exists, look for a maintained fork or an alternative SEO addon.
- Does it support Open Graph and Twitter card tags for social sharing?
- Yes, the addon outputs Open Graph and Twitter tags alongside standard SEO metadata. You define the values globally or per entry in the control panel, then render them in your Antlers layout. This keeps social preview data consistent across collections.
- Can I set a canonical URL and robots directives per page?
- The addon includes canonical and robots tags in its supported metadata set, with global defaults and per-entry overrides. Editors can adjust these values in the control panel for pages that need different indexing or canonical behavior. Verify the exact field behavior in the README for your version.
- What Laravel version do I need for gioppy/statamic-metatags?
- The addon targets Statamic 3, so your Laravel version is determined by the Statamic 3 release you run. Statamic 3 supports specific Laravel versions, and you should match the addon's Composer requirements to your project. Check the package's composer.json and the Statamic 3 upgrade notes before installing.
- How do I avoid duplicate meta tags when using this addon?
- Render the addon's metadata output once in your main Antlers layout and avoid hardcoding the same title, description, or social tags elsewhere. If you have existing SEO fields or partials, remove or conditionally disable them for pages managed by the addon. Then validate the rendered head section in your browser or with an SEO inspection tool.
- Is gioppy/statamic-metatags actively maintained, and what are the alternatives?
- Maintenance status is best checked on the GitHub repository through recent commits, releases, and open issues. Alternatives include managing SEO fields directly in Statamic blueprints or using other Statamic SEO addons. Evaluate based on your Statamic version and whether you need per-entry overrides in the control panel.