> For the complete documentation index, see [llms.txt](https://help.join.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.join.com/create-and-manage-jobs/job-optimisation.md).

# Job optimisation

Improve how your job ads perform on job boards: write a clear job ad that meets the content rules, and attract candidates where you're hiring.

Once you’ve learned how to create a job in JOIN, the next step is making sure your job ad performs well across job boards. Job optimisation helps you improve visibility, attract stronger candidates, and get better results from your hiring efforts.

The pages in this section give you tips and best practices to fine-tune your job ads:

* [Write a good job ad](https://help.join.com/create-and-manage-jobs/job-optimisation/write-a-good-job-ad.md): write a clear job title and description, and keep the ad within JOIN's and the job boards' content rules
* [Job visibility](https://help.join.com/create-and-manage-jobs/job-optimisation/job-visibility.md): understand where your job is published, and attract candidates from the location you're hiring in

***

## Benefits

Improving your job ad helps you achieve better hiring results.

Job optimisation can:

* Increase visibility by making your job more relevant for job board search algorithms
* Attract higher‑quality candidates through clearer, more engaging content
* Reduce time-to-hire by improving application volume and relevance
* Highlight areas that need improvement so you can adjust your job ad

These improvements help your job perform more effectively across both organic and premium job boards.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.join.com/create-and-manage-jobs/job-optimisation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
