Google Search Console for Multiple Websites: How to Manage and Compare Properties

If you manage more than one website, you already know the problem: Google Search Console is built for one site at a time. Every insight, every comparison, every alert is siloed inside a single property view. To see how two sites are performing, you have to open two browser tabs, screenshot both, and mentally compare them.

For agency owners, content portfolio managers, and any site owner with more than a handful of properties, this friction compounds fast. The data is there. The comparison isn't.

This guide covers how to manage multiple websites in Google Search Console efficiently: how the property system works, how to add and verify multiple sites, what GSC does and doesn't give you across properties, and how to get the cross-property view GSC was never designed to provide.

How Google Search Console Properties Work

GSC organizes everything around properties -- individual website addresses you've verified ownership of. Each property has its own:

Performance data (queries, pages, clicks, impressions, CTR, position)
Index coverage report
Sitemap submissions
Core Web Vitals data
Enhancement reports (structured data, etc.)

There is no native "portfolio view" or "combined report." If you own 10 sites and want to see total clicks across all of them, GSC can't show you that.

Domain Properties vs. URL-Prefix Properties

When adding a site, GSC offers two property types:

Domain property (e.g., example.com)

Covers all URLs across all subdomains (www, blog, shop, etc.)
Covers both HTTP and HTTPS
Requires DNS TXT record verification
Single property covers the entire domain footprint

