Skip to main content
Guides

How to Make a Recruitment Website: 10 Steps, Pages and Costs

Karan Singh BhakuniUpdated
  • 26 min read
  • 11 sections
  • 9 comparison tables
  • 16 questions answered

The short answer

To make a recruitment website, decide whether you are building an agency site, a careers site or a job board, plan separate paths for candidates and employers, publish one accurate page per vacancy (with pay where the law requires it), connect every Apply button to a monitored ATS or inbox, then test the whole route before launch. At published prices checked November 2026, a builder site such as Grigora starts at $144 a year. Among the plans compared in step 6, an applicant tracking system (ATS) adds from $0 (Zoho Recruit Free, one active job) to $3,588 a year (Workable Standard billed annually, 1 to 20 employees). The last step matters most: an Apply button is not finished until the right recruiter can privately receive and handle the application.

Want the site rather than the reading? Try Grigora free for 14 days

Contents11 sections

Start with the smallest useful release: a clear organization or agency, current jobs, a reliable way to apply and a named owner for updates. Add employer accounts, paid listings, saved searches or matching only when you can support the extra operations and data duties.

Here are the ten steps, in the order this guide covers them:

  1. Choose the model: careers site, agency site or job board.
  2. Map the candidate journey and the recruiter handoff.
  3. Plan the pages for candidates and employers.
  4. Set up one record per vacancy.
  5. Show pay and required disclosures in job ads.
  6. Choose the platform and application system, and price it.
  7. Design an accessible application.
  8. Handle candidate data and AI screening.
  9. Get jobs into Google and retire closed roles.
  10. Launch, then measure what reaches recruiters.
Recruitment website illustration with candidate profiles, a resume clipboard and a magnifying glass.

Read nextHow to Create a Career Page on Your Website: 2026 Checklist

1. Choose the recruitment website model

ModelMain visitor tasksWhat you need behind the pagesUsual tool route
One employer’s careers siteLearn about the employer, find a role and apply.An approved job source and an ATS or hiring process for that employer.An ATS hosted careers page, or website pages linking to ATS job pages.
Recruitment agency siteEmployers evaluate services; candidates find roles.Separate employer and candidate routes, control over who sees which jobs and applicants, and a named recruiter per role.A brand website plus an agency ATS or CRM holding jobs and applications.
Multi-employer job boardCandidates search many employers; employers submit or buy listings.Employer verification, moderation, billing, accounts and permissions, and clear ownership of each application.Job board software, or a custom build with employer accounts and billing.

These models overlap but are different projects. A company with a few vacancies may only need good job pages linked to its existing ATS; a job marketplace needs far more than a list styled like job cards. Decide who can publish, edit, view applications, close roles and receive payments before choosing a template.

Agency sites differ too. What to emphasize depends on how you recruit:

Site typeWhat it should emphasize
Boutique executive searchConsultant credibility, a discreet route for confidential inquiries, and fewer, more detailed role pages.
High-volume staffing or temp agencyFast search and filters, short phone-friendly applications, job alerts and a quick way for employers to request staff.
Niche specialist recruiterSector pages, market notes your consultants write, and roles grouped by specialism.

If your scope is one employer, the career-page guide helps you plan employer information. For a bigger project, write a short requirements document first; the website planning guide covers decisions and ownership.

2. Map the candidate journey and the recruiter handoff

Write down what happens from a job search to an application being received. For each step, specify the responsible system, owner and evidence of success. That makes a missing integration visible before real candidates send personal information.

StepExpected behaviorProof to check
Browse jobsCandidates find relevant current roles and can recover from an empty search.Filters and job counts match the roles actually open.
Read a jobThe page describes one real vacancy and its actual conditions.Approved details, a stable job ID and a current application destination.
ApplyThe candidate knows what is needed and can submit successfully.A controlled test reaches the intended system, including any external ATS.
ReceiveThe responsible recruiter can open the record privately.The record is attached to the right vacancy and visible only to the right people.
Confirm and follow upThe candidate gets an accurate acknowledgment and knows the next step.The confirmation reflects actual receipt, not just a button click.
Close or changeThe site responds when the role closes, changes or is withdrawn.Apply links, job status, feeds and structured data update together.

