Matador Jobs Lite

by Paul Bearne

Description

Connect your Bullhorn Account with your WordPress site and display your valuable jobs on your new self-hosted job board. Matador makes this as easy as it sounds, and lets you seamlessly integrate a powerful job board–a major marketing tool for your business–directly into your WordPress site. Everything that is great about WordPress is extended to Matador: great out-of-the-box SEO, easy templating/theming, endless customization options, and more. Matador goes further by listing your jobs with incredible job-specific SEO customization (optimized for Google Jobs Search), and more.

Use Matador’s powerful settings to connect our “Apply Now” button for jobs to a page that will collect applications, or look into purchasing Matador Jobs Pro to accept applications from Matador and see them turned into candidates submitted to jobs directly in your Bullhorn Account!

Installation

This section describes how to install the plugin and get it working.

Upload the plugin files to the ‘/wp-content/plugins/matador-jobs-pro’ directory, or install the plugin through the
WordPress plugins screen directly.
Activate the plugin through the ‘Plugins’ screen in WordPress
Configure the plugin by going to Matador Jobs > Settings.
Connect your site to Bullhorn by clicking on ‘Bullhorn Connection Assistant’ on the Settings Page, and following the.
prompts.

Screenshots

Options page - Bullhorn Import settings
CV/resume upload form
Notifications options page
Jobs listings in the admin

Faq

Does this Require a Bullhorn Account?

You must have an active Bullhorn Account to use Matador’s Bullhorn Import/Export features. It technically will function as a stand-alone jobs board without a Bullhorn Account, but there are better options out there for that.

How Do I Get Bullhorn API Credentials?

You must submit a ticket to Bullhorn support. Merely informing them you will be using Matador should give them all the info they need to help you, as we are now Bullhorn Marketplace Developer Partners and they know what a new Matador user needs. That said, we recommend first installing the plugin, activating it, and starting the Bullhorn Connection Assistant before you do this. Follow the prompts in the easy-to-use assistant and Matador will generate a copy-and-paste email you can send to Bullhorn Support to get you started.

So Matador downloads jobs from Bullhorn. Does it accept applications too?

Yes, if your a user of Matador Jobs Pro or All-Access. Once you’ve connected to Bullhorn and synced your first jobs, your visitors can apply to the jobs. Based on settings, the applications will be sent to your Bullhorn either immediately or in the next regularly scheduled sync with Bullhorn.

If you are only right now a user of the free Matador Jobs Lite, not yet. Matador Jobs lite allows you to designate a destination page for the “Apply” button, but you will need to handle your own applications, perhaps with a contact form plugin.

If you’d like more information on Matador Jobs Pro or All-Access, visit https://matadorjobs.com/.

How Can I Customize the Look of Matador?

Our documentation site https://docs.matadorjobs.com/ explains how to use our template system, theme functions, shortcodes, and actions and filters to make your site look amazing. You can also watch out for occasional client showcases on our where we feature creative and amazing looking implementations of Matador.

How Can I Customize the Function of Matador?

Matador is built by WordPress users for WordPress users. We included hundreds of Actions and Filters to help you customize how it works just like WordPress core. Some of those are documented at https://docs.matadorjobs.com/ while others can be discovered with a quick code review.

But that requires a developer and hours of work! If you haven’t already, check out our many official extensions that are viewable at https://matadorjobs.com/products/. These extend Matador’s core functionality in ways that can make each site feel unique! You can use an unlimited number of these All-Access Add-Ons with any Matador Jobs All-Access plan.

If you need something and you don’t see an add-on, feel free to write us. Leave a comment in the Support Forum or with our Pro support system http://www.matadorjobs.com/support/ (requires Matador Jobs Pro or All-Access). Simple modifications might already be documented and we can point you to them. And if you have a more complex modification, we may be able to take your input and idea and turn it into another All-Access Add-On.

Where can I get support?

Users of Matador Jobs Lite should use the plugin’s WordPress.org support forum. Users of Matador Jobs Pro and All-Access annual or lifetime plans can use our support ticket system at http://www.matadorjobs.com/support/.

Reviews

Changelog

3.9.15 & 3.9.16

