View
Read
Webflow
Integration

Webflow Greenhouse Integration - Three Ways to Run Your Careers Page

October 20, 2026
•
8
min read
By
Dennis Onalaja

What a Webflow Greenhouse integration is

A Webflow Greenhouse integration pulls your open roles out of Greenhouse and shows them on a page you control in Webflow, while applications still land back in Greenhouse. There are three ways to build it: the Greenhouse job board embed, a custom front end that reads Greenhouse's public Job Board API, or a sync that writes each role into a Webflow CMS collection. Greenhouse stays the system of record in all three, so recruiters keep working the way they already do.

The choice is not about features. It is about who owns the page, whether job pages can rank on your domain, and how much engineering time the careers page is allowed to take after launch.

Embed the Greenhouse job board and ship the same day

The embed is Greenhouse's own script. You drop it into a Webflow embed element, point it at your board token, and the list of open roles renders inside your page.

What you get:

  • A live careers page in an afternoon, with no developer on the ticket.
  • Roles that update themselves whenever a recruiter opens or closes a job in Greenhouse.
  • Application forms handled entirely by Greenhouse, so compliance questions, EEOC fields and source tracking keep working.

What you give up:

  • Design control. You are styling someone else's markup, and a Greenhouse release can change it.
  • Ranking on your own domain. Individual job pages usually live on the Greenhouse-hosted board, so the job detail URL, its metadata and its structured data sit there rather than on your site.
  • Page speed. The list renders after your page loads, which means a visible gap on slower mobile connections.

Pick this when you have a handful of roles, no engineering time, and the careers page is a stop on the way to a recruiter, not a channel.

Render roles yourself with the Job Board API

Greenhouse publishes a read-only Job Board API that returns your open roles as JSON. A script on the Webflow page fetches that feed and renders it into your own components, so the list looks like the rest of the site and you decide how roles are grouped, filtered and sorted.

Two things catch teams out here.

Keep the application submission server-side

The read endpoints are public, but submitting an application through the API needs a Job Board API key. A key in client-side JavaScript is a key you have published. Route submissions through a serverless function or your own middleware, or send candidates to the Greenhouse-hosted application form and keep the key out of the browser entirely.

Client-side rendering still leaves job pages off your domain

Fetching and rendering in the browser gives you design control, not indexable job pages. If the role detail page matters for search, you need the content to exist as a real page before the crawler arrives. That is the third option.

Sync Greenhouse jobs into the Webflow CMS

A sync writes each Greenhouse role into a Webflow CMS collection through the Webflow Data API. A scheduled job or an automation platform checks the Greenhouse feed, creates new items, updates changed ones, and unpublishes roles that have closed.

This is the version that behaves like the rest of your marketing site:

  • Every role gets a real URL on your domain, with your layout, your navigation and your internal links.
  • Job pages can carry JobPosting structured data, which is what makes a role eligible for job search results and easier for AI answer engines to quote. Our guide to structured data in Webflow covers the markup.
  • Marketing can edit copy around the job listing without touching Greenhouse or waiting on a developer. At M13 the same pattern cut work that used to take 3 weeks down to 24 hours or less.
  • The collection is reusable. Filter by team, feature three roles on the homepage, or build a department landing page from the same data. If you are new to modelling collections, start with the guide to Webflow CMS development.

The honest trade-off is that a sync is a system, and systems need an owner. It has to handle closed roles, avoid duplicates when a job is reposted, respect your Webflow plan's CMS item limits, and back off cleanly when the API rate-limits it. Build it with logging and an alert, not as a one-off script on someone's laptop. The middleware pattern is the same one used for a Webflow HubSpot integration, so if you already run one, you have the plumbing.

How to choose between the three

  • Choose the embed when speed matters more than the page and you have no engineering time this quarter.
  • Choose API rendering when you want the list to match your brand but job detail pages are not a search channel for you.
  • Choose the CMS sync when you hire continuously, when recruiters compete for candidates on search, or when the careers page is part of your employer brand.

