You can create links to hard-to-fill jobs on the Home page by using the following methods:
Within the Featured Jobs component: This component allows you to display a list of jobs that you want to highlight on the Home page. You can select the jobs manually or use rules to filter them based on criteria such as location, function, or industry1. This way, you can showcase the hard-to-fill jobs to the candidates and encourage them to apply.
Within the Top Job Searches link in the footer: This link allows you to display a list of popular or trending job searches on the Home page. You can configure the link to show the top job searches based on the number of clicks, views, or applications2. This way, you can attract the candidates to the hard-to-fill jobs that are in high demand.
Reference:
SAP SuccessFactors Recruiting: Candidate Experience Administration, Unit 4: Career Site Builder Pages and Components, Lesson: Creating and Configuring Components, Slide 13 SAP SuccessFactors Recruiting: Candidate Experience Academy, Unit 4: Career Site Builder Pages and Components, Lesson: Creating and Configuring Components, Slide 14 SAP SuccessFactors Recruiting: Candidate Experience 2H/2023, Topic Areas: Career Site Builder Pages and Components <= 10%

You will enable Limit Search by Locale under Global Search options in Career Site Builder (CSB) under the following conditions:
The customer plans to translate the title and description for all job requisitions that are relevant for a specific locale. This will ensure that the candidates see the job requisitions in their preferred language and can apply more easily1.
The customer wants jobs returned in a search to be restricted to the locale the candidate selects on the CSB site. This will provide a more personalized and relevant experience for the candidates and filter out the jobs that are not applicable for their region2.
The other options are not valid conditions for enabling Limit Search by Locale in CSB:
The customer wants to host multiple locales on their CSB site, and Limit Search by Locale is required for that. This is not true, as Limit Search by Locale is an optional feature that can be enabled or disabled for each locale. The customer can host multiple locales on their CSB site without using this feature3.
The customer wants job alerts that the candidate receives to be restricted to the locale the candidate selects on the CSB site. This is not possible, as job alerts are based on the candidate's profile settings and not on the CSB site settings. The candidate can choose the language and location preferences for the job alerts in their profile4.

To configure the About Us links in the header, you need to do the following:
Create a list type link in the header named About Us. This will create a drop-down menu that can contain multiple links under the About Us label.
Create category type links in the header under About Us that link to the three internal pages. These pages are created using the Page Builder tool in CSB, and they can contain various components and content related to the customer's organization, such as mission, vision, values, culture, etc.
Create an external type link in the header under About Us that opens a new session and links to the page hosted on the customer's corporate site. This will allow the candidates to access more information about the customer's company from their main website.
Reference:
SAP SuccessFactors Recruiting: Candidate Experience Administration, Unit 2: Career Site Builder Pages and Components, Lesson: Header and Footer SAP Certified Application Associate - SAP SuccessFactors Recruiting: Candidate Experience 2H/2023, Topic Area: Career Site Builder Pages and Components <= 10%

According to the SAP Help Portal1, you should consider the following regarding mapping candidate statuses for Advanced Analytics:
Any status that indicates that the candidate was NOT hired, such as Automatically Disqualified, does need to be mapped. This is because all statuses must be mapped to one of the five standard statuses in Advanced Analytics: Apply Completed, Qualified, Interviewed, Offer Made, or Hired. If you have multiple not hired statuses, you can map them to ATS Capture, which is a hidden status that does not appear in the reports1.
After saving the status mappings in Command Center, you can correct mapping errors as long as you do it during the same session. This is because the status mappings are not pushed to the Advanced Analytics database until you log out of Command Center or close the browser. If you need to make any changes after logging out, you must contact SAP Customer Support to request a data purge and re-sync1.
With some exceptions, if a status is NOT mapped when the OData integration is run, the sync will fail. This is because the OData integration requires that all statuses are mapped to ensure data consistency and accuracy. The exceptions are when you have a new status that has not been used by any candidates yet, or when you have a status that is not used by any active job requisitions. In these cases, the sync will not fail, but you will receive a warning message and you should map the status as soon as possible1.
Status mappings can be completed even when there is no candidate data associated with each status on the Talent Pipeline. This is because the status mappings are based on the status names and not on the candidate data. You can map any status that exists in your Recruiting Management system, regardless of whether it has been used by any candidates or not1.

When setting up Real Time Job Sync, the values to populate the Service Provider Settings in Provisioning can be found in two places:
The URLs, Username, and Password are from CSB > Tools > Manage API Credentials1. The Manage API Credentials page allows you to enter or modify authentication information that connects SAP SuccessFactors Recruiting with Career Site Builder for Real Time Job Sync1.
The API Key is from CSB > Settings > Site Configuration > Site Integrations2. The Site Integrations page provides information about the integration between your career site instance and SAP SuccessFactors2