Note: The below information relates to clients whose Personalised Job Pages (then Job Listing sites) were implemented prior to August 2021.
The following information has been written for a technical audience.
Commonly, a corporate careers home page will be hosted internally on your corporate website, for example: www.<clientname>.com/careers. This page may contain links to other content pages such as How to apply, Benefits of working with us and so on.
However, when implementing PageUp, portions of the careers website may be hosted by PageUp, namely Job search, Job alert and Existing applicant login. It is technically not possible for these parts of the website to also sit under www.<clientname>.com/careers as they are on PageUp servers, not yours.
Therefore PageUp requires for an alternative URL for these parts of the website, and our recommendation is a subdomain, for example http://careers.<clientname>.com. This URL can be pointed at our servers. Technical details of setting this up can be found below.
The design of the PageUp hosted parts of the website can look identical to your hosted careers website, and applicants will most likely not notice the change to the URL as they navigate around the site.
From a marketing perspective, you only need to advertise your corporate careers home page, for example http://www.<clientname>.com/careers as this can remain the single point of entry for your careers website.
- Create a new CNAME record under your current domain.
For example: http://careers.<clientname>.com
Note: the CNAME record needs to be created on both the Internal and External DNS servers.
- Point the new CNAME record to careers.pageuppeople.com
Ensure you use CNAMES, and do not simply redirect the page, otherwise careers.pageuppeople.com will display as the URL address instead of careers.<clientname>.com
- PageUp generates SSL certificate through AWS for the HTTPS site
- Client adds a new DNS record for the certificate, which validates the certificate.
Note: This must be done within 72 hours of the SSL certificate being generated by PageUp before it expires.
- PageUp generates the HTTPS version of the site
- Client updates original CNAME record for careers site to point to new HTTPS site rather than careers.pageuppeople.com
- Contact PageUp for the next steps.
All new career sites need to be setup under HTTPS as the standard default.
Managing certificate expiry and renewal
The certificates PageUp generate are valid for 12 months and will automatically renew for another 12 months provided the certificate remains active on the your side. If you remove the DNS record that verifies the certificate, the certificate will not renew.
PageUp cannot host your certificate as it can't be managed in a scalable manner. For example, if certificates expire every 12 months, there will the overhead to obtain and install a new certificate every 12 months. PageUp can only support the serving of client career sites over HTTPS via AWS Managed Certificates to which the process is automated on behalf of the client.
The HTTP version of the site displays despite the CNAME having been updated updated to point to the HTTPS site
This might be due to the TTL (time-to-live) setting. Check the duration set against this setting as the duration here will influence how soon you will see the CNAME updates become applicable. The standard default for this is 1 hour. You can also check if the delay is due to TTL by going to your CNAME via HTTP and provided the changes have been made, but you are not being redirected to HTTPS then this will be due to TTL.
Website not configured at this address
You may experience this message until the host headers are configured on PageUp servers.