nuxtjs-seo-skilld

name	nuxtjs-seo-skilld
description	ALWAYS use when writing code importing "@nuxtjs/seo". Consult for debugging, best practices, or modifying @nuxtjs/seo, nuxtjs/seo, nuxtjs seo, nuxt-seo, nuxt seo.
metadata	{"version":"4.0.2","generated_by":"Anthropic · Opus 4.6","generated_at":"2026-03-22T00:00:00.000Z"}

harlan-zw/nuxt-seo @nuxtjs/seo

Version: 4.0.2 Deps: @nuxt/kit@^4.4.2, @nuxtjs/robots@^5.7.1, @nuxtjs/sitemap@^7.6.0, nuxt-link-checker@^4.3.9, nuxt-og-image@^6.0.5, nuxt-schema-org@^5.0.10, nuxt-seo-utils@^7.0.19, nuxt-site-config@^3.2.21 Tags: latest: 4.0.2

References: package.json — exports, entry points • README — setup, basic usage • Docs — API reference, guides • GitHub Issues — bugs, workarounds, edge cases • GitHub Discussions — Q&A, patterns, recipes • Releases — changelog, breaking changes, new APIs

Search

Use skilld search instead of grepping .skilld/ directories — hybrid semantic + keyword search across all indexed docs, issues, and releases. If skilld is unavailable, use npx -y skilld search.

skilld search "query" -p @nuxtjs/seo
skilld search "issues:error handling" -p @nuxtjs/seo
skilld search "releases:deprecated" -p @nuxtjs/seo

Filters: docs:, issues:, releases: prefix narrows by source type.

Best Practices

• Set url, name, description, and defaultLocale in the site key of nuxt.config.ts -- this shared config feeds all 6 sub-modules (sitemap, robots, schema.org, og-image, link-checker, seo-utils) so they stay consistent without per-module duplication. Omit defaultLocale if @nuxtjs/i18n is installed since it provides it automatically source

• Use useSeoMeta() instead of useServerSeoMeta() for per-page descriptions -- useServerSeoMeta only sets meta server-side, and the SEO Utils client-side plugin will overwrite it with the site.description fallback on hydration. The maintainer has noted useServer* composables may be deprecated in Unhead v2 source

• When using Nuxt Content v3, load @nuxtjs/seo before @nuxt/content in the modules array -- the module order matters because asSeoCollection() augments content collections, and the SEO module must register its schemas before Content processes them source

• Wrap Nuxt Content v3 collections with asSeoCollection() from @nuxtjs/seo/content instead of composing individual asSitemapCollection/asSchemaOrgCollection/etc -- the unified helper applies all SEO collection augmentations in one call and avoids the composition problem where individual wrappers cannot be nested source

• Disable nuxt-og-image via ogImage: { enabled: false } if you are not using dynamic OG images -- it is opt-in (does nothing by default) but still adds 2-5MB to the server bundle. In serverless environments targeting sub-1MB workers, either disable it or use Zero Runtime mode to prerender images at build time source