gaash.ai

Local & Industries · 9 min read · September 25, 2026 · , gaash.ai

What clients and candidates ask about recruiters, in the order they ask

A hiring manager asks about a recruiter in the order a hire runs: whether to use an agency at all, what it costs, what happens if the hire leaves early, how soon a shortlist arrives, whether to sign an exclusive. A candidate's order runs from whether it costs anything to what happens after the interview. We have not measured what either side types; these are examples.

Examples, not a measurement, and why the order matters

We have not measured what hiring managers or candidates type into an AI assistant, and nothing on this page is a ranking or a count. The questions below come from how a hire runs on each side, written the way a person might put them in conversational search. Your own intake calls, client briefs and candidate registrations are a better source than this page, and the later sections say how to collect from them.

The order matters because each question belongs to a moment and to a page. A hiring manager deciding whether to use an agency at all is not yet asking about your replacement period, and a candidate who came out of an interview this morning is not asking whether registering costs anything. Each question carries its own search intent, and the page for the side that asks is where its answer goes.

In our audit of 9,483 small business websites (40 trades, 90 metros, late August to early September 2026), 61.5% had no question-and-answer content of any kind, and 50.7% asked a question in at least one heading but gave no answer beneath it in a form a machine could pick out. Both figures cover the whole sample, and the audit publishes no cut for recruiting agencies. A site that answers these ten questions in writing is already unlike the 61.5%.

The client's questions, from whether to use an agency to exclusivity

A hiring manager's questions in the order a hire runs, each worded as a hiring manager might put it, and what the answer on the client page states. The wording is an example, not a measured query.
StageThe question, as a hiring manager might put itWhat the answer on your client page states
1. Whether to use an agency"do i need a recruiter to hire a [role] or can we do it ourselves"Which roles you tell clients they can fill without you, and which ones you are set up to fill, in your own words
2. What it costs"how much does a recruiter charge to fill a [role] in [city]"The fee model (contingency, retained or an hourly markup), how the fee is worked out, and when it is invoiced
3. If the hire leaves"what happens if the person a recruiter placed quits in the first month"The replacement or refund period, its length, and the conditions attached, as your terms state them
4. How fast"how long does a recruiter take to send candidates for a [role]"The time from signed brief to first shortlist on that desk, taken from your own record and dated
5. Exclusivity"should we give one recruiter an exclusive on a [role] search"What you offer with and without exclusivity, for how long, and what changes for the client

The first question deserves an honest answer, including the roles a client could fill without you. A page that argues only for using an agency has not answered what the hiring manager asked, and the rest of the page reads as a pitch.

The replacement answer needs its conditions as much as its length: whether it is a free replacement or a partial refund, whether it applies when the client ends the employment, and whether the fee has to have been paid on time. A length with no conditions reads as a promise your terms may not make, so copy the conditions from the terms themselves.

Speed and exclusivity are answered with your own figures and your own terms. The time to a first shortlist comes from the desk's record, counted the way desk pages for a recruiting agency's specialties describes, and the exclusivity answer says what the client gets in return for it: a named recruiter, a shortlist date, a different fee, and a length after which either side can end it.

The candidate's questions, from registering to after the interview

A candidate's questions in the order a job search runs, each worded as a candidate might put it, and what the answer on the candidate page states. The wording is an example, not a measured query.
StageThe question, as a candidate might put itWhat the answer on your candidate page states
1. Whether it costs them"do i have to pay a recruitment agency to find me a job"Who pays the agency, in one sentence, and exactly what a candidate is ever charged for, if anything
2. The CV and their data"what does a recruiter do with my cv and who sees it"Who sees a CV, whether it goes to an employer without the candidate's say-so, how long it is kept and how to have it deleted, as your privacy notice states
3. How temporary pay works"how does pay work when you temp through an agency"Your pay day, method and timesheet rule, in the words of your worker terms
4. How long placement takes"how long does it take a recruiter to find you a [role] job"Your desk's typical time from registration to a first interview, dated, and what makes it longer
5. After the interview"what happens after an interview through a recruiter"Who gives feedback and by when, how an offer reaches the candidate, and what happens if the client goes quiet

The cost answer has a second reason to be plain. Google's job posting documentation does not allow job postings that require payment from applicants. Whether an agency may charge a candidate for anything at all is a question the rules answer differently by jurisdiction, so the page states what you do and counsel confirms it.

The CV answer has rules behind it that the page does not state. How long a CV may be kept, what consent is needed before it goes to an employer, and what a candidate may ask you to delete are set by data-protection rules that differ by jurisdiction, and your counsel or regulator states them. The candidate page gives your policy in plain words and links the full privacy notice.

