---
title: "Getting Your Nuxt Site Indexed"
description: "How to get your Nuxt site crawled, indexed, and cited in AI Overviews for the first time."
canonical_url: "https://nuxtseo.com/learn-seo/nuxt/launch-and-listen/going-live"
last_updated: "2026-01-29"
---

Deployed your Nuxt site to production? In 2026, 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, which means Google and AI crawlers see fully-rendered HTML immediately. No JavaScript execution delays.

This gives you faster, more reliable indexing compared to client-side SPAs. Your meta tags, content, and [structured data](/learn-seo/nuxt/mastering-meta/schema-org) (which AI engines rely on) 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`
- Set meta tags during SSR to ensure 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.

**Solutions:**

1. **Server-level redirect** (preferred): 301 redirect all non-canonical URLs
2. **Canonical tags**: Tell 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) you can use the `redirectToCanonicalSiteUrl` option to automatically redirect non-canonical URLs.

See [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 (best for catching all subdomains)
4. Submit your [sitemap](/learn-seo/nuxt/controlling-crawlers/sitemaps) at **Indexing > Sitemaps**

Monitor the **Performance** report for **AI Mode** data to see how often you're appearing in AI Overviews.

## 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**

You get [~10 requests per day](https://support.google.com/webmasters/answer/9012289). Use them for homepage and critical pages.

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

**Instant notification (Bing/Yandex):**[IndexNow](/learn-seo/nuxt/launch-and-listen/indexnow) notifies search engines immediately when content changes. This is critical for getting new content into Bing's AI chat features.

## Core Web Vitals Check

[Google uses Core Web Vitals](https://developers.google.com/search/docs/appearance/core-web-vitals) as a ranking signal. In 2026, **INP (Interaction to Next Paint)** is a primary focus for responsiveness.

<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>

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. Focus on **SEO** and **Accessibility**. 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/harlan-zw/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. Google and LLMs are skeptical of them. The best approach is to 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 [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
- AI crawlers may have crawled but Google decided not to show in Web or AI results
- 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. Monitor **AI Mode** impressions to track citation growth
3. Monitor [Core Web Vitals](/learn-seo/nuxt/launch-and-listen/core-web-vitals) in field data (RUM)
4. 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>