How to Set Up Google Search Console for a New Site

Setting up Google Search Console takes about fifteen minutes. Create a Domain property, verify it with a DNS TXT record, submit your XML sitemap, then use URL Inspection to request indexing on your best few pages. Data appears within two to three days. Do it on day one — Search Console collects nothing about the period before the property existed.

Choose the right property type first

This is the one decision that's genuinely annoying to undo, and most people get it wrong by pasting in whatever URL was in their address bar.

	Domain property	URL-prefix property
Covers	`example.com`, `www.example.com`, `blog.example.com`, http and https	Only the exact prefix you entered
Verification	DNS record only	Several methods, including HTML tag and file upload
Best for	Almost every site	A folder you control, or a site where you can't touch DNS

Use a Domain property. A URL-prefix property for https://example.com will not show you data for https://www.example.com, so one redirect misconfiguration can make your traffic look like it evaporated. A Domain property is protocol- and subdomain-agnostic, which means it keeps reporting straight through migrations, www changes and subdomain launches.

Adding a URL-prefix property alongside it costs nothing and occasionally helps, because a few third-party tools still expect a prefix. But the Domain property is the one you actually work from.

Verify it

For a Domain property there's exactly one route: a TXT record at your DNS provider.

Click Add property → Domain and enter example.com — no https://, no www.
Copy the TXT record Google shows you.
In your DNS provider (Cloudflare, Namecheap, Vercel, Route 53), add a TXT record on the root — host @ — with that value.
Wait a few minutes and click Verify. Propagation is usually fast but can take up to a day.

For a URL-prefix property you can instead drop a meta tag in <head>, upload an HTML file to your root, or piggyback on an existing Google Analytics tag or Tag Manager container. Google documents each option in its Search Console verification guide.

Never remove the verification token. Deleting the TXT record, or letting a theme update strip the meta tag, un-verifies the property and you lose your view of the reports. A good share of "Search Console stopped working" is someone tidying up DNS.

Submit your sitemap

Go to Indexing → Sitemaps and submit https://example.com/sitemap.xml.

It isn't strictly mandatory — Google finds pages through links eventually — but a new site has almost no inbound links, so the sitemap is the main way Google learns your URLs exist at all. If you're unsure whether you have one, start with do I need an XML sitemap.

Check back the next day. The report should say Success with a discovered-URL count. If that count is well below your real page count, you have a sitemap generation bug, not an indexing problem — fix the file before you go looking for anything else.

Request indexing on the pages that matter

Paste a URL into the search bar at the top of Search Console to open URL Inspection, then click Request Indexing. There's a small daily quota, so spend it on your homepage and your three or four strongest pages rather than working through the whole site.

URL Inspection is also the most useful debugging tool in the product. It tells you whether a URL is indexed, which canonical Google chose, when it was last crawled, and whether the HTML Google rendered matches what you see. When a page isn't ranking, start here — then work through how to get your website indexed by Google.

Your first-week checklist

Domain property created and DNS-verified.
Sitemap submitted and showing Success with a sane URL count.
Indexing requested on the homepage and top pages.
Indexing → Pages reviewed. "Discovered – currently not indexed" is normal on a brand-new site and usually resolves itself. "Blocked by robots.txt" or an exclusion by a noindex tag is a real bug.
Settings → Users and permissions: add a second owner, so one lost Google account doesn't lock you out.
robots.txt checked for an accidental Disallow: /. Staging configs get shipped more often than anyone admits.
Analytics linked, if you use it, under Settings → Associations.

What the reports will and won't show yet

Two expectations worth setting early.

There's a lag. The Performance report runs roughly two days behind. An empty chart on day one means nothing at all.

There's no backfill. Search Console holds 16 months of performance data, but only from the moment the property was verified. If your site has been live for a year without it, that year is simply gone. This is the whole argument for setting it up before you need it.

For the first month or two, Performance will be mostly zeros with a scatter of impressions on long, oddly specific queries. That's the normal shape of a new site, not a fault. Once you're seeing a few hundred impressions a week the numbers start to mean something — and it's worth understanding what average position actually measures before you draw conclusions from it. If you also run GA4, expect the two tools to disagree permanently and by design.

The part Search Console can't fix

Search Console tells you what Google currently thinks of your site. It does not make Google think more of it. A new domain with flawless indexation and zero external links will sit on impressions-without-clicks for a long time, because nothing is signalling that the site deserves a ranking.

That's a links problem, and it's the one lever a new site can pull immediately. Backlinkster pairs you with a site owner in a related niche for a one-for-one in-content swap, each link verified live by code — five a month on the free plan. The wider playbook is in how to get backlinks for a new website.

Frequently asked questions

Is Google Search Console free? Yes, entirely, with no paid tier. You need a Google account and the ability to either add a DNS record or edit your site's HTML.

Do I need Search Console if I already have Google Analytics? Yes. They measure different things. Analytics reports what visitors did once they arrived; Search Console reports what happened in Google's results beforehand — queries, impressions, position and indexing status. Analytics can't show you any of that.

How long until Search Console shows data? Performance data starts appearing two to three days after verification. Indexing reports populate faster, often within a day.

Which verification method is best? DNS. It survives redesigns, CMS migrations and template edits. HTML-tag verification breaks the first time someone deploys a theme that drops the tag from the page head.

Can I set up Search Console for a site I don't own? No. Every method requires control of the domain, its DNS, or its files. An existing owner can grant you access under Users and permissions instead.

Should I create separate properties for www and non-www? Not with a Domain property — it covers both automatically, along with every subdomain and both protocols. That's the main reason to prefer it.

The bottom line

Create a Domain property, verify with a DNS TXT record, submit the sitemap, request indexing on your best few pages, and add a second owner. Fifteen minutes, once. Do it before you think you need it, because Search Console can only ever show you the period during which it was watching.