SEO Virtual Assistant Job Description Template

An SEO job description should read like a real job

When content briefs is part of the SEO scope, candidates should be able to picture the week. Lead with the outcome, then explain the recurring work, hours, tools, communication expectations, and boundaries. Avoid opening with a long company story or a list of personality adjectives.

For SEO hiring, the responsibilities should reflect keyword research, on-page optimization, internal linking, content briefs, Google Search Console monitoring, and technical audit support. If a requirement does not change who you would interview, remove it.

Start with the outcome, not “we need a rockstar”

In an SEO handoff involving Google Search Console monitoring, write one or two sentences explaining why the role exists and what will be better when it is filled. A useful outcome sounds like “keep the intake queue current and every follow-up dated,” not “support our dynamic team.” Concrete language helps capable candidates self-select.

List responsibilities in groups

For SEO teams working on technical audit support, group related work so the candidate sees the shape of the job. Keep the launch scope separate from future responsibilities. That prevents a candidate from assuming they must be expert in every adjacent task on day one.

• Keyword research with a clear owner, deadline, and handoff rule.
• On-page optimization with a clear owner, deadline, and handoff rule.
• Internal linking with a clear owner, deadline, and handoff rule.
• Content briefs with a clear owner, deadline, and handoff rule.
• Google Search Console monitoring with a clear owner, deadline, and handoff rule.
• Technical audit support with a clear owner, deadline, and handoff rule.
• Competitor research with a clear owner, deadline, and handoff rule.
• SEO reporting with a clear owner, deadline, and handoff rule.

Separate required experience from trainable preferences

When competitor research is part of the SEO scope, required criteria should be things you genuinely cannot train in a reasonable onboarding period, such as a needed language level, a specific regulated workflow, or substantial experience in a complex system. Tool familiarity, industry exposure, and nice-to-have software should be labeled honestly.

• Search intent analysis: explain how you will assess it.
• On-page SEO: explain how you will assess it.
• Technical SEO basics: explain how you will assess it.
• Content optimization: explain how you will assess it.
• Reporting: explain how you will assess it.
• Attention to detail: explain how you will assess it.

Be explicit about hours, rate, and live overlap

In an SEO handoff involving SEO reporting, state whether the role is part time or full time, the expected weekly hours, the time zone, and how much live overlap is required. If the schedule is flexible, say that. VirtualAssistant.com.ph requires ongoing hourly jobs to pay at least $5 USD per hour, and specialized roles may need a higher budget.

Include the tools that matter at launch

List only systems the person will actually use in the first month. For this SEO VA role, that might include Ahrefs, Semrush, Google Search Console, GA4, Screaming Frog, and WordPress. Ask for evidence of real use during screening instead of rejecting good candidates because they have used an equivalent tool.

Sample job-post structure

When on-page optimization is part of the SEO scope, use this as a structure, then rewrite it in your own voice so candidates get a realistic picture of the team.

1. Outcome: We need an SEO VA to own a defined set of recurring workflows and keep the status visible.
2. Responsibilities: keyword research, on-page optimization, internal linking, content briefs, and Google Search Console monitoring.
3. Success after 30 days: the core queue is current, exceptions are escalated early, and records are complete.
4. Schedule: state weekly hours, time zone, and required live overlap.
5. Requirements: choose four or five evidence-based criteria from the real work.
6. Rate: state the budget clearly and keep it at or above the $5/hour platform floor.

What to remove before you publish

In an SEO handoff involving internal linking, delete clichés, inflated seniority, contradictory schedule requirements, and tools that are not actually required. Then read the post for hidden assumptions. If you expect phone work, say how much. If the person will handle sensitive data, say what type and how access is controlled. If the role includes weekend coverage, state it before the interview.

For SEO teams working on content briefs, a shorter, accurate description attracts better-fit applicants than a generic page of requirements copied from other listings.

Read the SEO job post from the candidate's side

Take content briefs from a recent week and trace it from the moment the request arrived to the final record or handoff. When candidates read competitor research in the scope, note who supplied the input, where the status lived, which decision caused delay, and how the manager knew the work was complete. To make ownership of SEO reporting clear, that example will expose missing instructions faster than another generic checklist.

If content briefs becomes predictable, add technical audit support only after the first queue is stable. If it still creates repeated questions or rework, fix the process before expanding the SEO role. When candidates read internal linking in the scope, that keeps onboarding tied to evidence and gives the manager a clear reason for every new responsibility.

Test one more workflow before expanding the SEO scope

Take Google Search Console monitoring from a recent week and trace it from the moment the request arrived to the final record or handoff. When the job brief assigns Google Search Console monitoring, note who supplied the input, where the status lived, which decision caused delay, and how the manager knew the work was complete. For an SEO posting centered on technical audit support, that example will expose missing instructions faster than another generic checklist.

If Google Search Console monitoring becomes predictable, add competitor research only after the first queue is stable. If it still creates repeated questions or rework, fix the process before expanding the SEO role. When the job brief assigns keyword research, that keeps onboarding tied to evidence and gives the manager a clear reason for every new responsibility.