Guide · #698

How to Set Up Multiple Properties in Google Search Console

Master multiple GSC properties: subdomains, subfolders, apex domains. Step-by-step setup for founders managing complex site structures.

Filed

May 4, 2026

Read

23 min

Author

The Seoable Team

Why Multiple Properties Matter

You shipped. Your product works. But Google doesn't know about all the versions of your site yet.

Most founders treat Google Search Console as a single property. One domain, one setup, done. That works if you're running a simple site. But the moment you add a subdomain (api.yoursite.com), launch a blog on a subfolder (yoursite.com/blog), migrate to HTTPS, or switch from www to non-www, you're creating separate properties in Google's eyes.

Here's the brutal truth: if you don't set these up correctly, you're splitting your organic visibility across multiple properties. Your rankings fragment. Your data scatters. You lose the ability to see the full picture of what's actually driving traffic.

This guide walks you through setting up multiple properties in Google Search Console so you can track all versions of your site, consolidate data, and stop leaving SEO wins on the table.

Prerequisites: What You Need Before Starting

Before you set up multiple properties, make sure you have these in place:

Access and Ownership

Admin access to your domain's DNS settings (or access to whoever controls them)
Admin access to your hosting provider or CDN
A Google account (use the same one across all properties for easier management)
Ownership verification capability via one of these methods: DNS record, HTML file upload, meta tag, Google Analytics, or Google Tag Manager

Technical Setup

All domains and subdomains you want to track must be live and accessible
SSL certificates installed (HTTPS is now standard; HTTP-only sites should migrate first)
A sitemap.xml file for each property (or one master sitemap if using a domain property)
Understanding of your site structure: which content lives where, whether you're using subdomains or subfolders, and which versions are canonical

Documentation

