23/09/2026
# WordPress Job Board to Indeed XML Feed: A Real-World Integration Case Study
# # How a WordPress Job Board Was Prepared for Automated Job Distribution to Indeed
# # # Introduction
Job boards depend on accurate, structured data to distribute job listings across external recruitment platforms. When a website uses WordPress and a job-board plugin, connecting that data to a third-party platform such as Indeed can require more than simply generating an XML file.
This case study documents a real-world WordPress XML feed project for "KA Resources", where the requirement was to make job listings from a WordPress/WPJobBoard website available to Indeed through an XML feed.
The project evolved from an initial feed requirement into an iterative integration and validation process involving XML structure, HTML formatting, escaped entities, industry information, and salary formatting.
---
# # The Challenge
The client initially approached us with a straightforward requirement:
> Export jobs from a WordPress website using WPJobBoard to Indeed through an XML/RSS feed.
The important distinction was that the client needed an "export feed", not an import solution.
At the beginning of the project, the first step was therefore not to immediately build a custom XML generator. We investigated the existing WordPress setup and discovered that WPJobBoard already provided an XML job feed intended for Indeed.
This changed the implementation approach.
Instead of unnecessarily rebuilding functionality that was already available, the focus shifted toward identifying the correct feed, making sure it contained the required information, and preparing it for Indeed's review process.
---
# # The Solution
# # # 1. Understanding the Existing WordPress Environment
The website was running WordPress with "WPJobBoard" as the job-management system.
The first technical objective was to determine how job information was already stored and exposed by the plugin.
Once the existing Indeed-compatible feed was identified, the client was provided with the feed URL that could be submitted to Indeed.
A key benefit of this approach was automation: when new jobs were added to WPJobBoard, they would automatically become available through the feed rather than requiring a separate manual export process.
---
# # 2. Preparing the Feed for Indeed Review
Generating a feed was only the first stage.
The client submitted the feed to Indeed, after which Indeed returned feedback regarding the formatting of job data.
The first validation response identified issues involving:
- Escaped HTML entities
- Job descriptions lacking the expected HTML formatting
- Proper handling of characters such as `&`, ``, and quotes
- Appropriate HTML tags within job descriptions
The feed was then reviewed against the requirements provided by Indeed.
This illustrates an important point about third-party XML integrations:
A feed can be technically valid XML and still require additional changes to satisfy the destination platform's data and formatting rules.
---
# # 3. Handling HTML Entities and Job Description Formatting
The job descriptions needed to be represented correctly inside the XML feed.
The implementation was reviewed to ensure that HTML entities were appropriately represented and that supported HTML formatting could be preserved.
The feed was subsequently updated and the client was asked to resubmit it to Indeed for another review.
This iterative process allowed the implementation to be tested against the actual requirements of the receiving platform rather than relying only on generic XML validation.
---
# # 4. Adding the Industry Field
Indeed subsequently requested additional information that could help its system understand the job listings.
One of the requested changes was an `industry` field.
The feed was updated to include the industry information, demonstrating how a custom feed can be extended when the receiving platform introduces or identifies additional data requirements.
---
# # 5. Handling Salary Data Correctly
Salary information presented another important integration detail.
Indeed required salary information to include both the amount and the applicable period, such as:
- per hour
- per week
- per month
- per year
The project revealed an important distinction between "feed-generation logic" and "source data quality".
The XML feed was collecting salary information from the website's database. Where the underlying job record did not contain the salary in the format expected by Indeed, changing the XML structure alone would not necessarily solve the underlying data problem.
For example, the project identified a job where the salary was stored as descriptive text rather than in the structured format expected by Indeed.
The solution therefore involved explaining how the job's source salary information needed to be entered correctly so that the feed could automatically reflect the structured data.
This is an important principle in feed development:
The quality of an XML feed depends not only on the code generating it, but also on the quality and structure of the underlying data.
---
# Technical Overview
# # # Website Environment
- CMS: WordPress
- Job Management: WPJobBoard
- Output: XML job feed
- Destination Platform: Indeed
- Integration Type: Automated job-feed distribution
- Data Source: WordPress/WPJobBoard database
# # # Feed Requirements Addressed
The project involved working with:
- Job listing data
- Job descriptions
- HTML formatting
- XML entity escaping
- Industry information
- Salary information
- Salary periods
- Feed submission and validation
- Iterative corrections based on destination-platform feedback
The implementation was not treated as a one-time XML export. It was handled as an integration where the feed needed to satisfy the requirements of the external platform.
---
# Beyond the Initial XML Feed
The project also demonstrates how solving one technical integration problem can establish the foundation for longer-term development work.
After the Indeed feed project, the client approached us with additional WordPress requirements involving ACF and WP All Import. Later, the client also discussed other WordPress/PHP development work.
Interestingly, not every requested task was accepted.
When a later ACF/WP All Import requirement fell outside the current technical scope, the limitation was communicated honestly rather than promising work that could not confidently be delivered. The client explicitly appreciated that honesty.
That approach remains important in technical consulting: understand the requirement, verify the available solution, communicate limitations clearly, and focus on delivering reliable work.
---
# Key Lessons From the Project
# # # 1. Investigate Before Building
Not every integration requires a completely custom solution.
The first step was to investigate WPJobBoard's existing capabilities. This avoided rebuilding functionality that was already available.
# # # 2. XML Validity Is Only One Part of Feed Development
A feed may be structurally valid XML but still fail a receiving platform's requirements.
Destination-specific requirements can include:
- Data formatting
- HTML handling
- Required fields
- Character escaping
- Salary structures
- Content conventions
# # # 3. Source Data Matters
A feed generator can only reliably transmit the data available to it.
If salary, location, category, or other information is stored incorrectly in the source system, the feed may faithfully reproduce that problem.
# # # 4. Third-Party Validation Is Part of the Development Process
External platforms may provide feedback that cannot be fully anticipated during the initial implementation.
A robust integration process therefore includes:
Build → Submit → Validate → Analyze → Adjust → Resubmit
# # # 5. Honest Technical Communication Builds Trust
The project also demonstrated that technical consulting is not simply about saying "yes" to every request.
When a later requirement was outside the current scope of expertise, it was communicated directly. The client responded positively to that transparency.
---
# Conclusion
This WordPress-to-Indeed project began with a simple requirement: make WordPress job listings available to Indeed through XML.
What initially appeared to be a straightforward feed-generation task became a practical integration exercise involving:
WordPress + WPJobBoard + XML + HTML formatting + structured salary data + industry mapping + third-party validation.
The project highlights why professional XML feed development is more than producing an XML document. The feed must accurately represent the source data, follow the destination platform's specifications, and remain maintainable as new content is added.
At wp2xml, we work with businesses that need structured data from WordPress websites to reach external platforms through XML, RSS, JSON feeds, APIs, and custom integrations.
# # Need a Custom XML or RSS Feed for Your WordPress Website?
Whether you need to connect a real-estate website, job board, directory, e-commerce site, or custom WordPress application to a third-party platform, we can help analyze your existing data structure and develop a feed around the actual requirements.
Have a WordPress website that needs a custom XML, RSS, or JSON feed?
Visit wp2xml.com to discuss your requirements and build a feed designed for your target platform.
https://wp2xml.com/case-study-17-wordpress-job-board-to-indeed-xml-feed-a-real-world-integration-case-study/
How a WordPress Job Board Was Prepared for Automated Job Distribution to Indeed Introduction Job boards depend on accurate, structured data to distribute job listings across external recruitment platforms. When a website uses WordPress and a job-board plugin, connecting that data to a third-party pl...
