JobsizyBot

What it reads

Job openings: from applicant-tracking systems' public job-board feeds, from job pages marked up for search engines, and from employers' own careers sites. Public facts about organisations: from an organisation's homepage, about page and careers page, the structured data it publishes for search engines (schema.org Organization markup, OpenGraph and meta tags), such as its name, logo, website, size, industry, the countries it works in and a short description. Never people's profiles, team or leadership pages, or people's contact details: we remove e-mail addresses and phone numbers before we store anything, except an organisation's own published role address (such as careers@ or contact@), which we keep only to write to it about how JobsizyBot reads its site; and we keep no page's text beyond that short description. It never reads job-advertising sites that list other employers' jobs, such as SEEK or Indeed, nor professional networks.

How it behaves

• It identifies itself as JobsizyBot.
• It follows robots.txt, which it rereads every day. If robots.txt keeps crawlers off your career site, JobsizyBot does not read that site's jobs through the data the site itself loads either, and takes any it already lists off the board.
• It sends one request at a time to a site, with a pause between requests, and backs off when a site asks it to (HTTP 429 or 503 with Retry-After).
• It asks only for what changed since its last visit when the site supports it.
• On an organisation's own site it reads only the homepage, the about page and the careers page, and its contact page only while we need the address it publishes for writing to it about access, and visits an organisation at most once a week. The one other request is its security.txt, read once when we first need that address.
• It honours a page's own robots meta tags and X-Robots-Tag headers, including those addressed to JobsizyBot (noindex, nosnippet, noimageindex), and TDMRep reservations of text and data mining.
• If a site answers 429 or 403, or shows a bot challenge, it stops reading that site's organisation pages for at least a week, and it never tries to get around a challenge.

Where it comes from

Requests come from 202.172.122.117.

Check that a request is ours

Its requests are signed with HTTP message signatures (Web Bot Auth): each carries Signature, Signature-Input and Signature-Agent headers, the Signature-Agent names https://jobsizy.com, and the public keys that verify them are published at https://jobsizy.com/.well-known/http-message-signatures-directory.

To check a request you have seen, or to ask about JobsizyBot, e-mail partners@jobsizy.com.

Stop it reading your site

To keep your organisation's pages from being read at all, but not your jobs, disallow JobsizyBot for those paths in robots.txt. A robots meta tag of noindex for JobsizyBot (<meta name="jobsizybot" content="noindex">) limits what it keeps from that page to your organisation's name, website, identifiers and careers link.

Add a robots.txt rule for JobsizyBot, or ask us to remove your company's jobs and its profile: employers can use the opt-out form or e-mail support@jobsizy.com from an address on their company's domain. We act within one working day.

Ask us to stop, or to read you

E-mail partners@jobsizy.com from an address on your organisation's domain. Ask us to stop reading your site, or, if your site turns automated readers away and you would like your jobs on Jobsizy, tell us how you would like them read: by letting JobsizyBot through, or with a feed of your jobs. No form is needed.