Test and hand over the OndaWorx Job Board
OndaWorx · Job Board implementation · Step 7

Test and hand over the Job Board

Complete the final public checks, confirm candidates can find and apply for Jobs safely, verify the SEO configuration and give the customer a clear record of how their OndaWorx implementation is configured.

Test the public site as a visitor, not as a Salesforce administrator. Carry out the final checks in a private/incognito browser while completely signed out of Salesforce. An Experience Cloud page that works while you are logged into Salesforce has not yet proved that the public Guest User permissions are correct.

1. Prepare the final test

Before starting, identify a small set of Job records that let you test both successful and unsuccessful cases.

Test record What you need
Published Job A normal live Job containing title, description, location, employment type and other fields used by the public Job Board.
Unpublished / closed Job A Job that should not appear publicly. Keep its direct Job Detail URL for testing.
Filter examples Jobs covering the values used by the public search filters, such as different industries, employment types and regions.
Incomplete Job A Job missing one or more optional fields so you can confirm the public page still displays cleanly.

Record the implementation details

Create a simple implementation record containing:

  • installed OndaWorx package version
  • public Experience Cloud site URL
  • main Jobs URL
  • Job Detail route
  • any additional landing-page URLs
  • Salesforce Job object API name
  • OW Job Board Page Developer Names in use
  • the field used to decide whether a Job is published
  • the exact value representing a public Job
  • any customer-specific field mappings
  • any Custom Metadata layouts that had to be manually updated after installation
  • whether CV upload is enabled
  • whether the separate OndaWorx Job SEO Links utility is installed
  • whether advanced Route Dimensions are being used
Why record Custom Metadata layout changes? If an administrator had to add packaged fields to a Custom Metadata Page Layout after installation, record which layouts were changed. This gives the customer and implementation partner a useful reference if future package upgrades introduce additional configurable fields.

2. Test the public Job List

Open the main Jobs page in a private/incognito browser.

  • the Jobs page loads without a Salesforce login
  • published eligible Jobs appear
  • unpublished or closed Jobs do not appear
  • the number of Jobs displayed is sensible
  • pagination or further results work correctly
  • Job titles are correct
  • location information is correct
  • employment type and other badges are correct
  • salary information is formatted correctly
  • summaries display correctly
  • missing optional fields do not leave empty or misleading labels
  • the Job cards work on a mobile-sized screen

Test every public search filter

  • each filter displays the expected choices
  • selecting a value narrows the results correctly
  • selecting several compatible filters works
  • Clear Filters restores the Job List
  • the filter state survives a page refresh where intended
  • dependent filters such as Region and County behave correctly
  • a search with no matching Jobs displays an appropriate empty result

Test sorting

  • the configured default sort is correct
  • each additional Sort option works
  • changing the sort does not remove the selected search filters

Test additional landing pages

If the customer has Permanent Jobs, regional pages, industry pages or other landing pages, test each one directly.

  • the public URL loads directly
  • refreshing the URL works
  • the correct fixed Jobs are displayed
  • unpublished Jobs remain hidden
  • H1 and introductory content match the purpose of the page
  • filters shown on the page are useful for that Job set

3. Test the public Job Detail page

Click a live Job from the Job List and also test the same Job using its direct public URL.

  • the correct Job opens
  • the page works from both the Job card and a direct URL
  • refreshing the page works
  • the Job title is correct
  • badges and Job facts are correct
  • salary or pay information is correct
  • the full Job Description displays correctly
  • blank optional fields do not create empty labels
  • the page remains usable on a mobile-sized screen

Test Job Location

  • the configured Job location appears correctly
  • the secondary location is correct where one is configured
  • the map button appears only when intended
  • the map search uses the expected location

Test an unavailable Job directly

Open the saved direct URL for an unpublished or closed Job.

This is a mandatory test. A Job disappearing from the Job List is not enough. Someone may still have the old Job URL from a search engine, email or bookmark.
  • the Job is not presented as an available live vacancy
  • the full unavailable Job content is not exposed incorrectly
  • the page provides the intended unavailable/expired Job behaviour
  • the visitor can return to the current Jobs page

4. Test the Application Form

OndaWorx Applications is part of the standard Job Board implementation, so a complete acceptance test should include a real test application.

Submit a test application

From a published Job Detail page:

  • the Application Form appears
  • the form is clearly associated with the correct Job
  • required fields behave correctly
  • privacy wording is visible
  • the Privacy Policy link opens the customer's correct privacy policy
  • the applicant can submit the form successfully
  • an OW Application record is created in Salesforce
  • the Application is linked to the correct Job
  • applicant name, email, phone and other submitted information are correct
  • consent information is recorded as intended

If CV upload is enabled

  • a candidate can upload the intended file type
  • the Application can still be submitted successfully
  • the uploaded CV appears under Files on the correct OW Application record
  • another public visitor cannot access that CV
If the customer deliberately uses an external application process replace these Application Form checks with equivalent acceptance tests for the customer's chosen ATS, external form or application destination. That is an alternative implementation rather than the standard OndaWorx path.

5. Confirm public access is restricted correctly

The public site should provide only the access required to browse Jobs and submit an Application.

  • public visitors can read only the Job information intended for the website
  • visitors cannot edit Job records
  • visitors cannot create or delete Jobs
  • visitors cannot browse Salesforce records outside the intended Job Board
  • visitors cannot browse existing OW Application records
  • visitors cannot open another candidate's Application
  • visitors cannot open another candidate's uploaded CV
  • the public site does not expose administrator-only functions