Keep employer inquiries and candidate applications on separate routes, and do not let sales users see resumes by default. Never send an Apply button to a generic contact form: link each job page to that vacancy’s own ATS page, or name the monitored inbox and job reference to quote, and tell candidates where an external ATS takes them.

3. Plan the pages for candidates and employers

A recruitment agency website serves two audiences with opposite goals: candidates want a role, and employers want people. Give each a clear route from the homepage, then plan the pages each route needs; a blog can wait until the job pages work. The free Website Page Planner can draft a page plan, and the agency website guide covers service pages and case studies.

PageWho it servesWhat it must do
HomeBothTwo routes (find a job, hire through you) and the sectors and places you cover.
Jobs indexCandidatesSearch, filters and a helpful empty-search message.
One page per vacancyCandidatesOne real role with pay, location, terms and close date (step 4).
Why work here (careers sites)CandidatesPay and benefits, how the team works and employee stories used with consent.
Apply route and acknowledgmentCandidatesThat vacancy’s own ATS page or a monitored inbox, then confirmation of real receipt.
Job alertsCandidatesNew roles by sector or location, sent to a consented email list.
Application helpCandidatesA monitored inbox or phone line for anyone the form fails.
Candidate privacy noticeCandidatesWhat you collect, who sees it and how long you keep it.
Recruitment scam noticeCandidatesWhether you ever charge candidates, your recruiters’ email domain and how to report a fake job.
Sectors or specialismsEmployersOne page per real specialism, not thin keyword pages.
How we recruit and case studiesEmployersYour process, terms and case studies used with permission.
Submit a vacancyEmployersRole, location, timing and contact in text fields, sent to a named consultant.
Consultant profilesBothReal names, sectors and photos used with consent, and how to reach each person.
About and ContactBothOffices, contact routes and any agency license you hold.
Blog or market notes (optional)BothOnly what you can keep current.
Recruitment website site map: candidate pages from jobs to application acknowledgment, and employer pages from sectors to a submit-a-vacancy form.
Plan both paths before you pick a template.

Design the first screen for both audiences

Give candidates and employers two equal routes above the fold, such as “Find a job” and “Hire through us”, and keep a Jobs or “Now hiring” link in the header and footer. High-volume agencies can put a job search in the hero. Show real consultants by name and photo, with consent, and only proof you may show; publish a salary guide only if you will update it yearly. Then check text and button contrast and run the checks that make a website look professional. Four large recruitment sites, checked on 17 November 2026:

SiteWhat it showsCopy this when
AerotekA hero job search (“I’m Looking For”, “Somewhere Near”) and two buttons: “I’m Looking For A Job” and “I’m Looking For Solutions”.You fill many roles.
Robert HalfA 2027 Salary Guide on the page with no form, plus a salary calculator for more than 250 US markets.You can update employer content every year.
Adecco USA banner warning of scammers impersonating its recruiters, then job seekers first and employers second.Scammers could use your name.
24 Seven TalentA testimonial carousel with one client and three candidates, and an office finder.You run several offices.
Recruitment website homepage layout: a Jobs link in the header, a scam notice, equal buttons for candidates and employers, a job search and consultant profiles.
Two equal routes above the fold.

4. Set up one record per vacancy

Every job card, search result, job page, alert email and piece of structured data should read from one record per vacancy. Agree its fields before you build anything:

