WHY POSTINGPARITY / PUBLICATION RELIABILITY

The careers page is part of the job.

PostingParity is being built for agencies that maintain custom Webflow careers pages fed by Greenhouse. It compares published job posts with what the careers site presents, giving your team evidence when the two drift apart.

Prelaunch notice.

We’re still validating the live service. The page below describes the planned first offering.

01 / THE PUBLICATION GAP

A good-looking page can still give the wrong answer.

Someone visits your client’s careers page with a practical question: what can I apply for?

They should be able to find the relevant post, understand its title and location, and follow the application link to the right destination. A beautiful layout cannot make up for a missing opening. A fast-loading page cannot explain why a post still appears after it disappears from the public source board.

For the agency maintaining that page, these details sit between systems. Recruiting publishes in Greenhouse. The website presents those posts through a custom Webflow build. A feed, integration, or publishing process connects them.

Each part has a job to do. The question is whether the finished public page still agrees with the source it is supposed to reflect. That is the question PostingParity is designed to check.

02 / A FAMILIAR FAILURE MODE

The gap often looks ordinary.

Consider a hypothetical client site.

On Monday, a recruiting team publishes a new engineering post in Greenhouse and changes the location on an existing one. The website’s integration runs. The careers page loads normally.

But the new post never appears in the custom job list. The existing post still shows its previous location. A third listing’s Apply button points to a different post.

Nothing about that situation requires the whole website to go down. A quick visual inspection might see a tidy grid of plausible vacancies. A successful integration run might confirm that a process finished, without establishing that every expected post and application destination is correct.

The discrepancy may eventually reach the agency as a message from the client. By then, somebody has to reconstruct what was published, what the website displayed, and which part needs attention. PostingParity is intended to make that review more direct.

03 / DIFFERENT QUESTIONS

Availability and accuracy need different checks.

Uptime monitoring answers an important question: is the site responding?

A publication check asks something more specific: does this careers page represent the public job posts it is meant to show?

Both matter. They examine different failure modes. A healthy response can contain an incomplete list. A working link can lead to the wrong application. A post’s title or location can differ even when every component involved is online.

PostingParity’s proposed role is an independent, read-only comparison of the published source and the public result. Your existing ATS, CMS, integration, and agency workflow remain responsible for their own work. The additional check gives your team another way to notice when the result needs review.

04 / THE FIRST CHECKS

Four discrepancies worth being able to explain.

The first offering focuses on four concrete questions.

Is a published post missing?
The source board contains a post that the corresponding careers page should present, but the check cannot find its matching listing.
Does the page show a post absent from the source?
This is a publication discrepancy. It is not proof that the underlying job has closed. The recruiting team may have unpublished, replaced, or otherwise changed the post; a person needs to establish the reason.
Do title and location agree?
A mismatch gives the reviewer something specific to investigate, including whether a difference is intentional.
Does Apply point to the expected destination?
A clickable button is only useful if it takes someone to the application destination associated with the intended post.

“Something seems off” becomes a question the right person can answer.

05 / THE EVIDENCE TRAIL

Evidence should do some of the work.

An alert should give the reviewer a starting point.

For each supported finding, the intended evidence includes the post identity, the source and careers-page URLs, the expected and observed information, and the time of observation.

Those details matter because publication state changes. “This post appeared on this page at this time” is more useful than a loose claim that the website is wrong. The reviewer can open the relevant sources, assess whether the difference remains, and decide what action is appropriate.

Evidence also keeps the claim proportionate. A public post disappearing does not establish a hiring decision. A failed read does not establish that a listing is absent. Findings need to be interpreted in light of what was actually observed and matched.

The value is a clearer review, with less reconstruction before work can begin.

06 / THE WORKFLOW

How it would fit into agency work.

The intended workflow begins with the site you are authorized to manage.

  1. Verify ownership or authority.The agency establishes its authority to monitor the client site, identifies the relevant public Greenhouse board, and confirms which careers pages should correspond to it.
  2. Establish the comparison.The setup needs to reflect the actual publication arrangement. A deliberately selected subset of posts should not be mistaken for an incomplete mirror.
  3. Check on a six-hour schedule.Scheduled comparisons look for the supported publication discrepancies. This is periodic monitoring, so changes between observations may wait until a later check.
  4. Review the finding and its evidence.The team assesses the post, URLs, values, and observation time before deciding whether a change is needed.
  5. Make the correction through the existing workflow.The agency or recruiting team handles the relevant CMS, integration, or source-board change. A subsequent observation can help establish whether the public pages now agree.

An agency workspace, a client-site overview, and Owner, Admin, Operator, and Viewer roles are part of the planned working model. The aim is to make review practical across client sites while keeping the responsible people involved.

07 / SCOPE AND BOUNDARY

Built for the custom careers-page problem.

The initial focus is deliberately specific: agencies managing custom Webflow careers sites that mirror Greenhouse public job posts. That arrangement creates a separate presentation of the source material. It is where publication parity becomes a useful operational question.

A careers page that simply uses Greenhouse’s embedded board has a different setup. There may still be other things to test, but the custom CMS mirror is the first use case PostingParity is being built around. Support for additional ATS platforms is planned. It should not be treated as supported today.

The initial scope is also read-only. It excludes applicant records, résumés, candidate scoring, and writes to the ATS or CMS. PostingParity would surface evidence for review; it would not automatically edit a client’s website or decide what their recruiting team ought to publish.

It cannot guarantee hiring outcomes, search performance, or compliance. Its useful contribution is narrower and testable: help an agency examine whether the supported public job-post information lines up.

08 / THE PILOT

A pilot should earn its place in your process.

Another dashboard is worthwhile only if it helps your team do useful work.

That is why the first engagement is designed as a bounded pilot: 30 days, up to 10 sites, and 500 concurrent jobs, for CAD 149 plus applicable tax. There is no automatic renewal, and additional capacity requires consent. Full scope and capacity pricing belong on the pricing page.

A careful pilot gives both sides concrete questions to answer. Can the supported pages be read and matched reliably? Are the findings understandable? Does the evidence help the person responsible investigate and resolve a real discrepancy?

Live-service validation is still in progress. Reviewing the pilot is an opportunity to assess fit, rather than an assumption that every careers-site setup is ready to onboard.

Your agency already puts care into the careers page. PostingParity is being built to help carry that care into the job information it presents, long after launch day.

Review the pilot scope ↗