Operations
Part of One named owner is what keeps local SEO operations honest
Why local SEO service standards need a named source behind every rule
How agencies set local SEO service standards with traceable data: source registers, verification dates and the compliance rules that back client claims in England.
What to take away
- A Manchester agency quoting "average local search growth of 12%" in a client proposal has to name where 12% came from, and when it was published.
- Local SEO service standards are the written rules a team applies to its own data, not a promise about rankings.
- Every figure in a client report needs a source, a publication date and a named owner.
- Compliance content needs the same treatment: health and safety claims, data requests and security guidance all come from named public sources.
- Review the source register quarterly, because rules and datasets change.
What service standards actually cover
The difference between a standard and a target
A target is a number the client wants, such as ten extra enquiries a month. A standard is the process the agency controls, such as "every reported figure carries a source and a date". Targets move with the market. Standards should not move at all without a written change.
Write standards as checks a reviewer can pass or fail. "We cite sources" fails that test. "Every figure in a monthly report shows the publisher, the page and the date we last checked it" passes.
Where standards sit in the delivery chain
Standards belong at the point where work leaves the person who did it. If a strategist pulls a statistic, the standard applies before the number reaches a client deck. Our Local SEO: operations and delivery guide for 2027 sets out the wider chain, from brief to handover, and shows where each check belongs.
For most agencies the chain is short: research, drafting, review, publication. A source register only works if one person owns it, which is why role design matters as much as process. The Local SEO team roles: selection guide for England explains how to split research, review and sign-off without creating gaps.
Building a source register that holds up
What goes in the record
Each entry needs four fields: the claim, the publisher, the full URL, and the date someone last opened the page. Add a fifth field for the owner. A claim without an owner is the first thing to rot.
Keep entries short. "England business population, ONS, checked 4 August 2026" is enough. Long notes get skipped, and skipped notes get copied into reports unchecked.
Checking sources before reuse
Reopen the page before you reuse the figure. Government guidance is revised without fanfare, and a statistic that was accurate in 2024 may have been superseded. If the page has moved, update the URL or drop the claim.
Where an agency advises clients on security or innovation funding, the business innovation, protection and cyber security guidance is a sensible starting point for public-sector wording. It is a GOV.UK browse page, so it stays current without you chasing individual documents.
Compliance claims in client content
Data requests and client customer data
Local SEO work often touches enquiry forms and review platforms, which means personal data. If a client receives a request from someone asking what data is held, the agency may need to help. The ICO's guidance on subject access request obligations sets out the one-month response window and the limits on what can be withheld.
Put that in the standard: who receives the request, who confirms identity, and who signs the reply. A shared inbox is not an owner.
Safety and premises content
Many local clients are trades, salons or workshops, and their pages carry safety statements. The HSE's health and safety basics for your business is a reasonable public reference for that wording, and it keeps the agency out of giving safety advice it is not qualified to give.
Standards here are simple: quote the source, link it, and date the check. If the client wants stronger wording, the client's insurer or competent adviser signs it off.
Glossary
- Source register: the shared list of claims, publishers, URLS and check dates behind client work.
- Check date: the day someone last opened the source page and confirmed the wording.
- Owner: the named person accountable for a claim staying accurate.
- Standard: a process rule the agency controls, as opposed to a result it hopes for.
- Claim: any factual statement in a report, audit or page that a reader could verify.
Common questions
How often should a source register be reviewed?
Quarterly is workable for most agencies, with an immediate check whenever a client challenges a figure. Rules and datasets change between reviews, so treat the check date as the trigger.
Does every figure need a public source?
No. Illustrative examples are fine if labelled as such, for example "a team paying £400 a month for tools". Anything presented as a market fact needs a named publisher.
Who owns the register in a small agency?
One named person, usually the delivery lead, even if others add entries. Shared ownership without a name is the most common reason registers go stale.
What happens when a source disappears?
Remove the claim or replace the source before the next report. A dead link in a client deck undermines every other number in it.
