The legal pages every website needs in Europe, and how to run them on 50 sites
Privacy notice, imprint, terms, cookie consent: what every site needs before it goes live, and how one line of code per site runs them on fifty.
Guides · Search Console
Connecting Search Console for 10+ sites without the busywork
Inventory first, one access grant per property, a clean site mapping and a short checklist for the first sync. The setup we recommend for every new workspace.
Guides · Search ConsoleConnecting one site to Google Search Console takes a few minutes. Connecting twelve tends to take an afternoon, mostly spent switching Google accounts and wondering which property belongs to which domain. This guide is the order of operations that keeps it short.
Start with an inventory
Before you touch Search Console, write down every site you want to report on, with the exact hostnames it serves. A site that answers on both example.com and www.example.com, or on a separate shop. subdomain, needs a decision about how it is measured.
- The primary hostname, and any redirecting variants
- Subdomains that should count as part of the site
- Which Google account already owns or can verify each property
Pick the right property type
Search Console offers two property types, and the choice changes what your totals include.
| Domain property | URL-prefix property | |
|---|---|---|
| Covers | All protocols and subdomains of the domain | Only URLs under the exact prefix, protocol included |
| Verification | DNS record only | DNS, HTML file, meta tag, Google Analytics or Tag Manager |
| Good for | The complete picture of one site | A single section, or when you cannot edit DNS |
Rule of thumb: use a domain property per site whenever you control DNS. Keep URL-prefix properties for subfolders you want to report on separately.
Grant access once per property
Reporting only needs read access. Instead of sharing owner rights, add the Google account you connect to Multisite Agent as a user on each property. Do it in one sitting, property by property, from the account that already owns them.
- Open the property in Search Console and go to Settings › Users and permissions.
- Add the connecting account with the lowest permission that still shows performance data.
- Repeat for the next property before switching accounts.
“Map each site to exactly one property, and the totals take care of themselves.”
Map properties to sites
Each site in your workspace should point at exactly one property. If a site has both a domain property and an older URL-prefix property, pick the domain property for the overview and leave the other unmapped, otherwise clicks are counted twice.
The connect screen lists every property the account can see and suggests a match by hostname. Check the suggestions, then confirm.
After the first sync
Search Console data arrives with a delay of a couple of days, and the performance report keeps about 16 months of history. The first import pulls what is available; after that, data refreshes daily.
- Compare one site’s clicks against the Search Console UI for the same date range.
- Look at indexing coverage per site, not only the portfolio average.
- Mark sites that still show “Pending” and follow up on their access.
That is the whole setup. From here, the overview screen tells you which site needs attention this week.