---
title: "How to Get Your Nuxt Site Indexed"
description: "Submit your sitemap, request indexing, and check Core Web Vitals so Google and AI crawlers find your Nuxt site fast."
canonical_url: "https://nuxtseo.com/learn-seo/nuxt/launch-and-listen/going-live"
last_updated: "2026-07-16"
---

<key-takeaways>

- Nuxt renders on the server by default, so Google and AI crawlers get complete HTML immediately, no render-queue wait
- Submit your sitemap in Search Console, then request indexing for your homepage and other critical pages
- Google's Core Web Vitals are a page-experience signal and tiebreaker, not a ranking requirement; INP under 200ms is the current bar

</key-takeaways>

Deployed your Nuxt site to production? You have three goals: get Google to crawl it, get Google to index it, and get LLMs to cite it. If you haven't launched yet, start with the [Pre-Launch SEO Warmup](/learn-seo/pre-launch-warmup) to build authority before day one. For a quick reference of every step, see the [SEO Checklist](/learn-seo/checklist).

## SSR by Default

Nuxt renders pages on the server by default, so Google and AI crawlers see fully-rendered HTML immediately with no JavaScript execution delay.

This gives you faster, more reliable indexing than a client-side SPA gets. Your meta tags, content, and [structured data](/learn-seo/nuxt/mastering-meta/schema-org) (which AI engines rely on to parse your content) are all present in the initial HTML response.

If you need client-side rendering for specific routes, use `ssr: false` in [route rules](/learn-seo/nuxt/routes-and-rendering/rendering), pre-render pages at build time with `prerender: true`, or set meta tags during SSR so they're always present. For authenticated pages or dashboards where SSR isn't needed, configure it per-route:

```ts
export default defineNuxtConfig({
  routeRules: {
    '/dashboard/**': { ssr: false },
    '/blog/**': { prerender: true }
  }
})
```

## Canonical URL Configuration

Multiple domains or subdomains pointing to your site? Only one version should be indexed and cited. This also prevents [duplicate content](/learn-seo/nuxt/controlling-crawlers/duplicate-content) issues that split your ranking signals.

Example: `www.example.com` and `example.com` both serve your app, but only `example.com` should appear in Google.

Two ways to fix it: a server-level 301 redirect from every non-canonical URL is preferred, since it removes the duplicate entirely. If you can't redirect, a canonical tag tells Google which version is authoritative:

