Configure Job Board URLs and routes | OndaWorx
OndaWorx · Job Board implementation · Step 6

Configure Job Board URLs and routes

Connect your OndaWorx Job Board configurations to real public Experience Cloud URLs and create useful landing pages for important Job searches.

Most customers do not need advanced routing. The simplest and recommended setup is to create normal Experience Cloud pages for the main Jobs page and any important landing pages. OndaWorx Route Dimensions are available for more advanced implementations, but they are not required for a standard Job Board.

How OndaWorx URLs work

There are two parts to an OndaWorx Job Board page:

OndaWorx configuration The OW Job Board Page record controls the jobs, filters, fields, headings and other settings for that logical Job Board page.
Experience Cloud page Salesforce Experience Builder creates the real public website page and URL that visitors open.
The URL Path field does not create a website page. For example, entering permanent-jobs in an OW Job Board Page record does not automatically create: https://www.example.com/permanent-jobs You must also create or configure the corresponding public route/page in Experience Builder.

1. Configure the main Jobs URL

The standard OndaWorx package includes the Jobs Page configuration.

In Experience Builder, create or open the customer's main public Jobs page.

A typical public URL might be: 

https://www.example.com/jobs

Add the OndaWorx Job List component to this page.

Set:

Component property Value
Job Board Page Developer Name Jobs

Make sure the corresponding OW Job Board Page record uses a sensible URL Path such as:

jobs

Keep the first implementation simple. Get the main Jobs page and Job Detail page working correctly before creating additional landing pages.

2. Create useful Job landing pages

A landing page is a dedicated public Job page focused on a useful category, location or employment type.

Examples might include:

  • Permanent Jobs
  • Temporary Jobs
  • IT Jobs
  • Construction Jobs
  • Jobs in London
  • Jobs in Yorkshire

These can be useful for visitors and for search engines because each page has a clear purpose and a relevant set of Jobs.

Recommended method: static landing pages

For a small number of important landing pages, use a dedicated OW Job Board Page record for each one.

For example, a Permanent Jobs page might use:

Setting Example
Label Permanent Jobs
Developer Name Permanent_Jobs
URL Path permanent-jobs
Fixed publication filter Published / Open Jobs only
Fixed employment filter Permanent

Then create the matching Experience Cloud page and connect the OndaWorx Job List component to:

Permanent_Jobs

Example: location landing page

A page such as: 

/jobs-in-yorkshire

could use a fixed Region filter so only Jobs in Yorkshire are shown.

Do not duplicate unnecessary filters. If a page already contains only Permanent Jobs, an Employment Type dropdown may not add much value. If a page already contains only Yorkshire Jobs, a Region dropdown may also be unnecessary. Keep each landing page useful and simple.

3. Connect each landing page in Experience Builder

For every public landing page:

  1. Open the customer's Experience Cloud site in Experience Builder.
  2. Create or open the page that will use the intended public URL.
  3. Add the OndaWorx Job List component.
  4. Select the component.
  5. Set Job Board Page Developer Name to the exact Developer Name of the matching OW Job Board Page record.
  6. Publish the Experience Cloud site.
  7. Open the public URL while signed out.
Developer Name must match exactly. If the OndaWorx Page Developer Name is: Permanent_Jobs enter exactly: Permanent_Jobs in the Job List component.

4. Check each public landing page before publishing it

A landing page should exist because it is useful to a Job seeker, not simply because a filter combination can be created.

Before making a landing page publicly available, check:

  • the page has a clear H1 heading
  • the introductory text explains what Jobs the page contains
  • the page contains a useful number of relevant Jobs
  • the fixed filters produce the intended results
  • unpublished Jobs remain excluded
  • the page title and SEO description are relevant
  • the public URL is clear and readable
  • visitors can reach the page through useful website links
  • the page is not a near-duplicate of another landing page
Avoid creating hundreds of thin Job pages. Do not create a landing page for every possible combination of profession, location and employment type simply because OndaWorx can filter the Jobs. Create pages where there is a genuine candidate use case and useful content.

Example

This can be useful: 

Veterinary Surgeon Jobs in Yorkshire

