SEO freelancer contracts: scope, access and exit
What to put in an SEO freelancer contract: a scope you can check, access that stays yours, continuity when one person is unavailable, and a clean exit.
By Roozbeh Nazari · CEO
Hiring an SEO freelancer is often the fastest way to get experienced help without the overhead of an agency. You work directly with the person doing the work, decisions are quick and the cost structure is usually simple. The same features create specific risks. One person means one point of failure: if they fall ill, take on too much work or move on, the project can stall. Tools, logins and documents may sit in their personal accounts. And many freelance agreements are a short email rather than a contract. This guide covers the clauses that matter most when you work with a freelancer: scope, access, continuity and exit. It focuses on what is different about a single-person engagement, rather than repeating general consulting terms.
Why freelance SEO needs its own contract terms
Agency contracts assume a team. There is an account manager, a backup specialist and a company that outlives any individual. With freelance SEO, the contract has to cover what the team structure would otherwise absorb. Who covers if the freelancer is away for three weeks? Can they hand parts of the work to someone else? Whose software licences produce your reports? What happens to half-finished work if either side ends the relationship? None of these questions implies distrust. They simply make the arrangement durable, which protects the freelancer as much as the client.
If you are still weighing a freelancer against an agency or a consultant, our guide to SEO consulting contracts, KPIs and exit clauses covers the general terms. The points below add what is specific to working with one person.
Scope: define deliverables, not hours alone
Many freelance arrangements start as "ten hours a month of SEO". That is easy to agree and hard to evaluate. A better scope lists the deliverables and the decisions they support. For example:
- A technical audit with a prioritised fix list, each item linked to the page type or template it affects.
- A fixed number of content briefs or page optimisations per month, with an agreed format.
- A monthly report covering work completed, changes shipped, and the metrics you agreed to track.
- A defined amount of time for questions, calls and reviews of work done by your developers or writers.
Write down what is out of scope as well: link buying, for instance, or development work the freelancer is not expected to carry out. If the freelancer will recommend changes that your developers implement, say so, and agree how recommendations are handed over. Clarity here prevents the most common dispute, which is not about quality but about expectations.
Access: your accounts, their user rights
A freelancer needs access to do the work, but ownership should stay with you. Create properties and accounts under your company's own login, then add the freelancer as a user. In Search Console, the owner role can manage users and settings, while full and restricted users have narrower rights; a freelancer rarely needs to be an owner. Google's guidance on hiring an SEO even suggests giving read-only Search Console access at the start of an engagement. In Google Ads, access levels range from email-only and read-only up to standard and admin, so you can match the level to the task and raise it only when needed.
Apply the same principle to analytics, the CMS, tag management and any rank tracking or crawling tools. If the freelancer uses their own tool subscriptions, agree in the contract that you will receive exports of the data they collect for you, in a usable format, while the engagement runs and when it ends. Keep a short access register listing each system, the freelancer's role and the date access was granted.
Continuity when you depend on one person
The biggest structural risk with a single SEO freelancer is availability. A contract can reduce it with a few simple clauses:
- Notice of planned absences, with an agreed minimum period, so you can plan around holidays or other commitments.
- A named backup or a clear statement that there is none, so you know what to expect during longer absences.
- A rule on subcontracting: whether the freelancer may use other people, whether you must approve them in advance, and that the same confidentiality and access rules apply to them.
- Working documentation: a shared folder with the audit, the priority list, a change log and notes on decisions, kept up to date as part of the service rather than produced only at the end.
Good documentation also makes the freelancer more effective. When a new developer joins your team or a question comes up months later, the reasoning is already written down.
Exit: how the engagement ends
Every contract should describe a clean exit, whoever initiates it. Agree a notice period that gives both sides time to wrap up. List what will be handed over: documents, data exports, briefs, reports and any assets created for you. State that the freelancer's user access will be removed on the last day and who is responsible for doing it. Clarify ownership of the work product, and whether the freelancer may mention your company as a client. Finally, agree how unfinished work is handled: completed and invoiced, paused and documented, or handed to your team.
Be wary of any promise that sounds like a guarantee. Google's guidance is clear that no one can guarantee a top ranking, and a freelancer who commits to one is either misunderstanding the work or overselling it. A trustworthy freelancer commits to a method, a timeline for deliverables and honest reporting instead.
If you would rather compare this with a team-based model, see how our services are structured, or contact us to talk through which setup fits your situation.