> 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/jobs/job-optimisation.md). # Job optimisation 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. By following the tips and best practices in this section, you’ll be able to fine-tune your job ads and get the most value from your JOIN account. *** ### Benefits Improving your job ad helps you achieve better hiring results with minimal effort. 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 confidently These improvements help your job perform more effectively across both organic and premium job boards. *** For detailed instructions and improvements, refer to the dedicated articles in this section. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.join.com/jobs/job-optimisation.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.