How to connect Giig to your WordPress website

What a Giig and WordPress connection usually covers

A Giig and WordPress connection usually shares a small number of things, each moving in one direction:

• Vacancies: supported vacancy details published from Giig onto your job pages, so you update a role in one place.
• Applications: candidates apply on your website, and the application reaches Giig linked to the vacancy they chose.
• Candidate registration: people who are not applying for a specific role can register, with the agreed fields sent to Giig.
• Linking and progress: where your account permissions allow, candidate records can be linked and some progress information shared.

Each of these is a separate operation with its own rules. Agree them one by one rather than asking for everything to “sync”.

What it does not do by default

• It does not copy every field. Only the information you agree moves between the systems.
• It does not guarantee every file arrives. Whether CVs and attachments can be passed to Giig depends on what your account allows.
• It does not handle sensitive onboarding paperwork. Payroll details, signed agreements and declarations need their own storage and access rules, usually outside the job connection.

What to check before you start

1. Your Giig account. Ask Giig which integration options and permissions your account includes. Recruitment Connected is independent and is not affiliated with Giig, so this is a question for your Giig account contact.
2. Your WordPress setup. Note your theme or page builder, your hosting, and the plugins that handle jobs and forms today. Some themes need presentation changes to display jobs well.
3. Your job pages. Decide which job details candidates should see, which filters matter (location, sector, hours) and what the apply route should ask.
4. Your process. Who reviews applications, what happens next, and which emails candidates and recruiters should receive.

The steps from first conversation to go-live

1. List what you want the connection to do, in order of importance. Jobs and applications are a natural place to begin.
2. Check the fit: your website, theme, hosting and Giig account access.
3. Agree the scope: each operation, the fields involved, what happens when something fails, and who is responsible for what.
4. Build the connection and the job pages, using test data first.
5. Test the real journeys, including the awkward ones: a vacancy closing mid-application, a missing field, a failed connection.
6. Go live, then watch the first applications closely and fix anything unexpected.
7. Agree updates and support, so the connection keeps working as WordPress, plugins and Giig change.

New website or existing website?

If your current WordPress site works well, an integration may be all you need. If it is slow, hard to update or does not present jobs clearly, it can be simpler to build a new site with the connection designed in from the start. A fit check usually makes the answer clear.

Job pages and Google search

Google can show vacancies in its job search experience when job pages include accurate structured data (JobPosting markup) and follow Google’s guidelines. Job-page structure can be assessed for search readiness as part of the work, but no one can guarantee how Google will display or rank your jobs.

A quick checklist

• Your Giig account contact, and what your account permissions allow
• WordPress access, shared through an agreed private channel rather than email
• The job details and filters candidates should see
• The questions your apply and registration forms need
• Who receives notifications, and what candidates are told after applying
• A test plan that includes failures, not just the happy path
• Who looks after updates and support once it is live