Job recordContent to establish
Identity and ownershipStable internal job ID, role title, hiring organization and responsible recruiter.
Location and work arrangementActual location, remote or hybrid conditions and any geographic limits. “Remote” does not always mean work from anywhere.
TermsEmployment type and hours. Pay range or fixed pay, with currency and period; many places require it in the posting itself (step 5).
Role descriptionResponsibilities, essential requirements and a realistic description of the work, with no invented benefits.
Dates and statusDate first posted (it should not reset on every edit), any deadline, open or closed state and who changes it.
Application routeThe exact ATS or form destination, required materials, a help contact and the acknowledgment candidates get.

Define these fields once so every view stays consistent. Separate required qualifications from preferences, avoid inflated titles, and write in plain language with short sentences; the free Readability Score Checker scores a draft. Have the employer or authorized recruiter approve each vacancy, and never publish fake positions, stale feeds or scraped jobs.

5. Show pay and required disclosures in job ads

As of November 2026, 14 US states and Washington DC require a pay range in job postings for covered employers, as do several Canadian provinces including Ontario; the EU’s pay directive, through national laws, gives applicants pay information before interview. Delaware joins on 26 September 2027. If you advertise for clients, check who carries the duty: in Ontario the employer stays responsible when a third party advertises, and in California the Labor Commissioner’s FAQ says a third party that posts the job must include the pay scale. The rules recruitment sites meet most often:

WhereWho is coveredWhat the job ad must include or avoid
California15 or more employeesPay scale in the posting itself, a good-faith estimate of the range you expect to pay; a link or QR code is not enough. No salary-history questions, at any size.
Washington15 or more employeesPay range or fixed wage plus a general description of benefits. Since 27 July 2025, no driver’s license requirement unless driving is an essential function or serves a legitimate business purpose.
New York State4 or more employeesPay range or fixed pay, the job description if one exists, and whether the role is commission based.
Other US states11 more states and DC; from all employers to 50 or morePay range in postings in Colorado, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, New Jersey, Vermont and DC; Virginia (1 July 2026, all employers), Maine (29 July 2026, 10 or more employees) and Connecticut (1 October 2026, all employers, plus benefits); Delaware from 26 September 2027 (more than 25 employees).
Ontario25 or more employees, from 1 January 2026Expected pay or a range no wider than C$50,000 (not required above C$200,000); whether AI screens applicants; whether a vacancy exists; no Canadian experience requirement.
European UnionEmployers, under each member state’s law (Directive (EU) 2023/970)Starting pay or range before interview; no pay-history questions; gender-neutral job titles. National laws were due by 7 June 2026.
Great BritainEmployment agencies and businessesThe agency’s full name, whether each job is temporary or permanent, and only roles a hirer has authorized. If pay is quoted, also the work, location and minimum experience or qualifications.

These are examples, not a complete list, so get advice for each place you hire. Ontario also requires employers to tell interviewed applicants within 45 days whether a hiring decision was made and to keep postings and forms for 3 years; any site listing other employers’ jobs, including an agency site, must offer a way to report fraudulent postings and post a written policy on them. Delaware will also want a description of benefits and other compensation. Sources: SixFifty’s state tracker (updated September 2026), Cooley’s July 2026 summary of new state laws and the California Labor Commissioner’s FAQ (questions 67, 79, 83 and 89).

Recruitment rules timeline 2026 to 2027: pay-in-job-ad laws in Ontario, Virginia, Maine, Connecticut and Delaware, the EU pay directive and EU AI Act dates.
Dates checked November 2026; check each place you hire.

Showing pay is also becoming normal. Indeed Hiring Lab measured the share of Indeed postings with pay in June 2026: 97% in Japan, 58% in the UK, 57% in Canada and 49% in the US; in Ontario it rose from 49% just before its rules began to 71%. In data to March 2026, published on 7 May 2026, Hiring Lab found pay in only 12% of postings in Germany and 17% in Spain, expected Germany and France to miss the June 2026 deadline, and noted that the Netherlands had moved its start to 2027.

Pay transparency in job ads: share of Indeed postings with pay in June 2026 by country, and job ad pay rules in California, Washington, New York, Ontario and the EU.
Where pay is required, put it on the job page itself.

