Debugging Modules

Disabling Modules

Since Nuxt SEO installs and enables modules for you, you may run into a situation where you want to disable a module.

The modules have these config keys:

• nuxt-og-image - ogImage
• @nuxtjs/sitemap - sitemap
• @nuxtjs/robots - robots
• nuxt-seo-utils - seo
• nuxt-schema-org - schemaOrg
• nuxt-link-checker - linkChecker
• nuxt-ai-ready - aiReady
• nuxt-skew-protection - skewProtection

You can disable any of these modules by setting the module's enabled value to false in your nuxt.config.ts file.

export default defineNuxtConfig({
  ogImage: {
    enabled: false
  },
  sitemap: {
    enabled: false
  },
  robots: {
    enabled: false
  },
  seo: { // seo utils
    enabled: false
  },
  schemaOrg: {
    enabled: false
  },
  linkChecker: {
    enabled: false
  },
  aiReady: {
    enabled: false
  },
  skewProtection: {
    enabled: false
  }
})

You can also set a key to false. false skips the module setup. enabled: false runs a setup that registers nothing. Both remove the module's routes, tags, and output.

export default defineNuxtConfig({
  ogImage: false,
  aiReady: false,
  skewProtection: false,
})

Keep site enabled. The other modules need Site Config.

To keep @nuxtjs/seo in your modules array but install none of its modules, set nuxtseo to false:

export default defineNuxtConfig({
  nuxtseo: false,
})

A module that you add to modules yourself still installs.

Creating a Minimal Reproduction

When submitting a GitHub issue, a minimal reproduction helps maintainers debug your problem quickly.

Use one of these StackBlitz playgrounds as a starting point:

Nuxt SEO

• Basic
• i18n
• Nuxt Content

Robots

• Basic
• i18n
• Custom Rules

Sitemap

• Basic
• i18n
• Dynamic URLs

OG Image

• Basic Takumi
• Basic Satori
• i18n
• Nuxt Content

Schema.org

• Basic

Link Checker

• Basic

SEO Utils

• Basic

Site Config

• Basic

AI Ready

• Basic

Skew Protection

• Basic

Once you've reproduced the issue, fork the StackBlitz and include the link in your GitHub issue.