GhostPost.us

What GhostPost.us can actually observe.

Coverage claims are easy to make and hard to verify, so this page states the whole inventory: every source read in production today, every source that needs the provider's permission first, and every source GhostPost.us deliberately declines to read. There are 16 sources on this list and 5 of them are read today.

A source GhostPost.us does not read is a gap in observation, never a finding about an employer. Nothing on this page implies an employer is or is not posting anywhere GhostPost.us cannot see.

What each status means

Observed today: GhostPost.us reads this source now, in production, with no further permission needed.
Requires the source's permission: The source publishes a sanctioned way in — a registered key or a partner agreement. Until that is in place, GhostPost.us reads nothing here.
GhostPost.us does not read this: The source's own rules prohibit automated reading of its listings. GhostPost.us respects that and never reads it. Absence here is never evidence about an employer.
Not built yet: Nothing technically or legally blocks this, but the collector does not exist. Nothing is claimed about it.

Employer-owned

Public job board found from a career site

Observed today

What GhostPost.us can see: Which public job board an employer's own career site is built on, so the board itself can then be read directly.
Access controls: Reads only the employer's own public career-site page.
How it is read: Reads the career-site page and identifies the public board it points to. Private applicant-tracking data is never accessed.

Employer career site (plain pages)

Observed today

What GhostPost.us can see: Openings listed directly in the page a browser receives, on the employer's own site, including pages that continue across several numbered pages.
Access controls: The employer's own public site. Same-site links only.
How it is read: Reads the page as delivered. It does not run the site's scripts, so a career site that builds its list after loading returns "could not check" — never "no openings". Field-tested limit: sites that identify each opening only by a tracking number in the address are not separated correctly today.
What broader coverage would take: Reading script-built career sites needs a rendering step that does not exist in the product yet. It is on the plan, not in the product.

Machine-readable job records in employer pages

Observed today

What GhostPost.us can see: The job record many hiring platforms publish inside the page for search engines: title, location, department, posting date, closing date, employment type and pay range where the employer published one. Often present even when the visible list is built after loading.
Access controls: Published by the employer in the page GhostPost.us already read. No extra request is made and no extra permission is needed.
How it is read: Reads the schema.org JobPosting records embedded in pages already fetched during the career-site read. Only records pointing at the employer's own site are kept. A record present is an observation; a record absent is "could not check", never "no openings".
What broader coverage would take: Nothing. It reads what an employer chose to publish. Employers who publish no such record are unaffected.

Employer site maps and job feeds

Observed today

What GhostPost.us can see: The addresses of individual job pages an employer lists in its own site map or job feed — including on sites whose visible list is built after loading.
Access controls: Files the employer publishes for machines. The site's own robots rules are read first and obeyed; a disallowed address is never requested.
How it is read: Reads robots.txt, follows the site maps it declares (one level of index), and falls back to the standard site-map and feed addresses. Same-site only, with a request and address ceiling. Titles are derived from the address, never invented.
What broader coverage would take: Nothing. A site map can lag the live site, so it is never treated as a complete read of the employer's openings.

Script-built hiring sites (Workday, iCIMS and similar)

Not built yet

What GhostPost.us can see: Nothing today. These sites build their opening list after the page loads, so a plain read returns "could not check".
Access controls: Publicly visible to a person in a browser. Access rules vary by employer and provider and are checked per employer.
How it is read: No collector exists.
What broader coverage would take: A rendering step that loads the page the way a browser does, or an employer-authorized feed.

Public job board

Public job boards (Greenhouse, Lever, Ashby)

Observed today

What GhostPost.us can see: The employer's complete public opening list as the board publishes it: title, location, department, employment type, posting address, and the board's own total.
Access controls: Published openly by the board provider for public job-board display. No login, no key, no private applicant data of any kind.
How it is read: One request to the board's public listing feed per look. The largest single read verified so far is 2,336 openings for one employer, returned complete in one request.

Job distribution site

Adzuna

Requires the source's permission

