NewProduct Score, 4T Segmentation, Price War and Broken Size are live.See what's new
Feedance
Jobboard logoJobboardChannel · Marketplaces and apps
Jobboard integration

Send Jobboard the products worth showing.

Feedance builds your Jobboard feed and adds product-level labels for score, 4T segment, price position and broken sizes, so every product carries its own performance signal.

Jobboard product feed
Generated by Feedance
XML, CSV or JSON exportUpdated on every sync
<item>
  <id>TS-1042</id>
  <title>Crew neck T-shirt</title>
  <price>49.90 USD</price>
  <availability>in stock</availability>
  <custom_label_0>score_86</custom_label_0>
  <custom_label_1>top</custom_label_1>
  <custom_label_2>best_price</custom_label_2>
  <custom_label_3>size_ok</custom_label_3>
</item>
Feedance labels, written as custom labels
What Feedance sends to Jobboard

A catalog with a performance signal on every product.

Jobboard reads your products from the feed. Feedance sends a complete, valid feed plus the signals Jobboard does not have on its own.

Product Scorecustom_label_0A 0 to 100 score from views, add to carts and purchases over 1, 7 and 30 days.
4T segmentcustom_label_1Top, Tolerable, Tranquil or Toxic, from each product's own traffic and return.
Price Warcustom_label_2Best, same or more expensive than named competitors.
Broken Sizecustom_label_3Flags styles whose size run is mostly out of stock.
Creativesimage_linkBranded images from Creative Suite, with price and campaign details from the feed.
How you use it: split campaigns, product groups or product sets by these labels, for example only Top products, or everything except Toxic and broken size runs. Label slots are configurable. Feedance does not change your bids or budgets.

What is Jobboard?

On Feedance, "Jobboard" is not a single named company or product with its own feed specification — it is a general-purpose connector for publishing job listings to online job board platforms. Feedance's own integration page defines it as "a website or platform that connects job seekers with employers by posting job listings and facilitating the application process," the same definition that applies broadly to well-known destinations such as Indeed, Monster, LinkedIn Jobs, Glassdoor, CareerBuilder, and ZipRecruiter.

Because there is no independent "Jobboard" platform to document, this page describes the general, industry-standard mechanics of job listing feeds — often called job XML feeds — rather than one company's exact technical rules. If you are connecting to a specific named destination (Indeed, LinkedIn, Google for Jobs, or another board), always check that destination's own documentation for its exact field names, formats, and limits, since implementations differ from board to board.

Why connect your job feed to a job board?

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.

What feed format does a job board require?

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.

Which job listing attributes are typically required?

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.

AttributeTypical statusNotes
Job titleRequiredShould match the title shown on the live job page.
DescriptionRequiredFull job description, in HTML or plain text.
Company / hiring organizationRequiredEmployer name; some specs also expect a company URL.
LocationRequiredFull address detail is recommended — street, city, state/region, postal code, country.
Apply URL or apply emailRequiredDestination for candidate applications.
Reference number / job IDRequiredMust be unique per listing; duplicate IDs cause jobs to be dropped or double-counted.
Date postedRequiredCommonly expected in ISO 8601 format.
Valid through / expiration dateRecommendedListings left live past this date can hurt trust with aggregators like Google for Jobs.
Employment typeRecommendedE.g. full-time, part-time, contract.
Salary / base salaryRecommendedNot always mandatory, but listings with salary data consistently see stronger placement and engagement.

How to connect your job feed with Feedance

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.

How often should the feed update?

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.

Common job feed errors

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.

Optimization tips (general industry practice)

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.

FAQ

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.

About Jobboard

A job board platform, also known as an online job board or job portal, is a website or platform that connects job seekers with employers by posting job listings and facilitating the application process. These platforms provide a centralized location for job seekers to search and apply for employment opportunities, while also allowing employers to advertise job openings and screen potential candidates.

Job board platforms have significantly evolved over the years due to advancements in technology and the increasing demand for efficient and effective recruiting processes. With features like advanced search functionalities, resume databases, applicant tracking systems, and automated job alerts, these platforms have become essential tools for both job seekers and employers.

There are numerous job board platforms available worldwide, each with its own unique features and target audience. Some of the most notable job board platforms include Indeed, Monster, LinkedIn, Glassdoor, CareerBuilder, and ZipRecruiter.

Indeed, one of the most popular job board platforms, was launched in 2004. Originally founded in Austin, Texas, it has grown to become one of the largest job search engines globally, operating in over 60 countries and available in 28 languages.

Monster, another well-known job board platform, was launched in 1999. It was founded in the United States and has since expanded to serve job seekers and employers in various countries across North America, Europe, and Asia.

LinkedIn, launched in 2003, initially started as a professional networking platform but later expanded to include job listings and recruitment functionalities. It originated in the United States and has grown to have a global presence, making it one of the largest professional networking and job board platforms.

Glassdoor, established in 2007, was founded in the United States with a focus on providing transparent company reviews and salary information. Over time, it expanded its offerings to include job listings and recruiting features, making it a notable player in the job board market.

CareerBuilder, launched in 1995, originated in the United States and has become one of the largest job board platforms in the country. It offers a wide range of services for both job seekers and employers, including job postings, resume database access, and applicant tracking systems.

ZipRecruiter, established in 2010, was founded in the United States and has since gained popularity for its user-friendly interface and streamlined job matching capabilities. It has expanded its services to multiple countries, making it accessible to a global audience.

Overall, job board platforms have revolutionized the way job seekers find employment and employers attract talent. Through their online presence and user-friendly features, these platforms have greatly facilitated the recruitment process and created a more efficient job market.

See which
products earn.

Connect your feed and GA4. We show Product Score, 4T, Price War and Broken Size on your own catalog.