If your roles live in Loxo.co and you want them on your WordPress site, you have three realistic routes. You can embed Loxo’s hosted job list in an iframe. You can pay a developer to build against the Loxo API. Or you can install a plugin that already does it.
The iframe is free and takes an afternoon. A custom build costs thousands and someone has to maintain it when the API changes. A plugin sits in between, and there are now several to choose from. This page compares them honestly, including the cases where a cheaper option is the right call.
One thing to settle first, because it drives everything else: does organic search matter to you? An iframe keeps your job content on Loxo’s domain, so it cannot rank for you. Every plugin here puts jobs on your domain instead. What separates the plugins is how much SEO machinery comes with them.
Feature and price comparison
Competitor rows below reflect only what each vendor advertises on their own site, checked on July 27, 2026. “Not advertised” means we could not find the feature claimed publicly. It does not mean the product lacks it.
| Feature | LoxoWp | LimeStaff | JobRelay | Iframe embed |
|---|---|---|---|---|
| Price per year | $69 single site; $159 for 5 sites | $39 single; $69 for 5; $99 unlimited | £419 per year, or £49 per month | Free |
| Job sync method | Loxo API sync plus real-time webhooks | API sync plus webhooks | Automatic sync into native WordPress posts | No sync; live embed of Loxo’s page |
| Google for Jobs JobPosting schema | Yes, on every job page | Yes, added in v2.3.1 | Not advertised | No; content is not on your domain |
| XML job sitemap | Yes | Not advertised | Not advertised | No |
| Application form | Yes, posts into Loxo | Yes, apply form with CV upload | Yes, applications tracked back into Loxo | Handled by Loxo |
| Spam protection on the form | Yes, Google reCAPTCHA v3 | Yes, captcha integration | Not advertised | Handled by Loxo |
| Real-time webhooks | Yes: job.create, job.update, job.destroy | Yes, with one-click regeneration | Not advertised | Not applicable |
| Google Indexing API | Yes | Not advertised | Not advertised | No |
| View and application tracking | Yes, per-job view and application counts | Not advertised | Applications tracked into Loxo | Not on your site |
| Gutenberg blocks | Yes, 7 blocks | Not advertised; Elementor, Bricks, WPBakery, shortcode | Not advertised; works with WP Job Manager, RecPress, custom post types | No |
| REST API | Yes, under loxo/v1 | Not advertised | Not advertised | No |
A note on the price row, because it is not a clean comparison. LimeStaff sells three tiers and LoxoWp sells two, so the tiers do not line up. LimeStaff is cheaper at every comparable tier. JobRelay is priced in pounds as a subscription service rather than a per-site license. Convert and compare against your own site count before deciding.
When each option fits
The iframe embed
Use it when the careers page is a formality. If candidates arrive from LinkedIn, job boards, or your recruiters directly, and nobody expects to be found on Google, an iframe is genuinely fine. It is free, it never breaks on a plugin update, and there is nothing to maintain.
The trade-offs are real, though. The embedded content is not indexed as yours, so those roles will not appear in Google for Jobs under your brand. Styling control is limited to whatever the embed allows. And you get no analytics on your own site about which roles people actually look at.
LimeStaff
It is the cheaper plugin, and it is page-builder-first. If your site is built in Elementor or Bricks, LimeStaff ships native widgets for both, plus a shortcode for WPBakery and anything else. That is a genuine advantage over blocks if a page builder is how your site is maintained.
Its recent releases also closed real gaps: JobPosting schema arrived in v2.3.1, and webhooks and captcha are both advertised. If what you need is a styled job list, working applications, and basic Google for Jobs eligibility, $39 buys that. We would rather say so than pretend otherwise.
JobRelay
JobRelay solves a different problem. It is a sync service that feeds Loxo jobs into a job board you already run, whether that is WP Job Manager, RecPress, or a custom post type. It maps Loxo fields onto your post meta and taxonomies, and it writes applications back into Loxo.
That makes it the right answer when you have already invested in a job board setup and do not want to replace it. You are paying a subscription for the pipe, not for the front end. If you have no job board yet, you would be buying JobRelay plus something to display the jobs.
LoxoWp
LoxoWp is built for agencies where organic search is part of how candidates arrive. That is the honest positioning. The sync, the board, and the application form are table stakes now. What you are paying the difference for is the SEO layer around them.
Concretely: an XML jobs sitemap so crawlers find listings, Google Indexing API pings so changes reach Google without waiting for a crawl, and per-job view and application counts so you can tell which roles are working. The free Auto-Extend Expiry add-on keeps expiration dates rolling forward, so long-running roles do not silently drop out of Google for Jobs.
It also assumes a developer might be involved. Seven Gutenberg blocks, overridable templates, a full REST API under loxo/v1, and documented filters mean the output can be reshaped rather than merely restyled.
If none of that matters to you, buy the cheaper plugin. If a candidate finding your listing on Google is worth more than $30 a year, this is the one to look at.
Try LoxoWp
$69 per year for a single site, or $159 for up to 5 sites. Both tiers include every feature, one year of updates, and one year of support. See pricing and get the plugin, or read the documentation first to check it fits your setup.
Frequently asked questions
Is the cheapest Loxo WordPress plugin good enough?
Often, yes. If you need a job list, an application form, and basic Google for Jobs eligibility, the cheaper options cover it. The difference shows up in SEO depth: sitemap, Indexing API, expiration management, and on-site tracking. Buy for the features you will actually use.
Can I switch plugins later without losing my job URLs?
Plan for URLs to change. Each plugin uses its own post type and permalink structure, so slugs rarely match after a migration. Jobs re-import from Loxo either way, since Loxo remains the source of truth. Set up redirects from the old job URLs to preserve any rankings you have built.
Why not just build the integration ourselves?
It is a fair option if you have in-house developers. Note what the build actually includes: API authentication, paginated background imports, webhook handling, valid JobPosting schema, a sitemap, and a spam-resistant application form. Most of the cost is not the first version. It is maintaining it as the API and Google’s requirements change.
Do any of these replace Loxo itself?
No. All of them require an active Loxo.co account and read from it. Your recruiters keep working in Loxo. These tools decide how those roles appear on your own website. More answers are on the FAQs page.