Distribute job postings via an Indeed XML job feed
domain: indeed.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an XML document conforming to the Indeed Job Sync XML feed specification, with a root <source> element and one <job> child element per posting
For each job include required child elements: <title>, <date>, <referencenumber>, <url>, <company>, <city>, <state>, <country>, and <description>
Host the feed at a stable HTTPS URL or upload it to an Indeed-provided FTP location; Indeed crawls URL-hosted feeds approximately four times per day
Register the feed URL with Indeed through the Indeed for Employers dashboard or via your Indeed partner agreement
Monitor the feed ingestion report in the Indeed Employer dashboard for parsing errors or rejected postings
Known gotchas
Indeed announced deprecation of XML-based job feeds for new integrations starting in mid-2025, with full discontinuation of single-source XML feeds planned for end of 2026; new integrations should evaluate API-based alternatives
Job descriptions must not contain HTML tags beyond basic formatting; excessive HTML or embedded scripts cause feed parsing failures
The referencenumber must be a stable unique identifier per job; changing it for the same position causes the old posting to be removed and a new one created, resetting apply counts
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?