Do NDIS and disability support providers actually need a website?
Yes, but not to win cold search traffic. Most of your work arrives through support coordinators, Local Area Coordinators and, in New Zealand, NASC assessors who already have your name. Your website is the check they run before they pass it on. It either confirms you are currently registered, safe and easy to contact, or it quietly costs you the referral and nobody tells you why.
A builder's website qualifies strangers. Yours reassures people who were already sent to you. That inverts what the page has to do: you are not persuading someone to want the service, you are removing the reasons a referrer might hesitate.
Participants and families also search the NDIS Provider Finder inside the myplace portal, by name, location and support category. That listing runs on your registration data held by the regulator, not on your website. The two have to agree. If the Finder says one thing and your site says another, the person checking assumes the site is out of date, because the site usually is.
An NDIS plan is reviewed roughly once a year. This is a long, low-frequency, high-trust decision: nobody is impulse-buying supported independent living at 9pm. So the page is not built for urgency. It is built to survive a careful read by someone who will act on it three weeks later.
You are not being shopped. You are being checked.
Who is actually reading your website?
Two people, doing different jobs. A participant or family member is deciding whether you will be safe and right for them, usually once a year around a plan review. A support coordinator is deciding whether to shortlist you this afternoon. They need the same facts in a different order, so we write both lanes onto the page instead of making one of them translate for the other.
| If you're a participant or family member | If you're a support coordinator or an LAC | |
|---|---|---|
| Will this be safe? | Worker screening, complaints process, who actually turns up. | Are they registered right now, and for what? Registration groups or certification, with a date. |
| Is this for someone like me, or do they cover this? | Disability type, age group, language, and, in New Zealand, Māori and Pasifika responsiveness stated rather than implied. | Do they have capacity? Regions covered, and whether they are currently taking referrals. |
| Can you take my funding? | Self-managed, plan-managed, NDIA-managed, or NASC and Enabling Good Lives. | How do I refer without three emails? A referral form built for their workflow, not the general contact form. |
| What happens first? | The meet and greet, described before anyone has to ring. | Who owns it? A named person, a direct line, and a stated acknowledgement window. |
Figure 1
Two readers, one URL
What has to be on a disability support provider's website?
Seven things, in roughly this order: current registration or certification status, a referral pathway built for professionals, an accessible build, plain-English service pages, services scoped to exactly what you are registered for, a visible complaints and safeguarding process, and a worker screening statement. Everything else on a provider website is optional.
Registration and certification, visible on the homepage and in the footer
A coordinator or family is screening for legitimacy before any other content matters. This is the entry condition for a referral, not a preference signal.
A separate refer-a-participant route
Coordinators have their own workflow and their own urgency. One general contact form loses the channel most providers actually run on.
WCAG 2.1 AA as the baseline build
For every other sector this is good practice. Here the audience includes people who cannot use an inaccessible site at all.
Plain-English service pages, roughly Grade 6 to 8
Families need to recognise the terms printed on their own plan, without being expected to already know them.
Services scoped to your current registration
Advertising a support outside your registered scope is a regulatory problem, not a marketing one.
A visible complaints and safeguarding process
Accountability is the specific anxiety this buyer carries into every provider decision.
A worker screening statement
'Our team is fully vetted' is worth nothing on its own. Name the check, name who holds it, name when it was last confirmed.
What's different if you operate in New Zealand instead of Australia?
The regulator and the vocabulary change. The job of the page does not. In Australia you are proving NDIS registration, your registration groups and Worker Screening Checks. In New Zealand you are proving Ngā Paerewa certification under the Health and Disability Services (Safety) Act 2001, and explaining NASC and Enabling Good Lives rather than plan management. One site can speak whichever applies to the reader.
| Australia | New Zealand | |
|---|---|---|
| Who funds the support | An NDIS plan, managed by the participant, a plan manager or the NDIA | Disability Support Services funding arranged through NASC, or Enabling Good Lives individualised funding |
| What proves you are legitimate | NDIS registration and your registration groups | Ngā Paerewa certification, NZS 8134:2021, under the Health and Disability Services (Safety) Act 2001 |
| Who screens your workers | NDIS Worker Screening Check | Police vetting and your own safety checking policy, named on the page |
| Who sends the referral | Support coordinator or Local Area Coordinator | NASC assessor, or an EGL connector |
| Where else people find you | The NDIS Provider Finder in the myplace portal, driven by your registration data rather than your website | NASC and regional provider lists, plus word of mouth |
| What people call the money | Core supports, capacity building, SIL, plan-managed, self-managed, NDIA-managed | Individualised funding, Carer Support, EGL |
Does my website have to be accessible by law?
Treat it as yes. In Australia the Disability Discrimination Act 1992 covers access to services. In New Zealand the Human Rights Act 1993 makes disability a prohibited ground of discrimination. Set the law aside and it still holds: an inaccessible website built by a disability provider contradicts the service it is advertising. We are not your lawyers, so get advice if you need certainty about your own obligations.
| Who it's for | What it looks like on your site | |
|---|---|---|
| Every action works on a keyboard | Someone who cannot use a mouse | Tab through the whole referral form, with a visible focus ring on every step |
| Body text at 4.5:1 contrast or better | Low vision, older eyes, a phone in daylight | Measured, not eyeballed. Our own grey at #999999 fails, so we do not use it for copy |
| Real text, never text baked into an image | Screen reader users | Your registration number is selectable text, not part of a logo graphic |
| Headings nested in order | Anyone navigating by heading | A screen reader user can jump straight to Services or Complaints |
| Labels and plain-language error messages on every field | Anyone filling in a referral under time pressure | 'Enter the participant's plan end date' rather than 'invalid input' |
| Captions and transcripts on video | Deaf and hard of hearing visitors | Your welcome video is usable with the sound off |
| Motion respects the reduced-motion setting | Vestibular conditions, migraine | Animations stop if the visitor's device asks them to |
Want to know what this looks like for your business? Fifteen minutes is usually enough to tell you.
How do you write about funding without drowning people in jargon?
You keep the word and explain it in the same breath. A family reading your site has terms like plan-managed or core supports printed on their own plan, so deleting the jargon leaves them unable to match you to their paperwork. We write service pages at roughly a Grade 6 to 8 reading level and gloss each term the first time it appears.
| Plain English | |
|---|---|
| Self-managed | You handle the money yourself and can choose any provider. |
| Plan-managed | A plan manager pays the invoices. You still choose the providers. |
| NDIA-managed | The agency pays. You use NDIS registered providers. |
| Core supports | The everyday part of a plan: help with daily life, getting out, consumables. |
| SIL | Supported Independent Living. Help with daily tasks where you live. |
| Support coordinator | The person who helps you find and organise providers. |
| LAC | Local Area Coordinator. Helps you build and use your plan. |
| NASC (New Zealand) | Needs Assessment and Service Coordination, the New Zealand service that assesses your needs and arranges support. |
| Enabling Good Lives (New Zealand) | The New Zealand approach that puts the funding and the choice with the disabled person and their whānau. |
| Ngā Paerewa (New Zealand) | The health and disability services standard, NZS 8134:2021, that your certification is measured against. |
What should happen between a coordinator finding you and a participant starting?
Five steps, and your website should carry the first three. A coordinator lands on a page, checks your registration and scope, then refers through a form built for the way they work. You acknowledge inside a stated window. Then the meet and greet, then support starts. Most provider sites stop at a general contact form and lose the referrer at step three. If you want to see what that referral form would ask for your supports, book a 15-minute call and we will walk through it with your service list open.
- 1
They check you are real
Registration or certification status and the date it was last confirmed, visible without scrolling. Not a logo. A status.
- 2
They check you cover the support
Service pages that match your registration groups or certification scope, named the way the scheme names them, so a coordinator can match in seconds.
- 3
They refer, on their terms
A referral form that asks what a coordinator actually has in front of them: participant initials, plan type, supports sought, plan end date, their own contact details and how urgent it is. Not how did you hear about us.
- 4
You acknowledge, inside a window you published
'We reply to referrals within one business day.' Publishing the window is the commitment. Meeting it is what gets you referred again.
- 5
Meet and greet, then support starts
Say what the first meeting involves and how long the wait usually is, currently 2 to 3 weeks. A family that can see the whole path is more likely to start walking it.
What happens to the website when our registration or services change?
You ask for the change, and it happens everywhere at once. Add a registration group, drop a service, renew a certificate, change the regions you cover, and every page that mentions it updates together. That matters more here than in any other sector we build for, because advertising a support you are not registered for is a compliance problem, not just a stale page.
Four things actually go stale on a provider site: a service you stopped delivering, still listed on a page nobody remembers exists; a certification or registration date in the footer that passed months ago; a region you no longer cover, still in your service-area copy; and a named contact who left, still taking referrals in theory.
Change anything. Just ask. It updates everywhere. The honest limit: the site will tell you what is drifting, in plain English, but it will not know your registration changed unless somebody tells it. So we set the review against the certificate, not the calendar.
We review these pages every six months, and the date at the bottom of this one is real.
Have you built a website for a disability support provider before?
Once, and we will tell you exactly what that proves. We rebuilt and migrated a Queensland NDIS provider, [[PERMISSION: client name]], onto a new platform and domain, with events browsable by category and a documented four-step onboarding path written for participants, families and support coordinators at the same time. Transactional email was smoke-tested in production on 19 August 2026.
What this proves: a full rebuild and platform migration, completed and live; services made browsable and concrete, by category, with dates and venues, rather than described in the abstract; a four-step path from first contact to support starting, published so a family can see the whole thing before committing to a conversation; one site that works for the participant, the family and the coordinator at once; and transactional email verified on a real sending domain, which matters where a missed confirmation means somebody does not get collected.
What it doesn't prove: enquiry volume, participant numbers or booking conversion. We have no analytics access for this client, so there is no percentage here and we are not going to invent one.
That client's name sits in brackets above because we do not publish a provider's name before they have said yes in writing. In a sector built on consent, that seemed like the minimum.
What we won't put on your website
Five things, deliberately. No stock photography of strangers in wheelchairs. No participant photos or quotes without written, informed consent that can be withdrawn later. No schema markup for reviews or questions that are not visible on the page. No service listed that your current registration or certification does not cover. And no ranking promises.
Stock disability imagery
It is recognisable, it is everywhere, and every visitor who lives it can tell. Photograph your actual team and venues, or use nothing.
Unconsented participant content
Consent has to be informed, recorded and revocable, and consent to be photographed at an event is not consent to appear in marketing. We build the consent record into the process rather than leaving it to a folder of photos.
Invisible schema
Marking up reviews you were not given, or questions the page does not display, is a spam signal in search and a trust problem in AI answers. We do not do it, including to test.
Anything outside your scope
If you are not registered or certified for it, it does not go on the page, however much work it might bring in.
Ranking promises
Nobody can guarantee a position in Google, and anyone who does is either uninformed or selling you something. We do everything known to influence ranking and citation, and none of the things known to hurt it.
Which build does a disability support provider actually need?
Three shapes, and which one you need is a scoping question rather than a shopping one. Three things move it: how much your current registration or certification covers, how many regions you work across, and whether referrals have to reach your rostering or client system rather than an inbox. A full site ships in 7 days, a landing page in 5. Book a 15-minute call, bring your registration details and your service list as it stands today, and you will leave the call with a figure for your actual job.
| What that usually covers for a provider | Ships in | Usually the right fit if | |
|---|---|---|---|
| Landing Page | one service line, one region, a referral route and a registration panel | 5 days | You are proving one support type in one area, or testing a new region before you commit to it |
| Website | your full service range, separate participant and coordinator paths, the plain-English glossary, an accessible build | 7 days | Your registration or certification covers several supports and coordinators need to match scope without ringing you |
| Custom | multiple regions, rostering or CRM connections, a participant portal | Scoped with you first | Referrals have to land in your rostering or client system, or participants and families need a login |
Where the rules actually come from
These are the regulator and legislation pages the claims on this page point back to, checked on 19 September 2026. If a registration, certification or legal detail on your own plan or certificate differs from what is written here, your document governs.
- NDIS Provider Finder, finding a registered providerAustraliaThe NDIA's own page on how participants find providers. Supports the point that the Provider Finder runs on registration data the regulator holds, not on your website. Checked 2026-09-19.
- Ngā Paerewa Health and Disability Services Standard, NZS 8134:2021New ZealandNames the certification standard New Zealand disability support providers are measured against. Checked 2026-09-19.
- Disability Support Services, information for providersNew ZealandThe New Zealand government body that funds and sets policy for disability support via NASC and Enabling Good Lives. Checked 2026-09-19.
- Whaikaha, Ministry of Disabled PeopleNew ZealandThe New Zealand ministry responsible for disability policy. Checked 2026-09-19.
- Health and Disability Services (Safety) Act 2001New ZealandPrimary legislation behind New Zealand certification. Checked 2026-09-19.
- Human Rights Act 1993New ZealandMakes disability a prohibited ground of discrimination in New Zealand. Checked 2026-09-19.
- Web Content Accessibility Guidelines (WCAG) 2.1International (W3C)The standard the accessible build promise points to. W3C Recommendation. Checked 2026-09-19.
Draft quote. Nobody said this. Replace before publishing.
Coordinators can see our registration and our capacity without ringing. The referrals that come through now are ones we can actually take.
Questions, answered.
Book a 15-minute demo Book a 15-minute demo
Bring your current registration or certification details, your service list as it stands today and who takes referrals. We will show you the referral route, the plain-English glossary and the accessible build in fifteen minutes, on a real device, not a slide deck.
Book a 15-minute demoNo commitment. No pitch deck. Just 15 minutes.