With fourteen domains and three people, the problem is not measurement. The work scatters across forty browser tabs, two spreadsheets and one person's memory, and that person is on holiday when the German distributor calls.
This is about search work done together when there are more sites than people to run them. The view is national and industrial: country domains, product-line sites, inherited domains, distant partners.
The example company is invented; the situation is ordinary. The chapter order is the rollout order: divide the portfolio, agree who sees what, then ask what a tool can answer.
Start with tags, not with views
In a portfolio of fourteen domains the first question is not which chart to open, but how you select in one move the five sites this conversation concerns.
Site tags answer that. They are a control, not labels: one tag narrows every view, so Search Console figures, rank tracking and indexing status describe the same set.
The temptation is a hierarchy — group, business area, country, language, product family. It looks tidy and fails within a year: nobody dares move a site off a wrong branch once a report rests on it.
| Axis | Example values | Question it answers | Sign the axis has gone bad |
|---|---|---|---|
| Market | market-fi, market-se, market-de, market-pl | Which country moves and which stands still | Language and country in one value |
| Product line | line-lifting-gear, line-ventilation, line-service | Does the line earn its own domain | Values follow the catalogue's item structure |
| Site purpose | purpose-sales, purpose-support, purpose-recruiting | Is the site judged by the right metric | Everything tagged as sales |
| Lifecycle stage | stage-new, stage-established, stage-inherited | Where attention belongs this quarter | Set once, never looked at since |
Acquisitions bring domains with history, links and often traffic that nobody decided to close or revive. A tag value of their own makes them countable in ten minutes.
Three or four axes suffice, and each extra one costs upkeep whenever a site joins.
One consent, many viewers, one revocation
In an industrial group more people want search data than work with it: the German subsidiary's marketer wants one country domain, an agency in Tampere a campaign, a Polish distributor their site, finance one number a quarter.
The connection to Google is made once: one approval covers email, search console and visitor analytics. Accounts can be grouped so the domain's owner keeps verification, even when group marketing reads the figures daily.
Verification resting on one employee's personal account becomes a problem when their employment ends.
Subsidiary marketer
Sees their country domain in full, no other markets and none of the group's tags.
- Shared to an email address
- Duration: open-ended
Advertising agency
Gets the sites the campaign covers, and only while it runs.
- End date agreed in advance
- Revocation logged as a task
Distributor
Sees their own market's site, not internal pricing notes meant for others.
- One site at a time
- No visibility into other shares
Consultant or intern
Joins for three months, stays on the access list for three years unless removed.
- Reviewed each quarter
- Removed when the contract ends
Sharing goes one site at a time to a registered email address, and the recipient sees only that: not other domains, shares, or your tags. Revocability makes it safe.
A model that first decides what to read
A general language model knows the vocabulary of search optimisation but never saw your Polish product site. Its answers hold for every site and therefore none; an assistant wired into your project data differs in what it does first.
The question goes to a routing model, which decides what material the answer needs. Four kinds of block exist — Search Console figures, rank tracking, campaign state and custom blocks you define — and zero to three load per question.
The custom block matters most to a group, holding what no interface produces: the fair calendar, a launch date, a plant shutdown, a distributor agreement ending in Poland, two weeks of shop downtime. These explain curves more often than technical causes.
Zero blocks is not a fault. Ask how position and click share relate and your numbers add nothing; ask which German terms left the top thirty last month and routing fetches exactly those.
- Name the site. Across fourteen domains, routing cannot know what you mean by "the site". One word saves one wrong answer.
- Name the period. Without one you get a default window; in a seasonal business the wrong window inverts the conclusion.
- Ask one thing at a time. Campaign status, competitors, country split and indexing at once exceed the three-block ceiling; an answer comes, but some material goes unread.
- Hand over lists in batches. Keyword and URL lists are taken in bundles, suiting a new product line or a new language version.
Text appears character by character as the model produces it, which is not decoration: two lines are enough to see the reasoning wander into the wrong country and stop it.
Where the work is kept when nobody does it full time
In a three-person department nobody sits with one domain daily. A site gets looked at when someone asks, which produces the familiar case: the answer exists, in one inbox, whose owner is in Poland.
The project timeline
Every project has a continuous stream where entries accumulate in chronological order as they arise.
- Questions with their answers. The reasoning is saved with the question, beside a note of which material it used.
- Automated reports. Summaries appear alongside the project instead of as an attachment to one recipient.
- New link placements. Each shows the source site, its DR value and traffic, so you judge rather than trust it.
- Campaign notifications. Automation reports on the timeline what it has done and when.
- Unfinished tasks. A task stays in the conversation that produced it.
The layout is familiar from any messaging app; the unusual part is authorship. Some entries come from a human hand, others from background processes, and figures stay current without manual updating.
The value shows at handover. A memo typed in a hurry does not help a successor; scrolling back to read what was tried and concluded does, and a timeline filling as a by-product is the note that never goes unwritten.
Four filters, three states and one search box
The flip side of a timeline is length: a busy product-line site gathers hundreds of entries in six months, and storage helps nobody if the right point cannot be found.
First comes the filter row: All, Links, Files and Tasks. Links lines up the period's placements with their values; Files gathers the reports for when the managing director rings about March.
Tasks shows the points awaiting a decision; All is worth opening after a break. Second come the three task states, few by design, because more states turn the choice into its own discussion.
| State | When you mark this | Example from the group portfolio | What moves it out |
|---|---|---|---|
| Active | Work is under way or starts this week | Swedish country domain's product pages lack technical specifications | The task finishes, or is split as too large |
| Deferred | The suggestion is right, the timing is not | Product structure changes only in next year's item-code revision | The blocker clears, or six months pass |
| Rejected | You decided against it and the reasoning is worth keeping | No public price list on the Polish site | The business changes and the reasoning lapses |
The middle state is the most useful and most often skipped. In an industrial year a good suggestion collides with timing: nomenclature is revised in spring, the fair season eats two months, the development queue runs three weeks.
Without it, such suggestions land on a list nobody reopens and return a year later as fresh insight. The third state records a decision already made in the negative, whose absence is billed whenever the discussion restarts with a new colleague.
Third, free-text search runs across the whole message history: one remembered word surfaces a half-forgotten investigation with the conversation around it, and that context is what a detached note lacks.
A week in the marketing of an industrial group
Take an ordinary invented example. An engineering group in Central Finland, plants in two towns, sales companies in four countries: fourteen domains — the group site, six country domains, three product-line sites, a recruitment site and three inherited addresses, two untouched for years.
Three people work in marketing, and for none is search visibility the first line of the job.
The Tuesday half hour recurs in the calendar: one tag value is filtered at a time, usually market, and figures are read against a six-month window.
The long window is not carelessness: volumes on Finnish and Estonian terms are too small for a shorter period to separate movement from noise. German and Polish figures would tolerate less, but consistency beats optimisation.
The rule is strict: anything unusual becomes a named task in the right stream before the half hour ends. Other domains are checked monthly, inherited addresses quarterly, only for whether any page still carries traffic.
The real work happens outside the slot. On Thursday the German sales company calls about fewer web enquiries than in spring; the question goes into that site's timeline, routing fetches search console and ranking data, and two clarifications later the picture is testable.
The first answer was half wrong, but it stays visible, so the next reader sees the dead end instead of walking into it. Seasonality differs by country: service is searched in autumn, investment at the budget turn, and a fair month lifts brand searches in a way that reads as organic growth.
Put close monitoring where the curve moves, not evenly across the year. Three people cannot cover everything, so the question is what to buy in.
When your own people cannot cover the portfolio
The difference between the tiers is less about features than about who makes the choices and who checks the changes.
- AutoSEO, 149 USD a month. The system finds and ranks search terms without anyone picking by hand, handles link acquisition and proposes site fixes. The analytics sections are open in full.
- FullSEO, 500 USD a month. You may choose terms yourself without losing automatic suggestions, set a DR threshold for link sources, and changes pass review before production.
- Add-ons priced separately. Wikipedia placements cost ten dollars each and PBN placements one dollar each, sold as ready-made packages.
- The upper tier comes with people. FullSEO brings search specialists, developers and writers — for a three-person department, roles not worth making permanent.
Pricing follows the domain, not the number of users: inviting a subsidiary marketer or distributor does not raise the invoice, so no shared login is needed. The tiers are set out in the description of the campaign automation; in euros roughly a hundred and forty and four hundred and seventy, though billing is in dollars.
Export, PDF and how the document looks
In a group a report rarely travels one way: the same material reaches a management slide, a sales company's tracking and sometimes a board appendix, so the reporting and export tools offer three output formats.
Machine-readable formats are for further processing: ten thousand rows cover a quarter's keyword material inside a spreadsheet. The printable version is generated server-side, and its ceiling of two hundred and fifty rows is intentional: the reader is a person, not a formula, and the limit forces the question of which part of the material describes the month.
Group logo and colours go onto the template: few build a presentation from a colourless tool document, while a branded one is attached as it stands.
Rising or falling
Answers the one question certain to be asked, and shows seasonality.
One figure at a time
Answers most questions without opening the detail view.
Direction inside a table row
A few millimetres of curve show whether the row moves or sits still.
Countries and devices
Shows what an average conceals: in one country a mobile visitor behaves unlike anywhere else.
Set report day in the week after the month turns, not the last working day. The two-day lag closes by itself, and nobody explains why the final days look empty. How we build the interpretation section is set out in the description of our services.
What the tool will not do for you
Everything so far concerned structure, which is put up once and stays. The content inside is never finished, and four parts of it stay human however well the automation works.
- Prioritisation. Which country domain or product line deserves this year's effort is a business decision. The tool shows movement; it does not know which product's margin the group lives on.
- Finding causes. The view tells you reliably which terms lost traffic and when. The explanation sits outside the system: a competitor's warehouse in Poland, a revised price list, a new distributor, lead times stretched to eight weeks.
- Setting goals. Awareness, the number of enquiries and their quality do not improve through the same measures. Which is weighted is a management call, not a figure in a report.
- Communication. Explaining to a sales company or the board why the quarter came in below expectation, and what will be done, stays a human task.
Frequently asked questions
All our domains are already in Search Console. What does this add?
Search Console answers what happened, one domain at a time. Missing are portfolio-level filters, a shared memory of decisions and their reasoning, and access that can be granted and revoked. With more than one person, the bottleneck is memory, not measurement.
Besides the country domains we hold old addresses from acquisitions. Worth including?
Yes, if only to force a decision. Give them a tag value and check quarterly whether they still produce traffic or hold links worth redirecting. Without figures, such domains get renewed every year while nobody decides anything.
Can a distributor see other countries' figures if we give them their own site?
No. A share covers one site and one registered email address. The recipient sees neither the other domains, your tag structure, nor who else holds access, and the right can be revoked at any time.
There are three of us and fourteen domains. Isn't this meant for larger organisations?
Take only part of it into use. One tag axis, say market, and one project stream per site genuinely looked after is enough. What is expensive is building the structure once the portfolio has grown confusing.
Can the assistant be given a whole item list at once?
Yes. Lists are processed in bundles, suiting a new product line or language version. Candidates come from three sources: search console data, live search results and the seed words you supply. Each is decided individually — in, out, or pending.
Roll this out in the order the article runs: domains and the Google connection, then a single tag axis, then access rights with end dates. Fourth, one real task through the timeline for a month; the report template last.
Two domains are enough for a trial. Sign in and attach your first domain, leave it a month, and bring in the rest only if the habit suits you; our other articles are in our blog.
Finally, a test that measures no rankings. Ask a colleague what was decided about the Polish site last spring: if they show it in two minutes rather than recalling it, the workspace is in order; if not, what you lack is a place to put things, not a metric.