Jobeezy bots

Jobeezy is a job-search app for hourly and frontline workers — retail, warehouse, hospitality, healthcare support, trades and admin. Everything below serves one purpose: showing a real job seeker a job they can actually apply to, and then helping them apply.

The clients we operate

User-Agent	What it does	robots.txt
jobeezy-ingest/1.0	Reads public job listings so we can show them to job seekers — employer sitemaps, public job-board APIs, and structured schema.org/JobPosting data that sites publish for exactly this purpose. Read-only. It never submits a form, never logs in, and never touches anything behind authentication.	Rolling out — see below
JobeezyApplyBot/1.0	Completes a job application on behalf of a specific signed-in user who asked us to, using details from their own profile and résumé. It only ever visits the apply page for a job that user chose. It is not a crawler and does not browse, index or collect anything.	Not applicable — user-directed

The distinction matters. jobeezy-ingest is a crawler and is governed by your robots.txt. JobeezyApplyBot is a person’s own application being submitted through us — the same request they would have made by hand. robots.txt governs crawling, not a user filling in your form, so we do not treat it as a block on that path. If you would rather Jobeezy users not apply through your site at all, email us and we will honor it.

How jobeezy-ingest behaves

Stated precisely, because a vague promise is worse than none. These are in force today:

• It identifies itself. Every request carries the jobeezy-ingest/1.0 User-Agent above, with this page’s URL and a working contact address. We do not spoof a browser and we do not rotate identities.
• Rate limiting is cluster-wide, not per-machine. Requests to one host are spaced by a minimum interval coordinated across all of our workers, and we cap ourselves at 5 concurrent connections per host.
• We honor Retry-After when a host sends one, in both the delta-seconds and HTTP-date forms.
• No JavaScript execution, no login, no form submission, no paywall or anti-bot circumvention. If a page is gated, we leave it alone.
• We prefer your structured data. If you publish a sitemap or JobPosting JSON-LD we read that instead of crawling pages — cheaper for both of us.
• Most of what we read is not a crawl at all. The large majority of our listings come from public applicant-tracking-system APIs we are a documented client of, not from fetching employer web pages.

robots.txt — where we actually are

We are being deliberately literal here rather than claiming a posture we have not finished building.

• Our crawler reads and parses robots.txt, and currently evaluates and logs what a Disallow would block. Enforcement is being switched on progressively, lane by lane.
• Crawl-delay is not read yet. Our pacing is our own fixed per-host interval. If you need us slower than that, email us — we will set it.
• Until enforcement is fully on, email is the channel that works immediately, and we treat it as binding.

Adding this is still worth doing — it is what we enforce against as the rollout completes:

User-agent: jobeezy-ingest
Disallow: /

But if you want us gone today, send the email. We would rather you did that than assume a file we have not finished honoring.

Talk to a human

If our traffic is causing you a problem, email support@jobeezy.com — put crawler in the subject and include your domain and roughly when you saw it. We would much rather fix our behaviour than have you block us, and we will answer. If your jobs are listed and you want them removed, tell us and we will remove them; you do not need to justify the request.

What we do not do

• We do not ignore robots.txt, spoof another crawler’s identity, or hide behind rotating IPs to evade a block.
• We do not collect personal data from the sites we read. We read job postings.
• We do not re-sell scraped content. Listings are shown to job seekers and link back to you.
• We do not crawl anything behind a login or a paywall.

Last updated: July 2026.