Skip to content
Loadbearing

Why your v0 site isn't showing on Google

Checked against the sources below on 20 September 2026.

Vercel says v0 builds SEO in from the start. If that is true and your site still isn't on Google, the cause is more likely in how it was deployed or configured than in the generated code. This guide shows what to check.

We checked Vercel's and Next.js's documentation on 20 September 2026.

What v0 sets up by default

Vercel's post about v0 lists these defaults:

  • Title and description management.
  • Open Graph and Twitter card generation.
  • Support for JSON-LD structured data.
  • Server-side rendering with the Next.js App Router and Server Components, so the full HTML arrives with the request.
  • Image optimisation with next/image, and font optimisation.
  • Mobile-responsive design.

The post doesn't mention a sitemap or a robots file, so check that yours has them.

Check 1: are you looking at a preview?

Vercel adds an X-Robots-Tag: noindex header to every preview deployment. When a new deployment is promoted to production, the previous production deployment also starts returning noindex. That is by design, so previews and old versions stay out of search. Vercel leaves the header off when you assign a custom domain to a non-production branch.

Two things follow. A shared preview link will not appear on Google. And if your domain points at a branch and not at production, check what it sends. In a terminal, run this and look for x-robots-tag in the output:

curl -I https://yourdomain.com

Check 2: does the project have a sitemap and a robots file?

Next.js lets you add both as small files in the app folder: app/sitemap.ts and app/robots.ts. The sitemap lists the pages you want indexed, and the robots file points crawlers to it. Open yourdomain.com/sitemap.xml and yourdomain.com/robots.txt. If either is missing, that is a quick fix.

Check 3: titles and descriptions on every page

v0 manages metadata for you, but the words in it come from what was written for each page. Open a few pages and read the title in the browser tab. Each should say what that page is about, and no two should match.

Check 4: domain and Search Console

  1. Make sure your custom domain is assigned to the production deployment.
  2. Verify the site in Google Search Console and submit your sitemap.
  3. Inspect an address and read the exact status Google gives. "Discovered, currently not indexed" and "Crawled, currently not indexed" mean different things.

Our Fix & Launch service starts at $450. We check the headers, sitemap, robots file, metadata and Search Console, fix what is missing in the code, and redeploy. We can't promise rankings, but we can make sure nothing in the setup is keeping your pages out.

Ask us to check your v0 site

Sources

More guides