A job website publishes hundreds, sometimes thousands of job listings per week. Each listing has its own page, with a short lifespan: a few days to a few weeks before it is filled or removed. Without a structured sitemap, a significant portion of these pages remains invisible to search engines, and therefore to candidates.
Indexing API and sitemap: the duo that Google recommends for job listings
Competitors often talk about the XML sitemap as a universal tool. On a job site, this approach is no longer sufficient. Google recommends using the Indexing API for pages containing JobPosting markup, to trigger a quick crawl as soon as a job is published, modified, or closed.
The sitemap then acts as a safety net. It ensures that all job listing URLs remain accessible to bots, even if the API call fails or if a page has been overlooked. The Indexing API handles responsiveness, the sitemap ensures overall coverage.
Specifically, when a recruiter publishes a job on a job site, the API sends an immediate signal to Google. The engine crawls the page within minutes instead of waiting for its bot’s next pass. For a candidate, this means seeing the listing in Google Jobs much sooner. You can check the sitemap of pleinemploi.net to observe the structure of a job-oriented sitemap.
Sitemap and Google Jobs eligibility: a unique URL per listing
Many job sites inadvertently create duplicates. The same listing appears under multiple URLs (filters, session parameters, distinct mobile versions). This situation prevents Google from determining which page to index.
A listing must correspond to a single dedicated, public, and canonical page. This URL is the one that appears in the sitemap. It does not carry a noindex directive, it is not blocked by robots.txt, and it does not redirect to another page.
This architectural constraint has a direct impact on site navigation. When a candidate clicks on a result in Google Jobs, they land on the correct page, with the right content. Application paths remain consistent, and the bounce rate decreases.
A common pitfall: leaving expired listings in the sitemap that redirect to a “This listing is no longer available” page. Google detects this inconsistency and penalizes the perceived reliability of the sitemap. It’s better to remove these URLs quickly or return a HTTP 410 (Gone) status.
Synchronizing the lastmod field with the lifecycle of listings
The XML sitemap contains an optional field for each URL called lastmod. It indicates the last modification date of the page. On a showcase site, this field rarely changes. On a job site, it should reflect every actual update of a listing.
Why does this precision matter so much? Because Google uses lastmod to prioritize pages for recrawling. If all listings display the same date, the engine has no signal to distinguish those that have changed. It has to check everything, which slows down the process.
A well-configured job site updates lastmod in three specific cases:
- When the content of the listing is modified (salary, location, job description).
- When the listing changes from “open” to “filled” or “closed,” triggering the removal of the page from the sitemap or its update.
- When the structured JobPosting markup is corrected or enriched, for example, to add a mode of work (remote, hybrid).
A reliable lastmod accelerates the consideration of changes by Google. Conversely, an artificial lastmod (updated daily without any real change) undermines the engine’s trust in the entire sitemap.
HTML sitemap and candidate navigation: beyond the XML file
The XML sitemap is for bots. The HTML sitemap, on the other hand, is for users. On a job site, a sitemap accessible from the footer can guide candidates to the main categories: professions, regions, types of contracts.
This page plays a role in internal linking. It distributes authority to deeper category pages that the main navigation may not always highlight. A candidate looking for listings in a niche sector can access it without going through faceted search.
For SEO, the HTML sitemap complements the XML without replacing it. It strengthens the site’s structure by creating additional pathways to strategic pages. Search engines follow these internal links and discover pages that traditional crawling might have missed.
The pitfall to avoid: listing thousands of individual listings in the HTML sitemap. This page would become unreadable and lose all utility. It’s better to limit it to categories, filtered result pages, and thematic landing pages.
Technical errors that sabotage a job site’s sitemap
Some errors frequently occur on job boards and go unnoticed for months.
- Including URLs in the sitemap that return a 404 or 301 code. Google eventually ignores the file if the error rate is too high.
- Exceeding the limit of 50,000 URLs per sitemap file without using a sitemap index to organize the files.
- Forgetting to declare the sitemap in robots.txt or Google Search Console, which delays its consideration.
- Mixing indexable pages and pages blocked by noindex in the same sitemap, which sends contradictory signals to engines.
On a high-volume job site, automating the generation of the sitemap is the only viable option. Synchronization with the job listings database should be daily, or even in real-time for the most active sites.
A well-maintained sitemap does not guarantee good SEO by itself. It remains a technical lever among others. But on a job site where content changes every day, it is the first signal that Google receives to understand what is new, what has changed, and what no longer exists.
