What Makes a Great NDIS Website? A 15-Point Checklist
Your website is often the first impression a participant, family or Support Coordinator has of your business. Use this 15-point checklist to see whether yours is helping - or quietly costing you referrals.
A great NDIS website doesn't need to be flashy. It needs to be clear, accessible and easy to act on. Go through this checklist with your current site open. Give yourself a tick for each one you can honestly say yes to.
Making contact easy
1. Your phone number is at the top of every page
Many families and coordinators would rather call than fill in a form. Put your number and hours in the top bar, with tap-to-call on mobile.
2. There's a clear enquiry form
A short form - name, phone, what support they need - on the home page and every service page.
3. There's a separate referral form for Support Coordinators
Coordinators need to send different details from families. A dedicated referral form shows you're set up to work with them. Read more in how to get NDIS referrals.
4. You respond fast - and say so
"We'll call you back within one business day" sets expectations and builds trust.
Showing what you do
5. Every service is named clearly
Use the words people search for - "in-home support", "community access", "SIL" - not internal jargon.
6. Each main service has its own page
Who it's for, what's included, where you offer it and how to start.
7. You show where you work
List the suburbs and regions you cover, so visitors know straight away whether you can help.
Building trust
8. Real reviews and feedback
Genuine Google reviews and participant or family feedback - shared only with consent - are more convincing than anything you say about yourself.
9. Real photos of your team
Stock photos all look the same. Faces of your actual team build trust.
10. Your registration and approach are clear
Registered or not, what you stand for, and how you work with participants.
Accessibility and design
11. It's accessible to people with disability
Meets WCAG 2.2 AA: keyboard navigation, screen-reader friendly, strong contrast, captions and alt text. See our plain-English accessibility guide.
12. Accessibility tools are visible
Text resize, high contrast and Easy Read options help many visitors - and show you care.
13. The design is modern and calm
Plenty of space, readable fonts, clear buttons. Cluttered, dated sites feel untrustworthy.
Behind the scenes
14. It's fast and works on phones
Most visitors are on a phone. Slow pages lose people before they read a word.
15. It's set up for Google
Every page has a clear title and description, your Google Business Profile links to it, and you track enquiries so you know what's working.
How did you score?
- 13-15: Great work. Focus on keeping content fresh and growing reviews.
- 8-12: A solid base with some quick wins - start with contact, referral and accessibility items.
- Under 8: Your website is probably costing you referrals. A redesign is likely worth it.
Frequently asked questions
How many pages does an NDIS website need?
At minimum: home, a page per main service, areas you cover, about, a referral or contact page, and a privacy policy. Easy Read versions of key pages are a strong addition.
Should our website have a referral form?
Yes. A short online referral form makes it easy for Support Coordinators and families to refer, and makes sure details aren't lost.
Do we need Easy Read pages?
They're not mandatory for every provider, but Easy Read versions of key information - services, how to refer, complaints - make your website more inclusive and are valued by participants.
How often should we update our website?
Review it at least every few months - services, staff, areas and vacancies change. Fresh content also helps with Google.
Get a free website review
Send us your website and we'll check it against this list and call you with the top fixes.
- Free and no obligation
- Practical advice for your NDIS business
- A call back within one business day
Call 0450 501 772
Email contact@digitalrabbit.com.au
Monday to Friday, 9am - 6pm
Request a call-back
Fields marked * are required.