Skip to main content
← All articles
SEOPublished October 1, 20262 min read

Google Search Console for a New Business Website

How to verify a new site in Google Search Console, submit a sitemap, and read the first indexing signals before you spend on ads.

Search ConsoleSEOSitemapIndexing
On this page

A new business site is invisible to Google until it is discovered and indexed. Google Search Console is the first place I check after go-live—before ads, before “SEO plugins,” and before arguing about rankings.

What you actually need on day one

  1. The production domain (HTTPS, not the staging URL).
  2. A property for the exact host you want indexed (https://example.com).
  3. An XML sitemap that lists real pages, not drafts.
  4. A way to verify ownership: DNS TXT, HTML file, or the tag your stack already prints.

Domain properties cover www and subdomains. URL-prefix properties are stricter. For most client brochure sites I use a domain property so www/apex mistakes show up in one place.

Verification without breaking email

DNS verification is the cleanest method. Add the TXT record Google gives you and wait for propagation. Do not delete existing MX, SPF, or DKIM records while you are in the DNS panel.

If the site is behind Cloudflare, add the TXT there and keep the proxy settings unchanged.

Submit the sitemap, then wait

After verification:

  • open Sitemaps and submit /sitemap-index.xml or /sitemap.xml;
  • confirm the file returns 200 and is not blocked in robots.txt;
  • request indexing only for the homepage and a few money pages—not every URL in a loop.

Indexing is not instant. A healthy small site often shows the first impressions within a few days. Empty reports on hour one are normal.

Signals I watch in the first two weeks

  • Pages — indexed vs. excluded. “Crawled – currently not indexed” on thin tag archives is fine; the same status on the homepage is not.
  • Experience / Core Web Vitals — field data appears only after enough traffic.
  • Enhancements — structured data errors, if you added JSON-LD.
  • Manual actions — should stay empty.

Fix crawl errors that point at the homepage, contact page, or service pages. Ignore vanity warnings on unused WordPress endpoints you already noindex.

Common mistakes on client launches

  • verifying staging (staging.example.com) and wondering why the live domain has no data;
  • submitting a sitemap full of noindex or redirected URLs;
  • blocking CSS/JS in robots.txt “for security”;
  • changing the domain after ads start, without a 301 and a new property.
WhatsApp