Write a small, specific assignment first
Start with your business goal, website, markets and the help already available. “We want more traffic” leaves too much open. “We need more relevant inquiries for these three services, and our developer can implement technical changes” gives a consultant something useful to respond to.
Ask for a proposed first phase rather than a free full audit. A useful response explains what needs checking, the access required, who will make changes and how priorities will be agreed. Read the audit deliverables guide if the proposal uses “audit” without defining it.
Check the contribution behind the result
For each example, ask what the person personally did, when the work happened and what else changed. A chart can show progress without proving that one particular edit caused it.
Not every experienced consultant can publish historical client analytics. Confidentiality can be a valid reason. Look for other verifiable evidence: a public project record, a clear implementation example, owned-site work with honest measurement notes, or a reference shared with permission.
On this site, Kliksa is an agency project with a public award record; the publisher projects are websites I own. They are different types of evidence, not interchangeable client case studies.
Use the same questions for each proposal
| Ask | A useful answer | Follow up if |
|---|---|---|
| What happens first? | Named checks and a reason for their order | Every site gets the same task list |
| Who publishes the changes? | A clear division of responsibility | “Optimization” has no named owner |
| What will I receive? | Findings, edits, decisions and verification | Only a score or ranking screenshot is offered |
| How will we communicate? | An agreed update format and contact route | The process depends on constant chasing |
| What counts as progress? | Relevant search visibility and business outcomes, with limitations | A position or revenue figure is guaranteed |
This is a comparison checklist, not a numerical rating of providers. A strong answer still needs to fit your team and budget.
Keep ownership and access sensible
Keep control of your domain, website and analytics accounts. For an initial review, give only the access needed; read access is often enough. Publishing permissions can follow once responsibilities and approval steps are agreed.
Also ask how changes are recorded, how backups are handled and what happens when the engagement ends. You should be able to understand what changed without reverse-engineering your own website.
Choose a manageable starting scope
An agreed first phase can cover a priority page group, an audit with implementation planning, or a defined set of fixes. It should be paid, bounded and useful even if you do not continue.
Compare consultant and agency arrangements and pricing models separately. If you would like my help, send your website and goal through the project form. We can agree the work in writing; an introductory call is not required.
Further reading: Google’s guidance on hiring an SEO.