--- title: "How to Connect Google Search Console to Your Site" slug: google-search-console-setup excerpt: "Step-by-step guide to setting up Google Search Console, choosing the right property type, and verifying site ownership without common pitfalls." author: RankWiz Team published_at: 2026-02-15 09:00:00 meta_title: "How to Set Up Google Search Console (2026)" meta_description: "Step-by-step guide to connecting Google Search Console to your site. Covers property types, verification methods, and common setup mistakes to avoid." category: gsc-analytics reading_time_minutes: 6 featured: false related_posts: - what-is-google-search-console - gsc-metrics-explained - google-search-console-guide --- ## Why Setup Matters Google Search Console is the starting point for any data-driven SEO workflow, but it can only help you if it is configured correctly. A misconfigured property means incomplete data, which leads to wrong conclusions. This guide walks you through setup from scratch, covering the decisions that trip up most site owners. New to GSC? Start with [What Is Google Search Console?](/blog/what-is-google-search-console) for a plain English overview of what it does and why it matters. For a broader guide to using GSC data for SEO, see [The Complete Guide to Google Search Console](/blog/google-search-console-guide). ## Step 1: Choose Your Property Type Google Search Console offers two property types, and the one you choose affects what data you see. ### Domain Property A Domain property covers **all subdomains, protocols, and paths** under a single domain. If you add `example.com` as a Domain property, it includes: - `https://example.com` - `http://example.com` - `https://www.example.com` - `https://blog.example.com` - `https://shop.example.com` **When to use it**: This is the recommended option for most sites. It gives you a unified view of all your search data without worrying about protocol or subdomain variations. **Verification requirement**: DNS verification only. You need access to your domain's DNS settings. ### URL-Prefix Property A URL-prefix property covers **only the exact prefix** you specify. If you add `https://www.example.com`, it does not include `https://example.com` (without www) or `http://www.example.com` (HTTP instead of HTTPS). **When to use it**: Choose this if you only manage a specific subdomain (e.g., `blog.example.com`) or cannot access DNS settings. You can also use it alongside a Domain property for more granular filtering. **Verification options**: HTML file upload, HTML meta tag, Google Analytics, Google Tag Manager, or DNS. ### Our Recommendation Set up a **Domain property** as your primary property. If you need to track a specific subdomain separately, add it as a URL-prefix property as well. Having both costs nothing and gives you maximum flexibility. ## Step 2: Verify Ownership Verification proves to Google that you own or manage the site. The available methods depend on which property type you chose. ### DNS Verification (Domain Properties) 1. Go to [Google Search Console](https://search.google.com/search-console) and click **Add Property**. 2. Select **Domain** and enter your domain (e.g., `example.com`). 3. Google provides a TXT record value (e.g., `google-site-verification=abc123...`). 4. Log in to your domain registrar (GoDaddy, Cloudflare, Namecheap, etc.) and add the TXT record to your DNS settings. 5. Return to GSC and click **Verify**. **Common pitfall**: DNS propagation can take anywhere from a few minutes to 48 hours. If verification fails immediately, wait 30 minutes and try again. Do not delete the record. ### HTML File Upload (URL-Prefix Properties) 1. Download the verification HTML file from GSC. 2. Upload it to the root directory of your site (e.g., `https://example.com/google1234567890.html`). 3. Confirm the file is accessible by visiting the URL in your browser. 4. Click **Verify** in GSC. **Common pitfall**: Some hosting setups or CMS platforms rewrite URLs or block access to files in the root directory. Test the URL in an incognito window before attempting verification. ### HTML Meta Tag 1. Copy the meta tag provided by GSC. 2. Add it to the `` section of your homepage. 3. Click **Verify**. **Common pitfall**: Caching plugins may serve a cached version of your homepage that does not include the new meta tag. Clear your cache before verifying. ### Google Analytics or Tag Manager If you already have Google Analytics or Google Tag Manager installed on your site, GSC can verify ownership through those existing connections. This is the fastest method if your analytics is already set up. ## Step 3: Submit Your Sitemap After verification, submit your XML sitemap to help Google discover your pages: 1. In GSC, go to **Sitemaps** in the left sidebar. 2. Enter your sitemap URL (typically `sitemap.xml` or `sitemap_index.xml`). 3. Click **Submit**. Google will process your sitemap and report back on how many URLs it discovered and how many were successfully indexed. Check back in a few days to review the results. **Tip**: If your site has multiple content types (posts, products, categories), consider using a sitemap index that references separate sitemaps for each type. This makes it easier to diagnose indexing issues by content type. ## Step 4: Configure Settings ### International Targeting If your site targets a specific country, you can set this in **Settings > International Targeting**. This is optional and mostly relevant for ccTLDs (country-code top-level domains) or sites using `hreflang` tags. ### Crawl Rate GSC allows you to reduce Google's crawl rate if your server is struggling under the load. In most cases, you should leave this at the default setting. Google's crawler is generally good at self-throttling. ### Users and Permissions You can add other users to your GSC property with different permission levels: - **Owner**: Full control, including adding and removing other users. - **Full**: Can view all data and take most actions, but cannot manage users. - **Restricted**: Can view most data but cannot take actions. Add your team members, SEO agency, or tools that need API access at the appropriate permission level. ## Common Setup Mistakes ### Verifying the Wrong Property The most frequent mistake is verifying `http://example.com` when your site actually runs on `https://example.com`. If you use a URL-prefix property, make sure the protocol matches exactly. Better yet, use a Domain property to avoid this issue entirely. ### Not Re-verifying After Migrations If you switch hosting providers, change your CMS, or migrate from HTTP to HTTPS, your verification may break. GSC periodically re-checks verification, and if it fails, you will lose access to your data. After any major infrastructure change, verify that your GSC verification is still valid. ### Ignoring the "www" vs "Non-www" Distinction `www.example.com` and `example.com` are technically different hosts. If you use a URL-prefix property, you need to verify both (or the one you actually use). Domain properties handle this automatically. ### Delaying Setup GSC does not backfill data. It only starts collecting data from the moment you verify your property. Every day without GSC is a day of search data you can never recover. Set it up as early as possible, even if you are not ready to act on the data yet. ## Connecting GSC to RankWiz Once your GSC property is verified and collecting data, you can connect it to RankWiz for automated analysis: 1. In RankWiz, navigate to your site's settings. 2. Click **Connect Google Search Console**. 3. Authorize RankWiz to access your GSC data via OAuth. 4. RankWiz begins syncing your historical data immediately. RankWiz preserves your GSC data beyond the [16-month retention limit](/blog/gsc-data-retention-workarounds), runs [before/after traffic analysis](/blog/seo-traffic-analysis-before-after) automatically, and generates actionable recommendations based on your actual search performance. --- ## Start Analyzing Your Search Data Once GSC is connected, RankWiz automatically syncs your data and starts generating insights. No spreadsheets, no manual exports -- just actionable SEO recommendations. [Explore Features](/features) | [View Pricing](/pricing)