If you are choosing between an SEO specialist and a web developer, start with the decision your website needs. An SEO specialist can investigate search demand, page purpose and visibility. A developer can change how the website works. Many projects need both capabilities, with someone clearly responsible for the handover and checks.
For a UK business owner, the useful purchase is a defined piece of work: understand the cause, agree the change, implement it and verify the result. A job title alone does not tell you which of those steps a supplier will deliver.
Separate the responsibilities before asking for a quote
Google lists several services an SEO may provide, including content and structure reviews, keyword research and technical advice. Its guidance on hiring an SEO also recommends asking about methods, communication and measurement. Those services can overlap with development; ask about the person's actual capabilities.
Use this responsibility matrix as a starting agreement. The suggested lead is a practical allocation, not a rule about professional titles.
| Website problem | Work to commission | Who usually needs to be involved |
|---|---|---|
| A service page is missing from Google | Establish its actual index status and intended purpose before selecting a repair | SEO reviewer, developer and business owner |
| Visitors land on a page for the wrong service | Compare the search task with the offer and choose the appropriate destination | SEO reviewer and owner; developer if structure changes |
| The wrong URL is being treated as the preferred version | Reconcile page purpose, duplicate versions and technical signals | SEO reviewer defines the intended relationship; developer implements it |
| Important content appears only after an interaction | Investigate what is delivered and rendered on the affected template | Developer, with SEO verification |
| A report counts contact-button clicks as enquiries | Define the event and reconcile it with real received messages | Measurement specialist, developer and owner |
| A contact form reports success but no message is received | Trace the submission, saved record and configured notification route | Developer or maintainer; staff confirm receipt |
The owner supplies accurate services, coverage and business priorities. The specialist explains the evidence and recommended decision. The implementer identifies the relevant code, CMS or provider setting. An agreed reviewer checks the finished work.
One competent person can cover several roles. The responsibility still needs to be explicit.
Establish whether the next step is investigation or implementation
If the cause is unknown, request a bounded investigation. Give the supplier the affected URLs, what a customer is trying to do and the evidence you already have. Ask what information is missing before agreeing a repair.
If a supported finding already exists, show it to the proposed implementer. Ask whether they can reproduce it, whether they have the appropriate platform experience and what else the change could affect.
For example, a green live URL test and the indexed report describe different things. Google's URL Inspection documentation distinguishes current indexability testing from stored indexed information. A useful brief records which result was observed instead of promising to fix an unspecified “Google problem”.
Our SEO audit deliverables guide helps you assess a report before commissioning its recommendations. For budgeting, use the separate UK small-business SEO cost guide.
A completed example of a shared handover
Consider a fictional Birmingham decorating business. Its interior-painting page has a distinct service, but a copied template points the canonical preference at a general services page. The following is an illustrative commissioning record, not an observed customer incident or a promised ranking outcome.
| Handover field | Completed example |
|---|---|
| Business decision | Keep the interior-painting page as a separate service destination because it explains that particular job |
| Evidence to attach | Exact page pair, dated response and HTML records, plus available indexed information; mark missing evidence as unknown |
| SEO responsibility | Explain why the two pages serve different customer tasks and specify the intended URL relationship |
| Developer responsibility | Locate the template source, correct the affected preference and check other pages using that template |
| Owner responsibility | Confirm service facts, area covered and the intended enquiry route |
| Acceptance | The released page has the agreed metadata, working navigation and relevant service information; private pages remain protected |
| Later search review | Record Google's subsequent indexed and selected-version information separately from technical completion |
That record gives each supplier a practical contribution. It also prevents an approved content decision from being quietly replaced by whichever setting is easiest to change.
For a broader investigation, begin with the existing small-business SEO audit checklist. Once the decision is accepted, turn it into a testable developer brief.
Compare suppliers using one common brief
Send each potential supplier the same short description: the website, main service, UK area served, affected pages, observed symptom and desired customer action. Include an existing report if you have one. Keep passwords out of the enquiry.
Ask who will diagnose the issue, who will make changes, what access is needed and who will approve release. Request the proposed deliverables, exclusions, dependencies and method of verification. For a quotation, clarify whether content work, development and later search review are included or separate.
A useful proposal explains what can be checked when the work is delivered and what needs later observation. Receiving more enquiries remains a business outcome to measure after implementation, rather than a substitute for a clear scope.
Discuss the website work you actually need
Nolixia's current services include SEO foundations, website engineering and ongoing improvements. If your project involves page structure, metadata, rendering or a website fault, send us the relevant URLs and your existing findings. Explain what the customer should be able to do, and we can discuss an appropriate scope for the implementation work.