One useful test: if a hiring manager has ever asked why a role does not show up in Google, you want the sync.

What it costs and who builds it

A Greenhouse embed is free to add and takes an hour. API rendering is a small front-end build. A CMS sync is the real piece of work, because it needs middleware, error handling and a test run against a live board.

Ammo's published rates give you a planning number. Growth Support, for companies under 100 employees, is "Starting at $4,800 / quarter" with a fixed scope and a 90-day usage window. Growth Partner, for companies with 100 or more employees, is "Starting at $5,200 / month". Plans are month-to-month, and new client onboarding is limited to 8 per month across all plans. Pricing is subject to change.

A careers page rebuild that includes the sync, the templates and the structured data is closer to a project than a ticket. Landing pages start around $10K and full builds run $70K-150K+, again subject to change. If you want the integration scoped and built alongside the rest of the site, that is what a Webflow development agency handles.

What breaks after launch and how to catch it

Most careers pages fail quietly. These are the four failures worth monitoring from day one.

Closed roles that stay live

A candidate applying to a filled role is a bad first impression and a support ticket. Your sync needs an unpublish path, not only a create path, and someone should get an alert when a sync run fails.

Lost source tracking

Greenhouse attributes applications using the gh_src parameter on the apply link. Rewrite that link in a custom template and you can strip the parameter, which makes your sourcing report wrong without anyone noticing. Test one application end to end before you ship.

Missing structured data

A job page with no JobPosting markup is invisible to job search surfaces. Add the markup to the template, not to individual items.

Slow mobile rendering

Client-side job lists are an extra request on top of your page. Only 48% of mobile websites pass all Core Web Vitals, according to HTTP Archive Web Almanac data from July 2025, and Google and SOASTA found in 2017 that mobile bounce probability rises 123% as load time goes from 1 to 10 seconds. A careers page that stalls loses candidates the same way a pricing page loses buyers.

See what your current site is costing you

If the careers page is one of several places where marketing waits on engineering, the integration is a symptom rather than the problem. Run the free GTM audit. It models the return on fixing your site using the Forrester TEI study commissioned by Webflow, which found 332% ROI over three years and $2.12M net present value with payback in under six months for Forrester's composite organization. Ammo's audit risk-adjusts those benefits down 15% and caps modeled ROI at 332%, so the number you get is conservative by design.

Frequently asked questions

Does Greenhouse have an official Webflow integration

No. Greenhouse does not publish a native Webflow app. Every working setup uses one of the three routes above: the Greenhouse job board embed, the public Job Board API, or a sync into the Webflow CMS through the Webflow Data API. Check the current Greenhouse developer documentation before you build, since endpoint behavior and board settings change.

Will job pages rank on my domain

Only if the job content exists as a page on your domain. The embed and most client-side API renders leave the job detail page on the Greenhouse-hosted board. A CMS sync creates a real Webflow page per role, which can carry your metadata and JobPosting structured data.

Do candidates still apply inside Greenhouse

Yes, in all three setups. Greenhouse remains the applicant tracking system, and your recruiters keep their existing workflow, scorecards and compliance fields. Webflow only controls what the candidate sees before they apply.

How long does a CMS sync take to build

Plan for a scoped build rather than an afternoon. The work is the middleware, the field mapping, the unpublish logic and a live test against your real board, not the Webflow side. Scope it with whoever owns your site before you commit to a hiring campaign date.

What happens if the sync fails

Nothing visible, which is the danger. Your last successful set of roles stays published until the next run succeeds. That is why the build needs logging and an alert to a channel a human reads, so a stale board is caught in hours rather than weeks.

Can we start with the embed and move to a sync later

Yes, and it is a reasonable sequence. Ship the embed to get the page live, then replace it when hiring volume or search performance justifies the build. Keep the careers URL the same so you do not lose the links pointing at it.

Table of contents

[
Faqs
]

Got questions for us? We got you!

No items found.

Let’s Build What’s Next

Whether you're building your first product or evolving a mature platform,
 we’d love to help you  craft what’s next.