URL-prefix property (e.g., https://www.example.com/)

Covers only the exact URL prefix specified
A separate property for http:// vs. https:// and for each subdomain
More verification options (HTML file, meta tag, Google Analytics, Google Tag Manager)
More granular if you need separate reporting per subdomain or protocol

For most sites, a domain property is the right choice: it's one property that captures everything, and it eliminates the "am I missing www traffic?" question that URL-prefix properties create.

Adding Multiple Websites to Google Search Console

There's no limit to how many properties you can add to a single Google account. The process is the same for each one.

Step 1: Add a Property

Open Google Search Console
Click the property dropdown at the top left
Select "Add property"
Choose Domain or URL-prefix, enter your site, click Continue

Step 2: Verify Ownership

Verification methods depend on the property type:

Domain property:

DNS TXT record (only option) -- log into your domain registrar, add a TXT record Google provides, verify in GSC

URL-prefix property (any of these):

HTML file upload
HTML meta tag in <head>
Google Analytics (if GA is already on the site)
Google Tag Manager (if GTM is installed)
DNS TXT record

DNS and HTML file verification are the most durable. Analytics/GTM verification breaks if the GA or GTM code is removed.

Step 3: Add Owners and Users

For agency setups or team accounts, you can grant access to each property separately:

Open the property in GSC
Go to Settings > Users and permissions
Add users by Google account email
Assign Owner (full access, can add/remove users) or Full/Restricted user roles

One important limitation: there's no way to grant access to "all properties" in bulk. Each property requires a separate permission grant. For large portfolios, this is a significant administrative friction point.

Switching Between Properties

With multiple sites added, switching is done through the property selector dropdown (top left in GSC). The dropdown shows all properties you have access to, grouped by account.

GSC remembers which property you last viewed, so each time you open the tool you'll land on the same site. For multi-site work, you'll be clicking that dropdown constantly.

A practical workaround: Bookmark the direct URL for each property's performance report. GSC URLs encode the property, so bookmarks land you directly inside the right site's data without going through the dropdown.

The URL pattern looks like:

https://search.google.com/search-console/performance/search-analytics?resource_id=sc-domain%3Aexample.com

What GSC Doesn't Give You Across Multiple Sites

Before trying to work around GSC's limitations, it's worth knowing exactly what they are.

No combined metrics view. You cannot see total clicks, impressions, or average position across all your properties in a single chart.

No cross-property query comparison. You can't search for a keyword and see how all your sites rank for it simultaneously. You check one property, switch, check another.

No unified alert system. If traffic drops 40% on one of your five sites, GSC won't notify you unless you've set up individual alerts per property (or use Google Search Console's email settings, which are property-specific).

No bulk sitemap submission. You submit sitemaps property by property.

No shared annotation across properties. If you ran a site-wide SEO campaign across multiple domains, there's no way to annotate all properties at once.

These aren't edge cases for power users. They're the daily friction of managing a content portfolio.

Google Search Console API: The Path to Real Multi-Site Analysis

For anyone serious about multi-property management, the Google Search Console API is what makes automation and aggregation possible.

The API exposes the same data as the GSC interface, but you can:

Query multiple properties in sequence or parallel
Aggregate clicks and impressions across all sites
Compare keyword rankings across properties
Build alerts triggered by traffic changes on any property
Export data to BigQuery, Google Sheets, or any database

Basic API Usage

The GSC API uses OAuth 2.0. Once authenticated, you can pull performance data for any property the authenticated account has access to.

A Python example pulling 7-day performance data:

from googleapiclient.discovery import build
from google.oauth2.credentials import Credentials

service = build('searchconsole', 'v1', credentials=creds)

response = service.searchanalytics().query(
    siteUrl='sc-domain:example.com',
    body={
        'startDate': '2026-10-10',
        'endDate': '2026-10-16',
        'dimensions': ['query'],
        'rowLimit': 25000
    }
).execute()

To aggregate across multiple sites, loop through your property list:

sites = ['sc-domain:site1.com', 'sc-domain:site2.com', 'sc-domain:site3.com']

all_data = []
for site in sites:
    response = service.searchanalytics().query(
        siteUrl=site,
        body={ ... }
    ).execute()
    for row in response.get('rows', []):
        row['site'] = site
        all_data.append(row)

The GSC API guide covers authentication setup in detail. Once you have credentials, cross-property queries are just loops.

25,000-Row Limit

The API returns a maximum of 25,000 rows per request. For large sites with broad keyword footprints, you'll need to paginate using the startRow parameter. Most portfolio sites won't hit this limit in a 7-day window, but high-volume sites will.

Using Search Console Tools for Cross-Property Comparison

Search Console Tools connects to your GSC account through the same OAuth and API layer described above, but surfaces cross-property views without requiring you to write code.

Once you connect your Google account, all your verified properties are available in one place. You can:

Switch between properties without leaving the dashboard
Compare performance trends side by side across two or more sites
See combined totals across your entire portfolio
Identify which properties are gaining or losing traffic relative to each other
Filter for striking-distance keywords across multiple sites at once

For site portfolio owners who live in GSC data, this is the view the native tool was never built to provide.

Multi-Site Monitoring: Building a Practical System

Whether you use the API, a tool, or manual GSC tab-switching, you need a workflow for catching problems across multiple properties before they compound.

Weekly Traffic Review

Pick a consistent day and check each property for:

Week-over-week clicks (looking for drops of 15%+)
New crawl errors or coverage issues
Any manual actions (GSC sends an email for these, but it's easy to miss)

For 5+ sites, this is easier with a spreadsheet that pulls from the API than with manual GSC reviews.

Traffic Drop Alerts

GSC sends email summaries but doesn't have configurable threshold alerts. To get notified when a specific property drops, you need either:

A custom API integration that compares week-over-week data and emails you
A third-party monitoring tool
A scheduled report in Google Looker Studio connected to your GSC data

The Looker Studio / GSC integration guide covers how to build a dashboard that spans multiple properties using the official GSC data source connector.

Index Monitoring

GSC's coverage report is per-property. For multi-site monitoring, the most important signals to watch per property are:

Valid pages count -- should trend up with publishing, not down unexpectedly
"Crawled - currently not indexed" and "Discovered - currently not indexed" page counts -- spikes indicate indexing problems
"Page with redirect" count -- should be near zero

Sudden drops in indexed pages or spikes in "not indexed" categories warrant investigation immediately. These don't get surfaced in the performance report -- you have to check the Coverage report directly.

Practical Setup for Agencies Managing Client Sites

If you're managing GSC for clients, the access model creates some friction to plan around.

Delegated Access vs. Shared Accounts

The cleanest setup: have clients add your agency Google account as an Owner on each of their properties. This keeps clients in control (they can revoke access) and keeps your account able to see all data.

Avoid the temptation to use a single shared Google account across your team for GSC access -- if that account is compromised or loses access, you lose visibility across all client properties simultaneously.

Service Accounts for API Access

For API-based reporting, use a Google service account rather than a personal OAuth token. Service accounts:

Don't expire when a person leaves the company
Can be granted read access to GSC properties
Work with server-to-server authentication (no browser flow needed)

Set up a service account in Google Cloud Console, grant it access to each GSC property under Settings > Users and permissions, and use it for all automated reporting.

Reporting Cadence

For agencies reporting to clients, a consistent format matters more than comprehensiveness. A weekly PDF or dashboard showing:

Total clicks (7-day and 28-day, with trend)
Top 5 pages by traffic
Top 5 queries
Any coverage errors

...beats a monthly deep-dive that clients never read. Keep it short, keep it consistent.

Common Multi-Site Mistakes

Adding URL-prefix properties instead of domain properties. This causes you to miss traffic from non-www or HTTP variants. If in doubt, use domain properties.

Not verifying DNS-level. Analytics-verified properties break when the analytics code is removed (e.g., during a site redesign). DNS verification is permanent as long as you own the domain.

Comparing sites with different verification dates. GSC only shows data from after the verification date. A site verified last month has a 30-day data history; a site verified three years ago has 16 months of data. Comparisons with short-history properties are misleading.

Treating impressions as traffic. Impressions count every time a URL appears in results, including the same user seeing the same result multiple times. Click trends are more meaningful than impression trends for measuring actual user interest.

Ignoring the "+" properties. If you see an unexpected property in your GSC account (one you didn't add), someone with DNS access to that domain has verified it. This can indicate a domain ownership issue or a former employee's account.

Summary

Google Search Console handles multiple websites by requiring you to manage each property separately. There's no native portfolio view, no bulk access management, and no cross-property reporting. For portfolio managers and agencies, the daily workflow becomes: switch properties, check one thing, switch again.

The practical solutions are:

Domain properties for each site (not URL-prefix -- they miss too much)
Bookmarked deep links to skip the dropdown for each site's performance report
API access for aggregation, automation, and alerting across all properties
A unified dashboard (like Search Console Tools) to skip the API build and get cross-property views today

The data you need is already in GSC. The friction is in how the interface forces you to access it one property at a time.