How Jobiba verifies jobs

Jobiba lists jobs from three kinds of source.

• Employer career sites and applicant tracking systems. Jobiba reads the public job-board interface that employers publish through Greenhouse, Lever, Ashby, Workday, Personio, Teamtailor, Recruitee and Pinpoint, and reads some company career pages directly.
• Employers posting directly. Employers add jobs in the Jobiba employer area.
• Employer and partner feeds. XML, JSON or CSV feeds that an employer or partner submits. See Partner Job Feeds.

• Before each scheduled fetch of a career-site feed, Jobiba checks that host's robots.txt (a successful read is reused for the rest of that run; a failed read is retried after a minute). If it disallows the path for all crawlers or for Jobiba, Jobiba does not fetch it, pauses that feed and does not retry or work around the refusal. A paused feed is re-enabled only with the site owner's written permission.
• A host that has no robots.txt file (the server answers that it is not found or not allowed) is treated as imposing no restriction. If the file cannot be read because the server returns an error, asks Jobiba to slow down or does not answer, Jobiba does not fetch that feed in that run. The feed is not paused; Jobiba tries again in a later run.
• Jobiba's fetcher identifies itself as Jobiba-Bot/1.0 and, when it reads a job list, adds a link to https://jobiba.com. Feed fetches to the same host are spaced at least 2 seconds apart.
• Feeds are refreshed every 24 hours by default; a Jobiba administrator can set a different interval per feed.

Each fetched record becomes a structured job (title, company, description, location, apply link, work mode, job type and pay) and is then checked.

• Records with no usable job title are skipped.
• Records that look like something other than a job, judged by fixed title and text rules, are rejected: product or service advertisements, local-service ads, property listings, adult content, informational articles and lead ads built around a phone number.
• Employer-feed jobs whose text asks applicants to pay a fee or hand over banking credentials are rejected at import. A job from any source whose text contains that language is left out of Jobiba's job search results.
• Locations are resolved to a city, state and country. A job that fails the completeness checks (a description under 160 characters or only placeholder text, or no resolvable country) is kept, but its page is marked noindex and it is left out of the sitemap and of Google job structured data until it is complete.
• Jobs that employers post directly are not read from a career site, so the import checks above do not run on them. The completeness checks for indexing and the search filter for applicant-payment language apply to every job.

• Each job carries a stable ID within its feed. Seeing the same ID again updates the existing listing instead of creating a copy, and a changed posting is processed again.
• In employer feeds, jobs with the same employer, title and place are collapsed into one.

• The pay shown as a job's own pay is what the posting, or the employer's structured pay data, states. Pay that fails Jobiba's currency and plausibility checks is corrected by fixed rules or dropped. See Methodology.
• When a posting states no pay, a job page may show a market range for comparable roles. It is labelled as a Jobiba estimate and as not provided by the employer.
• In Google job structured data, datePosted is the posting date the source published (or, for jobs posted directly on Jobiba, the time the employer posted it). Jobiba's own first-seen time is never used as the employer's posting date, and a scraped job with no source posting date gets no job structured data.

• Jobs read from career sites roll a 30-day window. The window is counted from the later of the source's posting date (or, when there is none, the day Jobiba first saw the job) and the last time the source listed the job. A job the source keeps listing stays live; one that is not confirmed for 30 days expires.
• Complete lists. For sources that return their whole list (Greenhouse, Lever, Ashby, Personio, Teamtailor, Recruitee and Pinpoint), a job missing from 3 successful complete fetches in a row is closed.
• Partial lists. Some sources cannot prove a job is gone, for example Workday career sites, which return a partial list, and some custom career pages. For these a job that is no longer listed can stay up to 90 days after Jobiba first saw it.
• Direct and feed jobs. A job posted directly on Jobiba expires on the date the employer sets; with no date it leaves search 90 days after it was posted. A job from an employer feed expires at the valid-through date the feed gives, if any, and is retired when the feed has not refreshed it for 45 days.
• Outage guard. If fewer than half of the active feeds fetched successfully in the last 48 hours, Jobiba pauses expiry of career-site jobs, so a Jobiba-side outage cannot empty the site.

A retired job leaves Jobiba search. Its page stays reachable and says the posting has expired. Where Jobiba had earlier told Google about the page it sends a removal notice, and Jobiba submits live and removed states of job pages to IndexNow (Bing and other participating search engines). A job that expired and that the source lists again is reopened.

• Logos, websites and descriptions are filled in only where they are missing, and never on a company profile that has been verified. Jobiba looks for the company's own domain in its job postings (apply links, contact-email domains, the career site's own address) or, failing that, builds a candidate from the company name, and scores it against the name. Applicant tracking systems, job boards, link shorteners and free-mail domains never count as a company's website.
• Unless the website was supplied by the company or an administrator, or is backed by strong evidence repeated across its postings, the site is used only if its own page names the company; otherwise the match is parked for review and nothing is taken from it. Logos come from the company's website or, where Jobiba has a logo service configured, from that service looked up by the chosen domain.
• A hiring email is shown only if it is a role inbox on the company's own domain (careers@, jobs@, hr@ and similar, or a general inbox such as info@), found on its site or in its own job postings. Personal addresses are never shown and addresses are never guessed.

Verification here means automated checks on data as it arrives and while it is live, plus the removal of jobs that sources stop listing. It is not a person checking every employer or every vacancy. These checks reduce, but cannot remove, the chance of an inaccurate, filled or fraudulent listing.

A legitimate employer does not ask you to pay to apply or to share passwords, one-time codes or banking details. See Trust & Safety.

Email [email protected] with the job URL and what is wrong, or use the contact page. Do not include passwords or access tokens.