A regional office rarely owns the estate it reports on. The question a shared workspace must answer is not how to organise your sites, but which of them you can change and which you can only watch.
Most advice about running many websites from one panel assumes you own them all: you hold the passwords, and the only problem is tidiness. That fails in an office answering to a headquarters elsewhere, where the estate is assembled out of other people's decisions.
Some was registered locally and can be edited this afternoon. Some belongs to a global team three time zones away who will not hand over edit rights, and are right not to. Some sits on a platform nobody here chose. All of it lands in the same quarterly review, where one person must explain why the numbers moved.
Count the surfaces before you count the sites
Take a maker of industrial sensing equipment, headquartered in Scandinavia, with a Benelux office of thirty near Sloterdijk. Ask the two marketers there how many websites they are responsible for and the answer is "one". Ask what surfaces when someone searches the company name from an Amsterdam address, and the count climbs.
- The Dutch domain. Registered locally years ago, still on the local system, and the one thing this office changes without asking.
- The English tree on it. Added when half the sales team stopped being Dutch. Same registration, entirely separate results pages.
- The group's global address. Held by central marketing. Edit rights are not on offer.
- The country subfolder on it. A dozen pages about the Netherlands, published and translated centrally, stale since the product line was renamed.
- The campaign microsite. Built by an agency for a launch two years ago, which still holds the domain and hosting.
- The careers presence. On a platform chosen by a human resources team abroad. Indexed, ranking, outside anyone's control here.
Six surfaces, and the pattern matters more than the number. Two respond to decisions made here; four do not. Yet several appear together for one brand search, compete for the same queries, and all six must be covered when the group asks about local visibility.
Read rights and edit rights are not the same estate
Once the list exists, the only classification worth making is what you may do with each entry. Ownership is a legal question and largely a distraction. What matters is whether a problem you can see is a problem you can fix.
Three states, worth naming because teams blur them: measure and change; measure but not change; and neither, where you observe from outside as you would a competitor.
Measure and act
The local domain and its English tree. Data comes from inside and findings become changes the same week.
- Property access already in hand
- Campaign spend belongs here first
Measure, then ask
The country subfolder, once someone central adds you to the property. Findings leave as tickets for another team's backlog.
- Needs a named owner abroad
- Buys evidence, not fixes
Act through an agreement
The microsite, where change is possible but travels through an invoice and someone else's release schedule.
- Access granted and revoked
- Speed set by the contract
Watch from a distance
The careers platform and anything a supplier hosts. No inside data, but position stays observable.
- Track it like a rival domain
- Report it as context only
One project per surface, including those you cannot touch
The workspace is built around projects. A project is a site, and everything gathered about it — search performance, position history, generative market context, the running feed — hangs off that rather than a global view you filter afresh each time.
The instinct is to create projects only for sites you own and keep the rest in a spreadsheet. That is backwards. The surfaces you cannot change are those you get asked about with the least warning, and a hand-updated spreadsheet is where a reporting line goes to die.
The project, and what attaches to it
For a team speaking about six surfaces and able to edit two.
- Search performance, per site. Clicks, impressions, click-through rate and health flags for each verified property, plus a dashboard spanning them.
- Positions and rivals. Average position, keyword counts, and the domains sharing your term space with their authority attached.
- Generative market context. A model-written read on how a domain is positioned and where content gaps sit.
- A feed per project. Assistant answers, automatic reports, new placements with donor rating and traffic, and to-dos, in one chronological stream.
Seats follow the estate. People are given the projects that concern them, so the intern handling the Dutch blog does not inherit a view of everything, and the colleague in Antwerp watching Flemish results skips past nothing to reach it. The single panel the platform assembles earns its place because the alternative — a login per tool, per site, per agency — is how access quietly outlives the people granted it.
Tag by permission, not by product line
Site tags filter the whole workspace rather than one screen, and the temptation is to spend them on the org chart: one per business unit, product family or market. In an estate defined by permission, that wastes the mechanism.
Tag by what you may do. Separating what you can edit from what you can only observe changes what every dashboard means, because it answers the question management actually has: of this quarter's movement, how much happened on the part we control?
| Surface | Edit rights sit with | Inside data | Tag |
|---|---|---|---|
| Local domain, Dutch tree | Benelux marketing | Yes | act |
| Local domain, English tree | Benelux marketing | Yes | act |
| Group global address | Central marketing | Only if granted | observe |
| Country subfolder | Central marketing | Only if granted | observe |
| Campaign microsite | Agency, under contract | Through the agency | contracted |
| Careers platform | Supplier chosen abroad | No | outside |
A second multiplier sits under all of it. English and Dutch here do not reach two audiences; they reach the same buyer on a different day, at a desk or on a phone, in whichever language the question arrived. The language surface is mirrored rather than additional — same pages, two sets of queries, two sets of results. Before anything is organised, the estate is twice the site count.
Data when nobody will give you the keys
Search Console figures arrive through a linked Google account, and the platform supports account groups rather than one connection — which matters here more than anywhere. The office signs in with its own identity for the local domain; the agency's, if microsite access is ever granted, arrives as a separate group. Access granted for one relationship does not silently extend to another.
One consent flow covers Gmail, Search Console and Analytics together, so connecting is one step. What it cannot do is conjure a property you were never added to. The performance views built on Search Console begin where somebody with rights over the domain adds your address — and that request is often the highest-value email a regional marketer sends all quarter.
Outside-in is a genuine fallback. Position tracking, competitor analysis and the generative market view work against any domain, since they read what results pages and models say rather than what a property tells you privately. Without access you cannot see impressions on the country subfolder, but you can see where it ranks, who sits above it, and whether it is slipping.
| What you want to know | With property access | Without it |
|---|---|---|
| Clicks and impressions | Per page and per query | Unavailable |
| Position for a term | Inside data and tracking | Live results tracking |
| Entries and exits from the top ten | Keyword dynamics | Tracked position history |
| Who else ranks alongside | Competitor view | Competitor view, unchanged |
| Device and country splits | Full breakdown | Unavailable |
Read it the way a regional office should: three rows of five survive the loss of access. Thinner, not empty. "The group's Dutch pages left the top ten for four of our eight priority terms, and here is who replaced them" is a serviceable sentence to put before a headquarters, and needs no permission at all.
One thousand URLs a day, across everything
The submission side is where sharing a workspace becomes concrete and slightly uncomfortable. The allowance is a thousand URLs per day, and it belongs to the account rather than a project. Every site you add draws on it, including those you cannot edit.
What the submission side allows
For an estate where the pages worth submitting are not always yours.
- A daily allowance per account. One thousand URLs each day, not per site, and the counter does not care which project spent it.
- Large batches at once. Up to ten thousand addresses in one batch, released against the daily allowance.
- Sitemaps by file or address. Parsed recursively to three levels, with up to a thousand sitemaps in one job.
- A queue with hard edges. Two jobs run together and twenty may wait, so bulk work is planned rather than improvised.
- A log per address. Bot visit with timestamp, status and error detail, plus live counters for submitted, discovered and failed.
Rationing follows the tags. Pages on a surface you can fix deserve the allowance, because a problem it reveals is one you can act on that day. Pages you cannot fix mostly do not — you would spend the budget to learn a central page goes unnoticed, then wait a quarter for anyone to care. Make the exception deliberately: when you want evidence for that very conversation, a day of allowance producing a timestamped log is well spent.
The mirrored surface makes the arithmetic tight. A relaunch of the Dutch tree relaunches the English one, and a thousand-page site becomes two thousand addresses behind one daily allowance. Two days, planned, is fine; two days discovered on launch morning is not, and the submission tools in the panel show you the queue without extending it.
Access you can take back is the only kind worth granting
Individual sites can be shared with other email addresses, and withdrawn again. In an estate held together by contracts and reporting lines rather than ownership, that one property does more work than any dashboard.
Consider who acquires a view in a normal year. The agency on the microsite needs one for the engagement. Whoever writes the group's quarterly deck needs one, or will keep asking for exports. A writer on the English tree for three months should lose it in month four. A colleague moving region should stop seeing the numbers that day.
The agency on the microsite
Share the one project the engagement covers and nothing adjacent. When the contract ends the view ends, with no credential to rotate.
- Scope the share to one site
- Withdraw on the last invoice
The reviewer at headquarters
Give whoever compiles the group deck a live view rather than a monthly attachment. Their questions improve, and so does what gets presented.
- Cheaper than a recurring export
- Takes you out of the loop
The writer on a short brief
Access to the English tree for the duration. A shared login passed round the team is the version nobody ever undoes.
- A named address, not a mailbox
- Diary the removal when granting
The colleague who moved on
Withdrawal is routine, not an incident. Leavers and internal transfers are one case: the view goes when the responsibility goes.
- Review the share list quarterly
- Nothing personal sits in a share
Saying which part was yours
All of it exists to make one report possible. Each quarter someone at headquarters asks what happened to visibility in the Netherlands, and the temptation is one number across everything — a boast you cannot support or a slump you did not cause.
Reporting runs per project, so the split needs no manual assembly. Exports reach ten thousand rows in CSV or JSON and two hundred and fifty in a server-rendered PDF; the builder decides what goes in and carries your logo and colours. Presenting upward, structure matters more than branding: one part you control, one part you observe.
| Section | Covers | Source | What it supports |
|---|---|---|---|
| What we changed | Local domain, both trees | Inside data and tracking | Judging our own quarter |
| What we asked for | Subfolder, group address | Tracking, inside data if granted | Escalating centrally |
| What we paid for | Campaign microsite | Shared access from the agency | Renewing or ending a contract |
| What we are watching | Careers and supplier pages | Position tracking only | Context, flagged |
An illustration with invented figures shows why the split changes the conclusion. Brand visibility across the estate is flat. Broken out: the two surfaces you control are up on non-brand terms in both languages, the country subfolder slipped from the top ten on four terms after a central template change, and the microsite is unchanged because nobody has touched it since launch. The aggregate says nothing happened. The split says the local team did well, a decision taken abroad cost visibility, and one contract produces nothing.
- Whether the local budget works. Answerable only against surfaces you can act on, so they must be separable.
- What to escalate, with evidence. A position history and a named list of terms travels further than an opinion.
- Whether a contract still earns its place. A microsite flat for four quarters is a renewal conversation, not a mystery.
- Where the second language pays. The mirrored tree is half the estate; an afterthought hides half the result.
The feed is the underrated half of reporting. Questions put to the assistant are answered against real project data — a router decides per question which blocks to load, between none and three, from search performance, position tracking, campaign state or your own material — and the exchange stays in the project's stream beside automatic reports and to-dos. Six months on, when someone asks why a decision was taken, the history is searchable rather than scattered across four inboxes. The reporting side of the platform repays being set up before the quarter you need it; how we read split figures runs through the rest of this blog.
Frequently asked questions
Can I add a site to the workspace if I do not own it?
Yes, and a regional office generally should. Any domain can be tracked from outside — position history, competitors, generative market context — since that reads public results rather than private data. Without being added to the property you lose the Search Console side: clicks, impressions, and the device and country breakdowns.
Does the daily indexing allowance grow as I add projects?
No. The thousand URLs a day belong to the account rather than a site, so every project draws on one pool. Plan submissions beyond a few hundred pages, and remember a bilingual relaunch doubles the queue before you begin.
How do we report on a site we are refused access to?
Track it from outside and label the section honestly. You can show where it ranks, which terms it lost and who ranks above it, all without permission. State that inside data is unavailable and why — that sentence is often what eventually produces the access.
If we share a project with an agency, can we take it back?
Yes. Sharing is per site and per email address, and reversible. Share only the project the engagement covers, note the end date as you grant it, and remove the view when the contract closes rather than at the next access review.
Do the Dutch and English trees need separate projects?
On one domain they are one property and one project, but read them apart regardless. The trees compete in different result sets against different rivals, and an average across both hides whichever is struggling. Use the language and country splits rather than inventing a second project.
The conclusion is not about software. A regional office is judged on an estate it did not design, and the useful thing a workspace does is separate what responds to your decisions from what responds only to somebody else's. With that line drawn and tagged, the quarterly conversation stops defending an average and becomes a set of specific claims, several of them requests aimed at a headquarters waiting for someone to be precise.
The inventory is the work, and it is an afternoon: list the surfaces, mark who holds edit rights, note where inside data exists. To turn that list into projects and start the first quarter of history, set up your workspace in the Semalt dashboard. If the split proves worse than expected, that is the finding — a better opening line than any average. How we approach estates like this is set out under the services we offer.
Hulp Nodig met Uw SEO?
Onze Amsterdam SEO-experts kunnen u helpen deze strategieën te implementeren en uw rankings te verbeteren.
Gratis Consult Aanvragen