Most companies hire through other people’s websites. The job goes up on a board, candidates arrive from the board, and the company’s own careers page — if it has one — is a static paragraph that has not changed in two years.
That is a reasonable way to fill a role quickly. It is a poor way to build anything, because none of the value compounds.
What you give up on a third-party board
A posting on someone else’s board is a rental agreement with terms you did not negotiate.
- The search ranking belongs to the board. When your posting ranks for a role and a location, the domain accumulating that authority is theirs. Take the posting down and nothing remains on your side.
- The first impression is theirs. A candidate reads your role in a template, next to nine other roles, in a layout designed to keep them browsing rather than applying to you.
- The competitor is one click away. Boards exist to show a candidate many options. That is the product working as intended, and it is not working for you.
- The candidate relationship starts in their account. The application arrives in your inbox, but the candidate’s relationship is with the platform.
None of this means never post to a board. It means the board should be a distribution channel pointing at something you own, not the thing itself.
What a careers page on your own domain is worth
A job board on your own domain behaves like an asset rather than an expense, for a few reasons that build on each other.
Search authority accrues to you. Every posting that gets indexed, linked to and visited contributes to your domain rather than someone else’s. Roles are repetitive — most companies hire similar positions repeatedly — so a careers domain that has ranked for a role before starts ahead the next time.
The candidate is on your site. They can read about the company from the same page, in your design, with your brand color. That is a materially different first impression from a listing in a template, and it is the moment a candidate decides whether to spend twenty minutes on an application.
And the page keeps working between hires. A careers page that lists current openings and is reachable from your site is a standing invitation, including to people who were not looking when they arrived.
Why most companies do not have one
Not because they disagree. Because building it is more work than it looks. A careers page that is actually useful needs per-posting pages that can be indexed individually, a way for the team to publish a role without a developer, an application flow that does not lose candidates, and somewhere for applications to land that is not an inbox.
That is a small product. It is why "we should do our own careers page" sits on a list for a year, and why the board gets used again.
How OneclickHR handles it
The public job board in OneclickHR is generated from the jobs you post in your workspace. It is built to be crawled and indexed, with pages a search for the role can find, and it carries the brand color configured in your workspace settings — so it looks like your company rather than like your HR vendor.
You can point your own custom domain at it from workspace settings. That is the part that makes the search authority yours: postings live under your domain, and what they earn stays with you.
Candidates apply directly through the board with their own lightweight external account. They see their own application and nothing else — no organization seat, no visibility into your workspace. Applications are tracked against the job they came in on, so the state of a pipeline is a screen rather than a reconstructed email thread. Candidates who were good but not right for one role go into the talent pool, so the next opening starts with people you have already met.
Recruiters, scoped to the job
Hiring usually involves people who should not see the rest of your HR system. An external recruiter working one role does not need the payroll module, the attendance sheet, or the other eleven roles in your pipeline.
Recruiter is its own role in OneclickHR, with scoped access to the hiring side only, and that access is toggleable per job. When a recruiter’s engagement on a role ends, you toggle it off and the access is gone on the next request — permissions are re-checked against the database rather than trusted from an existing session.
Those boundaries are enforced in Postgres with Row Level Security rather than by hiding parts of the interface, which is what makes it safe to give an outside recruiter an account at all.
A sensible setup
Owning your careers page does not mean abandoning distribution. The arrangement that works looks like this.
- Put the careers board on a domain you control, and link to it from your main site navigation rather than burying it in a footer.
- Write the posting once, on your own page, and treat that page as the canonical version of the role.
- Use boards and social posts as distribution that links back to your page, so traffic you pay for or earn lands somewhere that keeps the benefit.
- Fill internally first where you can. Employees see an internal job board in their own portal, so an opening can be offered inside before it goes public.
- Keep the talent pool current, because the cheapest hire is someone you already interviewed.
Distribution can be rented. The page it points at should not be.
For staffing and consulting firms the argument is stronger still, because hiring is the business rather than an occasional need. Placements are tracked as their own records, the careers domain is a channel you are building permanently, and every posting that ranks is an asset on the balance sheet rather than a month of rent.