Websites for NDIS support-worker agencies
Your website has two jobs running at the same time: help a participant or family decide whether to call you, and help a good support worker decide whether to apply. Most agency websites do a mediocre job of both, because they were never designed to tell the two apart. That's the specific problem we build for.
Who actually reads your site
An agency website carries more traffic types than most providers realise, often within the same afternoon. Each one is scanning for something different, and a page that tries to speak to everyone at once usually speaks clearly to no one.
Participants and families
Working out whether your agency offers the right kind of support, in their area, and whether the tone of the site feels safe enough to call.
People looking for support work
Checking whether shifts, pay basics and the areas you cover actually suit them before deciding whether it's worth applying at all.
Support coordinators
Scanning quickly to confirm you cover their region and are currently taking referrals before they'll put your name forward.
Plan managers
Checking your service descriptions are clear enough to confirm you'll slot smoothly into a participant's existing plan.
What we build for support-worker agencies
Every site we build follows the same named standard, the NDIS Front Door System — built to WCAG 2.1 AA accessibility as the flagship requirement, not an afterthought, because a screen-reader user who can't navigate your site is being turned away at the door before they ever speak to you. For an agency specifically, that system starts with a decision most template sites never make: splitting participant and worker paths apart, early, instead of burying one behind a generic "About us" menu item.
Two clear front doors
The homepage splits early into "I need support" and "I want to work here," so neither audience has to wade through content meant for the other. Our Pathway concept below demonstrates this in practice.
A recruitment page that respects workers
Real shift information, the areas you actually cover, and an honest sense of what it's like to work for you — not a stock "join our amazing team" paragraph that tells applicants nothing.
Trust cues, stated honestly
Screening, insurance and how you handle complaints, written to say plainly what your agency actually does — we never invent a claim or a policy on your behalf.
See it, don't imagine it
Rather than describe a two-front-door homepage in the abstract, we built one you can click through: Pathway Support Network, a fictional agency created to show how a participant path and a worker path can sit on the same homepage without either feeling like an afterthought. To be completely upfront — this is a concept design we built to demonstrate the approach, not a real client project or a real agency. WebQuest is a new studio and we won't pretend otherwise.
Free playbooks worth your time
Both of these are free to read in full, right now, with no email address needed — whether or not you ever get in touch with us.
The local SEO guide
Agencies compete hard on "support worker jobs [suburb]" and "support agency near me" searches at once — this guide covers the Google Business Profile and on-site basics that help with both.
The accessibility checklist
Many participants and families researching an agency use a screen reader or keyboard navigation — this 41-point checklist lets you check your current site against WCAG 2.1 AA yourself.
Questions support-worker agencies usually ask
Can one website serve both participants and job seekers?
Yes, and it's usually better than running two separate sites — but only if the homepage splits the paths early instead of forcing both audiences through the same generic navigation. Once someone picks "I need support" or "I want to work here," the rest of that journey should stay focused on them, without wandering back into content meant for the other audience.
What should our careers page actually say?
The things a support worker actually needs before applying: the areas you cover, roughly what shifts look like, how pay and travel work, and an honest sense of what it's like to work for you day to day. Vague enthusiasm ("join our passionate team!") doesn't help anyone decide anything — specifics do, even simple ones.
How do we show we're trustworthy without breaching participant privacy?
By describing your processes, not your people. State plainly what screening you carry out, how you're insured, and how a complaint would be handled — without naming or identifying any actual participant or worker. Trust signals come from clear, honest policy statements, not from stories that risk someone's privacy.
Want a second opinion on your agency's site?
We'll look at it the way a family and a job seeker each would, and tell you plainly what's working and what isn't — no obligation.
We also build for support coordinators, plan managers and SIL & SDA providers — each with its own audience and its own version of the NDIS Front Door System.