Recruitment website integrations: what to connect and what to check
In short
Plan a recruitment website integration as a set of specific journeys. Publishing a vacancy, accepting an application, registering a candidate and receiving an employer enquiry each need an agreed source, destination and failure process. Check your recruitment system’s permissions and supported operations before choosing an integration method or replacing your website.
Need help with this? Giig integration for WordPress
Map the journeys before choosing a plugin
Write down what the agency wants to happen and which system is responsible for each step. A connection that publishes vacancies does not necessarily accept applications or update candidate records. Avoid treating those as one feature called CRM integration.
- Vacancies: which published records should appear, which fields are public and how a closed job is removed.
- Applications: where the apply button leads, how the vacancy reference is retained and who reviews the result.
- General registration: what happens when someone is interested in future work rather than a named vacancy.
- Employer enquiries: which team receives a vacancy request and how it is followed up.
- Onboarding: which later forms or documents are requested and who can see them.
An embedded tool, a plugin or a custom connection?
An embedded or externally hosted jobs tool can provide a working application route with less work inside WordPress. Test the actual mobile journey, branding and navigation back to the agency site. An external destination is not automatically a problem.
A WordPress plugin or a custom connection may offer more control over presentation and routing. It also needs an owner for updates, account access and fault handling. WordPress provides APIs for exchanging content, but that does not establish which operations a separate recruitment system permits.
Ask the supplier to demonstrate your required journeys using the proposed method. Confirm what happens if an account changes, a service is unavailable or a software update affects the connection.
Define a field map and one main record
For each field, name its source and destination, accepted values and what should happen if it is missing. Decide which system owns the main vacancy and candidate record. Explain whether changes travel in one direction or both.
Use a sample vacancy with an unambiguous reference. Follow it from publication through an application and into the recruiter’s review route. Include a general registration so that someone without a vacancy reference still reaches the right process.
What to check for Giig and WordPress
Check the operations your Giig account supports, who can authorise access and which website changes are needed. List vacancy publishing, candidate registration, vacancy-linked applications and files separately. Agree a way to report and review failed operations.
Recruitment Connected assesses Giig connections around the account and website involved. The reusable plugin offer is in preparation; it is not presented as a download available for every account. Recruitment Connected is not affiliated with or endorsed by Giig.
Job-page visibility needs its own assessment
If your website publishes real vacancies, assess the individual job pages, their visible information and how closed roles are handled. Google’s JobPosting guidance describes requirements for eligible job pages and their structured data. Markup must match the actual vacancy; eligibility does not guarantee appearance.
A supplier’s service page or an illustrative vacancy in a demonstration is not a live job posting. Do not add JobPosting markup to those pages to try to attract job-search traffic.
A practical integration acceptance checklist
- Publish, change and close a sample vacancy. Confirm what the website shows at each stage.
- Apply on a phone and check that the recruiter receives the correct vacancy reference.
- Test a registration without a vacancy and a possible duplicate record.
- Test missing fields, invalid files and an interrupted submission without losing the candidate’s next step.
- Demonstrate a failed connection, a visible alert and a controlled retry.
- Check that only the agreed team can access restricted documents and connection settings.
- Agree who maintains the website, licences and connection, including the checks after an update.
Record the observed results and outstanding work before accepting the connection. A successful sample journey establishes that example, not every possible feature or future account change.
What to include in your project brief
Bring your website address, recruitment system, required journeys and the person who can confirm account access. Explain what already works and the hand-off that causes problems. Use blank forms and synthetic examples when discussing the initial scope.
Ask for initial work and ongoing responsibilities to be quoted separately. You can compare a focused integration with a wider website rebuild once the dependencies are understood.