//

Have you ever wondered why one vacancy immediately appears at the top of Google for Jobs, while your perfect job lingers somewhere in digital no man's land? You scroll, click, ask ChatGPT for help, and yet you miss opportunities. Frustrating, isn't it?
In this blog post, I will show you how findability really works. You will discover what role structured data, smart titles, and open accessibility play. And yes, I'll also show how Spadework lends a hand with the Vacancy Collector and the Vacancy Transformer. By the end, you'll know exactly which buttons to push to make your vacancies visible to Google, ChatGPT, and any other smart LLM.
Why do you keep seeing the same vacancies?
Imagine this: you type “junior data analyst Amsterdam” into Google. Take three guesses which vacancies you get. Exactly, the ones from the well-known names. Open ChatGPT right after? Big chance you stumble upon the exact same titles again. It almost feels like the rest of the web doesn't exist.
Time for a reality check. There are two major myths:
Only big brands rank at the top.
You need outrageously expensive tools to change that.
Both are untrue. It's mainly about the way you present your vacancy. Let's see how that works.
Google for Jobs: the engine room in plain English
Google sees a vacancy as a distinct type of page. Compare it to a recipe: there, too, Google wants to know the preparation time and the ingredients. With vacancies, the bot looks for specific schema.org labels. Those labels tell:
where the job is
what salary comes with it
when the position was posted
Without those labels, Google cannot be sure it's a vacancy. So you're immediately falling behind.
The essential labels you really need
title
description
date posted
employment type (part-time/full-time)
workplace
salary
Missing one? Then you'll almost always miss out on the blue job box.
Classic mistakes that still happen
The vacancy is hidden behind a login.
The text is only in a PDF.
The recruiter is in a hurry and types joblocation instead of jobLocation.
The publication date is weeks in the past.
Side-by-side comparison
Situation | Chance of visibility |
|---|---|
Open HTML + correct schema | High |
PDF only | Low |
Login required | Almost zero |
Think of it as a library. A book without a label ends up somewhere in the back room. With a clear label, it's right on the shelf, ready to be borrowed.
ChatGPT and other LLMs: how a language model views your vacancy
LLMs run on two sources:
training data that is sometimes months old
live web data via a browser-like function or plugin
Is your vacancy behind a paywall? Then the model won't see it. Has the publication date already expired? Then the bot will prefer something else. Simple as that.
Training data vs. live data
training data: static, less up to date
live data: fresh, but only accessible if the text is publicly available online
Prompt example
Only vacancies that are open and properly labeled end up in the response. The rest remains invisible.
Visibility revolves around three links
Structure
Use schema labels and break up the text with headings and bullet points.Title and metadata
Go for a title people actually type in. “Customer Success Manager (32-40 hours)” performs better than “Customer Success Hero”.Accessibility
No paywall, but do provide a mobile version. Ensure the bot can reach the page without hurdles.
Practical check with Spadework
Spadework scans a large volume of Dutch vacancies daily. In doing so, the same patterns keep surfacing:
Many texts are missing at least one required label.
Salary information is often left out, even though Google loves it.
A portion of the vacancies is behind a login and therefore invisible to both Google and ChatGPT.
How Spadework tools help
The Vacancy Collector gathers vacancies from all kinds of sources and neatly arranges them in one overview. No more scrolling stress.
VacancyTransformer automatically fills in missing labels and polishes the title. That saves manual work as well as time.
The result? Fewer missed clicks and the right candidate faster.
What will change in the coming years?
More and more ATS systems are offering direct feeds to LLMs.
Job seekers are searching more often by skills: “jobs where I can use Python” instead of just a job title.
Those who provide open, structured data today will be ahead tomorrow.
Checklist for tomorrow
Put every schema label in your vacancy.
Choose a searchable job title.
Leave at least a teaser page publicly accessible.
Update old vacancies with a fresh date.
Test your page in Google’s Rich Results Test and via a ChatGPT prompt.
Time to bring your vacancy out of the shadows
Curious how your vacancies can become more visible to Google, ChatGPT, and other AI tools?
Schedule a demo with Spadework to see the Vacancy Collector and Vacancy Transformer in action, or check out our website for more information.


