Release 16/2026 (11.08.2026)

Job alerts can now automatically adjust their send frequency based on candidate engagement, instead of staying fixed at a single interval. When a candidate regularly clicks into jobs included in the job alert email, the frequency stays daily; if they go inactive, it gradually steps down to weekly, then monthly, and eventually stops after prolonged inactivity, resetting to daily as soon as they engage again. This is an optional feature, and the default periods of inactivity can be adjusted to fit a job board's needs.

Location search on job search pages can now use a structured, pre-built location dataset instead of live autocomplete. This optional setup delivers the same accurate location matching while reducing costs from external geocoding services.

Job search pages now include structured breadcrumbs that reflect the site hierarchy: Jobs > Industry > Occupational Field > Job Title, helping Google better crawl and understand your content. Clear breadcrumb structure provides search engines with data in a structured way, supporting better indexing of your job pages.

Job detail pages now include internal links to location search pages, and employment type search pages, improving SEO visibility for job search pages. Well-structured internal linking helps search engines better discover and understand your content, which can improve rankings and traffic over time

If location restrictions are configured, they now apply consistently across all address fields: jobs, organizations, and applicant profiles. This keeps address data aligned platform-wide, so recruiters and applicants alike can only enter locations within the allowed area.

Site admins can now use a filter at the top of the GDPR consent overview in the backend to narrow the results to a single site. Selecting a frontend displays only its consent data, ensuring that exports are clearly scoped to that frontend.

When enabling the "recruiter approval by site admin" feature, admins can now automatically verify all existing recruiter accounts in one step, instead of approving each one manually. This bulk action is optional, so admins can still choose to verify accounts individually if preferred, and no verification emails are sent as a result of the bulk process.

For organizations with both an active job posting subscription and a job credit pack, posting a job now uses the subscription first instead of deducting a credit. Job credits are only used when no active subscription applies, ensuring organizations get full value from their subscription.

We fixed an issue on desktop job search pages where filters would load in shortly after the initial page render, causing content to minimally shift position. Since Google uses layout stability as part of its page experience ranking signals, this update supports better SEO performance alongside a smoother browsing experience for all sites.

For jobs with multiple locations, we fixed an issue that caused the location dropdown to sometimes appear in a random position on the page instead of beneath the "+" icon. 

On multi-language sites, CSV and Excel exports from the recruiter job manager page could come back empty when using non-English language settings. Exports now work correctly regardless of the site's language setting.

On multi-language sites, the resume database page could sometimes show no results for employers browsing in a non-default language. Resumes are now correctly indexed for all site languages, so employers see consistent results no matter which language they're using.

We fixed a bug that caused some landing pages to show a "too many redirects" error when the URL contained tracking parameters with special characters, such as spaces or commas that added automatically by some email marketing tools. Landing pages now load correctly regardless of the special characters in the URL.

We fixed an issue where an active site campaign with no text entered in its content (body) field could cause a server error on every page displaying it. Pages now load normally even if a campaign's content field is left blank.

We fixed a bug where changing the location of a job right after cloning it would update the backend correctly but still show the old location on the frontend. Now, cloned jobs display the updated location right away.

Whenever postal code validation failed, users were blocked from saving changes to geography taxonomy terms and synonyms, with an error shown instead of a save. Editing and saving taxonomy terms now works as expected, with a clear message shown if something needs to be corrected.

We fixed an issue where a job alert could show a job and a link for a different location than the one saved in the search. This happened when a search's title was changed manually and became out of sync with the actual saved location. The title field has been removed from the job alert edit form, so saved searches always match the location a user searched for.

Job searches could create new, incorrect location entries in the system, which sometimes caused mismatched location results, like a random address being linked to "UK, Remote" search entry. Location data has been cleaned up, and job searches can no longer generate taxonomy entries on their own, keeping search locations accurate.