Carerix Webflow integration: auto-sync vacancies for Google for Jobs

A Carerix Webflow integration is simple to describe: Carerix decides which vacancies exist, and your Webflow site follows. New publication in Carerix, new page on the site. Changed text or salary, updated page. Publication ended, page gone from the live site. Then you tell Google about each change straight away, so you can sync vacancies to your website and get them into Google for Jobs fast, without anyone copying text between two systems.

I built exactly this for Einvigi, a Dutch staffing and interim agency. Their assignments live in Carerix. Their website runs on Webflow. Before, those were two separate worlds. Keeping the live vacancies on the site in line with the ATS was manual work, and new vacancy pages weren't set up for Google for Jobs or indexed quickly.

The rule: your ATS is the source of truth

Most sync problems start with two places where people edit the same thing. So the first decision is the most important one: nobody edits vacancies in Webflow. Recruiters work in Carerix, like they already do. The website is a mirror.

The sync runs as a scheduled scenario in Make. Here is what it does on every run:

1. Get a token. Carerix uses OAuth2 client credentials, so the scenario asks for a fresh access token first.
2. Ask Carerix what is live today. Through the Carerix GraphQL API it fetches every publication whose start date has passed, whose end date is in the future, and that isn't deleted. With it come the title, six HTML text blocks (intro, company, role, requirements, offer, how to apply), salary min and max, salary period, hours per week, work location, workplace type, job type and function category.
3. Read what is on the site. The Webflow CMS API returns the current vacancy collection.
4. Compare and route. A router splits everything into three branches.

The three branches:

• New in Carerix: create a CMS item and publish it. The slug is built from the title plus the publication ID, so it reads well and is always unique. The six text blocks are merged into one rich-text body with H2 headings, which is also what Google likes to see.
• Changed in Carerix: update and publish. To detect a change, each item carries a "change marker" built from the Carerix modification dates and a version tag. If the marker matches, the item is left alone. No pointless republishing of vacancies that didn't change.
• No longer active in Carerix: unpublish from the live site, then delete.

Never delete when the ATS returns nothing valid

This is the part I'd check first in any sync someone else built for you.

Think about what happens when Carerix has a bad minute. The API times out, or returns an error, or an empty list. A naive sync compares "nothing in Carerix" with "40 vacancies on the site" and concludes that all 40 should go. One hiccup and your careers page is empty on a Monday morning.

So the delete branch only runs when the Carerix call came back with a valid result. No valid answer, no deletes. The site stays as it was until the next run. It's one filter, and it's the difference between an automation you can forget and one that bites you. I wrote more about that kind of risk in who is liable when a no-code automation breaks.

Google for Jobs on Webflow: tell Google, don't wait for it

Publishing a page isn't the same as Google knowing about it. Left alone, Google crawls when it feels like it. For a vacancy that is open for a few weeks, that's too slow. Getting Google for Jobs on Webflow right comes down to three pieces.

1. Ping the Indexing API on every change. In October 2026 I added Google Indexing API calls to the scenario. After every create or update it sends a URL_UPDATED notification. After every delete it sends URL_DELETED. Each ping has an ignore-on-error handler: if Google refuses one, the sync carries on. Indexing is a bonus, the sync is the job. To start clean, I forced one refresh of all live vacancies so each one pinged Google once.

2. JobPosting structured data on the template. Google for Jobs reads JobPosting JSON-LD, so part of the setup is a snippet on the Webflow vacancy template with the title, description, dates, location and employment type. Some details matter more than you'd expect:

• Freelance maps to CONTRACTOR, remote work to TELECOMMUTE.
• Salary is only included when it's above 0. Google rejects a salary of 0, and a lot of ATS records have exactly that in an empty field.

3. Redirect expired vacancies instead of a 404. Once a vacancy is gone, its URL is still out there: in Google, in a LinkedIn post, in someone's WhatsApp. A dead 404 page loses that visitor. A small script on the 404 page recognises old vacancy URLs (including the /en/ versions) and sends people to the vacancy overview. They land on other open roles instead of an error.

What you can connect

Nothing here is specific to Carerix. If you're looking for a Carerix koppeling website (or the same thing for another ATS), the building blocks stay the same: authenticate, pull, compare with a change marker, route to create, update or delete, add structured data, ping Google, catch expired URLs.

Other recruitment systems this works with:

• Recruitee
• Bullhorn
• Otys
• Homerun

Other catalogues that follow the same pattern:

• Property listings from your real estate system to your site
• Courses and events, where dates decide what's live
• Product catalogues, from the system where products are managed to the CMS
• Locations, branches or anything else you keep in one system and show on a website

The website doesn't have to be Webflow either. The target just needs an API to create, update and remove items. You can see more builds like this on our work page.

When this is not the right approach

• You post three vacancies a year. Then copy and paste is fine. The setup only pays off when vacancies change often.
• Your ATS has a good careers page built in. Many do. If you're happy with it and SEO isn't a priority, link to it and skip the sync.
• People want to edit vacancy text on the website. Then you have two sources of truth, and every sync will eventually overwrite someone's work. Pick one place to edit.
• Your ATS has no usable API. Some systems only export files. That can still work, but it's a different and more fragile build.

The hard part is never the API call. It's deciding which system is the boss, and making sure a bad moment in that system can't empty your website. If your vacancies live in one system and your website in another, let's talk for 30 minutes.

Can I connect Carerix to Webflow?

Yes. A scheduled scenario reads live publications from the Carerix GraphQL API and creates, updates or unpublishes items in the Webflow CMS through its API. Carerix stays the source of truth and the website follows automatically.

How do I get my vacancies into Google for Jobs on Webflow?

Add JobPosting structured data (JSON-LD) to your Webflow vacancy template, with title, description, dates, location and employment type. Then notify Google through the Indexing API whenever a vacancy is created, updated or removed, so you don't have to wait for a crawl.

How do I sync vacancies to my website automatically?

Pull the live vacancies from your ATS on a schedule, compare them with what's on the site using a change marker, and route each one to create, update or remove. Only delete when the ATS returned a valid answer, so an outage can't wipe your careers page.

What should happen to an expired vacancy page?

Don't leave it as a 404. Unpublish it, tell Google with a URL_DELETED notification, and redirect the old URL to your vacancy overview so visitors still find open roles.

Does this work with Recruitee, Bullhorn, Otys or Homerun?

The pattern does: any ATS with an API you can read vacancies from. The authentication and field names differ per system, but the compare-and-route logic, structured data and Indexing API steps stay the same.