Search for your company as an employer and count how many of the results you can actually edit. In most organisations the answer is one or two out of the first eight. The rest — review platforms, job board profiles, an industry directory somebody filled in years ago — carry your name, describe your company, and belong to other people.
This is a different multi-property problem from the usual one. It is not that a company runs several websites it forgot about; it is that a company's public description is spread across properties it does not own and cannot change, alongside two or three it does. Managing that means being clear about which is which, and then doing something quite different with each group.
Everything that carries your name
| Property | Who controls the text | What can be done |
|---|---|---|
| Main site | You | Anything |
| Careers domain | You, usually | Anything, once access exists |
| Applicant system pages | Partly you | Text yes, structure no |
| Review platforms and job boards | Not you | Only the company profile fields |
The bottom row is the one that absorbs the most emotional energy and offers the least return. Time spent trying to influence what appears there is largely wasted; time spent on the top two rows is not, because those are the only places where a company can publish something specific enough to be worth quoting. The practical consequence is that the correct response to a bad review page is not a better review page — it is a better page of your own.
A second observation follows from the same table and is easy to overlook. The two rows you control are the only ones where anything can be said that is specific to your company — what your process actually involves, what your ranges actually are, which of your roles genuinely require which language. Everything in the bottom two rows is either generic or written by somebody with partial information. That asymmetry is the entire opportunity, and it is why the correct allocation of effort is so lopsided towards the top.
Half of these you cannot currently log into
Before anything else, an ownership audit. Company profiles on job boards and directories were created by whoever was hiring at the time, frequently on a personal account, and that person has often moved on. The profile stays live and unmaintained, describing the company as it was when they left.
Profiles with a claim process
Most platforms have a route for a company to take over a profile created by a former employee. It takes paperwork and a fortnight and is almost never attempted.
- Worth the effort
- Do it before you need it
Aggregated listings nobody maintains
Directories that scraped your details years ago and have no contact route. The only remedy is publishing something more current elsewhere.
- Stop trying to fix these
- Outrank them instead
Inside the organisation the identical difficulty applies to the properties it genuinely owns. Whoever built the careers domain often still holds the analytics access, or it belongs to a colleague who has since moved departments. Everything runs perfectly well right up to the moment a page vanishes from the record or an alert comes through — and then the login that cannot be reached is precisely the login required. Half a day spent sorting it out removes the exposure for good.
There is a further effect that only shows up once the owned properties are looked at together: the same preparation performed twice. Somebody writing the careers pages researches the same questions as somebody writing the main site, neither aware of the other, because half-finished results have nowhere common to live. It surfaces only when both properties address the same wording with the same argument and both do worse than one properly resourced page would have.
Pages that answer something only you know
Role descriptions, relocation specifics, pay ranges, how the process runs. Each one contains a fact no external source holds.
- Four or five of them
- Publish and maintain
More material about culture and values
Indistinguishable from every other employer, unverifiable, and containing nothing that can be lifted into an answer.
- Any number of them
- Adds volume, changes nothing
What changes when the owned properties report together
Labels rather than separate accounts
Each property you control carries a marker that behaves as a filter everywhere.
- A single sign-in covers all of them. More than thirty-five interfaces sit behind it, from placement tracking through to observing what assembled answers say about the company.
- A filter, once applied, stays applied. Narrow to one property and the narrowing survives into the figures, the task list and every file produced.
- Eleven services feeding one record. Material coming in from Google, from Analytics and from elsewhere lands in a single dataset instead of being duplicated across several.
- One Google authorisation rather than three. Mailbox, Search Console and Analytics are covered by a single grant, which is what makes the scattered-access problem go away.
The daily rate is one pool
Rarely the binding constraint at this scale, and worth knowing anyway.
- One thousand a day, and it belongs to the account. Everything held there draws on the same figure. Three properties divide it between them rather than each receiving it.
- Up to ten thousand in one batch. The list is taken in whole and then worked through against the daily limit, which puts ten thousand at roughly two working weeks.
- Two processing, twenty queued. Submit changes for several properties at once and either you set the sequence or the clock does.
- Three levels of nesting, a thousand sitemaps per batch. Comfortably enough for a main site and a careers section combined.
At the scale most employers operate, this rarely binds — a main site and a careers section together clear well inside a day. The reason to know the figures anyway is that they eliminate one explanation: if a page has been waiting weeks to appear, capacity is not the reason, and the investigation should move to the page itself. That is a much shorter search.
The consolidated Google grant deserves more credit than it gets, particularly in organisations where the careers domain was built by an external supplier. Access typically hangs off whichever account the supplier used, and the relationship may have ended two years ago. In ordinary operation nothing goes wrong. The moment a page disappears from the record or a warning arrives, that account turns out to be the one nobody can reach — and reconstructing access under time pressure is a far worse experience than arranging it in advance.
Two different jobs, two different approaches
| Group | Objective | Method |
|---|---|---|
| Properties you own | Answer questions nobody else can | Publish specific, dated, checkable facts |
| Profiles you can claim | Keep the basic details current | Claim, fill in, review twice a year |
| Platforms you cannot edit | Be outranked by your own pages | Nothing directly — write better pages |
| Listings nobody maintains | Stop them being the first result | Same as above, plus patience |
Recording that split somewhere the whole team can see it — inside the same overview that holds the coverage data — stops the next person spending a fortnight on the bottom two rows.
The third row is where most of the frustration lives and where the least can be done directly. It is also where the least needs to be done, provided the first row is handled properly. A page of yours stating specific facts about how a role works will outperform a generic platform profile over time, and that is the only mechanism available.
Patience deserves a mention because it is the part most often abandoned. A platform profile that has existed for six years does not get displaced in six weeks. What can be observed within a quarter is movement — your own page appearing where it did not before, or climbing relative to the profile. Judging the work against the position of the platform itself, rather than against your own trajectory, produces a conclusion of failure at every checkpoint until the very last one.
One data set, several readers
Two or three owned properties with different internal owners produce a reporting problem before anything else: marketing wants the commercial view, recruiting wants the candidate view, leadership wants both together, and all of it comes from the same underlying record. Separate outputs settle this without argument.
- Marketing sees the commercial half, once a month. Between fifty and two hundred rows on a screen is plenty — the view ends up filtered in any case.
- Recruiting, monthly, candidate queries only. Usually the first time anybody has shown them search data, and usually the most useful half hour of their month.
- Leadership, quarterly, both together. A handful of figures against the same quarter last year. Printed exports hold two hundred and fifty rows, well beyond what gets read.
- Analysis, on demand, everything. Export files reach ten thousand rows and drop straight into whatever is already running.
The second item is the one that changes something in most companies. Recruiting teams almost never see this data because nobody classified them as an audience for it, and the candidate half of the record is frequently the only current, unfiltered evidence available about how the organisation is perceived as an employer. Producing that view costs an hour once.
How often something is sent matters as much as what is in it. Anything landing on a team's desk works monthly, since each edition prompts somebody to do something. Anything travelling upward suits a three-month cycle: its purpose is different, and issuing it more frequently mainly manufactures conversation that leads nowhere. Force the two onto a single timetable and you get either pointless effort or numbers past their usefulness — with a two-person marketing operation, generally both at the same time. Set the outputs up once for each audience inside a shared environment and nobody has to build one by hand ever again.
Asking a question across the owned properties
Once there is more than one property to look after, the hour goes on getting somewhere rather than on thinking: which report, which filter, where somebody saved the previous comparison. Typing the question as an ordinary sentence takes that away entirely. What gets retrieved varies with the question — sometimes nothing at all, at most three blocks — while the twenty preceding turns of the exchange remain in play so that anything asked next still makes sense.
Here one particular question repays being asked on purpose: which candidate questions does the main site appear for, and which does the careers domain appear for? Where both appear for the same wording, they are competing; where neither appears, the page has not been written. That answer takes minutes inside one workspace and is effectively unobtainable from two separate accounts.
What several properties cost
Billing attaches to each domain, and only to properties you actually control — nothing here applies to a platform profile. Three owned properties on the lower tier with a single encyclopedic placement and the smallest network quantity come to 477 dollars a month and 5 724 across a year. A mixed arrangement with the main site on the upper tier runs to 868 monthly and 10 416 annually.
| Configuration | Components | Monthly | Twelve-month total |
|---|---|---|---|
| Three owned, lower tier | 3 × AutoSEO, 1 encyclopedic (10 $), 20 network (20 $) | 477 $ | 5 724 $ |
| Mixed | 1 × FullSEO, 2 × AutoSEO, 5 encyclopedic (50 $), 20 network (20 $) | 868 $ | 10 416 $ |
| Main site and careers only | 2 × AutoSEO | 298 $ | 3 576 $ |
Working out which properties earn a place on the invoice starts with knowing what each one can presently be found for — a measurement, and therefore a job for keyword research, not for whoever argues hardest at the meeting. Establishing that each of them is delivered and taken in correctly belongs to a technical review. Whether anybody has ever written the pages that would answer what applicants ask is a matter for content strategy. Handle all three from a single account and the properties become comparable, which they otherwise are not.
The twenty-turn ceiling is a sensible boundary rather than a restriction. Anything worth asking about two or three properties resolves within half a dozen exchanges; needing substantially more usually means the opening question was framed too broadly. Hitting the ceiling repeatedly is a signal to split the question, and two narrow ones arrive somewhere faster than one sprawling thread.
Where the limits actually are
It is worth stating plainly what consolidating owned properties will not achieve. It will not remove a review platform from the results, will not change what former employees wrote, and will not stop a job board profile from existing. What it does is make it possible to see, month by month, whether your own material is gaining ground on theirs.
That measurement is the point. Without it the argument inside the company runs on impressions and anecdote — somebody saw a bad review, somebody else heard the careers page is fine — and decisions get made on whoever spoke last. With it the question becomes ordinary: over two quarters, did the pages we control move up relative to the pages we do not? That question has an answer, and the answer costs fifteen minutes a month to maintain.
Bring the properties you control into one view
Questions from HR and marketing
Can we do anything about the review platforms?
Not directly, and effort spent there mostly goes to waste. What works is publishing material of your own that is specific enough to be preferred — figures, durations, dated statements about how things actually run. A generic platform profile loses to a page that answers a question properly, and that is the only mechanism available to you.
Should we claim old job board profiles?
Yes, where the platform offers a claim process. They were usually created by somebody who has since left and still describe the company as it was then. Reclaiming takes paperwork and a couple of weeks, and it is far easier done now than during a hiring push when somebody notices the details are wrong.
Does each domain get its own daily allowance?
No, they share it. The thousand addresses a day belong to the account, and every property inside it draws on the same pool. At the scale of a main site plus a careers section this is rarely the binding constraint, but it becomes one if a larger clean-up is running at the same time.
Do all properties need the same tier?
No, and usually they should not. Since billing follows the domain, tiers can be mixed freely. The upper tier belongs where somebody genuinely participates in choosing what to answer — normally the main site — with the rest below it. Across three properties that arrangement comes to 868 dollars a month.
Can recruiting and marketing see separate reports?
Yes, and they should. Labels act as filters in every view, so each team can receive an output containing only what concerns them while leadership keeps the combined picture. All of it comes from one record, which removes any dispute about whose numbers are correct.
How do we know whether this is working?
Run the same search twice a year — company name plus three role titles — and note whether the properties you control have moved up relative to the ones you do not. That comparison is the actual measure here, it takes ten minutes, and no report produces it automatically. Everything else is a leading indicator for it.
Professionelle SEO-Beratung für Ihr Unternehmen
Möchten Sie die Sichtbarkeit Ihrer Website verbessern? Unsere SEO-Experten analysieren Ihre Website und entwickeln eine maßgeschneiderte Strategie.
Kostenlose Erstberatung anfragen