What GhostPost.us can see: Nothing until a key is registered. With one, it shows where an employer's postings appear on Adzuna and how those copies read.
Access controls: A registered key through Adzuna's own developer program. Free entry tier. Reading their pages directly is not permitted, and GhostPost.us does not.
How it is read: The collector is built and runs on every scan. Without a key it records the source as not searched — never as "no postings". One keyed request per employer per look.
What broader coverage would take: Register the key. No further build work.

Careerjet

Requires the source's permission

What GhostPost.us can see: Nothing until a partner ID is registered.
Access controls: A free partner ID through Careerjet's own program. Their robots file disallows automated reading of the search and listing pages, so only the sanctioned interface is used.
How it is read: The collector is built and runs on every scan, recording the source as not searched while no partner ID is held.
What broader coverage would take: Register the partner ID. No further build work.

Jooble

Requires the source's permission

What GhostPost.us can see: Nothing until a key is registered.
Access controls: A registered key through Jooble's own program. Their robots file disallows automated reading of the search pages, so only the sanctioned interface is used.
How it is read: The collector is built and runs on every scan, recording the source as not searched while no key is held.
What broader coverage would take: Register the key. No further build work.

Indeed

GhostPost.us does not read this

What GhostPost.us can see: Nothing. GhostPost.us does not read Indeed.
Access controls: Indeed's robots file disallows automated access to its job and listing paths, and its terms prohibit automated collection.
How it is read: No request is made.
What broader coverage would take: An approved place in Indeed's own partner program. Whether that program admits a product like GhostPost.us is unconfirmed.

LinkedIn Jobs

GhostPost.us does not read this

What GhostPost.us can see: Nothing. GhostPost.us does not read LinkedIn.
Access controls: LinkedIn's robots file disallows all automated access and carries an explicit notice that automated reading without written permission is prohibited.
How it is read: No request is made.
What broader coverage would take: A signed LinkedIn partner agreement and an approved integration.

Glassdoor

GhostPost.us does not read this

What GhostPost.us can see: Nothing. GhostPost.us does not read Glassdoor.
Access controls: Glassdoor's robots file disallows its job-view and search paths, and its terms prohibit automated collection. No self-serve interface is published.
How it is read: No request is made.
What broader coverage would take: A direct agreement with Glassdoor.

ZipRecruiter

GhostPost.us does not read this

What GhostPost.us can see: Nothing. GhostPost.us does not read ZipRecruiter.
Access controls: ZipRecruiter's robots file disallows its job and search paths, and its terms prohibit automated collection.
How it is read: No request is made.
What broader coverage would take: An approved place in ZipRecruiter's partner program.

Search & indexes

Google job results

Not built yet

What GhostPost.us can see: Nothing. There is no published way to ask Google's job results what an employer currently shows.
Access controls: No public interface exists for querying these results.
How it is read: Not a source GhostPost.us can read. Google's job results reflect posting details published on other sites, which GhostPost.us would read at those sites instead.
What broader coverage would take: Nothing available today.

General search indexes

Not built yet

What GhostPost.us can see: Nothing.
Access controls: Free programmatic search access has been retired by the major providers; current access is paid and contractual.
How it is read: Would add nothing beyond what the employer's own board and career site already show.
What broader coverage would take: A paid search agreement, for little added evidence value.

Government

Government job portals

Not built yet

What GhostPost.us can see: Openings on portals that deliver their list as a plain page can be read; most large state portals build their list after loading and return "could not check".
Access controls: Public portals. Read only where the portal's own rules allow it.
How it is read: The career-site path applies where the list arrives as a plain page. Field-tested: the largest plain-page portal found lists roughly 1,760 openings on a single page.
What broader coverage would take: The same rendering step as other script-built sites, plus separating openings identified only by a tracking number in the address.

How this list is kept honest

A source moves to “observed today” only when the product actually reads it in production. Access rules on this page come from each provider's own published rules and terms, checked directly rather than assumed.

Every look records what was attempted, not only what succeeded. A source that could not be read appears in the record as unread, with the date and the reason.

How GhostPost.us observes Request access

← Back to GhostPost.us