Distribution should be deliberate, not just everywhere.
Every job takes the routes its budget can pay for, reaches people where they already look, and stops the moment it should. Here's every channel, and the rules behind them.
Channels
Where a job can travel.
Hireoute search
Up to three sponsored slots on the first page of every matching search, ranked by bid, above organic results.
Publisher network
Funded jobs go into a live XML feed for every approved partner site, refreshed continuously, with signed tracking links.
Google for Jobs
Every job page carries schema.org JobPosting data, so it can appear in Google's job search, plus a sitemap of all live jobs.
Job alert emails
Seekers save searches; new matching jobs are emailed daily or weekly, sending people back to apply.
Your own apply flow
Take applications on the Hireoute form, or send candidates straight to your careers site or ATS.
Pacing
Budgets steer the route.
A job is sponsored only while its campaign can pay for the next click. The checks run on every single click.
- ✓
Campaign is live
Active, and inside its start and end dates.
- ✓
Total budget has room
Spent so far plus one more bid stays within the total.
- ✓
Today's budget has room
Daily caps reset at midnight UTC, so spend spreads across the month.
- ✓
Wallet can cover it
The prepaid balance covers the full bid. Wallets never go negative.
If any check fails, the job quietly drops out of sponsored slots and partner feeds, and keeps its free listing.
Click quality
What we never bill for.
Filtered clicks are recorded with a reason, visible to both sides, and cost nothing.
| Filter | Rule |
|---|---|
| Bots & automation | Crawlers, headless browsers, Selenium/Playwright/Puppeteer, scripts and empty user agents |
| Repeat clicks | Same visitor on the same job within 24 hours |
| Click velocity | More than 30 clicks from one visitor in an hour |
| Tampered links | Publisher tracking signature missing or altered |
| Unapproved sources | Publisher not yet approved, or suspended |
Feed formats
Standard XML in, standard XML out.
Use the same formats the industry already uses, so connecting takes minutes.
Employers: importing jobs
Standard XML <source><job> or RSS <item>. Jobs are matched by reference number, so re-imports update instead of duplicating. Feeds can re-sync daily.
<?xml version="1.0" encoding="utf-8"?>
<source>
<job>
<title><![CDATA[QA Engineer]]></title>
<referencenumber><![CDATA[REQ-1042]]></referencenumber>
<url><![CDATA[https://careers.example.com/jobs/1042]]></url>
<city><![CDATA[Austin]]></city>
<state><![CDATA[TX]]></state>
<country><![CDATA[US]]></country>
<jobtype><![CDATA[fulltime]]></jobtype>
<salary><![CDATA[$90,000 - $110,000 per year]]></salary>
<description><![CDATA[What you'll do...]]></description>
</job>
</source>Publishers: receiving jobs
A private feed URL per publisher. Each <job> includes title, company, location, salary, description, a signed <url> and your <cpc>.
| Field | Meaning |
|---|---|
url | Tracked link. Use as-is; add &sub=yoursite to label clicks |
cpc | What you earn per valid click (or per application on CPA) |
bid_model | CPC or CPA |
referencenumber | Stable job ID for de-duplication |
date | Posting date (RFC 822) |
Add ?sub=homepage to the feed URL itself to tag every link in that copy of the feed.
Questions
Distribution FAQ
Hello! Want to see where your jobs would travel? I can explain, or book a quick demo and we'll show you live.
How fast does a new job reach partners?+
Can I choose which partners show my job?+
What happens when my budget runs out?+
Do you send jobs to the big job boards?+
Give your jobs more routes.
Free to start. Add a budget when you want reach.
