Why local SEO service standards need a named source behind every rule

What to take away

A Manchester agency that puts "average local search growth of 12%" in a proposal is using a worked example, so it has to name where the figure 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 treatmenthealth 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

A written standard is the agency's own rulebook. No professional body accredits local SEO service standards in the UK, so the document has to stand on its own: where each piece of data comes from, who verifies it, what a client report may claim, and who signs off. Those four areas are what the rest of this page sets out.

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.

Target vs standard

Target

What it is: wanted number
Example: ten extra enquiries
Movement: moves with market
Test: result hoped for

Standard

What it is: controlled process
Example: source and date
Movement: fixed until written change
Test: pass or fail check

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 researcher pulls a statistic, the check applies before the number reaches a client deck. Name the gatekeepers: a research analyst sources the figure, a reviewer confirms the page still says what the report claims, the delivery lead owns the register, and the account lead signs off anything a client sees. Our own Local SEO: operations and delivery guide for 2027 sets out that chain from brief to handover and where each check belongs.

Most agencies run a short chain: research, drafting, review, sign-off and handover. A source register only works when one named person owns it, which is why role design matters as much as process. Our own 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

A register is one shared document, not a folder of bookmarks. Every entry follows the same format, so any reviewer can open it, read the claim and the publisher, and confirm the check date without asking anyone.

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.

Source register entry fields

Claim stated in one short line
Publisher named
Full URL recorded
Date page last opened
Named owner accountable

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.

A local SEO entry works the same way. Claim: "the client's profile appears in the local pack for the main service term"; publisher: Google Business Profile insights; owner: the delivery lead. A visibility claim points to Google Search Console performance data, a claim about review handling points to the review platform's own policy page, and a rule about what lifts local rankings points to Google's guidance on improving your local ranking. Any ranking claim records the search term and the location used, because "local" means nothing without them.

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

"Compliance" here means anything a client page states about the law, safety or personal data. Each of those topics has a named public source in the UK, and the standard is to quote it rather than to paraphrase it from memory.

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 about them, the agency may need to help. The right of access sits in Article 15 of the UK GDPR, as applied by the Data Protection Act 2018, and 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.

Where an agency decides how client enquiry data is used, it is a controller in its own right, so it must register with the ICO and pay the data protection fee. The register entry for that rule names the ICO page, the date it was last checked and the person who confirmed it.

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 registerthe shared list of claims, publishers, URLS and check dates behind client work.
Check datethe day someone last opened the source page and confirmed the wording.
Ownerthe named person accountable for a claim staying accurate.
Standarda process rule the agency controls, as opposed to a result it hopes for.
Claimany factual statement in a report, audit or page that a reader could verify.

Common questions

These are the questions agencies ask most often about keeping a register honest.

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.