Tool · tool guide

Nuxt SEO: Check Sitemap, Meta, and Schema

Nuxt SEO on the URL users open: confirm sitemap, robots, title, schema, and OG, then read eight lights in about 30 seconds. Greens are not a Google score.

Published Updated 12 min readBy William Zhu & InfiniSynapse Data Team

Author credentials: William Zhu is cofounder of InfiniSynapse (GitHub @allwefantasy · auto-coder). Desk: shipping SEO Health and the /en/tool/ visibility pages. No personal LinkedIn published. About: team / editorial standards.

Publisher credentials: InfiniSynapse has public profiles on GitHub, YouTube, and X. A 2026 WAIC Future Tech OPC excellence award covers the Agentic Data Infra entry (WAIC; third-party recap: Xinhua / Caohejing). That award does not review this page or SEO Health. Method CLI: infinitegrowth on npm. Archive: recognition and scope notes.

Nuxt SEO: Check Sitemap, Meta, and Schema
On this page

By William Zhu · Cofounder, InfiniSynapse · Published: 2026-09-08 · Last updated: 2026-09-27 · Last verified: 2026-09-14 · Reviewed by the InfiniSynapse Data Team.

Reviewed by: InfiniSynapse Data Team · method review 2026-09-14. First-party CLI review of the public nuxt.com homepage. We do not operate a Nuxt production site.

Trust / COI: About · Corrections. InfiniSynapse sells SEO Health and does not operate a Nuxt production host. The nuxt.com numbers below are a desk observation of infinitegrowth@0.1.1, not a Nuxt endorsement.

TL;DR

Nuxt SEO is the toolkit that can write robots, a sitemap, Schema.org, Open Graph, and default meta for a Nuxt app. This page does not install that toolkit. It checks the public URL those files are supposed to match: title, meta, headings, density, images, links, tech, and speed. Paste a route a stranger can open. Skip nuxt dev and localhost.

Direct answer: Use nuxt seo as two steps. The modules may emit crawl files and head tags. This board reads the shipped HTML. We do not operate a Nuxt production site, so the dated board is the public nuxt.com homepage.

On 2026-09-14 we ran npx --yes -p infinitegrowth@0.1.1 seo-health check https://nuxt.com/ --format json --lang en. The sample size is one third-party URL. One dated homepage does not prove every generate job and cannot establish a ranking outcome.

What Nuxt SEO emits on a public route

Key definition: Nuxt SEO names the module ecosystem that can emit crawl files and head metadata for a Nuxt app. On this page the job is a one-URL pass over the public HTML those outputs are supposed to match. Eight lights score that HTML. The pass does not install @nuxtjs/seo and does not grade nuxt.config.