Give pay its own fields in the vacancy record (minimum, maximum, currency and period) so the job card, job page and structured data all show the same figure, and keep it on the job page itself rather than behind a link.

6. Choose the platform and application system

A CMS manages public content; an ATS manages applicant records and hiring workflows. A general website builder does not provide an ATS, candidate portal, recruiter permissions or resume screening, so confirm each feature rather than trust a template labeled “recruitment.”

  • Existing ATS plus website: Link to or publish the ATS’s job pages; check identifiers, apply links, sync and closed-job behavior.
  • Specialist job-board software: Test employer accounts, moderation, search, listing payments, permissions and export against your workflow.
  • CMS with extensions: Check what each plugin stores, who maintains it, its cost and data access; plugins add responsibilities as well as features.
  • Custom development: Budget for authentication, access control, integrations, upload handling and maintenance as well as design.
  • Specialist recruitment website provider: A done-for-you site with job search synced from your ATS, quoted by scope; ask which ATS and multi-posters it supports, who owns the design and content if you leave, and the fee after launch.

Vendor pages use a few terms worth knowing. A multi-poster sends one vacancy from your ATS to several job boards. One-click or easy apply reuses a candidate’s job-board profile, so the application lands in that board’s or the ATS’s system, not your website. Job taxonomies are the sector, location and type fields your filters use. Ask each vendor which boards it posts to and how closed roles are withdrawn.

For feeds or APIs, name the source of truth, update frequency, permitted use and who fixes a mismatch. An imported title does not prove the role is open, so show an honest error when a feed fails.

Costs depend on the route. The published prices below were checked in November 2026, in US dollars before tax; what each route leaves out is often the bigger cost.

OptionPublished priceWhat you getWhat is not included
Grigora (website builder)Starter $15 a month, or $144 a year ($12 a month), one website; 14-day free trial, no card neededHosted pages drafted by AI, a CMS with a page per job, text-only inquiry formsAn ATS, CV uploads, candidate accounts or client portals
Workable (ATS)Standard, recruiting only, 1 to 20 employees: $360 a month billed monthly, or $299 a month billed annually ($3,588 a year); with HR added, $359 a month billed annually ($4,308 a year); 15-day free trialApplicant tracking, with a careers page builder on all plansA full brand or agency website
Breezy HR (ATS)Startup $189 a month, or $157 a month billed annually ($1,884 a year); 14-day trial; no free planApplicant tracking with a branded career siteA full brand or agency website
Zoho Recruit (ATS)Free plan: 1 active job per recruiter license; Standard: 10; paid prices come from its calculatorA branded careers site from the Standard planA branded careers site on the free plan
Manatal (ATS and CRM for agencies and employers)Professional $15 per user a month billed annually ($180 a year), or $19 billed monthly; up to 15 jobs per account and 10,000 candidates; 14-day free trial, no cardApplicant tracking and a recruitment CRM, with a branded career pageA full brand or agency website
WP Job Manager (WordPress plugin)Core plugin free; the paid Pro bundle adds applications, resumes, alerts and paid listingsJob listings inside a WordPress site you runHosting, updates, backups and the security of any uploads
Custom buildQuote basedWhat you specify, including employer accounts and integrationsAsk for integration, hosting and maintenance as separate lines

Year one by route: a Grigora Starter site alone is $144, or $204 with a Grigora Mail jobs@ inbox ($60 a year). A solo recruiter pairing Starter with Manatal Professional (one user, billed annually) pays $324. Add Breezy Startup billed annually and it is $2,028; add Workable Standard billed annually (recruiting only, 1 to 20 employees) and it is $3,732, or $4,464 paid monthly at $360. Zoho Recruit Free keeps the total at $144, but it allows one active job per recruiter license and no branded careers site. A domain name, which you register elsewhere, is extra.

Recruitment website first-year costs by route, November 2026: a $144 builder site, ATS plans from $0 to $3,588, and builder plus ATS totals.
First-year totals at annual billing; most sites need a website and an ATS.

