Google Job Posting SEO in 2026: Indexing API, Honest lastmod, and Clean Expiration Rules

Most hiring teams treat job page SEO like a publishing problem. In practice, it is usually an operations problem.

Job pages are short-lived, updated often, and expensive to leave stale. If Google recrawls them too slowly, you can end up with expired roles still surfacing in search, remote roles shown too broadly, or new openings taking too long to appear.

Google’s current documentation gives hiring teams a fairly clear playbook: put JobPosting markup on the individual job page, use the Indexing API for adds, updates, and removals, keep your sitemap accurate, and be precise about remote-work eligibility and expiration.

What Google explicitly recommends

Google’s Job Posting documentation says structured data belongs on the most detailed single-job page, not on a listings page. Its Indexing API documentation also says job posting pages are one of the supported page types that site owners can notify Google about directly when pages are added or removed.

That combination matters for recruiting operations. You do not need a complicated growth hack. You need a reliable publication workflow for every role lifecycle event:

• new job posted
• job details updated
• job filled or withdrawn
• remote eligibility changed

1. Put JobPosting on the job detail page, not the listings page

Google’s technical guidance is straightforward: apply structured data to the most specific page describing a single job, and make sure the markup appears on the same page as the job description that applicants can read in their browser.

For hiring teams, that means each open role needs its own stable URL with the visible job description, qualifications, location details, and application path on-page. A careers index page can link to those roles, but it should not be the page carrying the full job posting markup for every opening.

If your hiring workflow still publishes jobs into a JavaScript-heavy list without durable role URLs, that is the first issue to fix.

2. Use the Indexing API for role lifecycle events

Google’s Indexing API is specifically documented for pages with JobPosting markup. The practical value is speed and control: when a role is created, updated, or removed, you can notify Google directly instead of waiting for a normal recrawl cycle.

For recruiting teams, the highest-value triggers are:

• send a URL update when a new job page goes live
• send a URL update when title, location, compensation, or eligibility rules materially change
• send a URL removal request when the job is closed and the page is removed

This is especially useful for high-volume hiring, seasonal hiring, and any team with jobs that open and close quickly.

3. Keep your sitemap, but keep lastmod honest

The sitemap is still useful as a coverage layer for your careers site, but it is not the same thing as a freshness signal for short-lived jobs. Google’s sitemap documentation says lastmod should reflect the last significant update to the page, and it specifically notes that changefreq and priority are ignored.

That has two direct implications for job operations:

• do update lastmod when the actual job page content changes in a meaningful way
• do not fake daily freshness by rewriting timestamps when nothing important changed

When recruiters edit a posting, your publishing workflow should update the page, update the sitemap timestamp if the change is material, and notify Google through the Indexing API.

4. Treat expiration as part of your SEO workflow

Expired jobs create bad candidate experiences and noisy search results. Google’s job posting guidance includes validThrough for expiration, and it also provides guidance for removing job postings.

A practical rule is:

• if you know the role’s application deadline, include validThrough
• if the role is no longer open, remove or update the posting promptly and notify Google
• if you remove the page entirely, use the Indexing API removal flow rather than hoping Google figures it out quickly

This is one of the cleanest places where hiring operations and technical SEO should share ownership. Closed roles should not linger because a recruiter changed a spreadsheet but the website pipeline never fired.

5. Use remote-job markup precisely

Google’s documentation for work-from-home jobs is more specific than many teams realize. If a job is remote, Google says you should use jobLocationType and specify applicant geography with applicantLocationRequirements. At least one country is required for work-from-home jobs.

That matters because “remote” is rarely universal. A role may be remote only within the US, within certain states, or hybrid with one office option plus remote eligibility from selected regions.

If your public job page just says “remote” but your markup omits applicant location requirements, you risk showing the role to people who are not actually eligible.

6. Only mark directApply true when the posting really supports direct application

Schema.org defines directApply as a signal that the URL associated with the job posting enables direct application for the job through the posting website. In plain terms: a candidate should be able to start the application process directly from that URL.

If your page mainly routes users through multiple detours, account walls, or third-party discovery flows before they can begin, do not treat directApply as a decorative field. Use it only when it accurately reflects the application experience.

What to do next

1. Create one stable public URL per open role.
2. Render the job description and matching JobPosting markup on that same page.
3. Trigger Indexing API updates when jobs are created, materially edited, or removed.
4. Update sitemap lastmod only for real page changes.
5. Set expiration rules so closed roles are retired quickly.
6. For remote roles, specify eligible applicant geographies.
7. Use directApply only when the page truly supports direct application.

Why this fits Apikuo users

Apikuo already sits near the operational layer where hiring teams manage job pages, candidate flows, and recruiting updates. That makes this a good systems problem to solve once: when a role changes state, your publishing workflow should update the page, the structured data, the sitemap, and Google notification steps together.

That is less glamorous than talking about “AI SEO,” but it is exactly the kind of workflow discipline that keeps candidate-facing content accurate and discoverable.

Sources

• Google Search Central: JobPosting structured data
• Google Search Central: Indexing API quickstart
• Google Search Central: Build and submit a sitemap
• Schema.org: JobPosting