Independent citation: According to [Nuxt.js](https://en.wikipedia.org/wiki/Nuxt.js), Nuxt is an open-source Vue framework for server-rendered and static web apps. Wikipedia supplies that public definition. The CLI numbers below are first-party output, not Wikipedia’s rule.

The Nuxt SEO site documents robots, sitemaps, Schema.org, OG images, SEO utilities, and link checking, plus an AI Ready add-on for llms.txt. Its install line is npx nuxt module add seo. We did not run that command. People who type nuxt seo still need a second look: the file on the host a stranger opens.

Object the modules can emitWhere it lives after deployWhat this page checks
robots.txt and sitemap.xmlTheir own URLs on the public hostOpen the file. Tech only sees hints in this HTML
Schema.org, canonical, titleThe shipped HTMLTitle, meta, and tech
Open Graph imageShare metadata on that HTMLPresent as a tag. It is not one of the eight lights
llms.txtA separate URLOpen the file. These lights do not score it

Eight lights are not the eight modules

The product on infinitegrowth.agency scores title, meta, headings, density, images, links, tech, and speed. Each row is a traffic light. Those names are checker rows. They are not the Nuxt SEO module list. Green means that row did not fail the shipped rule.

Sitemap and robots after generate

Nuxt SEO crawl files are useful only on the hostname users type. sitemap.xml should list the canonical routes you intend to defend. robots.txt should point at that sitemap and should keep preview hosts out of the index. A hint inside one HTML response is not the file.

Google’s sitemap build guide describes how a sitemap lists URLs. It does not fetch your generate folder. After deploy, open /sitemap.xml and /robots.txt on the public host. If the XML itself is the question, continue with the sitemap audit. If the robots file is the question, continue with the robots.txt checker.

A nuxt seo paste of the homepage can still show a tech light for a robots meta tag while the sitemap URL 404s. Run the URL you put in the sitemap first. Then open the sitemap as its own URL.

Title, useSeoMeta, and the tag crawlers receive

Title and meta tell a result page what the URL claims. Headings tell a reader and a parser the same story. The official Nuxt SEO and meta guide defines how useSeoMeta and useHead emit tags. Those composables count for nuxt seo only when the tag is in the HTML a stranger receives.

A missing H1 after a default layout is a heading failure. Five H1s from nested pages are a heading failure. A title that still says “Nuxt” because titleTemplate was never set is a title failure. Those rows are assignable. They are checker findings.

nuxt.com on 2026-09-14

We do not operate a Nuxt production site. The dated nuxt seo board is the public homepage at https://nuxt.com/, not an InfiniSynapse route and not a generate folder on a laptop.

npx --yes -p infinitegrowth@0.1.1 seo-health check \
  https://nuxt.com/ --format json --lang en

Parsing rule: the probe keeps page.title, page.description, page.canonical, issues, images, and speed. It does not open nuxt.config. Exit code 0 means the request completed.

Fieldnuxt.com 2026-09-14
TitleNuxt: The Full-Stack Vue Framework — 34 characters (warning; package window 40–60)
Description140 characters (good; package window 120–160)
Words1491
Canonicalhttps://nuxt.com/
Images / missing alt53 / 0
Issue E/W/G0 / 1 / 7
Speed score79
Speed E/W/G0 / 3 / 4
HTML size356.1 KB (warning)
TTFB31 ms (good)
Blocking scripts0 (good)
Stylesheets4 (warning)
Total requests61 (warning)

The only page-issue warning was title length. Description 140 sat inside the package window. All 53 images had alt attributes. H1, URL, robots, sitemap, and page structure were good. Speed warnings sat in HTML size, stylesheets, and request count. That is a different ledger from the title row.

Those windows are checker rules. Keep nuxt seo on named fields. A credited explanation can reuse the same response. It does not rescore the output.

Grouped status bars for page-issue rows and speed metrics from the 2026-09-14 nuxt.com fetch

Figure: Two series from the nuxt.com CLI JSON. Page-issue statuses are not speed statuses. Title 34 sits in the page-issue family. HTML 356.1 KB sits in speed.

Official docs versus emitted HTML

Nuxt rendering modes and the deployment guide separate development from shipped output. They did not produce the 34-character title or the 356.1 KB HTML. No nuxt.config or development server was opened. On nuxt.com the only page-issue warning was title length, so the first owner is whoever emits <title>.

Schema.org and Open Graph on the live HTML

Schema.org and the share image have to be in the response, not only in a Vue file. MDN’s link-relation reference is the canonical rel context. Google’s structured data intro describes rich-result eligibility. Neither document scores your route.

For nuxt seo, confirm three things on the shipped HTML: a canonical that matches the URL you meant to rank, a JSON-LD block whose type matches the page, and an og:image that is an absolute URL. The Open Graph image is the picture a share card uses. It is not one of the eight lights. When the graph itself is wrong, continue on the schema markup audit. When the canonical target is wrong, continue on the canonical tag checker.

SSR, SSG, and why localhost hides Nuxt SEO

SSR and nuxt generate can emit different HTML for the same Vue file. nuxt dev answers whether the component compiled. A nuxt seo paste answers what is on the shipped URL. Google’s note on dynamic rendering is about what a crawler receives. It is not a reason to grade localhost.

What a localhost preview will hide

localhost:3000 and the Nuxt overlay are for authors. A loopback paste misses CDN headers, the real canonical, and the HTML the generate step wrote. The page you ship still sits on Vue.js, so the checker reads the rendered document. Preview tokens and basic-auth staging have the same limit. If a stranger cannot open the URL, it is the wrong nuxt seo input.

Many static outputs land on Azure Static Web Apps. Paste the hostname users open, not the local generate folder. Use the public route when you changed useSeoMeta or a hero and want lights in half a minute. The pillar hub for the same eight lights, without a framework name, is the SEO health checker. If the other app is App Router, open nextjs seo after this page. The lights do not change.

i18n canonical and one locale URL

Nuxt i18n documents useLocaleHead() for locale head tags. A homepage paste does not infer a second language. Nuxt SEO on a bilingual host means one public URL per locale: its own title, its own canonical, and hreflang only if that markup is in the response you fetched.

Paste /en/... and /zh/... separately. Continue on the multilingual SEO checker for the eight lights on each locale URL. Continue on a hreflang cluster when the question is the alternate cluster, not the title string.

AEO files beside robots and sitemap

Answer engines cite pages they can parse. Nuxt SEO on the module site treats clean HTML, Schema.org, sitemaps, and robots as that base, and documents llms.txt as an extra file. These eight lights do not score llms.txt. Open it on its own URL.

Independent citation 2: According to [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework), that framework is voluntary guidance for managing AI risk. It did not produce these lights, and it does not grade an `llms.txt` file.

When the extra file is the question, use the llms.txt checker. When you need the three crawl files compared, use llms.txt vs robots vs sitemap. Image alt follows the same text-alternative idea as the W3C WCAG guidelines. An amber image row is a repair list for people and parsers.

Eight lights after the modules are installed

Run nuxt seo as a board after the modules have shipped. Read red first, then amber, then green. Fix the light that blocks understanding before you polish density. Two people who paste the same public URL should see the same lights.

Density flags stuffing and thin copy. It is a heuristic. Images flag missing alt and obvious weight. Links flag empty hrefs the checker can already see. Tech reads robots directives, canonical hints, and HTTPS. Speed is a coarse load signal. If tech is red because the host looks unindexable, stop polishing adjectives in the Vue file.

Paste the shipped public URL

Open the SEO Health form or the CLI. Paste the canonical public URL. Skip localhost, skip a signed preview, and skip an admin route. If you would not email the URL to a stranger, do not run nuxt seo on it. After a release, the same paste belongs on SEO health check after deploy.

Wait for eight lights

Give the run about 30 seconds. The board should show title, meta, headings, density, images, links, tech, and speed. The CLI form is npx --yes -p infinitegrowth@0.1.1 seo-health check against that public URL. The click-by-click paste order is how to run an SEO health check.

Read red and amber first

Write every red row in one sentence, then amber. Assign title to whoever owns useSeoMeta. Assign images to the media owner. Assign tech to whoever can change robots or the host headers. A nuxt seo board that blends title 34 and speed 79 into one trophy hides both owners.

Re-run after the deploy

Ship the edit through the production path. Paste the same URL. Compare the outline and the two metadata strings. Hot reload is not a second measurement. One URL is not a 50–500 sample. That wider job is SEO health check vs site audit.

Selection scorecard

Score each row 0–2 when someone asks whether nuxt seo on this page is the right tool today. A row at 0 means pick a different job.

Question012
Do you have one public Nuxt URL?Localhost or a secret hostPreview with a public shareLive canonical route
Do the crawl files exist on that host?Only in the repoSitemap or robots, not bothBoth URLs return on the public host
Do you need lights in about 30 seconds?A build-wide component reviewYou can wait a few minutesYou need the board now
Can you assign a human to each red?No ownerShared inboxNamed owner per light
Will you re-run after the deploy?Trust hot reloadMaybe next sprintSame URL, same day

Under 6 means pick another instrument. 8–10 means paste the shipped URL. Keep the check on one public route and one board.

Failure modes that waste a Nuxt check

The first failure is pasting localhost or a signed preview. Those hosts are the wrong nuxt seo input. The second is treating green as a rank promise. Title 34 on nuxt.com cannot establish a ranking drop, and speed 79 cannot establish a Search Console recovery. The third is checking a draft route and shipping a different path. Re-run on the sitemap canonical. One third-party homepage cannot establish template prevalence.

Cluster guides for this pillar

Pick the next guide by the remaining uncertainty.

Job you actually haveGuide to open next
Same lights, no framework nameSEO health checker
App Router siblingnextjs seo
zh / en on the same hostMultilingual SEO checker
Click-by-click paste orderHow to run an SEO health check
One URL versus a 50–500 sampleSEO health check vs site audit

Check the shipped Nuxt URL, not localhost

Paste the public route and read title, meta, headings, density, images, links, tech, and speed in about 30 seconds.

Run SEO Health Checker

Use a public URL you can stand behind. Do not paste secrets.

Frequently Asked Questions

What is Nuxt SEO?

Nuxt SEO is the module ecosystem that can write head tags, a sitemap, robots, schema, and Open Graph for a Nuxt app. This page checks the public URL those outputs are supposed to match.

Is Nuxt SEO the same as @nuxtjs/seo?

@nuxtjs/seo is the package that installs the core modules together. This nuxt seo page does not run that install. It reads the HTML after deploy.

Does Nuxt SEO generate a sitemap and robots.txt?

The modules can emit sitemap.xml and robots.txt on the public host. This check does not generate them. Open each file on the shipped host, then read the eight lights on one canonical URL.

Do I need to check localhost first?

No. The useful paste is the shipped host. A green board on nuxt dev does not prove the generate output or the CDN headers. Run nuxt seo on the canonical users open.

Is this an official Google score?

No. Nuxt SEO here is a first-party rule board with eight traffic lights on one public URL. Google provides no official Nuxt health number. The 34-character title warning on nuxt.com stays a title warning.

Conclusion

Nuxt SEO emits crawl files and head tags through its modules. This page checks whether the public HTML matches. The 2026-09-14 nuxt.com board showed title 34, description 140, 53 images with alt, speed 79, and HTML 356.1 KB. We do not operate a Nuxt production site, so that homepage stays the labeled third-party fetch. Paste the shipped host, fix red, re-run.

Keep the board in SEO Health. After the generated hierarchy is corrected, a team may request one credited explanation in the InfiniSynapse web app if the raw nuxt seo rows are still unclear. The next useful click is the route you are about to ship.

WZ

William Zhu · Cofounder, InfiniSynapse · GitHub @allwefantasy

Desk-validated SEO Health methods. Corrections: zhuhl@infinisynapse.com · corrections policy.

Nuxt SEO: Check Sitemap, Meta, and Schema