---
title: "Troubleshooting"
description: "Learn how to troubleshoot common Nuxt SEO issues and find helpful resources."
canonical_url: "https://nuxtseo.com/docs/nuxt-seo/getting-started/troubleshooting"
last_updated: "2026-05-25T06:22:10.913Z"
---

## Debugging Tools

Use these free tools to diagnose SEO issues:

- [Meta Tag Checker](/tools/meta-tag-checker) - Validate title and description
- [Social Share Debugger](/tools/social-share-debugger) - Debug OG images
- [Robots.txt Generator](/tools/robots-txt-generator) - Test robots rules
- [Schema.org Validator](/tools/schema-validator) - Validate structured data
- [XML Sitemap Validator](/tools/xml-sitemap-validator) - Check sitemap structure

Have a question about Nuxt SEO? Check out the frequently asked questions below or
[Jump in the Discord](https://discord.com/invite/5jDAMswWwX) and ask me directly.

## Troubleshooting FAQ

### Should I use @nuxtjs/seo or the individual modules?

`@nuxtjs/seo` is an alias that installs all 6 modules at once. It contains no extra logic. You get the exact same modules, features, and configuration options either way.

Use `@nuxtjs/seo` for convenience. Install modules individually if you only need a few of them or want version pinning control.

See the [Introduction](/docs/nuxt-seo/getting-started/introduction#nuxtjsseo-vs-individual-modules) for more details.

### Can I use the modules separately?

Yes! Nuxt SEO is designed to be flexible and work however you need it to.

### Do I need to install nuxt-site-config separately?

No. `nuxt-site-config` installs automatically when you install any Nuxt SEO module (whether via `@nuxtjs/seo` or individually). You never need to add it to your `modules` array.

### How do I set up Nuxt Content with multiple SEO modules?

Use each module's `defineXxxSchema()` function in your `content.config.ts`. Only include schemas for the modules you use.

See the [Nuxt Content guide](/docs/nuxt-seo/guides/nuxt-content) for the full setup.

### Why does my production build go up so much?

Server-side features add 2-5MB to the production build but don't affect client-side runtime performance since most module logic runs on the server.

If the production build size is a concern, you can [disable the modules](/docs/nuxt-seo/guides/debugging-modules#disabling-modules) you don't need.

If you are using Nuxt SEO in a serverless environment, you may want to keep your workers under 1MB. The module that will contribute the most to your worker size is `nuxt-og-image`.

<warning>

If targeting <1MB workers (Cloudflare Workers free tier), disable nuxt-og-image or switch to Zero Runtime mode to stay under the size limit.

</warning>

Options:

1. Disable it: `ogImage: { enabled: false }`
2. Use [Zero Runtime](/docs/og-image/guides/zero-runtime) mode (build-time generation)

### What happened to Nuxt SEO Kit?

The Nuxt SEO Kit module was the initial version of Nuxt SEO.

While it generally worked great for some users, it was only useful for server-side generated Nuxt Sites and in turn its feature set was much more limited.

It has been deprecated in favour of the new Nuxt SEO module.

See the [migration guide](/docs/nuxt-seo/migration-guide/nuxt-seo-kit) for more information.

## Create a Reproduction

When filing issues, include a minimal reproduction. See [Debugging Modules](/docs/nuxt-seo/guides/debugging-modules#creating-a-minimal-reproduction) for [StackBlitz](https://stackblitz.com) playgrounds.