Christopher Abraham home
Christopher Abraham

SEO consultant: technical SEO, indexing, schema, and AI search

How to hire an SEO on Upwork: the questions that reveal real skill

Post an SEO job on Upwork and fifty proposals arrive within a day, most of them interchangeable. The screening questions you add to the posting are the fastest way to separate people who understand your problem from people who paste the same letter everywhere. I answer these questions for a living, so here is what I'd ask if I were on your side of the table.

Write the problem, not a wish list

The best postings describe a situation: what changed, when, what you've already checked, and what a good outcome would look like. "Service page rankings fell after the March redesign" gives an expert something to reason about. "Need SEO expert for growth" attracts the people least likely to help. A specific posting also lets you judge the replies, because you'll know whether a candidate engaged with your facts or skipped them.

Five questions worth adding

  1. "Based on this posting, what would you check first, and why?" A strong answer names two or three concrete things in a sensible order and explains what each would rule in or out. A weak answer lists every SEO activity in existence.
  2. "Describe one problem like this one: what was wrong, what you changed, and what happened." You want a mechanism and a result, described honestly. Real practitioners can explain a past diagnosis without naming the client.
  3. "What access would you need in the first week?" Search Console, analytics, and some form of access to the site or its developer are normal. Someone who needs nothing is planning to guess.
  4. "How would you know this worked?" Listen for measures you can check yourself: indexed pages, impressions and clicks on the affected pages, calls or form leads. Be wary of measures only the consultant can see.
  5. "What would you not do?" This one is revealing. Experienced people have boundaries: no link packages, no guaranteed positions, no changes without a reason they can explain.

What good answers sound like

Good answers are short and specific to your posting. They use your words, refer to your platform, and propose a first step small enough to test. They separate what is known from what needs checking. They read like a colleague thinking out loud about your site, not a brochure. If a candidate's answers would fit any other job on the platform, they weren't written for yours.

Red flags

Read the profile like evidence

Job Success Score, hours worked, and repeat clients tell you how a freelancer behaves over time, not how they write. Open the client reviews and look for specifics: what was fixed, how communication went, whether the client came back. One detailed review is worth more than ten five star ratings with no text.

Start with a small paid step

For anything bigger than a quick fix, pay for a defined first step: a diagnosis of one problem, an audit with a prioritized list, or a fixed number of hours. You learn how the person works, they learn your site, and either side can stop cleanly. It also prices the work honestly, because a good diagnosis is real labor and you should own the result.

Fixed price or hourly

Fixed price suits a well defined deliverable, such as an audit, a migration plan, or a set list of fixes. Hourly suits ongoing work where the next task depends on what the last one found. Either way, agree on what "done" means before work starts, and keep the scope written in the contract rather than scattered across messages.

Where I fit

I'm a technical SEO consultant on Upwork, and I like postings that ask hard questions, because they're the ones where I can show my thinking. If your problem sounds like indexing, rendering, migrations, local listings, or AI search visibility, tell me what happened, or see how I work on hiring me.

Sources