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 application URL or email (for example their applicant tracking system). A URL opens in a new tab. An email opens a mail draft.
• Native apply (Quick apply) collects the application on your board. A signed-in candidate applies from their job seeker profile, and the applicant lands in the employer's applicant pipeline.

A direct post uses whichever method its poster set on Create a job posting. A job added by backfill always uses external apply, because it keeps the application URL or email from the company's careers page. The candidate finishes in that company's ATS. Cavuno records the apply click and does not receive the completed application. An import that includes an application URL or email works the same way.

If you have the registration wall enabled, pressing Apply first prompts a signed-out visitor to create an account, then continues to the application. Signing in does not turn an external job into a native one.

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 an application URL or email on the job. A direct poster enters it. Backfill, and an import that includes one, brings it from the source. Native apply needs no extra destination beyond a Starter (or higher) plan.

Limitations

• For external-apply jobs, including every backfilled job, your board records the apply click but cannot confirm the application was completed, because the candidate finishes in the company's ATS. Native applications are captured in full. A job seeker profile does not turn an external job into a native one.
• 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.