← Field notes// field note

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

Your ATS already knows which jobs are live. Your website should follow it, and Google should hear about every change the moment it happens.

October 2026

7 min read

A Carerix website integration makes Carerix the single source of truth: a scheduled scenario reads live publications through the Carerix GraphQL API and creates, updates or unpublishes Webflow CMS items. Every change pings Google's Indexing API, the vacancy template carries JobPosting structured data, expired URLs redirect to the overview, and applications flow back into Carerix.

Carerix Webflow integration: auto-sync vacancies for Google for Jobs, QuikCode field note

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 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, every 15 minutes from 7 in the morning until midnight. Every run goes through four steps:

  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:

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 what lets you stop watching the sync. 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. 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:

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.

Applications back into Carerix

The website also works the other way. The application form on each vacancy page posts to a second scenario. It looks up the candidate in Carerix by email or mobile number, creates a new candidate only if there is none, attaches the CV and the motivation letter, and creates a match with the publication they applied for. The recruiter finds a complete application on the right vacancy in Carerix, and the source says it came from the website. How that works in the API is in the Carerix API note.

Carerix and WordPress

The same setup works for a WordPress site. Carerix has its own WordPress plugin for application forms, which is a good start if a form is all you need. To get vacancies in as real pages, with your own design and JobPosting data, the sync writes to the WordPress REST API instead of the Webflow CMS API. The compare, route and ping logic stays the same.

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:

Other catalogues that follow the same pattern:

The website doesn't have to be Webflow either. The target just needs an API to create, update and remove items. What I build around Carerix is on the Carerix integration page, and more builds are on the work page.

When this is not the right approach

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. For everything else the API offers, see the Carerix API note.

Can I connect Carerix to WordPress?

Yes. Carerix has a WordPress plugin for application forms. To show vacancies as real pages in WordPress, the same sync works through the WordPress REST API instead of the Webflow CMS API.

How do I get my vacancies into Google for Jobs?

Add JobPosting structured data (JSON-LD) to your 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.

Do applications from the website end up in Carerix?

They can. The form posts to a webhook that looks up or creates the candidate in Carerix, attaches the CV and motivation letter, and creates a match with the vacancy they applied for.

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.

Got a process that should be software?

Book a call
© 2026 QuikCode · software for better operations