How do you set up Google Search Console for a Next.js site on Vercel (fast)?

Conclusion

For most sites, you only need three steps:

1. Add a property (prefer Domain property)
2. Verify ownership via DNS TXT
3. Submit https://example.com/sitemap.xml

Before you start, confirm these endpoints exist:

• https://example.com/robots.txt
• https://example.com/sitemap.xml

If verification fails, it’s usually the wrong DNS provider or propagation delay.

Explanation

Search Console setup is easy to overcomplicate. The real problems are operational:

• adding the TXT record to the wrong “authoritative” DNS provider
• assuming DNS changes are instant
• submitting a sitemap that returns 404/blocked URLs

A checklist prevents wasted time and avoids early indexing traps.

Practical Guide

Step 1: choose Domain property vs URL prefix

• Domain property (recommended)

  • covers protocols + subdomains
  • verification is DNS TXT (most stable)

• URL prefix

  • covers a single prefix like https://example.com
  • may support HTML tag / GA / GTM verification

Decision rule:

• If you want the cleanest long-term setup, use Domain property.

Step 2: add the property

Search Console → Add property → Domain → enter:

• example.com

Step 3: add the DNS TXT record

• copy the TXT record Search Console provides
• add it to the DNS provider that is actually authoritative for the domain

Notes:

• propagation can take minutes to hours (sometimes longer)

Step 4: verify ownership

Back in Search Console → click Verify.

Step 5: submit the sitemap

Search Console → Sitemaps → submit:

• https://example.com/sitemap.xml

Step 6: post-setup validation (minimal but important)

Do these once:

• sitemap status becomes Success
• URL Inspection on one important URL
• confirm robots.txt is not blocking important paths

Decision rule:

• Request indexing only for the homepage, hubs, and top pages. Do not spam.

Pitfalls

• TXT record added to the wrong DNS provider (registrar vs Cloudflare vs Vercel)
• incorrect host/name for TXT record
• verification fails due to propagation delay
• robots.txt blocks key paths
• sitemap.xml includes duplicates (slash/casing/params) or blocked URLs

Checklist

• [ ] robots.txt returns 200 and is accessible
• [ ] sitemap.xml returns 200 and is accessible
• [ ] Domain property is used (or URL prefix is chosen intentionally)
• [ ] DNS TXT record is added to the authoritative DNS provider
• [ ] Ownership verification succeeds
• [ ] Sitemap is submitted in Search Console
• [ ] Sitemap status is Success (after processing)
• [ ] One representative URL is inspected
• [ ] Canonicals are consistent (no mixed slash/casing/params)
• [ ] Request indexing is used only for top pages (not daily spam)

FAQ

Q1. Domain property or URL prefix—what should I choose?

Domain property is usually best for long-term stability because it covers protocols and subdomains in one place.

Q2. Why is verification failing even after I added the TXT record?

Most often the record was added to the wrong DNS provider, or DNS propagation hasn’t completed yet.

Q3. When should I use “Request indexing”?

Use it for the homepage, hubs, and your most important pages. It is not a daily fix for broad indexing issues.

Internal links

• Parent hub: Indexing: start here
• Related:
  • Discovered but not indexed checklist
  • Crawled, currently not indexed fixes
  • Canonical + hreflang pitfalls (Next.js i18n)

Disclaimer

Indexing is probabilistic. You can improve signals, but you can’t force Google to index every URL.