Discussion
  • Technical SEO

For job boards, how much traffic comes from Google’s jobs experience versus organic landing pages now, and where are you investing?

Published 1 reply

Discussion starter: a programmatic SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    There is no trustworthy public benchmark for this split, and I would be sceptical of any single figure quoted for job boards as a group. The share varies by country, by job category, by how much of your inventory is exclusive to you, and by how many of your target queries show Google’s job unit at all. What you can do is measure your own split with reasonable precision, because jobs-experience traffic is identifiable in Search Console and, where Google’s tracking parameters come through, in analytics.

    On investment, I treat the jobs experience as a distribution channel to keep clean and eligible, not as the asset to build. The asset is what that unit cannot reproduce: listings nobody else carries, landing pages that turn browsers into alert subscribers, and employer and salary information the unit does not show. The main qualification is that the two sources do different jobs, so comparing them on sessions alone will point the budget in the wrong direction.

    The two sources deliver different visitors

    Google’s job posting documentation (last updated 8 September 2026) says JobPosting markup makes a page eligible for a special job search experience in Google Search, which can show your logo, reviews, ratings and job details. The searcher browses and compares inside Google, then clicks through to one job. By the time they reach you, they have chosen the job, and your site is where the application starts.

    A landing page such as “nurse jobs in Leeds” does something else. Its visitor is still browsing, and browsing is the stage where people compare roles, save searches, register and set up alerts. Where Google’s job unit sits above the organic results, that page competes for the clicks the unit leaves behind.

    Dimension Jobs experience Organic landing pages
    Where the visitor lands One job detail page A role, location or search results page
    Intent on arrival Apply to this job Compare, refine, then maybe apply
    What you control Data quality, freshness and inventory Content, inventory depth, internal links and conversion design
    Competition for the click Other sites carrying the same job, which can include the employer’s careers site Other boards, aggregators and the job unit itself
    Outcome to measure Applies per session, and how many visitors you keep Registrations, alert sign-ups, return visits and applies
    Platform risk Higher: Google owns the format and can change it Lower: ordinary ranking volatility

    How to measure your own split

    1. Search Console. In the Performance report for Search results, filter by the Job listing search appearance, then by Job details, and compare both with the unfiltered Web totals. Jobs-experience clicks land on job detail pages, but job pages also receive ordinary organic clicks, so a page-type breakdown alone will not separate the two sources.
    2. Analytics. Practitioners report that Google appends UTM parameters to clicks from the jobs experience, with google_jobs_apply as the source and organic as the medium. Confirm this in your own landing-page data before you build reports on it. If the parameters are present, GA4’s default channel grouping puts these sessions inside Organic Search, so split them out by source.
    3. Outcomes, not sessions. Compare applies (or outbound apply clicks, where jobs redirect to an applicant tracking system), registrations, alert sign-ups and 30-day return rate by source. If employers pay you per click or per applicant, add revenue per session.
    4. Query classes. Take your top non-brand queries by clicks and record which ones show the job unit, on mobile and on desktop. That shows where landing pages can realistically win clicks and where the unit caps them.
    5. Trend comparisons. Google stopped supporting the &num=100 results parameter in September 2025, and many sites then saw desktop impressions fall and average position improve in Search Console, while clicks were affected far less, according to Brodie Clark’s analysis. Compare clicks rather than impressions across that date.

    The number that matters:

    Traffic share is the wrong unit. What you want is each source’s share of applies and of newly registered users, multiplied by what each is worth under your revenue model.

    Where I would put the money

    1. Eligibility hygiene

    Valid markup on every live job page, the Indexing API on publish, update and expiry, accurate validThrough dates, and salary and employment type wherever the employer supplies them. Google recommends the Indexing API over sitemaps for job posting URLs “because the Indexing API prompts Googlebot to crawl your page sooner”, does not allow expired postings, and does not allow postings without a way to apply. It describes direct apply as a short, simple application on your page without unnecessary intermediate steps, so set directApply only where that is true. This work protects the channel. It does not set you apart from competitors who do the same.

    2. Exclusive inventory

    When five boards carry the same job, you are one of five routes to it. When a job exists only on your site (and perhaps the employer’s), the demand the jobs experience captures for that job has fewer places to go. No amount of markup work makes you the only route to a widely distributed job; direct employer relationships and niche feeds do. This is a sales budget more than an SEO one, but it changes your position in the jobs experience in a way markup cannot.

    3. Landing pages that build an audience

    Landing pages turn browsing visitors into registered users, alert subscribers and repeat visitors, which is traffic you do not have to win from Google every time. Publish them only where inventory is deep enough to be useful, keep them fresh, and design them around the next action (save the search, create the alert), not only the click through to a job.

    4. What the unit does not show

    Employer pages, salary information and hiring-process detail answer questions the job unit does not. Google announced the phase-out of Estimated Salary rich results in its June 2025 simplification, so salary pages now have to earn clicks as ordinary results. Career advice content targets informational queries that AI Overviews and AI Mode also answer. The Search generative AI performance report (impressions only, no clicks) shows how much AI exposure those pages get, which helps you decide whether to keep funding them.

    Hypothetical example:

    A regional board has 30,000 live jobs, about a third of them exclusive. Search Console shows the two jobs appearances produce a little over half of non-brand clicks. Analytics shows jobs-experience visitors apply at a higher rate than landing-page visitors but seldom register, while landing pages produce most new alert subscribers. Neither source is “winning”. The jobs experience pays this month’s bills; the landing pages build next quarter’s direct and email traffic. Cutting landing-page work because the jobs experience “drives more traffic” would swap a durable audience for a channel whose format Google controls.

    A fast test: can you keep the visitors Google sends?

    The weakness of jobs-experience traffic is that it arrives for one job and leaves. A short test shows whether that is fixable, and the answer changes what the channel is worth to you.

    • Hypothesis: an inline job-alert module on job pages, shown to visitors from the jobs experience, raises alert sign-ups without reducing applies.
    • Split: by user, 50/50, within jobs-experience sessions identified by the source parameter. Keep the module inline rather than a full-screen overlay, so a sign-up is not bought with a worse mobile experience.
    • Primary metric: alert sign-ups per jobs-experience session. Guardrail: applies per session.
    • Duration: at least two full weeks, so any weekday pattern in job search falls evenly across both arms, and until you reach the sample size you calculated in advance.
    • Decision: if sign-ups rise and applies hold, jobs-experience traffic becomes a source of owned audience, and feed quality and exclusive inventory deserve a larger share of budget. If applies drop, value the channel at apply revenue only and keep audience-building spend on landing pages.

    What would change the allocation

    • Per-click or per-applicant pricing: jobs-experience applies turn straight into revenue, which strengthens the case for feed quality and exclusive inventory.
    • Subscriptions, posting packages or recruiter tools: registered users and audience size carry more weight, so landing pages and alerts deserve the larger share.
    • Markets without the experience: Google lists the countries where it is available. Where the unit does not appear for your target queries, the split question disappears and landing pages carry the load.
    • Format changes: your exposure is the share of applies that arrive through the jobs experience with no registered user behind them. Google does retire features, as the Estimated Salary change showed.

    The rule I would work to

    Measure applies and new registered users by source for a full quarter before moving budget. Treat job-page eligibility as a fixed cost that stays at full coverage. Put incremental budget where the result is durable: exclusive inventory, and landing pages that convert browsers into alert subscribers. The jobs experience is worth maximising, but your plan should still stand if Google changes it tomorrow.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.