if the customer regularly has suitable Jobs in Yorkshire.

A highly specific page such as: 

Part-Time Veterinary Surgeon Jobs in One Small Town

may not be useful if it normally contains no Jobs or only duplicates another page.

5. Advanced option: Route Dimensions

Advanced configuration — most customers can skip this section. You do not need Route Dimensions to complete a normal OndaWorx implementation. Use static Experience Cloud landing pages for important public URLs unless the implementation specifically requires dynamic path-based routing.

OndaWorx includes OW Job Board Route Dimension metadata for advanced implementations.

Route Dimensions describe concepts such as:

  • industry
  • profession
  • employment type
  • region
  • county

They can be used by a supported routing implementation to map readable URL values to Job fields.

Creating a Route Dimension does not create a public URL. The Experience Cloud site must also have the routing implementation required to recognise and handle that dynamic path. Do not publish or promote dynamic URLs until they have been fully tested on the customer's public site.

Route Dimension settings

Open:

Setup Custom Metadata Types OW Job Board Route Dimension Manage Records
Field What it controls
Active Controls whether this Route Dimension is available.
Page The base OW Job Board Page that the dimension belongs to.
Dimension Name A stable internal name describing the route concept, for example county or industry.
Field API Name Salesforce Job field that the route value should filter. Example: County__c.
Operator How the route value is compared with the Salesforce field. Use the operator appropriate to the field and implementation.
Display Order Ordering of Route Dimension metadata where several dimensions are used.
SEO Label Human-readable wording for this dimension.
SEO Indexable Indicates whether matching routes may be considered for indexing by the wider routing/SEO implementation. It does not by itself guarantee that a URL will be indexed.
Route Dimensions are configuration for a routing system. They do not replace the Experience Cloud route itself and should not be treated as an automatic URL generator.

Before enabling dynamic routes

Confirm all of the following:

  • a direct dynamic URL loads while signed out
  • refreshing the dynamic URL continues to work
  • the path filters the correct Salesforce Jobs
  • unpublished Jobs remain excluded
  • unknown route values fail safely
  • ambiguous route values do not produce misleading results
  • H1, title and description match the route
  • canonical behaviour is correct
  • only useful intended routes are indexable
  • Job cards link to the correct public Job Detail pages

6. Test URLs while signed out

Test every important public URL in an incognito/private browser while signed out of Salesforce.

Main Jobs page

  • the direct Jobs URL loads correctly
  • refreshing the page works
  • the expected Jobs appear
  • filters work
  • View Job opens the correct public Job Detail page

Landing pages

  • every landing-page URL loads directly
  • refreshing the page works
  • the correct fixed filters are applied
  • the H1 and introductory copy match the intended page
  • the page contains useful Jobs
  • no unpublished Jobs appear

Job Detail URLs

  • a Job opens correctly from a Job card
  • the Job Detail URL can be opened directly
  • refreshing the Job Detail page works
  • unavailable Jobs do not expose live Job content
  • the canonical URL is the intended URL
URL and route setup complete If the standard Jobs page, landing pages and Job Detail URLs all work correctly while signed out, continue to: Testing and handover .

Common setup problems

Problem Check first
Page works in Builder but not at the public URL Confirm the Experience Cloud site has been published and the public route exists.
Job List is blank on one landing page Job List component Page Developer Name, active Page record, fixed filters and eligible test Jobs.
Landing page shows the wrong Jobs Fixed filters linked to that OW Job Board Page.
URL Path was entered but the URL returns an error Create or configure the matching Experience Cloud page/route. URL Path alone does not create it.
Dynamic Route Dimension does nothing A Route Dimension is only metadata. Confirm the site's supported dynamic routing integration is actually present and configured.
Dynamic URL works until the browser is refreshed The Experience Cloud route itself is not correctly handling the direct path.
Search engines could see too many similar pages Reduce unnecessary landing pages and review which routes are genuinely useful and intended to be indexable.

Continue: Testing and handover →

Guide updated 10 October 2026. For a standard implementation, static Experience Cloud pages are the recommended approach. Route Dimensions are an advanced option.