Google Search Console, end to end: verify your domain and get indexed

Search Console is the only place Google tells you what it thinks of your site. Setting it up takes twenty minutes; reading it correctly is what actually gets pages indexed.

11 min read · Last updated

Before you start

You need three things: a Google account, the ability to edit either your DNS records or the HTML of your homepage, and a site that is live on its final domain. Do not set Search Console up against a temporary staging address — the property is tied to the exact host, and moving later means starting again.

It also helps to have your sitemap ready at a stable URL, usually https://example.com/sitemap.xml. If you do not have one yet, create it before verification so the whole setup fits into a single sitting.

Step 1 — choose the right property type

When you add a property, Google offers two kinds, and the choice matters more than it looks.

  • Domain property (example.com): covers every subdomain and both http and https. Verified only by adding a DNS TXT record. This is the option to pick if you can edit DNS — it never breaks and never leaves half your traffic in a second property.
  • URL-prefix property (https://example.com/): covers exactly that scheme and host. https:// does not cover http://, and the bare domain does not cover www. Verified by HTML tag, HTML file, Google Analytics, Google Tag Manager or DNS.

If you cannot reach your DNS panel, use a URL-prefix property with the HTML meta tag — and add a second property for the www version so you are not blind to half your URLs.

Step 2 — verify ownership

For a domain property, Google shows you a TXT record. In your registrar or DNS host, add a TXT record on the root of the domain (host field @ or blank) with Google's string as the value. Save, wait — propagation is usually a few minutes but can take a few hours — then press Verify. If it fails the first time, wait and press it again rather than generating a new record.

For a URL-prefix property with the meta tag method, Google gives you a complete tag. Paste it, unchanged, inside the <head> of your homepage HTML — not in the body, not inside another tag, and not injected by JavaScript after the page loads, because Google fetches the raw HTML. Deploy the change, confirm the tag is live by viewing the page source of your real homepage, then press Verify.

  • Keep the verification tag or DNS record in place permanently. Removing it un-verifies the property and you lose access to the data.
  • Verification says nothing about indexing. A verified property with zero indexed pages is completely normal on day one.

Step 3 — submit the sitemap

  1. Open the sitemap URL in your own browser first. It must return XML, not an HTML error page, and every <loc> must use the same scheme and host as the property.
  2. In Search Console, open Sitemaps in the left menu.
  3. Enter the path relative to the domain — sitemap.xml, not the full URL — and press Submit.
  4. Refresh after a few minutes. Status should read Success with a discovered-URL count matching your file.

Also add a Sitemap: line pointing at the absolute sitemap URL at the bottom of robots.txt. It costs nothing and lets crawlers that never see Search Console find the file.

Step 4 — resubmitting after changes

You do not need to resubmit every time you publish. Google re-fetches a submitted sitemap on its own schedule, and a changed file is picked up automatically. Resubmit — by deleting the entry and adding it again, or simply pressing submit on the same path — when the sitemap URL itself changes, when the status shows an error you have since fixed, or after a large batch of new pages goes live and you want the re-fetch sooner.

  • Couldn't fetch: the URL 404s, times out, or is blocked in robots.txt. Load it yourself in a private window to reproduce.
  • Has errors: usually URLs from a different host, malformed XML, or entries returning 404. Fix the file, then resubmit.
  • Success but 0 discovered URLs: the file parsed as an empty urlset, or the <loc> hosts do not match the property.

Step 5 — ask for the first pages to be indexed

Use URL Inspection at the top of Search Console. Paste a full URL, wait for the result, then press Request Indexing. This puts the page into a priority crawl queue. It is rate-limited to a handful of requests a day, so use it on your homepage and two or three of your strongest pages, not on everything.

Read the result carefully. 'URL is not on Google' plus 'Discovered – currently not indexed' means Google knows about the page but has not judged it worth crawling yet; that is a content and internal-linking problem, not a technical one. 'Crawled – currently not indexed' means it was fetched and passed over — usually thin or near-duplicate content. 'Blocked by robots.txt' or 'Excluded by noindex tag' are direct instructions in your own code that you can remove today.

Step 6 — what to expect, and when to worry

  • Days 1–3: the property shows no data at all. Normal.
  • Week 1: the homepage and a few linked pages appear as indexed. Impressions in the Performance report are still near zero.
  • Weeks 2–4: most linked, substantial pages are indexed. Long-tail impressions begin.
  • Beyond six weeks with pages still unindexed: the pages are almost certainly reachable but judged not worth indexing. Add depth, merge thin pages, and link to them from somewhere prominent.

Indexing is not a queue you can jump. Repeatedly requesting indexing for the same URL does not increase its chances; improving the page and the links pointing at it does.

The three reports worth checking weekly

  • Pages (under Indexing): the split between indexed and not-indexed pages, with a reason for every exclusion. This is where 'Crawled – currently not indexed' shows up in bulk.
  • Performance: queries, impressions, clicks and average position. Zero clicks with rising impressions means you are ranking on page three or four — a content-depth signal, not a technical fault.
  • Sitemaps: last read date and discovered URL count. A last-read date weeks old on a site you keep updating suggests low crawl demand.

Frequently asked questions

Do I need Search Console for AdSense approval?
No, it is not a requirement. But an AdSense reviewer looks at a site Google can crawl and understand, and Search Console is the only place that tells you whether crawling is actually working. Fixing what it reports removes most of the technical grounds for rejection.
How long does verification take?
The meta-tag method verifies in seconds once the tag is live. The DNS method depends on your provider — usually minutes, occasionally several hours. If verification fails, confirm the record or tag is visible publicly before regenerating anything.
Should I submit every page with URL Inspection?
No. The daily quota is small and the sitemap already tells Google about every URL. Use it for the homepage, your best pages, and anything you have just substantially rewritten.
My sitemap says Success but nothing is indexed. What now?
Success means Google read the file, nothing more. Check the Pages report for the exclusion reason. Most commonly it reads 'Discovered – currently not indexed', which points at content depth and internal links rather than anything you can fix in the sitemap.
Can I verify a site I do not own?
No, and you should not try. Both verification methods require changing something only the owner controls, which is the point.

Check your own site

Run the free checker to see where your site stands on HTTPS, ads.txt, robots.txt, sitemap, viewport, policy pages, content depth and page speed.

Run the checker