NDIS and aged care website design for families and referrers
Choosing care is one of the hardest decisions a family makes. A daughter looking for home care for her father, a participant comparing NDIS providers, a support coordinator with three clients to place this week: each needs to know, fast, whether you cover their area, have availability, speak their language and can be trusted.
Why work with Nirmal Gyanwali on NDIS website design?
Good NDIS website design answers those questions before anyone picks up the phone.
I’m Nirmal Gyanwali, Founder and CEO of WP Creative, and I built PostCliq, which WP Creative operates. I built my first startup, a health portal, while I was at medical school. Today my team at WP Creative designs, builds and looks after websites for home care, aged care, NDIS and disability providers, from single services to groups running a dozen sites.
What does an NDIS or aged care provider website need?
An NDIS or aged care website needs to show, in plain language, what you provide, where, for whom and how to start, with separate paths for participants, families and referrers. It must be accessible to people with disability and older users, keep sensitive information safe, and state your registration and service areas accurately everywhere they appear.
01
Be found
by families searching on Google, and by the AI assistants they now ask to “find a home care provider near Parramatta that speaks Hindi”.
02
Be chosen
because service areas, availability, languages and registration are clear, and the next step takes one tap.
03
Grown
a site that keeps getting more accessible, private and stable, because the people using it may be vulnerable and the information is sensitive.
Problems I see on care provider websites
01
One form for everyone
Job seekers, families and referrers all use one contact form and land in the same inbox, so enquiries wait.
02
Referrers hit dead ends
Support coordinators want a short path to availability and an intake form, not the home page story.
03
A site per location
Each new facility or region added a website. None are maintained, and updates stopped.
04
Slow, fragile sites
Outdated plugins and heavy images on the phones older users and carers rely on.
05
Recruitment is buried
Providers who can’t find support workers can’t grow, and the careers page is an afterthought.
06
Forms miss the CRM
Enquiries collected on the site but re-keyed into the CRM by hand, with mistakes.
The five audiences your site must serve
What they need first
- Participant or older person Can you help me, here, soon?
- Family member or carer Can I trust you with someone I love?
- Support coordinator or referrer Do you have capacity, and how do I refer?
- Plan manager or case manager Will you make my job easier?
- Support worker (job seeker) Is this a good place to work?
What the site must provide
- Participant or older person Plain-language services, Easy Read options, large tap targets, a phone number
- Family member or carer Who you are, registration, how care works, what it costs them to start
- Support coordinator or referrer A referrer hub: availability, referral form, response time
- Plan manager or case manager Clear service agreements, contact roles, invoicing details
- Support worker (job seeker) Roles, locations, how to apply, a direct route to your recruitment system
What an AI assistant needs to read
- Participant or older person Services, service areas and languages as text
- Family member or carer Registration status, approvals, how intake works
- Support coordinator or referrer Current availability and the referral route
- Plan manager or case manager Contacts by role, plan types accepted
- Support worker (job seeker) Open roles as text, not image posts
What an AI-ready care website looks like
Some families now ask AI assistants to shortlist providers. Comparison platforms feed those answers too, and my team looks after one of them. An agent-ready website keeps the same facts on your site, your directory listings and your registration record, so an assistant isn’t left guessing which one is right.
Write registration status, service areas by suburb or region, languages spoken and how to start as text on the page. Keep availability honest and dated. Make referral and enquiry forms properly labelled, with a clear receipt and an accessible alternative contact route. A person or authorised referrer still needs to approve any submission; a labelled form is not permission for an assistant to upload a participant’s care plan or sensitive records. I’d rather a family’s assistant says “this provider has a waitlist in your area” than recommends you for a service you can’t deliver.
Care provider websites my team has built and runs
Care providers whose websites my team designs, builds or looks after.
myHomecare
Support, maintenance and design refinements for a national support worker platform
Mable
Nextt
“WP Creative has truly been an outstanding partner for us in maintaining and managing our WP sites. … Their professionalism and expertise have made a significant difference for us, and we couldn’t be happier with their services.”
“The team have been very prompt in undertaking tasks following our weekly catch-ups, with clear communication and setting of expectations.”
“We have had a great experience with the team, they have been thorough and professional from the beginning.”
When the answer isn’t a new website
The home care group in the cards above taught me this. It ran 13 websites. Updates never stopped, earlier developers had struggled with the deeper technical problems, and with no process the marketing team was firefighting while campaigns waited. It didn’t need 13 new websites. It needed someone to own them. My team upgraded the outdated plugins, PHP and WordPress underneath, lifted the measured mobile speed score from 33 to 62, and put all 13 sites on one monthly backlog with a fortnightly check-in and a monthly report.
If your site is slow and nobody can update it, stabilise and take ownership first, then redesign the pages that matter most: services, referrals and careers. Rebuild only when the platform can’t be made accessible or secure.
Rules that shape a care provider website
Your quality and compliance lead owns these obligations. My team builds so the website supports them.
The aged care reforms changed how home care services are described and accessed, so checking your pages against the department’s current guidance is ongoing work, not a job done once at launch.
Registration wording needs the same care. The NDIS Commission’s current register includes transitional application records for supported independent living and digital platform providers. An application in progress is not an approved registration. Ask your compliance lead to confirm the precise status, applicable service groups and wording before publishing it; do not turn a transition entry into a broad registered-provider claim.
01
Registration claims
State your NDIS registration status and groups exactly as the NDIS Commission’s provider register shows them, and recheck whenever they change. Never imply a registration you don’t hold.
02
Aged care reforms
The new Aged Care Act and the Support at Home program, which replaced Home Care Packages, started on 1 November 2025. Recheck your pages whenever the department’s guidance updates.
03
Sensitive information
Health and disability information is sensitive information under the Privacy Act. Ask only for what intake needs, send it securely, and keep it out of website form emails.
04
Testimonials and consent
Get written consent before publishing a participant’s or resident’s story or photo, and make consent as easy to withdraw as it was to give.
05
Accessibility
WCAG 2.2 AA is the target my team designs to, with Easy Read versions of key pages where your audience needs them.
NDIS and aged care website design FAQs
Do you build websites for clinics and allied health too?
Yes, but that’s a different job with different rules. See my page on medical website design.
Can enquiries go straight into our CRM or client management system?
Where the system provides supported API access for the required fields and actions, yes. We map families, referrers and job seekers to separate workflows, with an owner for a failed or misrouted enquiry. The intake automation should reduce repeated entry, while a person confirms capacity and any sensitive information needed for the next step. A successful form submission is not an offer of care.
We run a separate website for each location. Should we merge them?
Only if the shared structure suits the brands, services and publishing permissions. One platform can reduce repeated work, but each location still needs accurate service areas, contacts and capacity. Plan old-URL mappings, content and indexing checks before a merge to reduce search disruption; visibility cannot be guaranteed.
Can our staff update service areas and availability themselves?
Yes. Structured fields let staff update service areas and availability in the agreed website templates. Give each change an owner and review date, and recheck directory listings and referral systems separately. External copies and assistant answers do not update just because the website has changed.
Do you do NDIS marketing or SEO?
No. My team designs, builds and looks after the website. We don’t sell SEO or advertising; we’ll refer you to partners if you need them.
Running an NDIS, home care or aged care service?
Book a free call. You’ll talk with me or my team about your participants, your referrers and what your website should fix first. After launch, care plans keep it secure and current.
