Google Search Console for Multiple Sites: Properties and Access
How to run several sites in one Search Console account: adding and verifying each property, Domain vs URL-prefix, who gets access, and why no report adds them up.
One Google account can hold up to 1,000 Search Console properties, so running several sites from one login is normal. Each site is added and verified as its own property, each property has its own list of users, and every report reads one property at a time. That last part costs time. Search Console has no view that adds your sites together, in the web interface or the API.
TL;DR:
- Limit: "You can have up to 1,000 properties in your Search Console account."
- Add each site with + Add property in the property selector. Pick Domain (verified by DNS, covers every subdomain and protocol) or URL-prefix (one exact start of a URL).
- Access is per property: Owner, Full or Restricted, and at most 100 non-owners on each one.
- Reports and the API read one property per request. A cross-site view means pulling each site and joining the rows yourself.
How do you add another site to Search Console?
Open the property selector on any Search Console page and choose + Add property. Google's help is explicit that this is safe on a live site: "Adding a property does not affect your website or platform property on Google Search."
You then pick one of two property types, and the choice decides what the reports include.
Domain or URL-prefix: which property type?
- Domain property. "A Domain property aggregates data for all subdomains, protocols, and subpaths of the property."
example.comthen coverswww.example.com,blog.example.com, http and https in one place. It needs DNS: "A Domain property requires you to verify ownership using DNS record verification." - URL-prefix property. "A URL-prefix property specifies the start of a URL. Any URLs that begin with this prefix are included in that property."
https://www.example.com/excludeshttps://example.com/and every other subdomain. It accepts more verification methods: an HTML file, a meta tag, Google Analytics or Tag Manager.
For a team that controls DNS, Domain is the better default. You get one property per site, with nothing split across www and the bare domain. Add a URL-prefix property beside it only for a section you want reported on its own, such as /docs/ or a country folder.
In the API the two types are written differently, and a script that manages many sites needs both: http://www.example.com/ for a URL-prefix property, sc-domain:example.com for a Domain property.
How do you give a team access to each site?
Users are added per property, by an owner, under Settings > Users and permissions > Add user. There are three levels:
- Owner: "Has full control over properties in Search Console", including adding and removing users.
- Full user: "Has view rights to all data and can take some actions", such as submitting a sitemap or removing a URL, but cannot manage users.
- Restricted user: "Has simple view rights on most data."
The cap is per property: "A property can have a maximum of 100 non-owners." With ten sites, giving one new colleague access means ten trips through Settings, because nothing grants access to a whole account at once. Write down who holds Owner on each property while you are there. When the only verified owner leaves the company, getting control back means verifying the site again.
Try it
Point an SEO agent at your own site, not just an essay about one.
QueryScope holds the plan for your site, reads your real Search Console, and hands the coding agent you already have one change at a time to rank for the searches you decided to win. From $49/month, everything included.
Can you see all your sites in one Search Console report?
No. The property selector switches between sites; it does not combine them. Every report (Performance, Page indexing, Sitemaps, Core Web Vitals) is scoped to the property you have open, and so is the export button.
The API works the same way. The Search Analytics call is addressed to a single property:
POST https://www.googleapis.com/webmasters/v3/sites/siteUrl/searchAnalytics/query
where siteUrl is "The URL of the property as defined in Search Console." The sites.list method tells you which properties your account can read and at what permission level, so a script can loop over them. Adding the results up is your job. Watch two things when you do:
- Overlap. A Domain property and a URL-prefix property for the same site report the same clicks twice. Sum one property per site.
- Query rows do not add up to totals. Google withholds rare queries for privacy, so take totals from page-level rows. Page vs query data explains the gap.
A cross-site pull also runs into the export limits once a site is large. How to export Search Console data covers the row caps per route.
What does a multi-site setup need beyond Search Console?
Two things that Search Console leaves to you, and they matter more with every site you add:
- History. Each property keeps 16 months and then deletes. Store what you need from every site, not only the one that is busy this quarter. Search Console data retention covers what to set up.
- A record of what changed where. With five sites shipping changes, a drop on one is hard to place unless you know what was deployed on that site and when.
Reading several sites from your editor
This is how QueryScope is built for teams with more than one site in a repo. You connect each site's Search Console over a read-only grant. Your coding agent passes the domain of the repo it has open, so it reads that site's data and nobody switches properties by hand. Each site keeps its own plan of the searches it is going after, its own stored daily history, and its own record of every change. The Team plan covers 3 sites and the Pro plan 10, with every feature on each.
Sources
- Search Console Help, Add a website property to Search Console ("You can have up to 1,000 properties in your Search Console account"; "Adding a property does not affect your website or platform property on Google Search"; "A Domain property aggregates data for all subdomains, protocols, and subpaths of the property"; "A Domain property requires you to verify ownership using DNS record verification"; "A URL-prefix property specifies the start of a URL").
- Search Console Help, Managing owners, users, and permissions (Owner: "Has full control over properties in Search Console"; Full: "Has view rights to all data and can take some actions"; Restricted: "Has simple view rights on most data"; "A property can have a maximum of 100 non-owners").
- Search Console Help, Verify your site ownership ("HTML file upload can be used for URL-prefix properties", plus the HTML tag, Google Analytics and Tag Manager methods; when the only verified owner leaves, "you should verify ownership to maintain (or regain) access to the property").
- Google for Developers, Sites resource (
siteUrlexamples:http://www.example.com/for a URL-prefix property,sc-domain:example.comfor a Domain property;permissionLevelvalues). - Google for Developers, Search Analytics: query (the request path names one
siteUrl, described as "The URL of the property as defined in Search Console").
Try it
Put an SEO agent in your editor.
Ask your coding agent what to work on. QueryScope reads your real Search Console, holds the searches you decided to win, and hands back one move at a time with the proof it worked. From $49/month, everything included. 1, 3 or 10 sites.