To set up Google Search Console, add your site as a property, choose Domain if you can edit DNS or URL prefix if you can't, verify ownership with the method that matches, then submit your sitemap.xml and run URL Inspection on one live page. Verification takes minutes; the first useful data takes a few days.
The rest of this walkthrough is the detail — and, more importantly, how to confirm each step actually worked before you move to the next. Most broken Search Console setups aren't broken at the last step; they're broken at step one, and nobody notices for a month.
What do you need before you start?
Three things, and gathering them first saves a lot of backtracking:
- A Google account — any one will do, but use one you'll still control in two years. Not a contractor's.
- Access to either your DNS records or your site's HTML — this determines which verification method is available to you.
- A live, publicly reachable site. Search Console can verify a site that isn't finished, but it can't report on pages that are password-protected, behind a staging login, or blocked in
robots.txt.
If your site is still on a staging URL, wait. Verifying a staging domain and then migrating creates a property full of URLs that no longer exist.
The step-by-step setup walkthrough
Work through these in order. Each step ends with a check — don't skip the checks, because a silent failure early on produces empty reports that look identical to "no traffic yet."
-
Add the property. Go to Search Console and choose Add property. You'll be offered two types. Domain (
example.com) covers every subdomain and bothhttp://andhttps://in a single property — the cleaner choice, and the one to pick if you can add a DNS record. URL prefix (https://example.com/) covers only that exact protocol and subdomain, sohttps://www.example.com/would be a separate property. Verify it worked: the property appears in your property dropdown, marked unverified. Nothing more happens until step 2. -
Verify ownership with the matching method. A Domain property accepts one method only: a DNS TXT record. Copy the string Google gives you, add it as a TXT record at your registrar or DNS host, save, and click Verify. A URL prefix property offers more: an HTML meta tag in your homepage
<head>, an HTML file uploaded to your root, Google Analytics, or Google Tag Manager. Verify it worked: Search Console shows "Ownership verified." If it fails, wait — DNS changes can take anywhere from a few minutes to several hours to propagate, and clicking Verify repeatedly won't speed that up. Retry in an hour before assuming the record is wrong. -
Leave the verification in place. This is the step people undo six months later during a "cleanup." If you delete the TXT record, remove the meta tag, or swap themes and lose it, Google re-checks periodically and eventually unverifies the property — and you lose access to the data. Verify it worked: re-check the record or tag is still live after any DNS change, theme switch, or site migration.
-
Check for duplicate versions of your site. If you verified a URL prefix property, confirm which version actually resolves —
https://with or withoutwww— and that the others redirect to it rather than serving duplicate content. Verify it worked: type each variant into a browser. Every one should land on a single canonical URL. -
Submit your sitemap. Open Sitemaps in the left menu and enter the path — usually
sitemap.xml. Submit once. You don't need to resubmit after publishing a page; Google re-fetches sitemaps on its own. If you don't have one yet, our XML sitemap guide covers generating it and referencing it fromrobots.txt. Verify it worked: within a day or two the status reads Success with a discovered-URL count roughly matching your page count. "Couldn't fetch" almost always means a wrong path, a redirect chain, or arobots.txtblock — not a Google problem. -
Run URL Inspection on one real page. Paste a live URL into the search bar at the top. This tool tells you what Google actually knows about that specific page: whether it's indexed, when it was last crawled, which canonical Google chose, and whether anything blocks it. Verify it worked: you get a clear verdict. "URL is on Google" means indexed. "URL is not on Google" on a brand-new site is normal and expected — it isn't an error.
-
Request indexing — once — for a page that matters. In the URL Inspection result, click Request Indexing. This nudges Google to recrawl sooner. It does not force indexing, and requesting the same unchanged URL repeatedly accomplishes nothing. Verify it worked: the request is queued. Then wait days, not minutes, and re-inspect.
-
Check the Page Indexing report after a week. Under Indexing → Pages, you'll see how many URLs are indexed and the reasons the rest aren't. Verify it worked: you have data at all. If the report is still empty after two weeks on a live, linked site, revisit verification and your
robots.txt— something is blocking discovery. -
Add Bing Webmaster Tools too. Google isn't the only index worth being in, and Bing's setup can import your verified Search Console properties directly, which takes about a minute. Bing and Yandex also support IndexNow for instant URL submission — a genuinely useful push mechanism that Google does not currently use. Verify it worked: your site appears verified in Bing Webmaster Tools with a sitemap submitted.
What does Search Console actually tell you once it's running?
After a few days, four reports carry most of the value:
- Performance — the queries and pages that brought clicks and impressions from Google Search. This is real query data you cannot get anywhere else, and it's the single best reason to set Search Console up on day one.
- Page Indexing — which URLs are indexed and, for the rest, the specific reason. If yours show crawled or discovered but currently not indexed, that's a quality and priority signal, not a technical break.
- Sitemaps — whether Google can fetch your sitemap and how many URLs it found in it.
- URL Inspection — the per-page ground truth for any URL you're arguing about.
Note what's not there: Search Console reports on Google only, and it shows nothing at all about your presence in directories, business listings, or anywhere else people find businesses. Those channels need their own attention, which is what our website submission guide and the broader search engine indexing guide cover.
What should you not expect from Search Console?
Being verified in Search Console does not get you indexed, and submitting a sitemap does not get you indexed. Both help Google discover URLs faster. Indexing is a separate decision Google makes about whether a page is worth storing — and it says no to plenty of perfectly functional pages.
Two things to let go of. Mass submission tools that blast your URL at hundreds of "search engines" solve a discovery problem a sitemap and a few internal links already solved, and the era when bulk directory submission moved the needle is long over. And no setup step influences where you rank — Search Console is a diagnostic dashboard. It shows you what Google did; it doesn't instruct Google what to do.
FAQ
Should I choose a Domain or URL prefix property?
Pick Domain if you can add a DNS TXT record. It covers every subdomain and both protocols in one property, so you don't end up with four half-populated properties for the same site. Choose URL prefix only when you can't touch DNS — for example on a hosted platform that manages records for you — and verify with the HTML tag or file method instead.
How long does verification take?
The HTML tag and file methods usually verify instantly once the change is live. DNS verification depends on propagation and can take from a few minutes to several hours. If it fails on the first try, confirm the record saved correctly at your DNS host and try again an hour later rather than changing anything.
Do I need to submit my sitemap every time I publish?
No. Submit it once. Google re-fetches submitted sitemaps periodically and picks up new URLs automatically. Resubmitting manually after each post is a habit worth dropping — it doesn't speed anything up.
Why is Search Console showing no data after I verified?
Search Console only collects data from the moment of verification forward — it doesn't backfill history. Expect two to three days before Performance shows anything, and longer on a new site with little traffic. If reports are still completely empty after two weeks on a live, internally linked site, check that verification still holds and that robots.txt isn't disallowing crawlers.
Can I give someone else access without sharing my Google account?
Yes, and you should. Under Settings → Users and permissions, add their Google account as a Full or Restricted user. Keep the owner role on an account you personally control, and remove contractors' access when the engagement ends — an owner who verified via their own DNS record can be difficult to remove later.
Next step
Search Console setup is a one-evening job with a long payoff: verify once, submit the sitemap once, and from then on you have real query data and an honest answer whenever you wonder why a page isn't showing up. Work the nine steps in order, run each check before moving on, and add Bing Webmaster Tools while you're in the mindset. Then remember that Google is one discovery channel among several — getting your site listed where people browse by category is the other half of being found, and that's what AddTopWebsite is for.
