If you just launched a site, the fastest way to find out whether Google can actually see it is to set up Google Search Console for your new website. It is free, it takes about 20 minutes, and it is the only tool that tells you directly what Google thinks of your pages: which URLs are indexed, which are blocked, which queries bring clicks, and which technical errors are quietly holding you back.
This guide walks through the full setup in 7 steps, including the two decisions beginners usually get wrong (property type and verification method), and the verification and indexing errors that commonly block new sites during their first weeks online.
What You Need Before You Start
- A Google account (a free Gmail address works, but use a company account you will keep long term).
- Access to your DNS records at your domain registrar or hosting panel (recommended method).
- Or access to your site’s code or CMS (WordPress, Shopify, Squarespace, Wix, Webflow) if you prefer tag verification.
- A live site that returns a 200 status code on the homepage.
- A sitemap URL, usually
https://yourdomain.com/sitemap.xmlor/sitemap_index.xml.
Tip: do not use a personal account that a freelancer or former employee controls. Ownership verification is tied to the account that performs it, and recovering a property later is more painful than doing it right the first time. Related reading: How To Use Google Search Console.
Step 1: Open Search Console and Add a Property
- Go to search.google.com/search-console and sign in with your Google account.
- If it is your first time, Search Console will show the “Welcome” screen with two boxes: Domain and URL prefix.
- If you already have properties, open the property selector dropdown in the top left and click + Add property.
Do not type anything yet. The box you choose in the next step changes which data you see for the life of the property.
Step 2: Choose the Right Property Type (Domain vs URL Prefix)
This is the first fork in the road and the one that causes most confusion. Here is the practical difference:
| Criteria | Domain property | URL prefix property |
|---|---|---|
| What you enter | yourdomain.com | https://www.yourdomain.com/ |
| Data covered | All subdomains (www, blog, shop) and both http and https | Only the exact protocol, subdomain and path you entered |
| Verification methods | DNS record only | HTML file, HTML tag, Google Analytics, Google Tag Manager, DNS |
| Best for | Almost every new site owner who controls DNS | Hosted builders with no DNS access, or tracking a single section such as /blog/ |
| Main drawback | Requires registrar access | Misses traffic on other variants, so data can look artificially low |
Our recommendation
Create a Domain property first. It captures every version of your site in one place, which means you never wonder why the www data is missing or why the http to https migration broke your charts.
Then, if you want granular reporting, add a URL prefix property for the canonical version you actually use (for example https://www.yourdomain.com/). Having both costs nothing and Search Console allows up to 1,000 properties per account.
Step 3: Verify Ownership With a DNS TXT Record (Domain Property)
After you type your bare domain and click Continue, Search Console shows a TXT record that looks like this:
google-site-verification=xxXXxx1234AbCdEf...
How to add it
- Click Copy next to the TXT value in Search Console.
- Log in to the account where your DNS is managed. That is usually your registrar, but if you use Cloudflare or a managed host, DNS lives there instead.
- Open the DNS records or DNS management area.
- Create a new record with: Type = TXT, Name/Host = @ (or leave blank for the root domain), Value = the string you copied, TTL = default or 3600.
- Save the record.
- Wait a few minutes, then return to Search Console and click Verify.
Where DNS records live by provider
| Provider | Path to DNS records |
|---|---|
| Cloudflare | Select site > DNS > Records > Add record |
| GoDaddy | My Products > Domain > DNS > Add New Record |
| Namecheap | Domain List > Manage > Advanced DNS > Add New Record |
| OVH | Web Cloud > Domains > DNS zone > Add an entry |
| Squarespace / Wix / Shopify domains | Domain settings > DNS settings > Custom records |
| Google Domains migrated to Squarespace | Squarespace Domains dashboard > DNS |
Some registrars are listed directly inside Search Console and offer a one click flow. If yours appears in the dropdown, use it: it writes the record for you.
Important: never delete the TXT record after verification succeeds. Google rechecks it periodically, and removing it unverifies the property and cuts off your data and messages.
Step 4: Verify With an HTML Tag or File (URL Prefix Property)
If you cannot reach DNS, choose URL prefix and pick one of these methods.
| Method | How it works | Good for |
|---|---|---|
| HTML tag | Paste a meta tag in the <head> of the homepage | WordPress, Webflow, Shopify, most CMS platforms |
| HTML file | Upload a small file to the site root | Static sites and anyone with FTP or file manager access |
| Google Analytics | Uses an existing GA4 tag on the page | Sites already running GA4 with edit permission |
| Google Tag Manager | Uses an existing GTM container snippet | Teams already managing tags through GTM |
HTML tag on WordPress
- Copy the meta tag from Search Console.
- In Yoast SEO: Yoast SEO > Settings > Site connections > Google, paste only the content value.
- In Rank Math: General Settings > Webmaster Tools > Google Search Console.
- Without a plugin, add the tag to the theme
header.phpinside<head>, ideally in a child theme. - Load your homepage, view source, confirm the tag is there, then click Verify.
HTML tag on other platforms
- Shopify: Online Store > Themes > Edit code > theme.liquid, paste below the opening <head>.
- Squarespace: Settings > Developer Tools > Code Injection > Header.
- Wix: Settings > Marketing Integrations > Google Search Console > Connect.
- Webflow: Project Settings > Custom Code > Head Code, then publish.
The tag must be on the exact URL you entered. If you typed the non www version and your site redirects to www, verification can fail even though the tag is live.
Step 5: Fix the Verification Errors That Block New Sites
These are the failures we see most often during the first weeks of a launch, and several of them also block indexing, not just verification.
| Symptom | Likely cause | Fix |
|---|---|---|
| “Ownership verification failed” after adding TXT | DNS not propagated yet, or record added at the wrong provider | Wait up to 24 to 48 hours, confirm the record with a DNS lookup tool, and check which nameservers your domain really uses |
| TXT record duplicated or rejected | The host field was filled with the full domain when @ was expected, or quotes were pasted in | Use @ as host and paste the raw value without extra quotes or spaces |
| Meta tag not found | Tag added to the body, or cached page served to Googlebot | Move it inside <head>, purge CDN and plugin cache, then retry |
| Verification works but no data appears | Normal for a brand new site, or the wrong property variant is being checked | Allow 2 to 3 days for the first rows, and confirm you are looking at the version users land on |
| “Blocked by robots.txt” on most pages | A staging rule such as Disallow: / was pushed live | Edit robots.txt, remove the global disallow, then request indexing on key URLs |
| “Excluded by noindex tag” | WordPress setting “Discourage search engines from indexing this site” still enabled | Settings > Reading, uncheck the box, save, then re inspect a URL |
| Site disappears from Search Console later | Verification token removed during a redesign or DNS cleanup | Re add the record or tag and verify a second method as backup |
Pro move: once verified, add a second verification method under Settings > Ownership verification. If one breaks, the property stays alive.
Step 6: Submit Your Sitemap and Check robots.txt
Verification proves you own the site. It does not tell Google what to crawl. The sitemap does.
- Find your sitemap URL. WordPress with Yoast or Rank Math usually publishes
/sitemap_index.xml; Shopify, Wix and Squarespace publish/sitemap.xml. - Open it in a browser and confirm it loads and lists real URLs with the correct protocol and subdomain.
- In Search Console, open Sitemaps in the left menu.
- Enter the path after your domain, for example
sitemap_index.xml, then click Submit. - Refresh after a few hours. Status should read Success with a count of discovered URLs.
Also do this
- Visit
yourdomain.com/robots.txtand confirm it does not containDisallow: /. - Add the sitemap line to robots.txt:
Sitemap: https://yourdomain.com/sitemap_index.xml. - Use URL Inspection at the top of Search Console on your homepage and 3 to 5 key pages, then click Request indexing. Use it for important pages only, not for every URL.
A “Couldn’t fetch” status on a fresh sitemap is often temporary. Wait a day and resubmit before assuming something is broken.
Step 7: The First Four Reports Every New Site Owner Should Check
Search Console has a lot of menus. In the first month, four reports carry almost all the value.
1. Page indexing
Found under Indexing > Pages. It splits your URLs into indexed and not indexed, with a reason for each exclusion. Watch for:
- Discovered – currently not indexed: Google knows the URL but has not crawled it. Common on new sites with few links. Improve internal linking and get a few external mentions.
- Crawled – currently not indexed: Google looked and passed. Usually a thin or duplicate content signal.
- Excluded by noindex tag and Blocked by robots.txt: fix these immediately, they are self inflicted.
- Alternate page with proper canonical tag: normal in most cases.
2. URL Inspection
The search bar at the top of every screen. For any URL it shows whether it is on Google, which canonical Google chose, when it was last crawled, and how the rendered page looks to Googlebot. Use Test live URL to confirm a fix worked before requesting indexing.
3. Performance
Under Performance > Search results. Expect near zero for the first few weeks, which is normal. Once impressions appear, enable all four metrics (clicks, impressions, CTR, average position) and review the Queries and Pages tabs. Early impressions tell you which topics Google already associates with your site, which is gold for planning your next articles.
4. Experience and Core Web Vitals
Under Experience > Core Web Vitals. New sites often show “Not enough data” because the report relies on real user measurements. Check back once you have steady traffic, and in the meantime run PageSpeed Insights on your templates.
Bonus: Enhancements and Manual actions
Glance at Security & Manual actions once. It should say “No issues detected”. If structured data is present, the Enhancements section reports invalid items worth fixing.
Realistic Timeline After Setup
| Period | What you should see |
|---|---|
| Day 0 to 2 | Property verified, sitemap submitted, URL Inspection working |
| Day 2 to 7 | Sitemap status Success, first pages indexed, Performance shows first impressions |
| Week 2 to 4 | Page indexing report fills out, branded queries appear, exclusion reasons become meaningful |
| Month 2 to 3 | Enough query data to guide content decisions, Core Web Vitals may start reporting |
Quick Setup Checklist
- Domain property created and verified by DNS TXT
- Second verification method added as backup
- robots.txt checked, no global disallow
- WordPress search engine visibility box unchecked
- Sitemap submitted and showing Success
- Homepage and top pages inspected and indexed
- GA4 linked under Settings > Associations
- Team members added under Settings > Users and permissions
- Email notifications enabled so you hear about issues early
FAQ
How do I add a website in Google Search Console?
Sign in at search.google.com/search-console, open the property dropdown, click + Add property, choose Domain or URL prefix, enter your address and complete the verification step Google offers.
How do I connect my website to Google Search Console?
Connecting means proving ownership. For a Domain property you add a TXT record in DNS. For a URL prefix property you add an HTML meta tag to the head of your homepage, upload an HTML file, or reuse an existing GA4 or Tag Manager installation.
How do I get Google to find my new website?
Verify the site in Search Console, submit an XML sitemap, make sure robots.txt and meta robots tags allow crawling, use URL Inspection to request indexing on key pages, and earn a few links or mentions so Google has a reason to crawl more often.
How long does verification take?
HTML tag and file verification usually succeeds within seconds. DNS verification can be instant but may take up to 48 hours while the record propagates.
Do I need both a Domain and a URL prefix property?
Not strictly. A Domain property is enough for most sites. Adding a URL prefix property is useful when you want isolated data for one subdomain or folder, or when some tools only accept a URL prefix.
Does Search Console setup improve rankings?
Not by itself. It does not give a ranking boost. It gives you visibility into crawling, indexing and query data so you can fix the issues that are actually limiting your visibility.
Why does my Performance report show zero clicks?
Brand new sites have no rankings yet. Zero clicks with a few impressions after two or three weeks is normal. Zero impressions after a month usually points to an indexing problem, so start with the Page indexing report.
Can I set up Search Console without access to my website code?
Yes. Use DNS verification through your registrar, or use the built in integration offered by platforms such as Wix and Squarespace, which handles the tag for you. There is a practical rundown of it online.
Final Word
To set up Google Search Console for a new website, the order that avoids headaches is simple: Domain property, DNS verification, backup verification method, robots.txt and noindex check, sitemap submission, then the four core reports. Spend 20 minutes on it now and you will catch the indexing blockers that otherwise cost new sites their first two or three months of visibility.