```ts
const route = useRoute()

useHead({
  link: [
    { rel: 'canonical', href: `https://example.com${route.path}` }
  ]
})
```

If you're using the [Nuxt SEO module](/docs/nuxt-seo/getting-started/introduction), use the `redirectToCanonicalSiteUrl` option to redirect non-canonical URLs automatically.

See the [canonical URLs guide](/learn-seo/nuxt/controlling-crawlers/canonical-urls) for implementation details.

## Set Up Google Search Console

You need [Google Search Console](/learn-seo/nuxt/launch-and-listen/search-console) to monitor indexing and AI visibility. Ideally, set this up weeks before launch as part of your [pre-launch warmup](/learn-seo/pre-launch-warmup#set-up-search-console-before-launch). If you haven't yet:

1. Visit [search.google.com/search-console](https://search.google.com/search-console)
2. Add your property (domain property recommended)
3. Verify ownership via DNS, which catches all subdomains
4. Submit your [sitemap](/learn-seo/nuxt/controlling-crawlers/sitemaps) at **Indexing > Sitemaps**

Google rolled out a dedicated [Generative AI performance report](https://developers.google.com/search/blog/2026/06/gen-ai-performance-reports) in Search Console in June 2026, separate from the classic Performance report. It shows impressions, pages, countries, and devices across AI Overviews, AI Mode, and Discover's generative surfaces, combined rather than broken out, and without click or CTR data yet. It's still rolling out property by property, so it may not appear on your site immediately.

## Request Indexing

After sitemap submission, request indexing for important pages.

**Manual method:**

1. Open [URL Inspection](https://support.google.com/webmasters/answer/9012289) in Search Console
2. Enter your URL
3. Click **Request Indexing**

Google doesn't publish an exact quota, but roughly 10-12 requests per day is the commonly observed cap. Use them for your homepage and other critical pages.

**Bulk method:** use [RequestIndexing](https://requestindexing.com/) by @harlan_zw to submit multiple URLs automatically.

**Instant notification:** [IndexNow](/learn-seo/nuxt/launch-and-listen/indexnow) notifies Bing, Yandex, and Naver immediately when content changes. Faster Bing indexing helps content surface in Copilot, which draws on the Bing index; Bing's own [AI Performance dashboard](https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview), launched February 2026, tracks how often your pages get cited.

## Core Web Vitals Check

Google treats [Core Web Vitals](https://developers.google.com/search/docs/appearance/core-web-vitals) as a page-experience signal that its ranking systems reward, mainly as a tiebreaker between similarly relevant pages. INP (Interaction to Next Paint) measures responsiveness; keep it under 200ms.

<table>
<thead>
  <tr>
    <th>
      Metric
    </th>
    
    <th>
      Good
    </th>
    
    <th>
      Poor
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      LCP (Largest Contentful Paint)
    </td>
    
    <td>
      ≤2.5s
    </td>
    
    <td>
      >4s
    </td>
  </tr>
  
  <tr>
    <td>
      INP (Interaction to Next Paint)
    </td>
    
    <td>
      ≤200ms
    </td>
    
    <td>
      >500ms
    </td>
  </tr>
  
  <tr>
    <td>
      CLS (Cumulative Layout Shift)
    </td>
    
    <td>
      ≤0.1
    </td>
    
    <td>
      >0.25
    </td>
  </tr>
</tbody>
</table>

The bar is beatable but not universal: per the [2025 Web Almanac](https://almanac.httparchive.org/en/2025/performance), only 48% of mobile origins pass all three metrics, and LCP is the one that fails most often. Use [PageSpeed Insights](https://pagespeed.web.dev/) or Lighthouse to test. Don't chase perfect scores; fix red flags and move on.

See [Core Web Vitals for Nuxt](/learn-seo/nuxt/launch-and-listen/core-web-vitals) for optimization techniques.

## Lighthouse SEO & AI Audit

Run Lighthouse on your key pages, focusing on the SEO and Accessibility categories. Also check for AI-readiness:

- Structured data (JSON-LD) correctly implemented
- Clear, semantically meaningful headings (H1-H6)
- Descriptive [alt text](/learn-seo/nuxt/mastering-meta/alt-text) for all images
- [llms.txt](/learn-seo/nuxt/launch-and-listen/ai-optimized-content) or [nuxt-llms](https://github.com/nuxt-content/nuxt-llms) configured
- [Internal linking](/learn-seo/nuxt/routes-and-rendering/internal-linking) structure reviewed (no orphan pages)

Use [Unlighthouse](https://unlighthouse.dev/) to audit your entire site in bulk.

## Build Initial Authority

New sites have zero authority, and Google and LLMs are skeptical of them. Start building authority weeks before launch with the [Pre-Launch SEO Warmup](/learn-seo/pre-launch-warmup), which covers domain warmup, content seeding, and early backlink strategies. For ongoing link building after launch, see [Backlinks & Authority](/learn-seo/backlinks).

## Common Nuxt-Specific Issues

For a complete troubleshooting workflow, see the [debugging guide](/learn-seo/nuxt/launch-and-listen/debugging).

### Meta tags not updating on navigation

- Use reactive values in `useSeoMeta()` or `useHead()`
- Verify tags appear in **View Page Source** (not DevTools)
- Check the [Mastering Meta](/learn-seo/nuxt/mastering-meta) guides

### Slow Interaction to Next Paint (INP)

- Avoid long-running tasks on the main thread
- Use `scheduler.yield()` or `scheduler.postTask()` for heavy computations
- Check [Core Web Vitals](/learn-seo/nuxt/launch-and-listen/core-web-vitals) for INP fixes

### Pages "Crawled - currently not indexed"

- Content may be too thin or lack unique value
- This status describes Googlebot's own crawl-then-decide process; it's separate from whether GPTBot, ClaudeBot, or other AI crawlers have visited, since those crawl independently and don't feed Google's index
- See [Debugging Indexing Issues](/learn-seo/nuxt/launch-and-listen/indexing-issues)

## After Launch

1. Check [Search Console](/learn-seo/nuxt/launch-and-listen/search-console) weekly for errors
2. Watch the Generative AI performance report for citation trends once it's available on your property
3. Monitor [Core Web Vitals](/learn-seo/nuxt/launch-and-listen/core-web-vitals) in field data (RUM)
4. Track organic traffic with [SEO monitoring tools](/learn-seo/nuxt/launch-and-listen/seo-monitoring)
5. Keep publishing content and building authority

## Automate with Nuxt SEO

For automatic [sitemap](/learn-seo/nuxt/controlling-crawlers/sitemaps) generation, [robots.txt](/learn-seo/nuxt/controlling-crawlers/robots-txt), OG images, and Schema.org:

<module-card className="w-1/2" slug="sitemap">



</module-card>

<module-card className="w-1/2" slug="nuxt-seo">



</module-card>

## Checklist

<checklist id="going-live-nuxt">

- Set up Google Search Console and verify ownership
- Generate and submit your XML sitemap
- Verify meta tags appear in View Source (not just DevTools)
- Check canonical URLs point to the preferred domain version
- Run Lighthouse SEO and accessibility audits
- Test Core Web Vitals (INP, LCP, CLS) with PageSpeed Insights
- Request indexing for the homepage and key pages
- Build initial authority with the pre-launch warmup and early backlinks

</checklist>