Security: A user reported a vulnerability in a prior (2+ years old) version of Matador Jobs where a malicious script could bypass checks and directly upload PHP files via the Matador Application Form which later could be executed following either an administrator action or an unrelated exploit (hypothetically) gaining access to the filesystem. A review of the security report determined that our team had already hardened security around this area of the Matador source code since the users’ version was released. The user’s report provided additional insight to this known issue. This resulted in additional updates to further harden security and further protect Matador and its users from malicious file uploads.
- Code changes to improve and further ensure application form submissions cannot contain JavaScript, PHP, or other malicious scripts.
- New routine creates and configures a .htaccess file to all folders created by Matador. For Apache-powered web servers, this will prohibit PHP code execution in those folders. This hardens security on sites on the Apache webserver infrastructure.
- We will explore similar webserver-specific opportunities for sites hosted on NginX and ISS, among others. Thank you to Peter at Cyberunity for the responsible report and thoughtful feedback guiding us toward a quick patch.
Enhancement (Core): The Job Structured Data, also known as JSON+LD, which drives visibility on Google for Jobs, Search Engine Optimization (SEO), and Generative Engine Optimization (GEO) in Matador Jobs adheres to the Google standard, visible here (https://developers.google.com/search/docs/appearance/structured-data/job-posting#job-posting-definition). Recently, Google modified their standard to allow for “confidential” hiring company value. Going back to before the first public release of Matador Jobs, users have asked for confidential hiring companies and we’ve advised to use their firm info instead of their client’s for this value. Now they may elect to mark their jobs as confidential. While this means Google now endorses this option, it does not mean there may not be consequences in job searches, Google searches, or Google AI searches for users who use it.
- “‘Hiring Company’ Data Source” setting has new option, “Confidential”.
- When set to “Confidential,” jobs will not have a Hiring Company, Hiring Company URL, or Hiring Company Logo set in JSON+LD Job Structured Data.
Enhancement (Bullhorn): Added support for Bullhorn’s Amplify Trust Verify product. This new product is available to Enterprise users and is in pre-release status. Bullhorn Amplify Trust Verify will monitor user behavior on your website to build a “trust profile” around the application. The Trust Profile will profile the application to help its user determined application data is real (as opposed to AI-generated or fraudulent) and was submitted by a human.
- Added a setting to enable or disable Bullhorn Amplify Verify features.
- When enabled, initializes Bullhorn’s Amplify Trust Verify on the application form and communicates user behavior data back to Bullhorn.
- Note that users of this feature should update their Terms of Use and Privacy Policies to disclose the use of Bullhorn’s Amplify Trust Verify and may require inclusion of a link to Bullhorn’s Privacy Policy and more.
Misc: Tested up to WordPress 7.2
Misc: Requires PHP 8.2. Why? This week’s PHP security alert means all our users should upgrade to 8.2 ASAP (https://www.php.net/index.php#2026-10-21-5).
Misc: Updated Readme.txt to fix display issues on WordPress.org for Matador Jobs Lite.

3.9.14

Enhancement: (Applications & Performance) Added additional methods to communicate to caching systems that applications should not be cached. Cached applications cause “nonce errors.” A nonce, “number used once”, is designed to protect from malicious cross-site scripting but can incorrectly be cached by site caching systems. Ultimately, it is the responsibility of the site operator to configure caching properly, but by sending additional messages to caching systems about what should and shouldn’t be cached, we will help automatic caching settings avoid common user pain points.
Enhancement: Imported a 4.0.0 filter into the 3.9.x branch to simplify the upcoming update for our users. You may use matador_email_application_confirmation_for_candidate_body instead of the soon-to-be deprecated matador_email_application_applicant_body filter.
Bugfix: (Google Indexing API) Updates the login endpoint following the deprecation of the one used in previous versions.
Bugfix: (Template) Fixed an issue where the matador_job_field() template function (and the shortcodes and blocks which use it) were unnecessarily outputting empty HTML elements when a job had no value to display for the passed field.
Misc: Added a notice that Matador Jobs 4.0.0 is coming!
Misc: Tested up to WordPress 7.0.

3.9.13

Enhancement: (Bullhorn) Added filter matador_bullhorn_client_corporation_create_body to modify the body of the Client Corporation create request call.
Bugfix: (Core) Fixed an issue with backward-compatibility handling for legacy uses of the matador_variable_job_taxonomies filter.
Bugfix: (Admin) Fixed an issue recently created causing the remote source ID to not display in the WordPress admin list screen for the Matador job listings post type.
Bugfix: (Editor) Fixed an issue causing Matador’s WordPress Block Editor blocks to fail to fetch taxonomy terms.
Bugfix: (Bullhorn) Fixed an issue causing the Bullhorn category sync to fail when a job is assigned to more than five categories.

3.9.12

Enhancement: Modified the 3.9.0 application screening feature to give developers ways to create custom actions.
- Add a custom button to the application screening using the matador_application_screen_control_options filter (3.9.0).
- Add the custom application screening actions first with the matador_application_screen_allowed_actions filter.
- Program the action and hook it with either matador_application_screen_custom_action or matador_application_screen_{$action}_action actions.
- See our docs site (https://docs.matadorjobs.com/articles/custom-screening-actions/) for a complete example.
Bugfix: Fixed an error in our AllInOne SEO Third-Party Plugin support where if job sync fails in progress, JSON+LD metadata is not saved properly.
Bugfix: Fixed the wording on the setting determining if multiple job submissions by the same candidate should be permitted or not. Now the setting name and description accurately reflect the behavior of the setting (when off, multiple submissions by the same candidate will result in multiple job submissions).
Internationalization: Updated translations files.
Misc: Tested up to WordPress 6.9, which releases on 2025-12-02.

3.9.11

Enhancement: A RankMath SEO feature which redirects a user to a custom “not found” page when a resource is not found is now disabled for Matador Jobs job pages due to the dynamic nature of the content Matador Jobs manages.
Enhancement: Added the matador_bullhorn_submit_candidate_to_job_body filter to enable customisation of the fields set on the Job Submission during application sync.
Bugfix: Added a code protection for a rare issue caused by changes to the server configuration of the uploads directory after creation. This could also be triggered by improper migrations.
Bugfix: Fixed a bug in the jobs-listing-job.php and job-aside.php templates which caused some job parts not to rendered when an empty string is passed as a label.

Previous Versions

See CHANGELOG.md