What an SEO Agency Should Collect During Client Onboarding

Good SEO onboarding is less about sending a long questionnaire and more about collecting the information that prevents avoidable assumptions later. Small agencies need enough commercial, technical and editorial context to understand the website before recommending changes.

Clarify what the business actually wants from search

Ask which services, products or audiences matter and how website enquiries fit into the wider business. Broad goals such as “more traffic” are difficult to prioritise. Understanding what useful demand looks like gives later research and reporting a clearer frame.

Turn that conversation into a short operational brief. Which offerings can the client actually deliver today, which customer groups are suitable, and what enquiry would be considered useful rather than merely numerous? Ask how the customer typically discovers the business and which steps occur after contacting it. An agency cannot evaluate success simply by increasing search clicks if the website sends unsuitable people to an overstretched team. Equally, a narrow educational resource may be useful without generating an immediate sale. Record distinct definitions for search exposure, accepted enquiries, qualified opportunities and completed revenue rather than converting them into one imaginary metric.

Establish the reporting market, business constraints and decision horizon. A UK consultancy serving remote customers may not require dozens of city landing pages. A trade business limited to particular postcodes might need more careful coverage information. Ask what the company is willing to maintain, not only what keywords look popular. The outcome should be a written statement of the site's legitimate purpose and the questions the planned work must answer, approved by someone with authority over the offering.

Document the website's recent history

Record significant redesigns, migrations, domain changes, content removals and known technical problems. Historical context can explain unusual patterns and prevents the agency from treating every symptom as a new SEO issue.

Ask for a timeline of major website releases, hosting moves, URL structure changes, content imports and changes to analytics or consent handling. Record whether previous agencies created redirects, canonical rules, robots restrictions or automation that still runs. When a chart shows traffic changing near a reported algorithm update, the agency needs to know whether the business simultaneously removed a category from navigation. One timeline can turn an apparent search mystery into a reproducible deployment investigation.

Preserve original URLs, key landing-page roles and any available approved baseline data. Do not assume that a CMS export includes every public route or that a migrated article retains the same H1 as its stored record. Check representative actual addresses before making a plan. Google's site-move guidance describes URL inventories and relevant redirect mapping, but it cannot independently verify a particular client's migration or diagnose the cause of its historical traffic changes.

Arrange access deliberately

Identify the systems genuinely required for the agreed work, such as analytics, search performance data or the content management system. Use appropriate user accounts and permissions rather than casually sharing master credentials. Access should match responsibilities.

Create an access register naming the system, account owner, intended task, permission role, approval and removal condition. A consultant reviewing query performance may need reporting access without permission to publish articles or manage users. An engineer testing a staging deployment may need narrowly scoped technical access but no customer sales records. Verify that the authorised business owner controls the property before asking for additional privileges. Google's Search Console user and owner documentation distinguishes property owners from users with differing rights; there is no reason to grant owner status automatically to everyone who prepares an SEO report.

Handle personal data proportionately. The ICO's UK GDPR data-minimisation guidance explains why processing should be limited to what is necessary for the identified purpose, noting that its guidance is under review following legislative changes. An SEO agency should not request entire customer databases merely to understand a contact form's existence. Use approved test records, redacted examples and delegated access where sufficient. Never ask for passwords in ordinary onboarding documents, and record how credentials or delegated rights will be removed after the engagement.

Understand how content gets approved

Find out who can confirm technical facts, approve wording and make website changes. A sound recommendation can stall if nobody knows who owns the decision. This is particularly important where specialist or regulated subjects require careful review.

Identify separate decision makers for business facts, legal or regulated claims, editorial tone, technical implementation and final publication. The person who provides keyword research may not have authority to promise an emergency service or declare an office in a city. Establish who verifies credentials and customer examples and which claims cannot be published without supporting primary evidence. An illustrative image or fictional case can make copy vivid, but it must not be passed off as a real client result.

Agree a practical approval route, including the format of a review request, expected response owner, handling of conflicting comments and the rule for changing an approved page after it goes live. Document who can refuse an inaccurate statement. Treat a completed draft, an approved content record and a publicly tested page as separate states. Google encourages helpful, reliable content; that is an editorial principle rather than proof that any particular biography or testimonial is genuine.

Capture constraints before planning work

Legacy platforms, development schedules, brand requirements and internal resources can affect what is practical. Knowing these constraints early helps the agency propose work the client can actually implement rather than producing an idealised plan disconnected from operations.

Ask whether changes require scheduled releases, whether the website is maintained by an external supplier, and how long the client intends to retain its present platform. A proposed restructuring of URLs is a poor first step when a necessary product migration is already scheduled. Check whether the site uses shared article templates, caching or permissions that prevent direct public verification. An editor's ability to save a field does not establish that the public renderer will display it correctly.

Include a change-control agreement for urgent issues. A serious privacy exposure or broken enquiry route might take precedence over a planned content calendar, but its scope and approval still need to be recorded. Make the client aware of realistic dependencies such as engineering capacity, asset rights and access to original sources. Do not promise a fixed rank or a business uplift merely because a project plan contains a collection of SEO tasks.

Create a shared list of unresolved questions

Not everything will be known during onboarding. Keep uncertainties visible and assign follow-up owners instead of filling gaps with assumptions. A short unresolved-questions log can prevent early guesses from becoming embedded in strategy.

Mark each issue with its practical consequence: can content research proceed without this detail, does it block a production write, or does it affect only reporting? A missing service-area approval blocks truthful local claims. Unavailable analytics exports may limit a historical assessment without preventing a technical audit of public URLs. A broken image licence link can block use of that asset but need not justify inventing permission. Assign the next evidence source, owner and expected decision, and review the register regularly so uncertainties do not silently turn into agreed facts.

Finish onboarding by checking that the agency and the client can both explain the site's purpose, what work is authorised, who approves facts, how access is managed and what counts as a completed repair. A useful handover may be quite short, but it should prevent the most expensive misunderstandings: wrong service claims, uncontrolled accounts, a mistaken migration plan and reporting that confuses clicks with qualified customers. These are the questions worth collecting before the first recommendation becomes an implementation task.