Job URL redirect

allow jobylon job urls to seamlessly redirect candidates to externally hosted career site pages overview the job url redirect feature enables companies to host their job pages on their own cms or career site while continuing to use jobylon ats for recruitment workflows and candidate tracking when enabled, all public job urls redirect candidates to a corresponding external job page based on a configurable url pattern this allows career site builders and cms integrations to own the candidate facing job experience control seo and branding serve jobs from external infrastructure continue using jobylon as the ats backend how it works jobylon can redirect traffic to one configured destination pattern the redirect url is dynamically generated using identifiers associated with the job being viewed supported identifiers include job id company id job language important architectural principle jobylon only controls the destination url pattern the identifiers included in the redirect jobylon does not control how the external career site structures its pages internal routing on the client side additional redirects after the initial redirect cms specific logic think of it like package delivery jobylon provides the destination address and package metadata the career site decides how to process and route the visitor internally redirect flow example flow a candidate visits a public jobylon job url https //emp jobylon com/jobs/8471 software engineer/ jobylon generates a redirect url using the configured pattern https //company com/jobs/{{ job id }} placeholders are replaced with job specific values https //company com/jobs/8471?source=jobylon the candidate is redirected to the external career site the external career site handles page rendering internal routing localization additional redirects seo handling supported placeholders the redirect pattern supports the following placeholders \| placeholder | description | {{ job id }} the jobylon job id {{ company id }} the jobylon company id {{ job language }} the language code associated with the job no other placeholders are supported pattern examples given job id = 8471 company id = 356 job language = nl redirect pattern | final redirect url https //company com/jobs/{{ job id }} | https //company com/jobs/8471 https //company com/company/{{ company id }}/jobs/{{ job id }} | https //company com/company/356/jobs/8471 https //company com/jobs/{{ job language }}/{{ job id }} | https //company com/jobs/nl/8471 https //company com/jobs/?job={{ job id }} | https //company com/jobs/?job=8471 https //company com/jobs/#{{ job id }} | https //company com/jobs/#8471 https //company com/jobs/?utm source=jobylon#{{ job id }} | https //company com/jobs/?utm source=jobylon#8471 responsibilities of the career site the external career site or cms integration is responsible for hosting job pages synchronizing jobs from jobylon resolving jobylon identifiers rendering job content handling missing jobs managing localization managing seo handling internal redirects recommended implementation career site builders should sync jobs from jobylon into their platform store jobylon identifiers generate stable external urls resolve incoming identifiers to internal content gracefully handle missing or unpublished jobs handling missing jobs there may be situations where the external career site has not yet synchronized a job from jobylon examples include newly created jobs draft jobs delayed synchronization jobs excluded from publishing in these cases, the external site may return 404 pages placeholder content redirects to listings pages this behavior should be handled by the career site implementation redirect scope redirects apply only to public job pages preview and internal editing pages are excluded skip filters jobylon supports optional filters to exclude specific jobs from redirect behavior examples include hidden jobs internal jobs confidential jobs best practices for career site builders use stable urls avoid changing external job urls after publication store jobylon ids always persist job id company id language these identifiers are critical for redirect resolution support graceful fallbacks if a job cannot be resolved show a helpful 404 page redirect to open positions provide search functionality preserve tracking parameters maintain utm and campaign parameters through internal routing summary the job url redirect feature enables companies to fully own the candidate facing job experience while continuing to use jobylon ats operationally jobylon’s responsibility is limited to redirecting traffic to one destination pattern providing job specific identifiers the external career site is responsible for resolving identifiers rendering pages managing routing and ux this separation keeps the integration flexible, scalable, and cms agnostic