How to Choose an SEO Agency in the UK

A useful proposal should show evidence and prioritisation. Ask the agency to explain a specific technical or content issue on your site, its impact and the proposed response. This tests whether the plan is based on your business rather than a generic package.

Keep access to analytics, business profiles and the content produced for the site. Agree deliverables and reporting, including relevant enquiries or sales. Avoid accepting a ranking promise as a substitute for a defined programme of work and a way to evaluate progress.

Describe the kind of customer you want the website to help and the work the business actually offers. A hypothetical window-restoration firm may need better enquiries about repair assessments within its real service area. That is more specific than asking an agency for more traffic. Explain what makes an enquiry suitable, which work is outside scope and who handles the next step.

Give every candidate the same brief, including any practical limits on staff time, available photographs and website development. Ask what information they would need before estimating the work. Their questions should help clarify the problem. Keep a list of assumptions that remain unverified so a confident presentation does not turn a tentative idea about your customers into an accepted business fact.

Gather the reporting you already have and identify its dates, definitions and gaps. Distinguish people searching for your business name from people looking for the service more generally. Keep website visits separate from enquiries and accepted work. If a report cannot establish where an enquiry came from, leave that source uncertain. Do not manufacture a starting figure simply to make a proposal look complete.

For the restoration example, the useful baseline might describe the pages customers use, the questions received and whether the team can respond to the requested work. Ask the agency to explain which part of that picture its proposed work could affect. A recorded baseline gives future conversations a reference point and helps prevent a change in reporting definitions from being mistaken for business growth.

Choose a specific proposed improvement and ask the supplier to walk you through it. If it says that a service page is unclear, identify the customer question that remains unanswered. Ask what information is needed, who can verify it and how the changed page would help the visitor. Separate an observed problem from an assumption that still needs investigation.

A useful demonstration might compare the existing repair-enquiry instructions with a clearer explanation of the photographs and measurements an assessor needs. It should not invent a customer outcome or promise an appointment. Write down the expected benefit and the check that would confirm the page works. You then have a concrete item to compare across proposals rather than several differently worded claims about optimisation.

Ask the agency to explain its role in an example relevant to your situation. Identify what changed, when the work happened and which other changes could have influenced the outcome. A redesigned booking process, a wider service area or a larger advertising budget may be important context. Respect confidential client information; a useful explanation does not require another company’s private account credentials.

If references are available, ask practical questions about communication, implementation and the usefulness of reports. Keep a distinction between the agency’s description, a client’s account and evidence you have personally seen. One successful example does not establish the likely result for your website. Use it to understand how the supplier works and whether its experience matches the problem you need help solving.

Create a short comparison sheet for each proposal. Record the work included, the expected output, who supplies information, who implements changes and how completion will be reviewed. A content recommendation and a finished, checked page are different deliverables. A technical audit may identify work that your web developer must still estimate. Ask the supplier to make those boundaries clear.

Also record decisions that can delay progress. Someone may need to approve service descriptions, locate original photographs or confirm access to the content-management system. Allocate those responsibilities before treating a timetable as realistic. This comparison helps you see whether two prices cover the same work and whether the business has the capacity to support the proposed programme without neglecting normal customer enquiries.

Request a sample brief showing the reader’s question, the existing page it relates to and the information needed to answer it well. For the restoration business, that might involve explaining assessment limits, showing genuine work with appropriate permission and clarifying how customers request a visit. Ask whether the existing page can be improved before approving another article aimed at a very similar search.

Agree who checks facts, dates, images and translations. Google’s guidance on generative AI content emphasises value and accuracy; large-scale production without useful added information can be a problem. An editorial length target can help scope the work, but it is not evidence that every paragraph earns its place. Ask the reviewer to identify the decision each section helps the reader make.

For a local service, ask how the proposal handles the facts customers need before contacting you. These may include the actual service area, appointment arrangements, the correct contact route and evidence relevant to the work. Keep those facts aligned with your website and appropriate business profiles. Do not approve an invented office or an expanded service claim simply because it could target another location.

Google’s business representation guidelines require an accurate real-world identity and appropriate address or service-area information. Check which proposed changes concern your website and which concern a separate business profile. A directory listing is another publishing surface, not automatic verification of a Google profile. Give the supplier approved facts and identify who must confirm a change before it appears in public.

Ask for named tasks when a proposal mentions Bing, assistants or AI visibility. These could include checking public-page access, source clarity, canonical URLs, sitemap coverage or the accuracy of business facts. Ask what evidence prompted each task. A new label on an invoice does not tell you whether the work is relevant to your website or who will implement it.

Bing’s AI Performance reporting distinguishes observed citations from ranking or placement within an answer. Keep that distinction when discussing results. Ask the agency to separate reported citations, website visits and suitable enquiries, with the actual dates and measurement limits. If a service does not provide enough reporting to attribute an outcome, the report should say so instead of assigning every improvement to an assistant.

Google’s hiring guidance recommends read-only Search Console access during an initial audit. Treat access as a defined part of the engagement. List the systems involved and the role needed for each stage. Keep business ownership with the appropriate people and use the service’s supported invitation process. A supplier should be able to explain why it needs a permission before you provide it.

For implementation, identify who can publish, alter redirects or change integrations, and how the business will review that work. Keep a record of permissions granted and the contact responsible for removing them at the end. If the scope expands to another system, review that separately. Do not assume that permission to read a report includes authority to rewrite pages, send messages or change account settings.

Ask the supplier to identify what its current fee covers, what requires a separate estimate and how additional work will be agreed. Clarify whether reporting, writing, development and third-party subscriptions are included. Keep the scope with the price so you can compare proposals fairly. This guide does not offer a universal agency rate because the work and commercial arrangements need to be specified.

Before starting, ask what the business receives if the engagement ends: content, reports, change records, access information and any agreed training. Read the actual contract and obtain appropriate advice on terms you do not understand. Record renewal, notice and transfer arrangements rather than relying on a sales conversation. A clear handover plan helps your team maintain improvements and investigate a later problem without reconstructing the whole project.

Ask for a report that connects completed work with the evidence available. It should identify the pages changed, the checks performed and the questions that remain open. Keep equivalent date ranges and reporting definitions where possible. If availability, demand or the contact process changed during the period, include that context rather than presenting a chart as a complete explanation of the outcome.

Use the report to decide what happens next. A working page with an unclear enquiry step suggests a different task from a page that cannot be reached. A rise in unsuitable enquiries may need a clearer service explanation. Agree a review process that allows the plan to change when the evidence does not support the expected benefit. More completed tasks do not automatically establish more useful customer outcomes.

Before a substantial website release, ask how the supplier will test the changed pages and the main customer journey. Useful checks include readable content, working contact links, appropriate canonical URLs and consistency between visible facts and structured data. Keep the test result tied to the actual version being published. A screenshot of an earlier design is not confirmation that the final page works.

Keep the previous version and a concise record of the changes. Agree who responds if a release breaks a form, removes useful information or changes an established URL unexpectedly. Google’s starter guide describes SEO as helping search engines understand content and helping users make decisions, with no automatic first-place shortcut. Judge the supplier by explainable work and verified outcomes, while treating fixed ranking promises as a reason to investigate further.