The multi-property playbook
Search Console grants quota and visibility per property, not per site. Verify more views of a site you already own and Index Monitor multiplies what it can inspect, pull, and recover. This page shows exactly how that works.
First, the vocabulary
A property is a verified view of your site, and one site can have many. Each one comes with its own daily quota and its own version of your data. Verifying extra views takes minutes in Search Console when you already hold DNS or an existing verification, and it needs no code changes.
sc-domain:example.comthe domain property: every protocol, subdomain and pathhttps://example.com/URL-prefix: everything under the roothttps://example.com/blog/URL-prefix: just the bloghttps://shop.example.com/URL-prefix: just the shopURL inspection allows 2,000 checks per property, per day. Four properties means four budgets.
Web Search Analytics ingest runs per property, up to 50,000 rows a day each, and a prefix property is a pre-filtered deep feed of that section.
Google anonymises per view. What one property hides, another often shows.
Payoff one
Google caps URL inspections at 2,000 per property, per day. Index Monitor treats your overlapping properties as one pooled budget for the site: when a property spends its own allowance, the scheduler hands the overflow to the sibling with the longest matching URL prefix and bills that sibling’s quota instead.
| Property | Budget / day |
|---|---|
| sc-domain:example.com | 2,000 |
| https://example.com/ | 2,000 |
| https://example.com/blog/ | 2,000 |
| https://shop.example.com/ | 2,000 |
| Combined ceiling for the site | 8,000 |
/blog/why-prune-in-march→https://example.com/blog/most specific match/products/hori-hori-knife→https://example.com/next best prefixshop.example.com/basket→https://shop.example.com/subdomain prefixanything else→sc-domain:example.comdomain property catches allBorrowing only starts once the owning property’s own budget is spent, and your Core / High / Medium / Low priorities still decide who goes first.
Payoff two
Every property view anonymises a different slice of your queries. GSC Analytics pulls all of them nightly, stores the union, and logs the anonymisation gap per property, per day, so you can see how much any single view was hiding from you.
sc-domain:example.comhides queries A, Chttps://example.com/hides queries B, Chttps://example.com/blog/hides query ARows are keyed on date × query × page × device × country, so the union never double-counts.
Every ingest run compares the detailed pull against a totals-only baseline and records the difference. You get a number for what Google withheld, per property, per day.
A prefix property spends its whole 50,000-row daily budget on its own section, so a huge blog or shop gets coverage a single flat view can never reach.
Setup
One DNS record verifies sc-domain:example.com in Search Console. If you already have it, skip ahead.
Root, blog, shop, docs: whichever sections carry the most URLs or matter most. Existing domain verification usually covers them instantly.
Authorize every property under your Google account. Overlap detection is automatic, by longest prefix. There is nothing else to configure.
Put it to work
Five properties free, forever. That is a domain property plus four sections of pooled quota, recovered queries and deep section feeds, before you spend a penny.