Skip to main content

XML feed requirements and setup checklist

Updated

This article explains what information your XML feed should contain, provides an example and lists what to prepare if you want Jobiqo to configure the importer for you.

To configure the importer yourself, follow XML Importer Configuration Guide.

Feed requirements

Item Requirement or limit
Format Valid XML with a consistent structure
Access Accessible to the importer, with authentication details if protected
Feed file size Maximum 42 MB
Jobs per XML file Maximum 10,000
Job title Maximum 255 characters
Job description Maximum 32,000 characters
Logo formats PNG, GIF, JPG or JPEG
Logo file size Maximum 5 MB

Keep the feed URL stable and update the content at that address rather than providing a new URL for each update.

Use the same tag for every job. For example, an outer <jobs> tag can contain a separate <job> tag for each listing. Other tag names are supported: you do not need to rename your tags to match the examples below.

Job information

The tag names below are examples. Your feed can use different names, which are mapped to XPath fields during configuration:

Field / Tag Requirement Description
<jobId> Required A unique identifier for each job listing. This value is used to track jobs across feed updates and must not change for the lifetime of the job listing.
<title> Required The job title as plain text (e.g., "Senior Software Engineer").
<description> Required The full job description. HTML content is supported and should be wrapped in a CDATA section.
<company> Required The name of the hiring organisation.
<country> Required ISO 3166-1 alpha-2 country code (e.g., US, GB, DE).
<state> Recommended The state, province, or administrative region of the job location.
<city> Recommended The city or locality of the job location.
<postalCode> Recommended The postal or ZIP code of the job location.
<applicationWorkflow> Required Defines the application workflow type ("internal", "external", or "none").
<postedAt> Recommended The date the job was originally published.
<jobUrl> Recommended The URL to which candidates are directed when they click the Apply button. Must be a fully-qualified URL.
<applicationEmail> Conditionally required An email address to which applications should be forwarded. Useful for ATS systems that accept inbound applications via email. This can be ignored if the URL is used instead.
<category> Recommended The occupational category or job function (e.g., Engineering, Sales, Healthcare).
<companyLogo> Recommended A publicly accessible URL to the hiring company’s logo image.
<address> Recommended A full formatted street address, if available (e.g., "123 Main St, Richmond, VA 23890").
<salaryMin> Recommended The minimum value of the advertised salary range (numeric value only).
<salaryMax> Recommended The maximum value of the advertised salary range (numeric value only).
<salaryCurrency> Recommended ISO 4217 currency code for the salary values (e.g., USD, EUR, GBP).
<salaryFrequency> Recommended The payment frequency. Accepted values: Hourly, Daily, Weekly, Monthly, Yearly.
<requiredDegreeLevel> Optional Maps the required degree level terms to the existing taxonomy terms.
<employmentType> Optional Maps the required employment type terms to the existing taxonomy terms.
<yearsOfExperience> Optional Maps the required years of experience terms to the existing taxonomy terms.
<fieldsOfStudy> Optional Maps the required fields of study terms to the existing taxonomy terms.
<requiredLanguage> Optional Maps the required language terms to the existing taxonomy terms.
<occupations> Optional Maps the required occupational fields to the existing taxonomy terms.
<requiredSkills> Optional Maps the required skill terms to the existing taxonomy terms.
<remoteOptions> Optional Maps the remote options to the existing taxonomy terms.
<industry> Optional Maps the industry to the existing taxonomy terms.

The core and application requirements above follow the Simple XML Import documentation; the additional fields and example formats come from the existing field reference.

For taxonomy fields, values should match your site’s terms or their synonyms. See How can I edit an imported job? for matching instructions.

HTML descriptions can be supplied inside CDATA, but their appearance depends on the selected description format and the site’s formatting restrictions. 

Example XML feed

This example shows one job with additional employer, location, application and salary information. The tag names are illustrative, not a required template.

<jobs>
  <job>
    <jobId><![CDATA[12345]]></jobId>
    <title><![CDATA[Senior Software Engineer]]></title>
    <description><![CDATA[Full job description here...]]></description>
    <company><![CDATA[Acme Corporation]]></company>
    <city><![CDATA[Richmond]]></city>
    <state><![CDATA[VA]]></state>
    <country><![CDATA[US]]></country>
    <postalCode><![CDATA[23890]]></postalCode>
    <postedAt><![CDATA[2024-03-01T10:00:00Z]]></postedAt>
    <jobUrl><![CDATA[https://example.com/apply/12345]]></jobUrl>
    <applicationEmail><![CDATA[jobs@example.com]]></applicationEmail>
    <category><![CDATA[Engineering]]></category>
    <companyLogo><![CDATA[https://example.com/logo.png]]></companyLogo>
    <salaryMin><![CDATA[80000]]></salaryMin>
    <salaryMax><![CDATA[120000]]></salaryMax>
    <salaryCurrency><![CDATA[USD]]></salaryCurrency>
    <salaryFrequency><![CDATA[Yearly]]></salaryFrequency>
  </job>
</jobs>

This example provides an application URL for an External workflow. For an Internal or Quick Apply workflow, provide an application email instead.

Request setup by Jobiqo

If you want Jobiqo to configure the importer, prepare the information below and contact your Project Manager or Customer Success Manager. They can confirm the setup scope and applicable costs.

Topic Question Examples / Options
Site * Where should the importer be set up (if you have a multi-frontend)? www.jobiqo.com
Feed Link * Link to the XML feed that should be integrated. www.jobiqo.com/feed.xml
Size How many jobs on average are expected in the XML feed? Any number less than 10.000
Company profile Should jobs from this feed be linked to a specific company profile, or do they belong to various companies? Do they have a company profile? How should we map them? Map all jobs to the company profile "jobiqo" based on the company name.
Job Type * Do you prefer to set up the jobs via template or link? via template (regular text content) or via link (embedded).
Application workflow * Do you prefer to set up jobs via "an internal or an external application" workflow? (Or "no application system" to hide the apply button). internal application workflow (email) or external application workflow (URL).
Publishing options Should we auto-publish all imported jobs, or should imported jobs be in a "needs review" state? Auto-publish jobs or Needs review.
Mapping * Which XML tags should be used for which field? position - Occupation
employment_type - Employment type
Backfill jobs Should the imported jobs be marked as backfill? Yes/No
(Note: Backfill jobs rank lower in search results and appear after manually generated jobs. They can also be excluded from exports).
Emails Should the author of the imported job be reminded when a job posting is published/unpublished? Yes/No.