Job Pages

Every job has its own page at /companies/{company}/jobs/{job}. A job page needs both the company and the job to resolve, which keeps each listing tied to its employer's brand.

What the page shows

The job page renders the full description, employer, location, salary range (when provided), employment type, and remote-work requirements. Below the listing it shows similar jobs, computed by semantic similarity to the current role, which keeps a visitor browsing when a specific job is not the right fit.

The two apply paths

The Apply button adapts to how the job was posted:

• External apply sends the candidate to the employer's own application URL (for example their applicant tracking system), opening it in a new tab.
• Native apply (Quick apply) collects the application directly on your board through a built-in form, so the applicant lands in the employer's applicant pipeline without leaving your site.

If you have the registration wall enabled, pressing Apply first prompts a signed-out visitor to create an account, then continues to the application.

Google for Jobs data

Each job page automatically emits JobPosting structured data, which is what powers a listing's appearance in Google for Jobs. The emitted data includes the title, hiring organization, job location, base salary, employment type, posting date, expiry date, and remote-work (applicant location) requirements. You do not configure any of this; it is generated from the job's fields. See Google for Jobs for how to get the most out of it.

Availability

• Plan: All paid plans for job pages and external apply. Native apply (Quick apply) requires the Starter plan or higher, since it is part of the built-in applications feature.
• Setting: None for the page itself. Native applications depend on candidate accounts being enabled so the applicant can submit.
• Setup required: External apply needs the employer to supply an application URL on the job. Native apply needs no setup beyond a Starter (or higher) plan.

Limitations

• For external-apply jobs your board records the apply click but cannot confirm the application was completed, because the candidate finishes on the employer's site. Native applications are captured in full.
• Similar jobs are ranked by semantic similarity, so on a board with very few jobs there may be few or no similar results to show.