Customer installation guide
OndaWorx Job SEO Links
OndaWorx Job SEO Links is a lightweight Salesforce Experience Cloud utility that adds useful internal links to public job-detail pages. The component is configured with Custom Metadata, so it can work with different job objects, field names, industries and public job-board URLs.
Important: this utility does not require the OndaWorx Job Board package.
It can be configured against a customer's own job object and public Experience Cloud job pages.
1. What the component does
On a public job-detail page the component can display links such as:
Looking for something else? Locum Veterinary Jobs in South West England · Locum Veterinary Jobs · Veterinary Surgeon Jobs
Each link is a normal crawlable <a href> link. The component does not create
JobPosting structured data and does not alter canonical URLs.
2. Before you configure it
Identify the following information in the customer Salesforce org:
- The API name of the job object.
- The field that represents the main job category, profession or discipline.
- The employment-type field, if used.
- The county/local-area field, if used.
- The region/state field, if used.
- The field used to decide whether a job is publicly published.
- The value that represents a published job.
- The public job-search/list URL.
- The query-string parameters used by the public job search.
3. Create the main SEO Link Configuration record
In Salesforce Setup, open Custom Metadata Types, find OW SEO Link Config, and select Manage Records. Create one configuration record for the public job board.
| Field | What to enter |
|---|---|
| Label | A clear customer/site name, for example Recruit4vets. |
| Developer Name | A unique API-safe name, for example Recruit4vets. You will also enter this value in Experience Builder. |
| Enabled | Tick to make the configuration active. |
| Job Object | The API name of the job object, for example Job__c or OW_Job__c. |
| Category Field | The API name of the profession/category/industry field. |
| Employment Type Field | The API name of the employment-type or role-type field. Leave blank if not used. |
| County Field | The API name of the county/local-area field. Leave blank if not used. |
| Region Field | The API name of the state/region field. Leave blank if not used. |
| Published Field | The API name of the field that determines whether the job is public. |
| Published Value |
Enter the exact value stored in the Published Field for a publicly available job.
Examples: true for a checkbox field, Open for a text/picklist status,
or Published if that is the value used by the customer.
|
| Base Search URL | The public job-list/search page, for example https://www.example.com/jobs. |
| Section Heading | The heading shown above the links, for example Looking for something else?. |
Published Value must match the stored value exactly.
Do not assume it is
true. If the Published Field is a text or picklist field,
inspect an existing live job and use the actual value stored there.
Do not use the individual job-detail URL as the Base Search URL.
This value must point to the public job-list/search page that accepts the filter parameters used in the link templates.
4. Create SEO Link Template records
In Custom Metadata Types, find OW SEO Link Template, select Manage Records, and create the links you want displayed. Each template belongs to the configuration record created above.
| Field | Purpose |
|---|---|
| Enabled | Tick to make this template active. |
| Sort Order | Controls the order of links. Lower numbers appear first. |
| Anchor Template | The human-readable link text shown to visitors. |
| URL Template | The target URL using tokens and the customer's public search parameters. |
| Required Values | A comma-separated list of tokens that must contain values before this link is shown. |
| Config | Select the configuration record for this customer/site. |
Supported tokens
| Token | Value |
|---|---|
{BaseSearchURL} | The Base Search URL from the configuration record. |
{Category} | The current job's configured category/profession/industry value. |
{EmploymentType} | The current job's configured employment-type value. |
{County} | The current job's configured county/local-area value. |
{Region} | The current job's configured region/state value. |
Token values in URLs are encoded automatically. For example, IT & Technology
becomes IT+%26+Technology.
Example template set
The exact parameter names depend on the customer's public job-search page.
| Sort | Anchor Template | URL Template | Required Values |
|---|---|---|---|
| 10 | {EmploymentType} {Category} Jobs in {Region} |
{BaseSearchURL}?employment-type={EmploymentType}&category={Category}®ion={Region} |
EmploymentType,Category,Region |
| 20 | {EmploymentType} {Category} Jobs |
{BaseSearchURL}?employment-type={EmploymentType}&category={Category} |
EmploymentType,Category |
| 30 | {Category} Jobs |
{BaseSearchURL}?category={Category} |
Category |
A template is automatically omitted when one of its Required Values is missing.
This avoids malformed or misleading links.
5. Public Experience Cloud permissions
The public Experience Cloud guest user must be able to execute the SEO Links Apex service and read both SEO Links Custom Metadata Types.
The guest user must also already have appropriate public read access to the configured job object, the configured job fields, and the specific published job records. OndaWorx Job SEO Links does not grant broad access to the customer's job data.
Grant access through the Guest User Profile
- In Salesforce Setup, go to Digital Experiences → All Sites and open the public Experience Cloud site.
- Open the site's Public Access Settings or Guest User Profile.
- On the Guest User Profile, open Enabled Apex Class Access.
-
Click Edit, add
OWSeoLinkServiceto the enabled Apex classes, and save. - Return to the Guest User Profile and open Enabled Custom Metadata Type Access.
-
Click Edit and enable:
- OW SEO Link Config
- OW SEO Link Template
- Save the changes.
- Confirm that the Guest User Profile already has read access to the configured job object and every job field used by the SEO Links configuration.
- Confirm that published job records are shared to the guest user using the customer's existing public-sharing model.
Do not add OndaWorx SEO Links Public under Experience Cloud Members.
The Members screen controls site membership. It does not grant the required access to the
unauthenticated guest user.
The supplied OndaWorx SEO Links Public permission set contains the utility-specific
Apex and Custom Metadata permissions, but for unauthenticated Experience Cloud guest users the
clearest manual setup is to enable the Apex class and Custom Metadata Type access directly
on the site's Guest User Profile as described above.
6. Add the component in Experience Builder
- Open the customer's public Experience Cloud site in Experience Builder.
- Open the job-detail page.
- Drag OndaWorx Job SEO Links onto the page, normally below the main job content or application section.
- Select the component.
- In SEO Link Configuration, enter the exact Developer Name of the configuration record created earlier.
- Publish the Experience Cloud site.
The component is intentionally shipped without a customer-specific default configuration.
The Experience Builder property must point to a valid enabled configuration record in the customer org.
7. Test while signed out
Always test the finished page in a private/incognito browser window.
If the component is blank in Experience Builder as well as on the public site, check the
Custom Metadata configuration first, particularly Published Field,
Published Value, the configured field API names, and whether the templates
are enabled and linked to the correct Config record.
- Open a published job-detail URL.
- Confirm the SEO section appears.
- Confirm the link wording matches the current job.
- Click every link and confirm the correct filtered job-search results appear.
- Confirm the links open in the same browser tab.
- Test jobs with missing optional values and confirm unsuitable links are omitted.
- Test an unpublished/inaccessible job and confirm the SEO links are not exposed.
8. Troubleshooting
| Symptom | Check |
|---|---|
| The component is blank only when signed out. |
Check the Guest User Profile has access to OWSeoLinkService,
OW SEO Link Config, OW SEO Link Template,
the configured job object and fields, and the published job records.
|
| The component is blank in Builder and on the public page. | Check that the configuration is enabled, that the Experience Builder component uses the exact configuration Developer Name, and that Published Value exactly matches the value stored on a live job. |
| The component works in Builder but not on the public page. | Use the browser Network panel to inspect failed Apex requests. A Custom Metadata access problem can appear as an unsupported sObject-type error. |
| Only some links appear. | Check the template's Required Values and the corresponding values on the current job. |
| A link opens the wrong results. | Check the URL Template parameter names against the customer's actual public job-search filters. |
| No links appear on any job. | Check that the configuration is enabled and that the Experience Builder component uses the exact configuration Developer Name. |
9. Design principles
- No dependency on the OndaWorx Job Board package.
- No customer-specific object or field names hard-coded in the component.
- No customer-specific URLs hard-coded in the component.
- No customer-specific Custom Metadata configuration is supplied by default.
- No AI, external API or sitemap dependency.
- No JobPosting structured data generated by this utility.
- Normal crawlable links are used for internal navigation and SEO.
OndaWorx Job SEO Links – customer setup guide.