For Possible Finance

Getting your jobs seen by ChatGPT, Claude and Google

Your careers page works well for people. AI tools and search crawlers can't see the jobs on it. Here is why, the fix, and the one choice we need from you. Sam does all the work.

The problem, in one minute

  1. Your jobs live in Ashby. When a person opens the careers page, a script loads them.
  2. AI crawlers (ChatGPT, Claude, Perplexity) don't run scripts. To them, the job list is empty.
  3. So when someone asks an AI "who is hiring?", your open roles don't show up.

The fix

Put a ready-made copy of the jobs inside the page itself, so crawlers can read it with no script. People keep seeing the live list straight from Ashby.

People: always live

When someone opens the page, the script fetches the jobs from Ashby right then. They always see the current list, with no waiting on us and no errors.

AI crawlers: the copy from the last publish

Crawlers read the copy stored in the page. It's as fresh as the last time the site was published.

How the copy gets there

1

Fetch the jobs

Something has to ask Ashby for the latest jobs and save them in our Framer component. A site can't do this by itself, so a small helper does it (two ways below).

2

Publish the site

Saved jobs only live inside Framer's editor until the site is published. Publishing turns them into plain HTML on the live page.

3

Crawlers read it

From then on, crawlers see those jobs in the page, until the next publish.

No extra publishing needed

Your team already publishes the site for other changes: news, CMS posts, edits. Each normal publish carries the newest jobs to AI crawlers with it. Nobody has to publish just for jobs.

Pick one way to fetch the jobs

Recommended

Option 1: Automatic (free Cloudflare account)

A tiny free script on Cloudflare checks Ashby every hour and saves the latest jobs into the Framer component. Nobody on your team has to remember anything.

What you do (about 5 minutes):

  1. Go to dash.cloudflare.com/sign-up and create an account with a work email. The free plan is all that's needed, and you don't have to enter a card.
  2. Open Manage Account, then Members, then Invite. Enter Sam's email and choose Administrator.
  3. Tell Sam. He does everything else.

Cost: $0, now and later. Cloudflare doesn't charge for adding a team member, and the script fits inside the free plan. You can remove Sam whenever you like.

Your site stays where it is. It doesn't move to Cloudflare, and your domain and DNS aren't touched.

Option 2: Manual (no Cloudflare)

Sam adds a "Sync jobs" button inside Framer. When your jobs change, someone on your team clicks it. No other account or service is needed.

What you do:

  1. Tell Sam you prefer this option.
  2. When jobs change: open the site in Framer and click Sync jobs. The next publish carries it live.

Cost: $0 to run. Sam builds the button, which takes a little extra work compared with Option 1.

The catch: if nobody clicks Sync, the copy goes out of date.

Not sure? Pick Option 1. It takes you 5 minutes once, and then it runs by itself.

The result, either way

People: always live. AI: as of the last publish.

Visitors always see Ashby's current jobs. AI crawlers see the jobs as of your last publish, and every normal publish by anyone on the team refreshes them. That is the most reliable setup for a Framer site, and it costs nothing.