For site operators

Jobeezy bots

Jobeezy runs a small number of automated clients. This page exists so anyone who sees one in their logs can identify it, understand exactly what it does, and control or stop it — without having to guess or block a whole IP range.

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-AgentWhat it doesrobots.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. Honored
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

  • robots.txt is fetched and obeyed before we request anything from a host, and cached so we do not re-fetch it for every page.
  • One request at a time per host, with a minimum interval between them. Pacing is coordinated across all of our workers, not per-process — so the limit is real, not per-machine.
  • We honor Retry-After in both the delta-seconds and HTTP-date forms.
  • 429, 403 and 5xx mean stop. Repeated push-back trips a per-host circuit breaker and we back off that host entirely rather than retrying into it.
  • 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.

Blocking us

Add this to your robots.txt and we stop, usually within an hour:

User-agent: jobeezy-ingest
Disallow: /

To slow us down instead of stopping us:

User-agent: jobeezy-ingest
Crawl-delay: 10

To keep us out of one section only:

User-agent: jobeezy-ingest
Disallow: /internal/

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.