The pay answer is the worker terms, restated for someone who has not signed anything yet; a temp agency's licenses and terms has those terms as sentences to fill in. The placement-time answer is a range from your own record, with the reasons a search takes longer, because a candidate plans around it.

Where both sides' questions are already written down

An agency hears both sides every working day, in places that already keep a record:

  • Intake calls with clients: the questions a hiring manager asks before agreeing terms, which may already be in the call notes.
  • Client briefs and the emails around them: the questions about fees, timing and exclusivity that come before a brief is signed.
  • Candidate registrations: the questions asked on the registration call, or typed into the form's free-text box.
  • The first week of a temporary assignment: the pay and timesheet questions a new worker brings to the office.
  • The recruiters' inboxes and the site's contact form: the same questions again, in the asker's own words.

Collect for a set period, such as a month, with the side and the date beside each question, then count which questions come back. The ones that recur on both your list and the lists above are where the first answers go.

Keeping the question and removing the person

What goes into the log is the question, never the person who asked it. Before a recruiter adds a line:

  • Remove names, employers, salaries, addresses and anything else that points to one client or one candidate.
  • Turn a candidate's own situation into a general question: "I was let go from [company] last month, will that count against me" becomes "do employers ask why I left my last job".
  • Leave out anything about health, family, age or any other personal characteristic, even as a general question, unless counsel has cleared an answer for the site.
  • Never paste from a CV or a brief. The brief is the client's; the CV is the candidate's.
  • Keep the log where every recruiter can add to it, and mark which side asked.

What an agency may keep about the people who ask, and for how long, is a question for counsel where you operate. A log that holds only questions, with the people removed, keeps that question small.

One page for each side, and where each answer goes

Answer each question on the page for the side that asks it: the client's on the pages for employers (how it works, fees, the replacement period, exclusivity), the candidate's on the pages for candidates (registering, pay, the CV, after the interview). One FAQ that mixes them can put the employer pitch above the candidate's answer, which is the wrong-side problem that AI visibility for recruiters sets up a column to catch.

Each answer takes the shape set out in writing to be cited: the question as a heading, a first paragraph of 40 to 80 words that answers it completely, with the agency's name, the place and the figure where there is one, and the detail after it. The answer-page template lays out a whole answer page in that shape. Two answers written out, one for each side:

<h2>What happens if the person you placed leaves in the first [period]?</h2>
<p>[Agency name] replaces a permanent hire who leaves within [period]
of starting, once and at no fee, provided [the conditions in your
terms]. If we cannot find a replacement within [time], we [refund or
credit rule]. Temporary staff are covered by the separate terms on
our [client terms page]. Last reviewed [month year].</p>

<h2>Do I pay anything to register with [Agency name]?</h2>
<p>[No. The employers we recruit for pay our fee, and you pay nothing
to register, interview or be placed.] [Or: state exactly what a
candidate pays, and why.] Registering takes [time]: [the steps].
Last reviewed [month year].</p>

The rest of what an agency's site states, for both sides, is on the recruiting and staffing overview.

Common questions

Can one FAQ page hold both sides' questions?

It can, if it is split under two headings, one for employers and one for candidates, with each answer complete on its own. Better still, put each answer on the page it belongs to (the fee answer on the employer page, the pay answer on the candidate page) and link each half of the FAQ to the other, so neither side has to read the other's answers first.

A candidate asked how much we bill the client for them. Do we answer that on the site?

Answer what is the candidate's to know: how their own pay is set and when it arrives. What you bill a client is a term between you and the client, and the candidate page can say so plainly. Whether a worker is entitled to see any of it is a question the rules answer differently by jurisdiction, so ask counsel before writing that sentence.

Should the site answer questions about overtime, notice periods or pay law?

No. Those rules differ by jurisdiction and change over time, and a page that states them can be wrong for the reader's place and date. State the agency's own terms instead: how overtime is paid on your assignments, the notice you ask for. Then link the body a worker can ask about the rules, named the way it names itself.

How many questions should we collect before writing any answers?

Enough to see which ones come back. Start with the five per side on this page, check them against a month of your own intake notes and registrations, and write answers first for the questions that recur on both lists. Add a question when it keeps arriving, and date each answer so you know when it was last true.

Sources

The questions are examples written from how a hire runs on each side, not a measurement of what anyone types. The two audit figures cover all 40 trades, with no recruiting cut.

Sources: our audit of 9,483 small-business sites, with its method · writing to be cited: the answer block · the answer-page template · Google, job posting structured data

All articles