> For the complete documentation index, see [llms.txt](https://docs.arthajobboard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arthajobboard.com/faq/frequently-asked-questions/which-is-the-best-option-to-host-a-job-board.md).

# Which is the best option to host a job board?

Host on the main domain

{% hint style="success" %}
Hosting on the main domain can be beneficial for SEO purposes as it consolidates domain authority and helps with branding.
{% endhint %}

Host on subdomain

{% hint style="success" %}
A subdomain can be useful if you want to separate the job board from the main content of your website, which can be easier to manage.
{% endhint %}

Iframe

{% hint style="success" %}
Using an iframe is less common because it can have limitations with SEO and user experience.
{% endhint %}

Sub Page

{% hint style="success" %}
A sub-page is a good option if you want to keep the job board integrated within the site’s structure and navigation.
{% endhint %}

Which hosting options are supported by the Artha Job Board?

{% hint style="success" %}
Hosting options supported by the Artha Job Board are mentioned below:

1. AWS (Amazon Web Services)
2. Azure
3. GCP (Google Cloud Platform)
4. Any cloud virtual machine
   {% endhint %}


---

# 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://docs.arthajobboard.com/faq/frequently-asked-questions/which-is-the-best-option-to-host-a-job-board.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.