Sources: Grigora pricing, Workable pricing, Breezy pricing, Zoho Recruit pricing, Manatal pricing and the WP Job Manager Pro bundle. To estimate the website side (agency, freelancer or building it yourself), try the free Website Cost Calculator.

Grigora suits the public side of an agency or employer site: its AI drafts the pages, copy and images, and you change them by prompt. Vacancies can live in a CMS collection with typed fields (title, location, employment type, pay minimum and maximum, currency, period, posting date, apply link and a switch for filled roles), one page per job; consultant profiles can be a second collection.

Forms send text-only entries to a Leads screen, with email alerts to one recipient list per site: fine for employer inquiries, but CVs need your ATS or a monitored jobs@ inbox (Grigora Mail, $5 per inbox a month). A newsletter can carry job alerts you send yourself (trial: 50 subscribers, one campaign a month). Grigora is not an ATS: no candidate accounts, client portals or CV uploads, and CMS changes go live when you republish, so close a filled role the same day. See the recruitment website builder page and what Grigora suits and where its limits are; plans start at $15 a month, or $144 a year ($12 a month), after a 14-day free trial with no card needed.

Also worth readingHow to Make an Agency Website: 8 Steps and a Launch Checklist

7. Design an accessible application

Use clear headings, readable job details and visible Apply buttons. Let candidates read the vacancy before asking them to create an account, keep the first form short, and state required fields, file types and size limits before an upload fails.

The W3C WAI forms tutorial covers labels, instructions, validation and success and error messages; apply it to the whole path, including any ATS embed. WCAG 2.2 added criteria that bear on applications: 3.3.7 Redundant Entry (do not make candidates retype information in one process), 3.3.8 Accessible Authentication (Minimum) (no sign-in that relies on remembering a password or solving a puzzle unless paste or a password manager works), 2.5.8 Target Size (Minimum) and 2.4.11 Focus Not Obscured (Minimum). The free Accessibility Checker is a useful first pass, but no scan confirms that a form works with a keyboard or screen reader.

Test keyboard use, visible focus, errors that name the field, text at zoom and completion on a phone; the mobile-friendly website guide covers the phone checks. Keep entered information after recoverable errors, and if the process times out, uses an inaccessible CAPTCHA or rejects required material, offer a monitored alternative route.

Use genuine team images with permission, never stock portraits labeled as staff or invented testimonials, and do not put essential vacancy details only in an image or video.

8. Handle candidate data and AI screening

Before collecting applications, document what you need, why, where it goes, who can access it and how retention, deletion and requests work. Link a candidate privacy notice at each collection point; the guide to a website’s legal documents explains where it fits. The free Privacy Policy Generator gives a starting draft, but have it reviewed for candidate data and the laws where you hire.

Review application questions for each hiring stage. For example, U.S. EEOC guidance on the ADA restricts pre-offer disability-related and medical inquiries. Do not add sensitive questions just because a form template includes them, and remove salary-history questions where they are banned, as in California and under the EU directive (step 5).

Have a competent team verify access controls, storage and uploads. The OWASP file-upload guidance explains why file types, content checks, limits, storage and permissions each need controls, and it helps to know what HTTPS does and does not protect: it will not stop public access to a badly configured resume download. Keep applicant data out of public file libraries, URLs, page source, search indexes and analytics, limit session recording on application pages, and never switch on automatic ranking or rejection without its own fairness, privacy and legal review.

Specific rules already cover automated screening. New York City’s Local Law 144, enforced since 5 July 2023, requires a bias audit within one year before an automated employment decision tool is used, a published summary and notice to candidates 10 business days before use. The EU AI Act lists AI that targets job ads, filters applications or evaluates candidates as high-risk (Annex III, point 4(a)); after the AI Omnibus took effect on 27 July 2026, those duties apply from 2 December 2027, according to the Commission’s AI Act timeline. Ontario postings must already say whether AI screens applicants.

