Rutledge Group · February 2026
Rutledge Group website & admin console
The public site and admin console for an 18-branch recruitment, training and care group, with its own mail infrastructure and SEO stack.
- React
- TypeScript
- Vite
- Tailwind
- Managed Postgres + auth
- HR system integration
Live at rutledgegroup.co.uk
The numbers
- more enquiries and applications a month through the site in four months, May to August 2026
- 5.4×more enquiries and applications a month through the site in four months, May to August 2026Source: Site database, monthly form submissions
- of visits arrive from search engines rather than paid or social channels
- 57%of visits arrive from search engines rather than paid or social channelsSource: Site analytics, June to September 2026
Rutledge Group · enquiries through the site
- May 20261× May's volume
- June 20261.3× May's volume
- July 20262.1× May's volume
- August 20265.4× May's volume
- September 2026, to 23 September4.7× May's volume
| Month | Multiple of May |
|---|---|
| May 2026 | 1× |
| June 2026 | 1.3× |
| July 2026 | 2.1× |
| August 2026 | 5.4× |
| September 2026 (to 23 September) | 4.7× |
Indexed to May 2026 = 1×. Source: rutledgegroup.co.uk form records, September 2026
The brief
What had to change.
A multi-branch group whose public presence had to carry job search, training enrolment, care enquiries and employer leads across 18 branches and 17 towns, while the team behind it needed to manage all of it without a developer.
Jobs, courses, branches, blog posts and team members all change weekly. Anything that required an engineer to publish would have gone stale within a month.
Lead capture had to know which branch it belonged to, because the branch is who follows it up.
How it is put together
Public
- Group website
- Vacancy listings
Source of truth
- Operations platform
- Applicant capture
Measurement
- Consent-aware analytics
Approach
How it was built.
Make every branch and town a real page
Sector, branch and town landing pages with a dynamic sitemap, job structured data, dynamic share images and correct expiry handling for closed roles, wired to search console.
Protect the forms without punishing the user
Bot challenge, rate limiting and server-side validation on every form, with branch-aware confirmations so applicants hear from the right people.
Own the email path
A dedicated authenticated sending domain with transactional templates, a retrying queue, suppression handling and unsubscribe, so delivery is observable rather than hoped for.
Hand the content to the team
Admin dashboards with full editing across vacancies, applications, contacts, enquiries, courses, blog, branches, team, alerts and feedback, under role-based access with audit logging and row-level rules, plus AI assist for drafting vacancies and posts.
What was built
7 parts, one system.
Job search, sector/branch/town landing pages, job alerts and candidate registration
Training
apprenticeships, youth training, qualifications, leadership and sales academies
Domiciliary care and employer hub sections, blog, branch finder, team and policies
Checkout handoff to a hosted payment provider
Admin console with role-based access, audit logging, uptime, email-health and error monitoring
Own sender domain with queue, retries, suppression and unsubscribe
SEO infrastructure
dynamic sitemap, job structured data, dynamic share images, search console integration
Outcome
Most enquiries now arrive from search rather than paid or social channels. The group's own staff publish jobs, courses and posts without a developer, and every lead reaches the branch that follows it up.
Ownership
Integrated with the group's HR system, search console, bot protection and a hosted payment provider. The group holds the code, the data and the sending domain.
Next step
Tell us what the business runs on today.
No pitch deck and no discovery fee. If something off the shelf would serve you better, we will say so before either of us spends money.
Or email zbarnett@nexuz.uk