Google for Jobs in 2026: Publishing a Job Opening That Surfaces (and What the TrueCalling Job Board Does)

Most job searches now start on a search engine, not on a job board. When a candidate types "React developer Manchester", Google shows a block of openings above the first classic result: that is Google for Jobs. Most openings published by SMEs and agencies never appear there — not because they are bad, but because the page carrying them does not contain the structured data Google expects. This guide explains what Google actually reads, the fields that make or break indexing, the mistakes that make an opening vanish, and what the TrueCalling job board does concretely so that every role published from the platform surfaces with no extra work.

Google for Jobs is not a job board

It is an aggregator. Google does not ask you to post an ad: it crawls web pages, looks for JobPosting markup in JSON-LD, and assembles its results from what it finds. An opening is therefore visible in Google for Jobs if, and only if, it lives on a public, indexable page that describes the role with that markup. A PDF, an image, or a listing page grouping twenty openings does not surface. The rule is strict: one page per opening, one JobPosting per page.

The practical consequence is simple. The job board you publish on matters less than the quality of the final page. An opening published on an in-house site with complete markup outranks the same opening dropped on a generalist platform that renders it behind a script, without salary and without an expiry date.

The six fields that make or break indexing

1. The exact job title. "Senior Data Engineer", not "Senior Data Engineer — Permanent — London — Urgent". Google treats the title as a title, not a slogan; bolted-on keywords degrade the match instead of improving it.
2. The full description, in HTML. The entire text of the opening — mission, profile, qualifications — must sit in the markup's description field, not just on screen. A description truncated to two sentences is the number one cause of non-display on otherwise correct openings.
3. Posting date and expiry date. datePosted is mandatory; validThrough is not, but an opening with no expiry is treated as stale as it ages, and one whose expiry has passed is removed — and can trigger a manual action against the whole site if it lingers.
4. The hiring organisation, with logo. hiringOrganization must name the real employer. The logo is not mandatory but it gates the rich display; without it the opening shows as plain text among illustrated cards.
5. Location, or explicit remote. jobLocation with a city and country code for an on-site role; for a remote role, jobLocationType: TELECOMMUTE plus the country of eligible applicants. A role spelled out as "remote" in the description but without that marker is classified as an on-site role with no address — that is, nowhere.
6. The salary range. baseSalary remains optional for Google, but it has become decisive for candidates — and the EU Pay Transparency Directive, to be transposed by 7 June 2026, requires informing applicants of the range before the interview. You may as well publish it in the ad.

The mistakes that make an opening vanish

• The same opening under several URLs. A multilingual site serving an identical opening under /fr, /en and /de with no canonical ends up with three competing pages, none of which gets picked.
• The filled role that stays online. Google asks you to remove the page, set it to noindex, or let validThrough expire. An expired opening still showing an application form is the most frequent guideline violation.
• No way to apply. A page that describes the role but points to a broken form, an email address, or "contact us" fails the direct-apply condition and loses the corresponding badge.
• The padded description. Pasting three paragraphs of company boilerplate before describing the role dilutes the signals Google uses for matching.
• Markup on the listing page. Placing a JobPosting on the page that lists every opening is explicitly prohibited; that page gets an ItemList, and the JobPosting goes on each individual opening.

What the TrueCalling job board actually does

TrueCalling is first a sourcing tool: EMILY reads a brief and goes to find candidates. But any job description created in the platform can also be made public in one click, and that is where the truecalling.ai job board comes in. Here is what happens when a recruiter switches publishing on.

• One page per opening, generated with complete markup. Title, full description (summary, profile, qualifications, soft skills), employer with logo and website, location with country, remote status, contract type, annual salary range: every field filled in the job description becomes the matching JobPosting field, with direct apply declared. It is live in under five minutes.
• A rolling expiry. As long as the role is active in the platform, its validity date is pushed forward 60 days automatically each time the page regenerates. When the recruiter deactivates the role, the page disappears and the opening leaves the index cleanly — without anyone having to think about it.
• One canonical URL per opening. The page exists in the site's 13 languages, but the markup designates the version matching the job description's language as canonical. No duplicates, no internal competition.
• An application that lands in your pipeline. The form (name, email, phone, location, LinkedIn if you require it, CV as PDF) is bot-protected, and the application goes straight into the pipeline of the role concerned, inside the app — not into an inbox to be re-keyed.
• Semantic search on the candidate side. Visitors can browse roles by country, filter by contract and remote status, or describe what they want in natural language — "senior React developer, remote, fintech" — and get results ranked by proximity. They can also upload their CV and let the engine find the openings that fit, graded as strong, good or possible match.
• A talent pool that fills itself. CVs uploaded for matching, like those from the Drop your CV page, join the talent pool — inbound profiles that outbound sourcing never had to go and find.

There is nothing to configure, nothing extra to buy, and no Google rule to learn: the markup follows the job description. The recruiter's only job is to fill in the description properly — which, as we are about to see, is exactly the job that matters.

Inbound and outbound: the two halves of the funnel

A well-indexed job board and active sourcing do not compete: they cover two populations that barely overlap. Google for Jobs and the job board capture active job seekers — 20-30 % of the market depending on the function. Sourcing goes after the remaining 70 %, the people who will never apply but will answer a relevant message: that is the subject of our guide to passive candidate sourcing. Teams that handle both flows in the same pipeline — inbound applications and sourced profiles, scored on the same grid — avoid the classic failure: an excellent inbound application ignored because it arrived in a different tool. That is also why the TrueCalling job board stores nothing separately: everything converges on the role, then on your ATS through the existing integration.

Checklist: publish an opening that surfaces, in 6 steps

1. Write a complete, sectioned job description. Role summary, target profile, qualifications, soft skills — four distinct blocks rather than one wall of text. This is what feeds the structured description.
2. Enter a precise location and the work mode. A city, not a region; and remote as a field, not a mention in the text.
3. State the contract type and the salary range. The two fields candidates look at most, and the two most often left empty.
4. Add the company logo and website. This is what turns a text result into an illustrated card.
5. Publish, then verify. Run the opening's URL through Google's Rich Results Test and watch the "Job postings" report in Search Console — indexing usually takes from a few hours to a few days.
6. Deactivate as soon as the role is filled. A ghost opening loses the trust of candidates and of Google. On TrueCalling, deactivating the job description is enough.

Google for Jobs rewards one thing: a clean page describing a real role with complete data. The TrueCalling job board automates that part so the recruiter can focus on the job description, then on the candidates — inbound and outbound alike. See the open roles on the job board or find out how EMILY sources the profiles the job board does not attract.