A recruiting agency website: role pages for candidates and landing pages for employers
Short answer: A recruiting or staffing firm website needs two kinds of pages: one page per open job for candidates, and a small set of landing pages for the employers who pay you. Google can show jobs in its job search only from pages that hold a single real job with the required details, and it can take action against expired jobs left up. Job ads must also avoid wording that discourages protected groups, and candidate data needs a privacy notice. No page design guarantees applicants or clients.
You run a recruiting or staffing firm and want job pages that Google can read, employer pages that win clients, and a site that does not trip over hiring and privacy rules.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Short answer: give every real job its own page with a clear title and full description, give every employer type you serve one strong landing page, and make removing a filled job part of the process, not an afterthought. Candidates search for roles and places. Employers search for a firm that fills a type of role. They are different readers and need different pages.
The work is repetitive, which is where a platform with a built-in database helps. Ploy, an AI platform that builds and hosts business websites, is one such option. It has no applicant tracking system (ATS, the software recruiters use to manage candidates and jobs) of its own, so treat it as the website layer only, as explained below.
This page may contain affiliate links from which Blur Studio earns commissions.
The two page types
| Role pages (candidates) | Employer landing pages (clients) | |
|---|---|---|
| Search they answer | "warehouse supervisor jobs in Leeds" | "IT staffing agency for healthcare" |
| How many | One per live job | A handful: by industry, role family or service (permanent, contract, temp) |
| Lifespan | Short: until the job is filled | Long: updated over time |
| Main goal | Get a qualified application | Get a hiring brief or a call |
| Main risk | Expired jobs, vague ads, discriminatory wording | Thin copy repeated across industries |
Role pages that Google can read
Google's job posting documentation (last updated September 2026) sets the rules for appearing in its job experience. Google has no portal to post jobs. It reads them from marked-up pages on an employer's or job board's site. There is no charge. The rules that matter most to an agency:
- Put the markup only on a page that holds a single job posting. Do not mark up a list page.
- The markup must match what the visitor sees on the page.
- Expired postings are not allowed. Leaving them can lead to a manual action, a penalty applied by a Google reviewer.
- People must see the details without logging in, and there must be a way to apply. A career-fair invitation does not count.
- "We are always hiring" evergreen pages should not be marked up as a job.
Required fields in the markup: the date posted, the full description in HTML (different from the title), the hiring organization, the job location including country, and the title. The title is the job title only, with no codes, dates, salaries or company names. A fully remote role uses applicant location requirements instead of a street address.
Recommended fields include base salary with its unit, employment type, an identifier, validThrough (the date the job stops being valid) and a remote flag only for 100 percent remote roles. Google describes its "direct apply" field as still in development, so do not expect it to improve ranking.
Markup is the code that tells Google these details, written in a format called JSON-LD. Your site builder or developer adds it. Test any page with Google's Rich Results Test, and watch the job posting report in Search Console for errors each month.
Confidential clients
Agencies often cannot name the client. Google's documentation allows "confidential" as the hiring organization name. Use it, and never invent a company name. Also never copy jobs from another site. If you post a client's job and the client posts it too, expect two versions and make sure the details match.
Own site or a job board
Google reads jobs from your site and from boards. Your own site gives you the candidate relationship and the data. Boards give reach. Whether a board posting also needs your own markup depends on the board's setup, so check it. Many agencies do both: post on their own site first, then syndicate.
Handling filled and expired jobs
This is the part most agency sites get wrong, and Google warns that failing to act on expired jobs in time may lead to a manual action. Make it a rule in your process.
| Situation | What to do |
|---|---|
| Job filled or cancelled | Remove the markup the same day, or remove the page so it returns a not-found response (404 or 410, the codes that mean gone), or redirect to a close match |
| Job has a known end date | Set validThrough so the job lapses on its own, and still check weekly |
| You post many jobs | Google recommends its Indexing API (a way to tell Google about a changed or removed URL) over sitemaps alone, because it speeds up crawling and removal |
| Page has candidates in progress | Keep the page, remove the markup and say "this role is now closed", and link to similar jobs |
In your database or ATS, give every job a status field (open, on hold, filled) and let that field drive the page and the markup. The status field is the single place a coordinator has to touch.
Job ad language
The US Equal Employment Opportunity Commission (EEOC) says it is unlawful to publish a job ad that shows a preference for, or discourages, applicants based on race, religion, sex, national origin, age, disability or genetic information. Its own examples say ads seeking "females" or "recent college graduates" may violate the law, since they can discourage men and people over 40. The EEOC page speaks of employers. Check the EEOC's current pages and ask counsel how its rules apply to staffing and employment agencies.
A simple screen for every ad: no age hints ("digital native", "recent graduate", "young and energetic"), no gender-coded titles, no requirement unrelated to the job, and the same description on your site as on every board. Local laws, such as pay transparency rules in some states, may add duties. That is a topic to check with counsel, not one to guess.
Employer landing pages that win clients
An employer landing page answers a hiring manager's questions in the order they ask them. Build one for each industry or role family you really serve. A made-up outline for "healthcare IT staffing":
- Headline: who you place and where.
- How it works: brief, shortlist, interview, offer, with realistic timing you can back up from your own placements.
- Roles you fill in this field, with examples.
- Fee model: permanent placement, contract, temp-to-hire, in plain words. Give a range or say what drives the fee.
- Guarantee terms you actually honor, in writing.
- Compliance steps you handle: screening, right-to-work checks, payroll for temps. State only what you do.
- Proof: client names with permission, or anonymised facts you can document. See claims and testimonials on websites.
- One call to action: a short hiring-brief form.
The danger is repeating the same page for every industry with the word swapped. Google's spam policies target pages built to funnel searches to one place and mass-produced pages with little original value, covered in doorway pages and thin content at scale. A sound test: could this page exist without the industry word changed? If so, add real content, such as role types you actually fill, typical lead times from your own data, and a real placement story. If you cannot, do not publish that page. For location-based pages see programmatic and service-area landing pages.
Candidate data, privacy and AI screening
- Privacy notice at the form. Put a short notice at the point of collecting a CV or application: what you collect, why, who sees it, how long you keep it, how to ask for deletion. In California, the employment-related exemptions in the privacy law (CCPA) expired on 31 December 2022, and the state's FAQ says a notice at collection must list categories and purposes and link to the privacy policy. The FAQ speaks of "consumers" and does not name applicants, so check with counsel how it applies to your candidates.
- Automated screening. New York City's Local Law 144 says employers and employment agencies may not use an automated employment decision tool unless it has had a bias audit within one year of use. A summary of the results must be public, and candidates must be notified before use (the city's training slides said 10 business days). Enforcement began on 5 July 2023. Check the city's current page, and see recruitment CRM tools and the law on AI resume screening.
- Email outreach. The CAN-SPAM Act has no exception for business-to-business messages. See cold email and outreach laws.
- Candidate data in AI tools. Do not paste CVs or notes into a general chatbot unless you have checked the vendor's terms and your own privacy notice allow it.
This is information, not legal advice. Check local law.
Where an AI site platform fits
Ploy has a built-in spreadsheet-style database, PloyDB. One template turns every row into a page, and adding a row publishes a page, with edits reaching visitors usually within a minute, per its docs as of November 2026. For a firm with 30 live jobs, that means a spreadsheet-style table of jobs could drive the job pages. Ploy's forms capture submissions into a dashboard and can pass them to HubSpot, a CRM (customer database), on the Pro plan, and to Attio, another CRM. Its integrations marketing page also lists Ashby, an applicant tracking tool, though it is not in the docs table, so ask what that connection does.
Limits to know. Ploy documents no ATS, no job feed and no automatic JobPosting markup. Ask its agent to add the markup and test the result with Google's tool. Its docs describe no automatic expiry of a job page when a row changes, so test what happens when you delete a row or change its status, and check that the old URL returns the response you expect. Its docs also describe no duplicate or thin-content check. Pricing as of November 2026: Free $0, Starter $50 a month, Pro $300 a month, with AI credits that reset monthly, and CRM connections such as HubSpot on Pro. Check the pricing page.
Who should skip it: firms whose ATS already publishes careers pages and feeds Google well, firms with hundreds of jobs a day that need a real job board product, and anyone who needs a candidate portal. For tools aimed at the whole recruiting workflow see staffing agency software and recruitment CRM.
Worked example with made-up numbers
A made-up firm, Northgate Staffing, places warehouse and logistics staff. It has 24 live jobs and serves three employer groups: food distribution, ecommerce fulfilment and cold storage.
| Item | Plan |
|---|---|
| Role pages | 24 pages, each one job, with salary range, shift pattern, location and a three-field apply form |
| Employer pages | 3 pages, each with its own list of roles filled, typical timelines from the firm's own records, fee model and a hiring-brief form |
| Status rule | Coordinator sets status to filled the day an offer is accepted; the page shows "closed" and markup is removed |
| Weekly check | Friday: scan Search Console job posting report and the list of closed pages |
| Ad screen | Second person reads each new ad for age, gender and unrelated requirements |
Nothing here predicts applicants. It sets up pages that are accurate when they go live and stay accurate when jobs change.
Copy-ready checklist
- One URL per job, one job per page, no jobs on list pages as markup.
- Required fields filled: date posted, full description, hiring organization (or "confidential"), location with country, title only.
- Salary and employment type filled where you can state them accurately.
- Apply form works without a login, with a privacy notice beside it.
- Status field drives page and markup; filled jobs removed the same day.
- Rich Results Test passed on one page of each type.
- Monthly look at Search Console's job posting errors.
- Ads screened for age, gender and unrelated requirements.
- Employer pages have original content, not swapped words.
- No candidate data pasted into tools you have not checked.
Test plan with pass and fail
| Check | Pass | Fail |
|---|---|---|
| Markup | Rich Results Test shows a valid job posting with no errors | Missing required field or mismatch with visible text |
| Closing a job | Marking a job filled removes the markup or page within a day | Page and markup still live a week later |
| Apply path | A stranger applies on a phone in under three minutes with no login | Login or a long form blocks them |
| Form delivery | 3 of 3 test applications reach your inbox and ATS | Any lost application |
| Employer page | A reader can tell what is different from your other industries | Reads like a copy with a swapped word |
How I'd approach this
I would fix the process before the pages. A recruiting site fails when jobs go stale, so the status rule matters more than any template. Start with your live jobs and one employer group, and get both right before adding more.
First week: Day 1, export your live jobs and decide which fields you can fill accurately. Day 2, build one role page template and test its markup on one job. Day 3, write one employer landing page from real placement facts. Day 4, add the status rule and a Friday check, then connect applications to your inbox or ATS and test three applications. Day 5, screen ads for wording, add the privacy notice beside the form, and publish. If you want to try an AI platform for the repeat pages, try Ploy's free plan on one job page and check closing a job first. If you need a custom careers site connected to your ATS, Blur Studio builds the custom version, including CRM and calendar connections and ongoing care: see what that includes.
I'm not a lawyer, accountant or other licensed adviser, and this page is general information, not advice. Rules and prices differ by country and change often, so treat it as a direction to think along, and please check with a lawyer or the relevant regulator before you act on it.
Questions people ask
Can Google show my agency's jobs?
Yes, if each job has its own page with valid job posting markup and the required details, and the page lets people see the job and apply without logging in. Google has no posting portal and charges nothing. It does not guarantee any job will appear.
What do I do with expired jobs?
Remove the markup or the page the same day a job is filled, and use validThrough for jobs with a known end date. Google warns that failing to act on expired jobs may lead to a manual action. For many postings, Google recommends its Indexing API over sitemaps.
Can I hide the client's name?
Google's documentation allows "confidential" as the hiring organization. Do not invent a company name. See recruitment CRM tools for ways to keep client and job data tidy.
Can I mark up an always hiring page?
No. Google's rules say markup is for a page with a single real job, and expired or evergreen postings are not allowed. Use a talent-network page with a simple form for "we are always hiring" and keep it unmarked.
Are there rules about the words in job ads?
Yes. The EEOC says ads that show a preference for or discourage applicants by race, religion, sex, national origin, age, disability or genetic information are unlawful, and gives "females" and "recent college graduates" as examples that may violate the law. Check local law and ask counsel. This is information, not legal advice.
Do I need a privacy notice on the application form?
Put one beside the form saying what you collect, why, who sees it and how long you keep it. California's privacy law employment exemptions expired on 31 December 2022, so check with counsel how it applies to your candidates. See cold email and outreach laws for the outreach side.
Is AI resume screening regulated?
In some places, yes. New York City's Local Law 144 requires a bias audit within one year before an employer or employment agency uses an automated employment decision tool, with public results and candidate notice. Check the city's current page. See AI for recruitment agencies for lower-risk uses such as follow-up.
Does Ploy work as a recruiting site?
As a website layer it can: its database turns rows into pages and forms can pass leads to a CRM. It documents no ATS, job feed or automatic job markup, so test those steps yourself. See how Ploy's database-driven pages work.
More in this topic: Websites: by industry and audience (10 guides) →