Jobboard Integration

Employers, staffing agencies, and applicant tracking systems (ATS) typically maintain job openings in one internal system, then need those same openings visible on multiple external job boards, aggregators, and search engines. Keeping every destination updated by hand does not scale once you have more than a handful of open roles or more than one board.

1. New openings appear on external boards automatically instead of being re-typed on each site.
2. Filled or closed positions are removed or expired everywhere on the same cycle, reducing dead links and stale listings.
3. Consistent, correctly formatted data (title, location, salary, dates) improves eligibility for enhanced listings, such as rich results in Google for Jobs.
4. A single feed can be mapped to the field requirements of several boards at once instead of maintaining separate manual exports.

General industry practice, not one specific "Jobboard" rule: the most common exchange format for job listings remains an XML job feed — a structured file where each job is one repeated element (commonly <job>) containing tagged fields for title, description, location, and so on. XML feeds are widely supported because they require no custom engineering per destination and are compatible with most job board content-management systems.

Two other formats show up regularly across the industry and are worth knowing even though they are not universal:

1. JobPosting JSON-LD schema — used specifically to make listings eligible for Google for Jobs rich results; this is structured data embedded in a page's HTML rather than a separate feed file.
2. CSV/JSON exports — used by some ATS platforms and aggregators as an alternative to XML, particularly for bulk or API-based imports.

Always confirm the exact format, encoding, and file delivery method (URL pull vs. upload vs. API) with the specific board you are targeting.

Exact field names vary by destination, so the table below reflects attributes that recur across general job-feed specifications (including Indeed's Job Sync XML fields and the Google for Jobs JobPosting schema), labeled by how consistently they are treated as required versus recommended across the industry — not a single platform's mandated list.

The general workflow for setting up a job feed export in Feedance follows the same pattern used for its other data-channel integrations:

1. In the Feedance dashboard, create a new feed and either upload your job listing data or connect the system where your openings are managed.
2. Go to Data Channels, create a new channel, and select the job board you are exporting to as the destination.
3. Map each of your source fields (title, description, location, apply link, reference number, dates, etc.) to the field names your chosen job board expects.
4. Copy the feed URL Feedance generates and submit it in that job board's feed-import or XML-feed settings.
5. Set an update schedule so the feed refreshes automatically, then confirm in the destination board that new and expired listings are syncing correctly.

Because "Jobboard" covers multiple possible destinations rather than one fixed platform, double-check the receiving board's own submission instructions for anything beyond these general steps.

There is no single universal number, but general guidance across job board and ATS documentation converges on a few points:

1. Most feeds are refreshed somewhere between every 4 hours and once daily, with daily being a common default for moderate-volume feeds.
2. Feed pull frequency should roughly match how often your source data changes — a large, fast-moving feed benefits from more frequent syncs than a small, slow-moving one.
3. Individual listings that are refreshed or lightly edited within the last 7 days tend to get noticeably more views than untouched listings of the same age, since recency is a ranking signal on many boards.
4. Listings are generally expected to be refreshed or removed within roughly 90–120 days; leaving stale postings live past that window can hurt visibility and trust with aggregators.

These are errors documented broadly across job-feed and Google for Jobs guidance, not specific to a single "Jobboard" product:

1. Missing required fields — absent or incomplete title, description, location, or company data is one of the most common reasons a listing is rejected or dropped.
2. Duplicate reference numbers — reusing or failing to set a unique job ID causes listings to be dropped or counted twice.
3. Expired postings left live — a job whose valid-through date has passed but whose page and markup remain active creates a poor candidate experience and can reduce a domain's trust score with aggregators such as Google for Jobs over time.
4. XML formatting mistakes — unescaped special characters or inconsistent field-name capitalization can block a feed from being processed at all.
5. Incorrect date formats — dates not supplied in the expected format (commonly ISO 8601) are a frequent cause of rejected or misread fields.

These are general job-feed best practices gathered from job board and job-schema documentation, not guarantees tied to any single destination:

1. Keep unique reference numbers stable across feed runs so updates are recognized as edits, not new duplicate postings.
2. Populate salary and employment type wherever you can — feeds with this data tend to perform better in ranking and candidate engagement.
3. Automate expiration handling so filled roles drop out of the feed promptly rather than lingering past their valid-through date.
4. Validate XML output for proper character escaping before every submission to avoid silent parsing failures.
5. Refresh high-priority listings on a shorter cycle than the rest of the feed if a specific board rewards recency.

Is "Jobboard" one specific company?
No. On Feedance it refers generically to the job-board feed model — the same mechanics used by many named boards — rather than a single identifiable platform.

Should I use XML or the Google for Jobs JSON-LD schema?

They serve different purposes: XML feeds are typically used to submit listings to a job board's import system, while JobPosting JSON-LD is markup embedded on your own job pages so Google for Jobs can find and display them. Some setups use both.

How do I know which fields a specific board actually requires?
Check that board's own feed or import documentation directly — required fields, formats, and limits are not identical across boards, even though most share a similar core (title, description, company, location, apply link, reference number, and dates).

What happens if I leave expired jobs in the feed?
They can create a poor experience for applicants and, on aggregators like Google for Jobs, repeated stale postings can reduce your domain's trust over time — so removing or expiring closed roles promptly is worth automating.