A list of all site versions you want to track (write these down now—you'll need them)
Your current Google Search Console setup (if you already have one)
Any existing 301 redirects or canonical tags in place

If you haven't set up Google Search Console at all yet, start with How to Set Up Google Search Console in 10 Minutes — SEOABLE first. That guide covers the basics. This article assumes you understand the fundamentals and are now expanding to manage multiple properties.

Understanding Property Types: Domain vs. URL-Prefix

Google Search Console offers two main ways to set up properties, and choosing the right one changes everything about how you track and manage your site.

Domain Properties

A domain property covers your entire domain and all its subdomains automatically. If you add yoursite.com as a domain property, Google automatically includes:

yoursite.com
www.yoursite.com
blog.yoursite.com
api.yoursite.com
Any other subdomain under yoursite.com

Domain properties require DNS verification only. You add a TXT record to your domain's DNS, and you're done. Google handles the rest.

Why use domain properties? You get a unified view of all your subdomains in one place. You don't have to manage ten separate properties. Your data is consolidated. This is the approach most technical founders prefer because it's simpler and scales as you add new subdomains.

The catch: domain properties only work if you can verify ownership via DNS. If you're on shared hosting or can't access DNS, you'll need URL-prefix properties instead.

URL-Prefix Properties

URL-prefix properties are specific. You add exactly what you type:

Each one is a separate property. Each requires separate verification. If you add https://yoursite.com/, it does not automatically include https://www.yoursite.com/. They're treated as completely different sites.

Why use URL-prefix properties? You need them when you can't verify via DNS. You're on shared hosting. You're managing a subdomain on a third-party platform. You want granular control over which specific URLs you track.

The downside: managing ten separate properties gets messy fast. Your data fragments across multiple dashboards. You have to manually consolidate reports.

The recommendation for founders: If you control your domain's DNS, use a domain property. One setup, automatic subdomain coverage, unified reporting. If you can't access DNS, use URL-prefix properties for the specific versions you need to track.

Step 1: Audit Your Site Structure and List All Versions

Before you add anything to Google Search Console, map out exactly what you're running.

Open a spreadsheet or text file and document every version of your site:

Protocol versions

http://yoursite.com (if still live)
https://yoursite.com (the secure version)

WWW versions

https://www.yoursite.com
https://yoursite.com (non-www)

Subdomains

Subfolders

https://yoursite.com/blog/
https://yoursite.com/resources/
Any major content structure living in subfolders

Regional or language versions

Now, for each version, ask: Is this live? Does it have unique content? Do I want to track it separately, or should it redirect to a canonical version?

Here's the key insight: not every version needs its own property. If you have https://yoursite.com and https://www.yoursite.com pointing to the same content, you don't need two properties. One domain property covers both. If you have a staging environment (staging.yoursite.com), you probably don't want to add that to Search Console at all.

The goal is to identify the canonical versions you actually want to track in Google's eyes. For most founders, that's:

Your primary domain (with or without www)
Any subdomains with unique, indexable content
Any subfolders with significant content (like a blog)

Once you have this list, you're ready to start adding properties.

Step 2: Add Your First Property (Domain Property Method)

This is the fastest approach if you control your domain's DNS.

Navigate to Google Search Console

Go to Google Search Console. Sign in with your Google account. You'll see the property selector in the top left—it looks like a dropdown menu.

Click "Add Property"

You'll see two options:

Domain — Enter just your domain name (yoursite.com)
URL-prefix — Enter the full URL (https://www.yoursite.com/)

Select Domain. Type your domain name without www or https. Just: yoursite.com

Click Continue.

Verify via DNS

Google will show you a TXT record to add to your domain's DNS. It looks like:

google-site-verification=ABC123XYZ...

Copy this record. Log in to your domain registrar (GoDaddy, Namecheap, Route 53, Cloudflare, etc.) and add it as a TXT record.

The exact steps vary by registrar, but the process is:

Go to DNS settings
Add a new TXT record
Leave the name/host blank (or enter @ if required)
Paste the verification string in the value field
Save

DNS changes take 5-60 minutes to propagate. Come back to Google Search Console and click Verify. Google will check for the TXT record. Once found, your domain property is live.

Submit Your Sitemap

Once verified, Google Search Console will prompt you to submit a sitemap. If you have one (and you should), paste the URL here. Common paths:

yoursite.com/sitemap.xml
yoursite.com/sitemap_index.xml
yoursite.com/sitemaps/sitemap.xml

If you don't have a sitemap yet, Submitting Your First Sitemap in Google Search Console — SEOABLE walks you through generating one in minutes.

Once you submit your sitemap, Google will start crawling and indexing your site. You won't see data immediately—indexing takes 48 hours to a few weeks depending on your site's authority and crawl budget.

Step 3: Add Additional Properties (URL-Prefix Method for Subdomains and Subfolders)

Now that your domain property is live, you might also want to add specific subdomains or subfolders as separate properties. This is useful if:

You want to monitor a subdomain's performance independently (blog.yoursite.com gets its own tracking)
You're managing a subdomain on a third-party platform and can't verify the parent domain
You want granular control over crawl settings and indexing for specific sections

Add a Subdomain Property

Go back to the property selector. Click Add Property. This time, select URL-prefix.

Enter the full URL:

https://blog.yoursite.com/

Include the protocol (https://), the subdomain, and the trailing slash. Click Continue.

Google will show you verification options:

HTML file — Download a file and upload it to your server
HTML tag — Add a meta tag to your homepage
Google Analytics — Verify via existing GA4 property
Google Tag Manager — Verify via GTM container
DNS record — Add a TXT record (if you control DNS for the subdomain)

Choose the method that works for your setup. For most founders:

If you control DNS for the subdomain, use DNS (fastest)
If the subdomain is hosted elsewhere, use HTML file or HTML tag
If you already have GA4 set up for this subdomain, use Google Analytics (no verification needed—it's instant)

Complete the verification. Once done, submit the sitemap for that subdomain and you're set.

Add a Subfolder Property

If you have a blog living in a subfolder (yoursite.com/blog/), you can add that as a separate property too.

Go to property selector. Click Add Property. Select URL-prefix.

Enter:

https://yoursite.com/blog/

Verify using one of the methods above. Submit the sitemap for the blog folder if you have a separate one.

Note: If your blog lives in a subfolder and uses the same domain, you already have visibility in your domain property. Adding it as a separate URL-prefix property gives you granular reporting, but the data will overlap with your domain property's data. This is fine—it's useful for isolating blog performance.

Step 4: Verify Multiple Properties Correctly

Verification is where most founders stumble. Let's break down each method so you don't waste time.

DNS Verification (Fastest for Domain Properties)

DNS verification is the gold standard. You add one TXT record to your domain, and Google automatically covers yoursite.com, www.yoursite.com, and all subdomains.

Steps:

In Google Search Console, select DNS record as your verification method
Copy the TXT record Google provides
Log in to your domain registrar's DNS settings
Add a new TXT record with the name @ (or leave blank) and paste the value
Save and wait 5-60 minutes for propagation
Return to Google Search Console and click Verify

If verification fails, check:

Did you paste the entire string, including the verification code?
Did you add it as a TXT record, not an A record or CNAME?
Did you wait long enough for DNS to propagate? Use DNS Checker to confirm the record is live.

HTML File Verification

Use this if you can't access DNS but can upload files to your server.

Google gives you a file to download (usually google[verification-code].html)
Upload it to your root directory (yoursite.com/google[code].html)
Return to Google Search Console and click Verify
Google checks if the file is accessible

Make sure:

The file is in your root directory, not in a subfolder
It's accessible via HTTP (no authentication required)
You don't delete it after verification (Google re-checks periodically)

HTML Meta Tag Verification

Use this if you can edit your homepage HTML.

Google gives you a meta tag: <meta name="google-site-verification" content="ABC123XYZ..." />
Add it to the <head> section of your homepage
Return to Google Search Console and click Verify

Make sure:

The meta tag is in the <head>, not the <body>
It's on your homepage (index.html or equivalent)
It stays on the page (don't remove it after verification)

Google Analytics Verification

If you already have GA4 set up, this is instant.

In Google Search Console, select Google Analytics as your verification method
Choose the GA4 property that matches your website
Click Verify

Google checks if you have admin access to that GA4 property. If you do, verification is instant. No additional setup needed.

This is the fastest method if you've already set up GA4. If you haven't, Setting Up Google Analytics 4 for SEO Tracking from Day One — SEOABLE shows you how to do it in minutes.

DNS Verification for Subdomains

If you're adding a subdomain as a separate property and want to verify via DNS, the process is similar, but you add the record to the subdomain's DNS, not the parent domain.

For example, if you're verifying blog.yoursite.com:

Get the TXT record from Google
Log in to your DNS provider
Add the TXT record to the blog subdomain's DNS (name: @, or leave blank)
Wait for propagation
Verify in Google Search Console

If your subdomain doesn't have separate DNS control (it's just a CNAME pointing elsewhere), use HTML file or meta tag verification instead.

Step 5: Handle WWW vs. Non-WWW Canonicalization

Here's a common scenario: you have both www.yoursite.com and yoursite.com live. They serve the same content. Google sees them as two different sites.

You need to tell Google which one is canonical. Otherwise, you're splitting your authority and rankings across two properties.

Option 1: Use a Domain Property (Simplest)

Add yoursite.com as a domain property via DNS. Google automatically treats www and non-www as the same property. Done.

Option 2: Set Canonical via 301 Redirect

If you're using URL-prefix properties, redirect one version to the other.

Decide which version you want to keep (usually non-www is simpler). Then redirect the other version:

# In your .htaccess or server config:
RewriteCond %{HTTP_HOST} ^www\.yoursite\.com$ [NC]
RewriteRule ^(.*)$ https://yoursite.com/$1 [R=301,L]

This tells Google: "All www traffic goes to non-www. Consider them the same site."

For detailed steps, WWW vs. Non-WWW: Choosing and Enforcing Your Canonical Domain — SEOABLE walks you through every method.

Option 3: Set Preferred Domain in Google Search Console

If you're using URL-prefix properties and can't redirect, you can tell Google which version is preferred:

In Google Search Console, go to Settings
Select Preferred domain
Choose www or non-www

Google will try to consolidate data toward your preferred version. This isn't as strong as a 301 redirect, but it helps.

Step 6: Consolidate Data with Property Sets

Once you have multiple properties set up, you might want to see them all in one report. That's where property sets come in.

Property sets let you tie your sites together with property sets in Search Console to aggregate data from multiple properties into one unified view.

Create a Property Set

In Google Search Console, go to Property sets (in the left menu)
Click Create property set
Name it (e.g., "All Versions of MyProduct")
Add properties to the set by clicking Add property
Select which properties to include (yoursite.com domain property, blog.yoursite.com, api.yoursite.com, etc.)
Save

Now you'll have a unified dashboard showing impressions, clicks, and rankings across all your properties. This is incredibly useful for founders who want one view of their entire organic presence.

What Property Sets Show

Combined impressions and clicks across all properties
Top queries across your entire site structure
Coverage issues across all properties
Mobile usability issues
Security issues

What they don't show:

Individual property details (you still need to click into each property for granular data)
Subdomain-specific rankings (you see aggregate data only)

Property sets are useful for high-level monitoring, but you'll still need to dig into individual properties for detailed analysis. Think of them as your executive dashboard.

Step 7: Submit Sitemaps for Each Property

Every property needs its own sitemap submission. Google won't automatically find it—you have to tell Search Console where it is.

Submit a Sitemap to Your Domain Property

In Google Search Console, select your domain property
Go to Sitemaps (in the left menu)
Click Add/test sitemap
Enter the sitemap URL (usually yoursite.com/sitemap.xml)
Click Submit

Google will crawl the sitemap and start indexing URLs from it.

Submit Sitemaps for Subdomains and Subfolders

For each URL-prefix property, submit its sitemap the same way:

Select the property (blog.yoursite.com)
Go to Sitemaps
Submit blog.yoursite.com/sitemap.xml (or wherever your blog sitemap lives)

If you have multiple sitemaps (one for blog, one for docs, one for main site), you can submit a sitemap index instead:

https://yoursite.com/sitemap_index.xml

The index file lists all your other sitemaps, so Google finds everything in one submission. For detailed instructions, Submitting Sitemaps to Google, Bing, and Yandex in 5 Minutes — SEOABLE shows you how to generate and submit them.

Step 8: Monitor Coverage and Indexing

Once your properties are set up and sitemaps submitted, the next step is monitoring what Google actually indexes.

Check Coverage Reports

Each property has a Coverage report showing:

Indexed — Pages Google successfully indexed
Excluded — Pages you told Google not to index (via robots.txt or noindex tags)
Error — Pages Google tried to crawl but couldn't access
Valid with warnings — Pages indexed but with issues (like missing meta descriptions)

To view coverage:

Select a property
Go to Coverage (in the left menu)
Review the status breakdown

If you see errors, click on them to see which URLs are affected. Common errors:

404 errors — Pages that no longer exist. Either restore them or remove them from your sitemap.
Server errors — Your server returned a 5xx error. Fix your server or contact your hosting provider.
Redirect errors — Broken redirect chains. Check your 301 redirects.
Crawl anomalies — Google couldn't reach your site. Check if your server is up and robots.txt isn't blocking Google.

For a detailed breakdown, Coverage Issues in Google Search Console: A Plain-English Guide — SEOABLE shows you how to diagnose and fix every issue type.

Use URL Inspection to Check Individual Pages

Want to know if a specific page is indexed? Use the URL Inspection tool.

In Google Search Console, click the search bar at the top
Paste the full URL (https://yoursite.com/specific-page/)
Press Enter

Google shows you:

Indexed — Yes or no
Last crawl date — When Google last visited this page
Crawl stats — How long it took to crawl, how much data was fetched
AMP status — If applicable
Mobile usability — Any mobile issues

If a page isn't indexed, you can request indexing directly from this tool. Click Request indexing and Google will prioritize it. How to Request Indexing in Google Search Console (And When to Do It) — SEOABLE explains when this is actually useful and when you should skip it.

For quick checks without Google Search Console, How to Check If Google Has Indexed Your Page in 30 Seconds — SEOABLE shows you three instant methods.

Step 9: Connect Google Analytics for Full Visibility

Google Search Console tells you what Google sees. Google Analytics tells you what users do. Together, they're powerful.

Link GA4 to Google Search Console

In Google Search Console, go to Settings (bottom of left menu)
Click Google Analytics property
Select your GA4 property from the dropdown
Save

Once linked, you'll see a new report in Google Search Console: Performance. This shows search queries, impressions, clicks, and CTR—plus you can see which queries drive the most traffic to your site.

For the reverse direction (seeing GSC data in GA4), follow Linking GA4 with Google Search Console: The 2-Minute Setup — SEOABLE. Once connected, you'll see search performance dimensions directly in GA4.

Build a Unified Dashboard in Looker Studio

If you want one dashboard showing data from all your properties (GSC + GA4), use Looker Studio (Google's free data visualization tool).

Go to Looker Studio
Create a new report
Connect your Google Search Console property as a data source
Add your GA4 property as another data source
Build cards showing impressions, clicks, conversions, etc.

You now have one view of your entire organic pipeline: what Google shows, what users click, and what they do after clicking.

Connecting Google Search Console to Looker Studio for Founders — SEOABLE walks you through building this in under 30 minutes.

Step 10: Manage and Maintain Your Properties

Setting up multiple properties is one thing. Maintaining them is another.

Review Properties Monthly

Set a calendar reminder to check each property's performance:

Are all properties still indexing pages?
Are there new coverage errors?
Is CTR dropping on any property?
Are there crawl anomalies or server errors?

This takes 15 minutes per month and catches issues before they hurt your rankings.

Update Sitemaps When You Add Content

Every time you add a new page (blog post, feature docs, etc.), make sure it's in your sitemap. If you're using a dynamic sitemap (generated automatically by your CMS or framework), this happens automatically. If you're manually managing sitemaps, update them when you ship new content.

Monitor Indexing Requests

Google Search Console has a daily quota for indexing requests. You can request up to 50 URLs per day per property. How to Request Indexing in Google Search Console (And When to Do It) — SEOABLE explains when to use this and when to just let Google discover content naturally.

Handle Domain Migrations Carefully

If you ever migrate to a new domain (new-domain.com), you need to:

Set up a new property in Google Search Console for the new domain
Set up 301 redirects from old domain to new domain
Update your sitemap
Use the URL Inspection tool to verify new URLs are being indexed
Monitor the old property for a few months to ensure all traffic is flowing to the new domain

Setting Up 301 Redirects for a Domain Migration — SEOABLE gives you the complete checklist.

Archive Properties You No Longer Need

If you deprecate a subdomain or shut down a section of your site, you can remove the property from Google Search Console. This keeps your dashboard clean and prevents confusion.

To remove a property:

Select the property
Go to Settings
Click Remove property

This doesn't delete your site from Google—it just removes it from your Search Console dashboard.

Pro Tips: Advanced Setup for Founders

Tip 1: Use Domain Properties Whenever Possible

Domain properties are simpler, more scalable, and give you better data consolidation. If you control your domain's DNS, always choose domain properties over URL-prefix properties. You'll save yourself hours of maintenance.

Tip 2: Set Up HTTPS Before Adding Properties

If you're running HTTP and haven't migrated to HTTPS yet, do that first. Then add your property. Adding HTTP properties and later migrating to HTTPS creates duplicate properties and complicates your reporting.

Tip 3: Consolidate Subdomains Into One Domain Property

If you have multiple subdomains (blog.yoursite.com, docs.yoursite.com, api.yoursite.com), don't add them as separate properties. Add yoursite.com as a domain property via DNS, and Google automatically covers all subdomains. One property, unified reporting.

The exception: if a subdomain is on a completely separate domain (blog.medium.com instead of blog.yoursite.com), then yes, add it as a separate property.

Tip 4: Use Property Sets for Reporting, Not for Crawl Settings

Property sets aggregate data, but they don't let you change crawl settings or manage coverage issues. You still need to manage each property individually for technical SEO work. Use property sets for executive reporting only.

Tip 5: Request Indexing Sparingly

Google's indexing request feature is useful for new pages that aren't being discovered naturally. But it has a 50-URL-per-day limit per property. Don't waste your quota on old pages. Use it for new content only.

Tip 6: Monitor Performance Reports to Find Opportunities

Once your properties are set up and indexed, spend time in the Performance report. Look for:

Queries with high impressions but low CTR (improve your title and meta description)
Queries on page 2-3 (optimize those pages to rank higher)
New queries appearing (new content opportunities)

Reading the Google Search Console Performance Report Like a Founder — SEOABLE shows you how to spot these opportunities in 10 minutes.

Common Mistakes to Avoid

Mistake 1: Not Verifying All Versions

Adding a property to Google Search Console doesn't automatically verify it. You have to complete verification. If you skip this step, Google won't crawl or index your site. Always verify before moving on.

Mistake 2: Forgetting to Submit Sitemaps

Google doesn't automatically discover your sitemap. You have to tell it where to find it. If you add a property but don't submit a sitemap, indexing will be slow.

Mistake 3: Creating Duplicate Properties for WWW and Non-WWW

If you add both www.yoursite.com and yoursite.com as separate URL-prefix properties without redirecting one to the other, you're splitting your authority. Use a domain property or set up a 301 redirect to avoid this.

Mistake 4: Not Checking Coverage Reports

Many founders set up properties and then never look at them again. Coverage reports show you what's actually being indexed. If you have 100 URLs in your sitemap but only 50 are indexed, something's wrong. Check coverage monthly.

Mistake 5: Mixing HTTP and HTTPS

HTTP and HTTPS are treated as different properties. If you have both live, pick one and redirect the other. Don't add both to Google Search Console—you'll fragment your data.

Summary: Your Setup Checklist

Here's the complete checklist for setting up multiple properties in Google Search Console:

Before You Start

Document all versions of your site (domain, subdomains, subfolders, protocols)
Ensure all versions are live and accessible
Verify you have DNS access (or choose an alternative verification method)
Decide: domain property or URL-prefix property?

Add and Verify Properties

Add your primary domain as a domain property (if you control DNS) or URL-prefix property
Complete verification (DNS, HTML file, meta tag, or Analytics)
Add any subdomains as separate URL-prefix properties if needed
Add any major subfolders as separate URL-prefix properties if needed
Verify each property

Submit Sitemaps

Submit sitemap for domain property
Submit sitemaps for each subdomain/subfolder property
Verify sitemaps are being crawled (check Sitemaps report)

Consolidate Data

Set up 301 redirects for WWW vs. non-WWW (or use domain property)
Create a property set to aggregate data from all properties
Link GA4 to Google Search Console
(Optional) Build a Looker Studio dashboard

Monitor

Check Coverage reports for errors
Use URL Inspection to verify key pages are indexed
Review Performance reports for ranking opportunities
Set a monthly reminder to check all properties

What's Next: Beyond Setup

Once your properties are set up and indexed, the real SEO work begins. Your Google Search Console is now feeding you data. What you do with that data matters.

Your next steps:

Audit your existing rankings using the Reading the Google Search Console Performance Report Like a Founder — SEOABLE guide. Find quick wins where you can improve CTR or push pages from position 2-3 to position 1.
Fix coverage issues using Coverage Issues in Google Search Console: A Plain-English Guide — SEOABLE. Every error you fix is potential traffic you recover.
Use URL Inspection to diagnose why specific pages aren't ranking using URL Inspection Tool: The Search Console Feature Founders Underuse — SEOABLE. This tool catches issues that other founders miss.
Build your free SEO stack with The Free SEO Tool Stack Every Founder Should Set Up Today — SEOABLE. GSC is just one piece. Add GA4, Bing Webmaster Tools, Lighthouse, and free keyword tools for complete visibility.

You've now got the foundation. Google knows about all versions of your site. Your data is consolidated. You can see what's working and what isn't.

The founders who win aren't the ones with the most properties. They're the ones who actually use the data to ship better content and fix technical issues. Your Google Search Console setup is just the start.

Ship fast. Track everything. Fix what breaks. That's how you build organic visibility that lasts.

Free weekly newsletter

Get the next one on Sunday.

One short email a week. What is working in SEO right now. Unsubscribe in one click.

Subscribe on Substack →

Keep reading