Post a remote job
Listings are aggregated from public job sources rather than submitted through a form, so the fastest way to get a remote role listed is to publish it on your careers page with an explicit remote location line and email us the URL.
Last reviewed:
Key takeaways
- There is no self-serve posting form today; listings are aggregated from public job sources.
- Email the job URL to the support address to have a role picked up or corrected.
- State the eligible region explicitly — 'Remote' with no region is the most common classification failure.
- Publish a salary range if you want the listing to survive salary filtering.
- Expired roles are removed on request; include the job URL.
How do you get a remote job listed?
Publish the role on your own careers page with a clear remote location line, then email the URL to the support address. Roles are aggregated from employer sources, so a public posting is the input the classifier needs.
There is no paid placement and no self-serve posting form at the moment. That is a deliberate consequence of the model: the corpus is built from employer sources so that every listing on the site links back to an authoritative original.
If you want a role considered quickly, send the direct URL of the posting rather than a link to your careers index. The posting page is what gets classified.
What to send
- The direct URL of the job posting on your own domain.
- The eligible region or countries, if the posting itself is vague.
- The contract type: full-time, part-time, contract, or internship.
- The salary range and currency, if it is not already on the posting.
What makes a job listing classify correctly?
Explicit structure in the posting itself: a location line that names the eligible region, a contract type, a seniority signal in the title, and a salary range. Everything the classifier cannot find becomes a filter your role will not appear under.
A role posted as 'Remote' with no region has to be treated conservatively, and it will not surface on the country landing pages where candidates in your eligible countries are actually searching.
The same applies to seniority. A title like 'Engineer' carries no level, so the role misses the experience-level pages; 'Senior Backend Engineer' lands on both the role and the senior experience landing.
Fields that drive placement
- Location line: 'Remote (Brazil)', 'Remote (EMEA)', or 'Remote — worldwide'.
- Contract type: full-time, part-time, contract, or internship.
- Seniority in the job title, not only in the body text.
- Salary range with a currency.
- A stable posting URL that does not change when the role is edited.
Should you say which countries you can hire in?
Yes, always. Most remote roles are legally restricted to countries where you have an entity or an employer-of-record arrangement, and stating that upfront reduces ineligible applications more than any screening question.
Candidates read the location line before the job description. A posting that says 'Remote' and only reveals a United States restriction in the fourth paragraph generates applications you will reject and a reputation you do not want.
If you hire contractors internationally, say so explicitly — it is a different and much larger candidate pool than direct employment, and many strong candidates filter for it.
How do you correct or remove a listing?
Email the job URL and what is wrong to the support address. Corrections are applied at classification, so the fix propagates to every landing page and sitemap entry that listing appears on.
Common requests
- The role is filled or expired and should be removed.
- The region is wrong or the role is not actually remote.
- The seniority, contract type, or salary was classified incorrectly.
- The listing should point at a different canonical URL.
What does an employer get from a listing?
A canonical, indexable page that links back to your posting, inclusion in the role, country, experience, and contract landing pages your role qualifies for, and exposure to agent clients reading the same corpus through the API.
Listings are server-rendered with JobPosting structured data, so they are readable by search engines, answer engines, and agent clients without JavaScript. There is no application funnel in between — candidates apply on your own site.
Frequently asked questions
How much does it cost to post a job?
Nothing. There is no paid placement and no self-serve posting product today. Roles are aggregated from public job sources, and being listed does not cost the employer anything.
How long does it take for a job to appear?
New listings enter the feed as they are collected and classified. If you email a specific posting URL, ask for confirmation rather than assuming — a posting that lacks a region or contract type may need clarification before it can be classified.
Can you post a hybrid or onsite role?
No. The corpus is remote-only by design and every landing feed locks to remote before applying any other filter, so a hybrid or onsite role would be filtered out even if it were collected.
Do candidates apply through OnlyRemoteJobs?
No. Every listing links to the employer's own posting and candidates apply there, so applications arrive in your existing applicant tracking system with no intermediary and no data handoff.
Start searching
Related guides
- About usWhat OnlyRemoteJobs is, where the listings come from, how the job board makes money, and why it is safe to use as a job seeker.
- Tips for finding remote jobsA practical method for finding a remote job: pick a narrow target, apply within 48 hours of a posting, and prove asynchronous work in writing.
Questions or corrections? Email reativatecnologia@gmail.com.