Do not test security while logged into Salesforce. Administrator access can hide public-permission problems. Always perform these checks while signed out.

6. Complete the SEO checks

Test at least one live Job and one unavailable Job.

Live Job

  • the Job page has one clear H1 containing the correct Job title
  • the browser/page title is correct
  • the SEO description is appropriate
  • the canonical URL points to the intended preferred Job URL
  • JobPosting structured data is present
  • JobPosting title matches the actual Job
  • description matches the actual Job
  • employment type is correct
  • location data is correct
  • salary and currency are correct where supplied
  • date posted is correct
  • valid-through date is correct where supplied
  • Hiring Organisation Name is correct and is not left as an example value

Unavailable Job

  • it is not presented as an available vacancy
  • it does not incorrectly expose active JobPosting structured data
  • the public behaviour is appropriate for an expired or withdrawn Job

Google checks before handover

For the production website, check at least one representative live Job using Google's public testing tools.

  • test a live Job URL with Google's Rich Results Test
  • confirm the JobPosting data can be read correctly
  • make sure the public Job URLs are included in the customer's sitemap where applicable
  • make sure the customer has access to Google Search Console for the production domain
  • inspect a representative Job URL in Search Console after launch
Google Indexing API is not required for standard OndaWorx setup. OndaWorx Job Board pages can be crawled and indexed using the normal website, sitemap, internal linking and Search Console process. Any separate Indexing API implementation is an additional customer-specific service and is not part of this standard setup checklist.

7. Test separately supplied or advanced features when used

OndaWorx Job SEO Links

Job SEO Links is a free companion utility supplied separately from the managed Job Board package.

If it has been installed for this customer, test it now.

  • the SEO Links section appears on an eligible public Job
  • the wording reflects the current Job
  • every link points to the correct public Job search
  • links use normal crawlable public URLs
  • missing Job values cause unsuitable links to be omitted
  • the component also works while signed out

If Job SEO Links has not been installed, simply skip these checks.

Advanced Route Dimensions

If the implementation does not use dynamic Route Dimensions, skip this section.

If they are used, confirm:

  • the dynamic URL opens directly while signed out
  • refreshing the URL works
  • the correct route value is applied
  • unpublished Jobs remain excluded
  • unknown route values fail safely
  • page heading and SEO information match the route
  • canonical and indexability behaviour are correct

8. Test normal day-to-day operation

The customer should not need to change Custom Metadata simply to publish and withdraw normal Jobs.

With an authorised internal user:

  1. Create or identify a test Job.
  2. Enter the information used by the public Job Board.
  3. Change the Job into the customer's published/open state.
  4. Confirm it appears publicly as expected.
  5. Update a visible field and confirm the public page reflects the change.
  6. Withdraw or close the Job.
  7. Confirm it disappears from current Job Lists.
  8. Open its previous direct URL and confirm the unavailable Job behaviour.
This is the most important customer test. Once OndaWorx has been configured, normal Job publishing should feel like normal Salesforce Job management. The customer should not need an implementation partner every time a Job is added, changed or withdrawn.

9. Hand over to the customer

The customer should receive enough information to manage the Job Board confidently without needing to understand how the managed package was built.

Give the customer

  • the OndaWorx package version installed
  • public site URL
  • main Jobs URL
  • Job Detail URL pattern
  • list of additional landing pages
  • Job object used
  • Page Developer Names used
  • publication field and public value
  • important customer-specific field mappings
  • privacy-policy URL and approved consent wording
  • whether CV uploads are enabled
  • whether Job SEO Links is installed
  • whether any advanced Route Dimensions are used
  • any manual Custom Metadata Page Layout changes made after installation
  • links to the relevant OndaWorx setup documentation

Demonstrate these normal tasks

  • publish a Job
  • edit a published Job
  • withdraw or close a Job
  • view Applications received against a Job
  • find an uploaded CV where CV upload is enabled
  • identify the public URL for a Job

Explain what normally requires configuration

Examples include:

  • adding a new public Job field
  • adding a new search filter
  • creating a new landing page
  • changing Job Detail layout
  • changing SEO field mappings
  • changing the public URL structure
  • switching to an external application process

Agree ownership

Area Suggested owner
Job content and publishing Recruitment / HR team
Applications and candidate data Recruitment / HR team
Salesforce permissions Salesforce administrator
OndaWorx Custom Metadata Salesforce administrator or implementation partner
Experience Cloud pages Salesforce administrator / website owner
Search Console and SEO monitoring Website / marketing owner
Package upgrades Salesforce administrator / implementation partner

10. Final acceptance

Before declaring the implementation complete, confirm:

  • the public Job List works while signed out
  • publication rules prevent unavailable Jobs appearing
  • direct unavailable Job URLs behave correctly
  • filters and sorting work
  • Job Detail fields are correct
  • Job Location works
  • applications are submitted successfully
  • candidate Applications and CVs remain private
  • privacy wording is correct
  • SEO title, description, canonical and JobPosting have been checked
  • important landing pages work directly
  • mobile behaviour has been checked
  • normal publish/edit/withdraw workflow has been demonstrated
  • the customer has received the configuration record and documentation
Record customer-specific differences. If the implementation differs from the standard OndaWorx setup — for example a custom Job object, external ATS, unusual publication rule, cross-site canonical or dynamic routes — record that clearly in the handover.
OndaWorx Job Board implementation complete The customer should now be able to manage normal Jobs and Applications without OndaWorx or the implementation partner being involved in day-to-day operation.

Return to: OndaWorx Job Board · Start Here

Guide updated 10 October 2026. Complete these checks against the customer's actual production configuration before final handover.