GSC (Google Search Console) Setup Guide

Third-party tools are great for competitive analysis, but they are essentially scraping Google and guessing your traffic. GSC is different. It is Google explicitly telling you: “Here is what we crawled, here is why we didn’t index this, and here is an estimate of how many clicks you get.”

Setting up Gooagle Search Console is easy. Setting it up correctly, so you capture every subdomain and protocol, requires a specific approach.

Step 1. Verification (Domain vs. URL Prefix)

When you click “Add Property,” Google gives you two choices. This is an IQ test.

Option A: Domain Property – This verifies yoursite.com and everything attached to it. All subdomains, all protocols, all paths. I would recommend – always choose Domain Property.
Option B: URL Prefix – This verifies only the exact URL string you enter (e.g., https://www.yoursite.com). It misses http://, it misses non-www, and it misses m.yoursite.com. You end up with fragmented data.

How to Verify via DNS (The TXT Record)

To get a Domain Property, you can’t just upload an HTML file. You need to prove you own the infrastructure.

Select Domain Property and enter your root domain (no https, no www).
Google will generate a TXT Record string (e.g., google-site-verification=...).
Log into your DNS Provider (GoDaddy, Namecheap, Cloudflare, AWS Route53, or via WordPress domain settings).
Add a new TXT record.
- Host/Name: @ (or leave blank).
- Value: Paste the Google string.
- TTL: Set to lowest possible (usually 1 min or Auto).
Click Verify in GSC.

Note: DNS changes can take a few minutes (or hours) to propagate. If it fails immediately, grab a coffee and try again in 15 minutes.

Step 2. The Sitemap Injection

Once you are verified, don’t wait for Google to find your content. Hand them the map.

Navigate to Sitemaps in the left sidebar.
Enter the URL of your main index.
- Usually: /sitemap_index.xml or /sitemap.xml.
The Status Check:
- Success – Good. Google can read it.
- Could Not Fetch – Usually a bug or a robots.txt block.
- Has Errors – Click to debug. You might have formatting issues.

Nerd Tip: Don’t just submit the index. If you have a massive site, you can submit individual sub-sitemaps (e.g., post-sitemap.xml) to monitor indexation rates for specific content types separately.

Step 3. Associations

GSC data is powerful, but it’s siloed. You need to pipe that data into your analytics stack via the GSC Associations tab.

Go to Settings > Associations.
Google Analytics (GA4) – Link your GSC property to your GA4 stream. (Why, you might ask. This unlocks the “Organic Search Query” report inside GA4, allowing you to see GSC data alongside conversion revenue.)
Search Console Insights – This creates a simplified “content performance” dashboard that merges GA4 “Time on Page” with GSC “Clicks.”

Step 4: User Management

Do not share your Google login. If your developer or agency needs access, delegate it.

Go to Settings > Users and permissions.
Click Add User.
Permission Levels:
- Owner – Can add users and link other Google tools. (Keep this for yourself).
- Full – Can see all data and perform actions (like submitting sitemaps).
- Restricted – Can only view data.

“Data Horizon” Warning

Here is a hard technical constraint – GSC only stores 16 months of data.

On month 17, month 1 is deleted forever.

If you want to perform year-over-year analysis two years from now, or if you want to train an internal AI model on your historical seasonality, you need to start exporting data now.

The Manual Way – Click “Export” every month.
The Automata Ways:
- Use the Bulk Data Export (Settings > Bulk data export) to pipe raw data directly into BigQuery (Google’s data warehouse). It costs pennies, and it saves everything forever.
- Fill your own data storage using the Search Console API.

Final Status Check

You are verified via DNS. Your sitemap is submitted. Your data pipeline to GA4 is open. You have officially established the baseline.

Now, wait 48 hours for the telemetry to roll in. Then you analyze.