How to Set Up Google Search Console for a New Website
To set up Google Search Console for a new website, sign in at search.google.com/search-console with a Google account, add your site as a Domain property, verify ownership through your DNS provider, then submit your XML sitemap. The whole process takes about 15 minutes, and once verified, Google starts collecting search data you can use to track rankings, find crawl issues, and see which queries bring traffic. Below is the exact walkthrough plus what to do in your first week.
Why Google Search Console Is the First Thing to Set Up on a New Site
Search Console (GSC) is Google's free direct line to your website. Google Analytics tells you what people do once they land. Search Console tells you how they found you in the first place: the exact queries, your average position, your click-through rate, and which pages Google indexed. No SEO tool can replace this data because it comes straight from Google.
For a new website, GSC does three critical jobs immediately. It lets you tell Google your site exists (via sitemap submission), it surfaces indexing problems before they cost you traffic, and it gives you a baseline of query and ranking data you will lean on for months. Skip it and you are flying blind.
Domain Property vs URL Prefix: Which One to Choose
When you add a property, Google gives you two options. Pick the right one before you verify or you will end up managing multiple duplicate properties.
| Property type | What it covers | Best for |
|---|---|---|
| Domain | Every subdomain (www, blog, shop) and both http and https | Almost everyone. Choose this by default. |
| URL prefix | Only the exact prefix you enter (e.g. https://www.site.com) | Tracking a single subdomain or a specific protocol separately |
Use the Domain property. It captures all versions of your site in one place, so you never miss data because someone linked to the http or non-www version. The only trade-off is that Domain properties require DNS verification, which is slightly more involved than the file or tag options. It is worth it.
Step-by-Step: Set Up and Verify Google Search Console
- Sign in. Go to search.google.com/search-console and log in with the Google account you want tied to the site. Use a business account you control long-term, not a personal Gmail you might lose access to.
- Add your property. Click the property dropdown, choose "Add property," and select the Domain option. Enter your bare domain without https or www (for example, yoursite.com).
- Copy the TXT verification record. Google generates a TXT record that looks like google-site-verification=xxxxxx. Copy it.
- Add the record to your DNS. Log in to your domain registrar or DNS host (GoDaddy, Namecheap, Cloudflare, etc.). Find the DNS settings, add a new TXT record, paste the value, and save. Leave the host/name field as @ or blank unless your provider requires the root domain.
- Verify. Return to Search Console and click Verify. DNS changes can take a few minutes to a few hours to propagate. If it fails on the first try, wait 30 minutes and click Verify again.
If you use a website builder (Wix, Squarespace, Shopify), most have a built-in Search Console integration or offer the HTML tag method under a URL prefix property. That works, but if you can access DNS, the Domain property is still the cleaner setup.
Verification Methods Compared
- DNS TXT record: Required for Domain properties. Most reliable and covers everything.
- HTML file upload: Upload a file to your root directory. Works only for URL prefix properties.
- HTML tag: Paste a meta tag into your homepage <head>. Easy on WordPress with an SEO plugin.
- Google Analytics or Tag Manager: Verify automatically if you already have GA4 or GTM installed with edit access.
Submit Your XML Sitemap So Google Can Find Every Page
Once verified, the single most important next step is submitting your sitemap. A sitemap is a file that lists every URL you want indexed, and handing it to Google speeds up discovery of a brand-new site that has few or no backlinks yet.
- Find your sitemap URL. On WordPress it is usually yoursite.com/sitemap.xml or yoursite.com/sitemap_index.xml if you use Yoast or Rank Math.
- In Search Console, open Sitemaps in the left menu.
- Enter the path (just sitemap.xml, not the full URL) and click Submit.
- Check back in a day or two. The status should read "Success" with a count of discovered URLs.
If you do not have a sitemap yet, follow our guide on how to create an XML sitemap and submit it to Google before moving on. It walks through generating one for any platform.
Request Indexing for Your Most Important Pages
Sitemaps tell Google what exists, but you can nudge specific pages to the front of the line. Use the URL Inspection tool at the top of Search Console. Paste in your homepage URL, wait for the check, then click "Request Indexing." Do this for your homepage, main service or product pages, and any cornerstone content you have published.
Do not spam this. Requesting indexing for the same URL over and over does nothing, and there is a daily quota. Prioritize the 5 to 10 pages that matter most, then let the sitemap handle the rest.
Connect Google Analytics 4 for the Full Picture
Search Console shows pre-click data (impressions, position, clicks). GA4 shows post-click behavior (sessions, conversions, engagement). Link them so you can see both in one place. In GSC, go to Settings > Associations and connect your GA4 property. This unlocks the Search Console reports inside GA4 and makes it far easier to measure SEO results in Google Analytics 4 down the line.
Your First-Week Checklist After Setup
Verification is the start, not the finish. Work through this list in your first seven days:
- Confirm the sitemap says "Success" and the URL count roughly matches your page count.
- Check the Pages (Indexing) report. It splits URLs into indexed and not indexed. A brand-new site will have few indexed pages at first; that is normal.
- Review the not-indexed reasons. "Discovered - currently not indexed" and "Crawled - not indexed" are common for new sites and usually resolve with time and internal links. "Blocked by robots.txt" or "noindex" tags need immediate fixing.
- Set your preferred domain behavior. Make sure non-www redirects to www or vice versa (301 redirect), so you are not splitting signals.
- Add all owners and users under Settings > Users and permissions. Give your developer or agency the right access level.
- Enable email notifications. GSC will alert you to manual actions, indexing spikes, and Core Web Vitals problems.
How to Read the Performance Report (Your Ranking Data)
The Performance report is where GSC earns its keep. Open it and you will see four metrics: total clicks, total impressions, average CTR, and average position. Filter by Queries to see the exact search terms bringing impressions, and by Pages to see which URLs perform.
For a new site, impressions will show up before clicks. That is Google testing your pages in the results. Watch which queries you appear for, then optimize the matching page to climb from page two to page one. Pair this with a rank tracker so you get daily position data instead of GSC's smoothed averages. You can start with our rundown of how to track keyword rankings for free, or use RankLoco to monitor positions, run site audits, and find keyword opportunities in one dashboard.
Common Queries to Act On
- Queries where you rank positions 5 to 15: closest to a quick win. Improve the title tag and content depth.
- Queries with high impressions but low CTR: rewrite the title and meta description. Our guide on writing title tags and meta descriptions that get clicks covers this.
- Queries you did not target but appear for: content gaps you can build dedicated pages around.
Fix Errors Before They Compound
New sites accumulate small technical problems fast: broken redirects, orphaned pages, blocked resources. Check the Indexing report weekly for the first month. When you see errors pile up, our walkthrough on how to fix crawl errors in Google Search Console shows how to diagnose and clear each type. Catching these early keeps Google crawling your site efficiently while it is still building trust in your domain.
Once your setup is solid, GSC becomes the reporting backbone for the rest of your SEO work. Browse more tactical guides in the RankLoco blog to turn this data into rankings.
Frequently Asked Questions
How long does it take for a new site to show data in Search Console?
Verification is instant, but performance data (clicks, impressions, position) takes 2 to 3 days to start appearing and builds up over the following weeks. Indexing of your pages can take anywhere from a few days to a few weeks for a brand-new domain with no backlinks. Submitting a sitemap speeds this up.
Do I need Google Search Console if I already have Google Analytics?
Yes. They measure different things. Analytics tracks what visitors do on your site after arriving. Search Console shows how people found you in Google: the queries, your rankings, impressions, and any indexing or manual action problems. You need both, and linking them gives you the complete search-to-conversion picture.
Why is my new website not indexed in Google Search Console?
New domains often show "Discovered - currently not indexed" simply because Google has not crawled them yet, which resolves with time, internal links, and a submitted sitemap. If pages stay unindexed, check for a noindex tag, a robots.txt block, thin content, or lack of internal links pointing to the page.
Can I use Search Console for multiple websites under one account?
Yes. One Google account can manage unlimited properties. Just click "Add property" for each new site and verify each one separately. You can also add multiple users to a single property with different permission levels, which is handy for teams and agencies.
Is Domain or URL prefix better for a new website?
Choose Domain unless you have a specific reason not to. A Domain property captures every subdomain and both http and https in one place, so you never lose data to a version mismatch. URL prefix only tracks the exact address you enter, which fragments your data across multiple properties.
How often should I check Google Search Console?
For a new site, check weekly during the first month to catch indexing and crawl issues early. After things stabilize, a thorough review every one to two weeks is enough, plus acting on any email alerts Google sends about manual actions, security issues, or Core Web Vitals problems.