9. Get jobs into Google and retire closed roles

Give each vacancy an understandable page and title, keep current jobs easy to find, check indexing settings, and keep closed jobs and applicant pages out of your sitemap. Do not create thin location pages for roles that do not exist.

Google’s JobPosting documentation requires five properties on each job page: title, description, datePosted, hiringOrganization and jobLocation (or applicantLocationRequirements for a fully remote job). It recommends baseSalary (the employer’s actual pay, not an estimate), employmentType, validThrough, identifier, directApply, jobLocationType (TELECOMMUTE, required for 100% remote jobs, not hybrid ones) and applicantLocationRequirements. Markup belongs only on a single-job page and must match what it shows; it is not allowed on list pages, login-gated descriptions, jobs that charge applicants or CV collection for roles that are not open.

When a role closes, set validThrough to a past date, make the page return 404 or 410, or remove the markup; Google warns that ignoring expired jobs can lead to a manual action. For fast updates it recommends its Indexing API (job posting and livestream pages only) alongside a sitemap. As of November 2026, Google’s job experience did not cover Ireland, Australia, New Zealand, Poland or Sweden. Google announced on 12 June 2025 that it was retiring its Estimated salary result, so baseSalary in your markup is how you give Google your pay figure. Markup makes a page eligible, not guaranteed.

PropertyWhere it comes from on the pageCommon mistake
titleThe job title headingAdding codes, locations or salary to the title
descriptionThe full visible job descriptionA short teaser instead of the full text
datePostedThe date the job was first postedResetting it on every edit
hiringOrganizationThe company offering the jobNaming the agency or a branch; for an undisclosed client Google says to use “confidential”
jobLocationWhere the employee will workUsing the agency’s office for a role based elsewhere
baseSalaryThe pay shown on the pageMarking up an estimate rather than the employer’s figure
validThroughThe closing date, if the role has oneLeaving it in the future after the role closes
One job per pageA single vacancy pageAdding JobPosting markup to the jobs list page
Google job posting markup: the 5 required and 7 recommended JobPosting properties, and the three ways to close an expired job.
Markup must match the visible job page and change when the role closes.

The free Job Posting Schema Generator builds JobPosting markup, including baseSalary, validThrough and remote fields; check your live page with Google’s Rich Results Test. Grigora does not add JobPosting markup automatically. Name an owner for closing jobs: on a static site, including Grigora AI-built sites, a closed role leaves the live page only when you republish (see what makes a change go live), so a weekly refresh is too slow. Test the closed state before launch, including links from emails, listings and the ATS.

10. Launch, then measure what reaches recruiters

Test in a staging or controlled environment with fictional applicants and files you created, never real resumes. Go beyond a happy-path submission:

  • A current vacancy, an empty search and a closed or withdrawn role.
  • A successful application on phone and desktop, plus keyboard and screen reader checks.
  • Invalid fields, an allowed test file, a rejected or oversized file, and an interrupted request.
  • The right ATS record and vacancy ID, restricted access and an accurate acknowledgment.
  • Repeat submission, notification failure, broken external links and the support contact.
  • Job source, privacy text, indexing settings and structured data against the live output.

Keep a launch record of the version, checks, results, open issues and owner. The website testing guide shows how to make findings reproducible, and the free Website Launch Checklist covers general site checks. Passing form tests do not prove security, accessibility or legal compliance; report the coverage you actually completed.

After launch, count four stages per role: job page views, Apply clicks, applications received in the ATS or inbox, and failed attempts; only the ATS or inbox proves an application arrived. Record each application’s source (job board, your site, referral) to see which few channels produce most applications, and keep personal data out of analytics. A website creates a route for recruitment; it cannot guarantee hires.

Recruitment website FAQs

Get the next guide by email

Practical writing on building a site, growing an audience and sending email people open. No more than one a week.

Karan Singh Bhakuni

120 articles on the Grigora blog

More on Guides