The regional office reports on one website and is judged on four. The global domain it does not control, the legacy regional domain from before the group consolidated, the distributor sites carrying the brand in six markets, and a microsite built for a trade fair in 2021 that nobody has switched off. All four appear when a buyer searches, and only one of them appears in the quarterly report.
This is the standard shape after a decade of corporate consolidation, and it produces a specific difficulty: the properties a regional office is accountable for and the properties it can measure are two different sets, overlapping only partly. Making that overlap visible is the work — and it turns out to be considerably more useful than any single one of the reports it replaces.
Four kinds of property carrying one brand
| Property | Who controls it | Who can measure it |
|---|---|---|
| Global domain, country folders | Headquarters | Headquarters, sometimes the region |
| Legacy regional domain | The region, in principle | Whoever still has the login |
| Distributor sites | The distributor | Nobody at the group |
| Abandoned campaign microsites | Formally nobody | Nobody |
The third column is the finding and it is worse than the second. A property nobody can measure is one where a problem produces no signal at all — the legacy domain can drop out of the record entirely and the first indication will be a customer mentioning it eighteen months later. In a group that reports quarterly on everything, having four properties and two measurements is the actual governance gap.
Half of these nobody can currently log into
Before any consolidation, an access audit. The legacy regional domain was set up by an agency that no longer works with the group; the microsite was built by a colleague who has moved to another subsidiary; the country folder analytics sit with a headquarters team in a different time zone. None of this is unusual and all of it is fixable, but only deliberately.
Properties the group owns
Legacy domains, microsites, anything registered to the company. Access can be restored through the registrar or the hosting provider with paperwork and a fortnight.
- Worth doing before you need it
- Paperwork rather than negotiation
Properties others control
Country folders held by headquarters, distributor sites. Access is a request, and the request is far easier to make before there is a problem than during one.
- Read access is usually granted
- Nobody asks until it is urgent
The right-hand card is where regional offices consistently underinvest. Read access to the country folders in the group's reporting costs headquarters nothing and is normally granted on request — but the request has to be made, and it tends not to be, because in ordinary weeks nothing depends on it. The week it does depend on it is the week somebody needs an answer within the hour.
What changes when the measurable properties report together
Labels rather than separate accounts
Each property carries a marker behaving as a filter across every screen.
- One sign-in covers everything included. More than thirty-five interfaces sit behind it, from placement tracking to observing what assembled answers say about the group.
- A restriction, once set, travels. Narrow to one property or one market and the narrowing holds in the figures, the task list and every file that comes out.
- Eleven services feeding one record. Material from Google, from Analytics and elsewhere lands in a single dataset rather than being duplicated per property.
- Google authorised once per property. Mailbox, Search Console and Analytics under a single grant — and a grant that can be cleanly withdrawn when a property is retired.
The daily allowance is shared
Relevant here mainly because the global domain is enormous and the regional ones are not.
- One thousand a day belongs to the account. Everything inside it draws from the same figure, whether that is a two-hundred-page legacy domain or a country folder of a global site.
- Up to ten thousand in a batch. Accepted whole and processed against the daily limit, putting ten thousand at roughly two working weeks.
- Two processing, twenty queued. Where a global template change and a regional clean-up coincide, the order has to be decided rather than left to filing time.
- Three levels of nesting, a thousand sitemaps per batch. Ample for regional properties; the global domain is a different scale and a different conversation.
For the regional properties this rarely binds — a legacy domain of two hundred pages clears inside a day. The reason to know the figures is different: when a global relaunch is running, the allowance is being consumed by headquarters, and a regional clean-up filed in the same week will simply wait. Knowing that in advance turns an unexplained delay into a scheduling decision.
A second effect appears only once the measurable properties are viewed together: identical groundwork carried out twice. Somebody preparing material for the country folders researches the same wordings as somebody maintaining the legacy domain, neither aware of the other, because there is nowhere common to leave a half-finished result. It surfaces when both properties address the same query with the same argument and each performs worse than one properly resourced page would have.
Properties you can both control and measure
The legacy regional domain, any regional microsite still serving a purpose, and the country folders if read access exists.
- Two to four of them
- Include deliberately
Properties you can do nothing about
Distributor sites, aggregator listings, anything where neither the content nor the access is yours. Spending here buys nothing.
- Several of them
- Monitor, do not fund
Four properties, four different treatments
| Property | Objective | Method |
|---|---|---|
| Country folders | Get the regional facts published | Content requests with evidence attached |
| Legacy regional domain | Decide: consolidate or maintain | Redirect page by page, or fund it properly |
| Distributor sites | Keep their information current | Supply data in a form they can publish |
| Abandoned microsites | Remove them | Redirect to the regional pages, one hop |
Recording that decision per property in a shared overview — what happens to each and why — stops the next reorganisation from creating a fifth property alongside the four.
The second row is the decision most regional offices avoid for years. A legacy domain that still ranks, still receives visitors and nobody maintains is neither an asset nor a liability until somebody decides which it is. Consolidating it into the country folders preserves what it accumulated and removes a competitor; leaving it running unmaintained means the group has two answers to every question and no control over which one a buyer finds.
Row four looks trivial and is worth doing first, precisely because it is trivial. A microsite from a trade fair three years ago costs nothing to retire, produces an immediate small improvement, and — more usefully in a group setting — demonstrates that the exercise produces results before anybody has been asked to decide anything difficult. Starting a consolidation with the item nobody will defend is not a technical argument; it is how the harder rows get agreed two months later.
The sites carrying your brand that are not yours
In markets served through distributors, their pages frequently outrank the group's for the group's own product names. That is not automatically bad — a distributor ranking well is a distributor selling — and it becomes a problem in exactly one situation: when their information is out of date.
- Supply current data in a publishable form. Specifications, certifications and availability as a document they can copy from, updated when the products change. Most distributors will use it because writing it themselves is work.
- Check what they actually published. Twice a year, per market. This takes an afternoon and regularly finds a specification two revisions behind on a page ranking above yours.
- Make sure your own page exists. Where the group has no page for a market at all, a distributor's page is the group's page whether or not anybody intended that.
- Accept the ranking, correct the content. Trying to outrank your own distributor is a poor use of a regional budget. Making sure what they publish is accurate is not.
The last point runs against instinct and is the right approach commercially. A distributor page that ranks and carries current information sells the product; the same page carrying an obsolete specification loses a deal and the group is blamed for it. The regional office cannot change their ranking and can entirely determine whether what they publish is correct — which is the higher-leverage half of the problem.
There is a further reason to keep the distributor check on a fixed schedule rather than doing it when somebody complains. Product data changes on the group's timetable and distributor pages change on theirs, so the gap between the two widens continuously and invisibly. A twice-yearly check catches it while the divergence is one revision; waiting until a customer raises it means catching it at three, by which point the conversation is about a delivery rather than about a web page.
One data set, headquarters and country managers
A regional office reports in two directions simultaneously, and the two want opposite things. Headquarters wants the region rolled up and compared with other regions; country managers want their own market and specifically not a comparison. Both come from the same underlying record, which is what makes producing them separately practical.
- Headquarters, quarterly, region rolled up. Few figures, year-on-year, in the group's format. Printed exports hold two hundred and fifty rows, well beyond what will be read.
- Country managers, monthly, their market alone. Fifty to two hundred rows per screen suffices, since the view is filtered anyway.
- The regional team, monthly, everything measurable. Including the properties nobody else looks at, which is where problems surface first.
- Attached to requests, narrowest possible. One market, one page, one figure, one comparison. The format that gets scheduled rather than deferred.
Configuring the four outputs once inside a shared environment means none of them has to be rebuilt by hand before a deadline.
The tension between the first two is familiar in any regional structure and resolves cleanly here. The comparison across markets is the most useful view for headquarters and the least welcome one for whichever country comes off worst. Producing both from one record at least removes any argument about whose figures are correct, which in a group reporting environment is most of the argument.
Cadence matters as much as format here, and in a group structure it is partly fixed for you. Headquarters reporting follows the group's quarterly cycle whether or not that suits the data. What goes to country managers should be monthly, because it leads to action in their market. What the regional team reads should also be monthly, and it is the only one of the three that ever surfaces a problem early — the other two are, by construction, summaries of what has already happened.
Asking a question across the measurable properties
With several properties and thirty markets, most of the working hour goes on navigation rather than analysis. Putting the question in ordinary words removes that: between none and three data blocks get fetched according to what the question needs, and the last twenty exchanges stay in view so a follow-up still makes sense.
One question repays being asked deliberately in this configuration: for which wordings does the legacy domain appear at the same time as the country folder? Every such wording is a case where the group is competing with itself, and the list is the working brief for the consolidation decision. Producing it takes minutes inside one workspace and is effectively impossible across separate accounts.
What the measurable properties cost
Billing attaches to each domain, and only to properties the group actually controls — nothing here applies to a distributor site. Four measurable properties on the smaller package, with one encyclopedic placement and the lowest network quantity, come to 626 dollars a month and 7 512 across a year. A mixed arrangement with the main regional property on the larger package runs to 957 monthly and 11 484 annually.
| Configuration | Components | Monthly | Twelve-month total |
|---|---|---|---|
| Four properties, smaller package | 4 × AutoSEO, 1 encyclopedic (10 $), 20 network (20 $) | 626 $ | 7 512 $ |
| Mixed | 1 × FullSEO, 3 × AutoSEO, 1 encyclopedic (10 $) | 957 $ | 11 484 $ |
| After consolidation | 2 × AutoSEO | 298 $ | 3 576 $ |
Deciding which properties justify inclusion means establishing what each is currently found for, which is a keyword research question rather than an internal negotiation. Whether each ships and gets catalogued properly is a technical review matter, and whether the regional pages that ought to answer local questions exist at all falls to content strategy. Running all three out of a single account is what makes the properties comparable in the first place.
A closing note on what this does and does not achieve. Bringing the measurable properties together does not reduce the amount of work; it makes the work visible and comparable, and it closes the gap between what a regional office is accountable for and what it can actually see. The first weeks are frequently uncomfortable, because a single screen now shows how many properties carry the brand without anybody maintaining them. That discomfort is the output — it is the information needed to decide which two deserve attention and which two should be retired, and it is not available any other way.
Bring the measurable properties into one view
Questions from regional offices
We cannot access the country folder data. What can we do?
Ask for read access, in writing, before anything depends on it. It costs headquarters nothing, it is normally granted, and the request is far harder to make in the week somebody needs an answer urgently. Where it is genuinely refused, that refusal is itself worth documenting — it defines what the regional office can be held accountable for.
Should we keep the legacy regional domain?
Only if it contains something the country folders do not, and in that case the material should move rather than the domain being maintained around it. Otherwise it competes with the group's own pages for the same wordings and has been doing so for years. Consolidating it page by page preserves what it accumulated; switching it off without redirects throws that away.
Our distributor outranks us for our own products. Is that a problem?
Not in itself — that distributor is selling. It becomes a problem when their specifications are out of date, because a buyer specifying against obsolete figures blames the manufacturer. Supply them with current data in a form they can publish and check twice a year what they actually put up. Trying to outrank them is a poor use of a regional budget.
Does each property get its own daily allowance?
No, they share it. The thousand addresses a day belong to the account. At regional scale this rarely binds, but during a global relaunch the allowance is being consumed elsewhere and anything you file will simply wait — which is worth knowing before it looks like a failure.
Can country managers see each other's figures?
Only if configured that way. Markers act as filters everywhere, so each manager can receive an output covering their market alone while the region keeps the comparison for headquarters. Both come from one record, which removes any dispute about whose numbers are right — and in a group structure that dispute is usually most of the meeting.
Do all properties need the same package?
No, and usually they should not. Since billing follows the domain, packages can be mixed. The larger one belongs where somebody actually participates in choosing what to pursue — normally the main regional property — with the rest below it. Across four properties that arrangement comes to 957 dollars a month.