SEO Freelancer Hiring Brief Template

SEO Freelancer Hiring Brief (fill-in)

When to use: One row per workstream with the business objective, skill need, least-privilege access, deliverables, paid test task and owner, plus a completion check.

SEO freelancer hiring brief

One brief, five fields, one row per workstream. Fill it before you post the job, so every candidate answers the same question.

Business: [company + site URL] - Hiring owner: [name] - Brief date: [YYYY-MM-DD] - Start date wanted: [date]

Brief detail (fill for every row)

• Why now: [what changed: traffic drop, new site, new market, no one in-house]
• Baseline: [current clicks, leads or rankings, with source and date range]
• Out of scope: [what this freelancer will not touch]
• Proof to request: [past work that matches this skill need]
• Access window: [start date] to [revoke date], granted by [name]
• Acceptance rule: [how you decide a deliverable is done]
• Test task pay and limit: [fixed fee + hour cap], paid even if you do not hire
• Budget range and term: [project or monthly + review date]

Next action

• Hiring owner: [name] - task: confirm the objective and baseline with whoever owns revenue by [date]
• Access owner: [name] - task: prepare invites at the roles listed, not shared passwords, by [date]
• Reviewer: [name] - task: score test tasks against the rubric within [N] working days
• Finance: [name] - task: pay every completed test task by [date]

Completion check

• Every row has one business objective with a metric, a baseline and a date.
• The skill need names one specialism, not "general SEO".
• Each access line names a system, a role below owner or admin, and a revoke date.
• Every deliverable has a format and an acceptance rule.
• The test task has a fee, an hour cap and a scoring rubric written before anyone applies.
• Each row has a named owner.

Skill Need Picker

When to use: Match your problem to one SEO specialism, the proof to ask for and a test task that fits it.

Skill need picker

Hire for the problem you have, not for a job title. Pick one main skill per brief. A second skill can be a nice-to-have.

Questions before you pick

• What is the one result that would make this hire worth it? [result]
• Who will make the changes the freelancer recommends? [developer / writer / freelancer]
• Is this a one-off project or ongoing work? [project / monthly]

Not sure a freelancer is the right fit at all? Read SEO agency vs freelancer vs in-house before you post the brief.

Before you write the brief, run a free Website Audit and a Keyword Research check. The results show which skill you actually need.

Least-Privilege Access Plan

When to use: Which role to grant in Search Console, GA4, the CMS and SEO tools, what never to grant, and when to revoke it.

Least-privilege access plan

Give the lowest role that lets the freelancer do the task. Invite their own email. Never share your login. Set a revoke date on day one.

Access rules

• Read first, write later. Start with view-only access. Raise it after the test task, for a named reason.
• One account per person. Invites to their email make removal clean and leave an audit trail.
• Test tasks need no live access. Send exports, screenshots or a short URL list instead.
• Offboarding is part of the brief. On the revoke date, remove every invite and record it.

Roles checked on Google's own help pages on 15 November 2026. Role names can change, so open them again before you send invites.

Deliverables and Acceptance Sheet

When to use: Name each deliverable, its format, due date and the rule that decides it is done.

Deliverables and acceptance

Name each deliverable, its format and the rule that says it is done. Vague deliverables are hard to sign off and easy to argue about.

Write deliverables that can be checked

• Say what you get, not what they do. "A prioritised fix list" beats "technical SEO support".
• Name the file type and where it lives, so nothing sits in a private inbox.
• Say who implements. A recommendation and a shipped change are different deliverables.
• State that you own the work you paid for, including test task output.

For monthly work, give the freelancer the Monthly SEO Report Template as the report format.

Paid Test Task Brief and Rubric

When to use: A small paid task with a time cap, fixed fee and a five-point scoring rubric written before anyone applies.

Paid test task brief

A short, paid task shows how someone thinks. Keep it small, pay for it, and score it against a rubric you wrote first.

Scoring rubric (score 1 to 3)

Test task rules

• Same task, same material, same deadline for every candidate.
• Do not use test tasks to get free work done. Pay for every one you receive.
• Score before you look at rates, so price does not colour quality.

Want a quick benchmark before scoring? Run your domain through Competitor Analysis or the AI Visibility Checker yourself, so you know what a good answer looks like.

Spreadsheet Header (CSV)

When to use: A paste-ready header row and allowed values to run the brief and candidate scoring in Google Sheets or Excel.

Paste-ready spreadsheet header

Paste this row into cell A1 of Google Sheets or Excel, then split text to columns by comma. One row per workstream in the brief.

brief_date,business,site_url,hiring_owner,business_objective,metric,baseline,baseline_source,target_date,skill_need,out_of_scope,proof_requested,access_system,access_role,access_restrictions,access_granted_by,access_revoke_date,deliverable,deliverable_format,acceptance_rule,deliverable_due,test_task,test_fee,test_hour_cap,test_deadline,rubric_score,owner,next_action,status,notes

Allowed values

• skill_need: technical, content, keyword_strategy, local, links, geo
• access_role: none, export_only, gsc_restricted, gsc_full, ga4_viewer, ga4_analyst, cms_limited
• access_restrictions: none, no_revenue, no_cost, no_revenue_no_cost
• status: draft, posted, testing, hired, closed

Sheet tips

• Highlight rows with an empty access_revoke_date. Those invites will outlive the project.
• Highlight rows where acceptance_rule is empty. Those deliverables cannot be signed off.
• Sort candidates by rubric_score before you open their rates.

Worked Example (fictional Wenlowby tea shop)

When to use: A filled brief for an invented online tea shop hiring for content and technical SEO, with access, test tasks and owners.

Worked example: Wenlowby loose-leaf tea

Example only. Wenlowby is an invented online tea shop. The brand, domain, people, numbers and dates are made up to show a filled-in brief.

Business: Wenlowby, wenlowby.example - Hiring owner: founder - Brief date: 2026-11-15 - Start date wanted: 2026-12-01

Brief detail

• Why now: sales from search fell after the theme change in September.
• Out of scope: link building, paid ads, the wholesale site.
• Access window: 2026-12-01 to 2027-03-31, invites sent by the founder, removed on the revoke date.
• Acceptance rule: each brief names one target query, one URL and the questions the page must answer.

Next action

• Founder - task: send the test task to 3 shortlisted freelancers by 2026-11-20.
• Developer - task: export the 10 URLs and the Search Console query report by 2026-11-18.
• Founder - task: score all tasks with the rubric, then pay every candidate, by 2026-11-27.

Completion check

• Both rows have a metric, a baseline and a date.
• No access line grants owner or admin, and every invite has a revoke date.
• Test tasks used exports, not live accounts.
• The rubric was written before the first application arrived.

Why this works

• Two separate skill needs became two rows, so the founder did not hire one generalist for both.
• Candidates scored on the same exports, so the comparison was fair.
• The revoke date was set before access was granted, so nothing lingered after the project.

Need help scoping the brief or rather hand the work to a team? Book a free consultation with Anatolii Ulitovskyi, or see our SEO and GEO services.