How white label SEO software should work for an agency
Agencies · 5 min read · Updated
White label SEO software is only genuinely white label when a client can reach it on your own domain, sees your name and colours rather than the vendor's, receives reports with no vendor branding anywhere in them, and never encounters a login or an email that names the software. Anything short of that is a rebranded logo in the corner, which clients notice. The commercial question underneath is simpler: the software has to cost you less per client than the reporting time it removes, and for most agencies the reporting time is the larger number by some distance.
What white label has to cover
| Surface | What proper white label means | The common shortfall |
|---|---|---|
| Domain | Clients reach it at reports.youragency.co.uk, with a valid certificate you did not have to buy. | A vendor subdomain: youragency.vendorname.com. |
| Branding | Your logo, your colours, your product name throughout the interface. | Your logo in the header, the vendor's name in every button, email and page title. |
| Client portals | A link you send a client that shows their site and nothing else, with no account to create. | The client must register, and the registration email is from the vendor. |
| Reports | Exports carrying your branding and no vendor marks at all. | A footer credit that cannot be removed. |
| Permissions | Each client sees only their own sites; your staff see the ones assigned to them. | One shared login for everything, which is how one client ends up seeing another's data. |
The test: could a client use this for six months and not learn the vendor's name? If the answer is no, price it as a tool you use, not as a service you sell.
The margin arithmetic
An agency managing fifteen retained clients typically spends between two and four hours a month per client on data gathering, report assembly and the meeting that follows. At £60 an hour internal cost, fifteen clients is somewhere between £1,800 and £3,600 a month of time, most of which is assembly rather than thinking.
Software that reduces assembly to reviewing a generated report pays for itself at almost any realistic price, provided two things are true: the generated report is actually good enough to send, and the time saved is redeployed into work the client pays for rather than absorbed.
- Count the hours honestly, including the ones spent chasing analytics access and rebuilding last month's spreadsheet.
- Price the software per client, not as a lump — a £199 platform across fifteen clients is £13 a client.
- Compare against what you already pay for rank tracking, crawling and reporting separately, which is usually three subscriptions.
- Decide whether you are reselling it as a line item or absorbing it into the retainer. Both work; mixing them by client does not.
Questions to ask a vendor before you put your name on it
- Can I use my own domain, and who issues the certificate?
- Is the vendor's name visible anywhere a client can reach — emails, page titles, export footers, the sign-in page?
- Can a client view their data without creating an account, and if a portal link leaks, what does it expose and can I revoke it?
- How are per-client permissions enforced — in the interface, or on the server? Only one of those answers is a real one.
- If I leave, what can I export, and in what format?
- When the software makes a change to a client's site, who is recorded as having approved it, and can that record be altered afterwards?
- What does it refuse to do automatically, and why? A vendor with no such list has not thought about it.
That last pair matters more than it sounds. If you are presenting the output as your agency's work, the audit trail is your defence when a client asks why their homepage title changed, and "the software did it" is not one.
How this works in SEOGrowPilot
Agency plans include a custom domain, configurable branding, and client portals reached by a link rather than a registration. Portals are scoped to one client's websites and the scoping is enforced server-side — the interface not showing something is never what keeps it hidden.
Portal links are treated as bearer credentials, which has a few visible consequences: they can be revoked, they are excluded from search engines by our own robots rules, and what they expose is deliberately narrower than what your staff see.
Every applied change records who approved it, the note they wrote, the state of the page before it, and the revenue it was forecast to produce — in a log that is append-only and hash-chained, so it cannot be tidied up later. That is the part you would want in front of you in an awkward client meeting.