Audit NDIS Search Readiness in 2026

Start this section with evidence, not assumptions. The goal is to confirm that participants and referrers can reach, understand, and use important service information across devices and assistive technologies.

Accessibility review against WCAG 2.1 Level AA. Evidence required: an accessibility test report covering templates, navigation, forms, headings, images, focus order, keyboard use, and common screen-reader interactions.

Pass condition: material barriers affecting core service discovery or contact paths are not present in the tested sample, and known exceptions are documented with owners. Fail condition: a participant cannot complete a core information or enquiry task because of an avoidable interface or content barrier.

Severity: critical when the barrier blocks access to essential service or contact information; otherwise prioritize by user impact. Owner: web product lead with accessibility review support. Corrective action: repair the underlying component, content, label, focus behavior, contrast issue, or document alternative rather than relying on an overlay alone.

Validation step: rerun automated checks and a representative manual keyboard and assistive-technology review, then retain the evidence. Tools: Axe DevTools, WAVE Accessibility Tool, Google Lighthouse.

Structured data for visible NDIS service information. Evidence required: the rendered page, the deployed JSON-LD, and a record showing that each marked-up property is supported by visible content. Pass condition: markup is syntactically valid, describes the actual page entity, and does not add claims that users cannot verify on the page.

Fail condition: properties are inaccurate, unsupported, duplicated across the wrong entity, or used solely in the expectation of a ranking boost. Severity: medium. Owner: technical SEO lead and developer.

Corrective action: remove unsupported properties and map the page to the most appropriate Schema.org types without inventing registration, clinical, or service attributes. Validation step: retest the deployed markup with Google's supported validation tooling and compare it against the visible page. Tools: Schema.org, Google Rich Results Test.

Mobile performance and interaction quality. Evidence required: field or lab performance reports plus a manual walkthrough of high-intent service pages, contact flows, referral forms, and downloadable resources on representative mobile devices.

Pass condition: important content is readable, controls are usable, pages respond predictably, and performance issues do not obstruct service evaluation or contact. Fail condition: layout shifts, blocking scripts, oversized media, broken forms, or hard-to-use controls materially impede the journey.

Severity: high. Owner: web engineering lead. Corrective action: reduce unnecessary scripts and media weight, repair responsive layouts, simplify blocking interactions, and prioritize the content needed to evaluate services.

Validation step: repeat the same test journey after deployment and compare the before-and-after evidence. Tools: PageSpeed Insights, Search Console.

HTTPS and participant-data handling. Evidence required: certificate status, redirect behavior, form inventory, analytics tags, consent configuration, and a data-flow record for information submitted through the site.

Pass condition: public pages use secure transport and the organization can explain where enquiry data goes and which systems receive it. Fail condition: insecure resources, broken certificate behavior, unexplained third-party collection, or forms that gather sensitive information without an approved handling process.

Severity: critical where participant information may be exposed. Owner: security or privacy lead with web engineering. Corrective action: fix transport issues, minimize unnecessary collection, remove unauthorized trackers, and align forms with the organization's approved privacy process. Validation step: retest transport, form submission, and tag behavior on production. Tools: SSL Labs, Hosting Provider

Local discovery should reflect where the provider genuinely operates, not a list of aspirational suburbs. Each check below separates verifiable business information from optional operating practices.

Google Business Profile accuracy. Evidence required: the live profile, current website contact details, verified business address or service-area configuration, categories, hours, and an internal record of services actually delivered from or through that location.

Pass condition: public details are accurate and consistent with the provider's real operations. Fail condition: the profile implies a location, service, opening status, or capability that the provider cannot substantiate.

Severity: high. Owner: local marketing lead with operations approval. Corrective action: correct the profile and remove unsupported claims or categories. Validation step: compare the live profile with the website and current operational records after edits. Tools: Google Business Profile Manager.

Location-specific landing pages. Evidence required: proof of a genuine location or meaningful local service operation plus unique information such as access details, team availability, service coverage, referral process, or local contact information.

Pass condition: the page helps a participant or referrer evaluate that real location and is materially different from generic service-area copy. Fail condition: pages exist only to swap place names or imply a physical presence that is not real.

Severity: high. Owner: SEO lead with operations. Corrective action: consolidate thin pages and create a dedicated page only where a genuine location or useful location-specific service information exists.

Validation step: confirm every published location statement against current operational records and test that internal links point to the correct page. Tools: SurferSEO, Keyword Planner.

Local citation consistency. Evidence required: a citation inventory covering major business listings and disability-sector directories that the provider legitimately uses. Pass condition: name, contact details, website, and location information agree with the organization's approved public record.

Fail condition: stale addresses, duplicate profiles, mismatched contact details, or listings for services no longer offered. Severity: medium. Owner: local SEO lead. Corrective action: update or suppress inaccurate records and document any listing that cannot be changed. Validation step: rerun the citation audit and spot-check priority listings. Tools: BrightLocal, Whitespark.

Participant and customer review process. Evidence required: the written request process, eligibility criteria for who receives a request, and examples showing that feedback is requested consistently.

Pass condition: eligible customers are asked for honest feedback without incentives, discouraging negative feedback, or selecting only satisfied customers. Fail condition: staff gate requests based on sentiment, offer rewards, pressure reviewers, or publish misleading review claims.

Severity: high. Owner: customer experience lead with compliance oversight. Corrective action: replace selective outreach with a consistent, neutral request process and clear escalation for privacy or safeguarding concerns. Validation step: sample recent requests and compare them with the documented process. Tools: Trustpilot, Google Reviews

For participant-facing health and disability content, the audit should identify who is responsible for accuracy, what evidence supports material claims, and whether the page clearly separates service information from medical or legal guidance.

Author and reviewer context. Evidence required: the live byline or reviewer note, role description, professional profile, and any credential or registration reference that the organization is permitted to publish.

Pass condition: readers can understand why the named person is an appropriate contributor or reviewer for the topic. Fail condition: sensitive health guidance appears under an anonymous or misleading attribution, or credentials are claimed without internal verification.

Severity: critical for health or safety guidance. Owner: content lead with the relevant clinical or professional reviewer. Corrective action: assign an appropriate reviewer, correct the attribution, narrow unsupported advice, and add sources where needed.

Validation step: compare the published page with the approved review record and credential source. Tools: LinkedIn, AHPRA Register.

NDIS safety, complaints, and service-governance information. Evidence required: approved public wording for registration status, complaints pathways, incident or safeguarding information that the organization is authorized to publish, and the internal policy owner.

Pass condition: the page gives participants a clear route to verify material service and safety information without overstating the provider's status. Fail condition: outdated statements, vague assurances, or claims of compliance that have not been reviewed by the responsible function.

Severity: critical. Owner: quality or governance lead. Corrective action: replace broad assurances with current, reviewable information and link internal publication controls to the page owner. Validation step: recheck the page against the latest approved organizational records. Tools: NDIS Commission Guidelines.

De-identified service examples. Evidence required: consent or authorization record where applicable, a privacy review, source notes supporting the facts, and confirmation that identifying details have been removed or generalized appropriately.

Pass condition: the example demonstrates real service experience without exposing a participant or promising the same outcome to others. Fail condition: the story can reasonably identify a person, includes unsupported outcome claims, or presents an individual result as typical.

Severity: high. Owner: service lead with privacy review. Corrective action: remove or generalize identifying details, qualify the context, and delete unsupported performance language. Validation step: perform a final privacy and claim review against the source notes before publication. Tools: Internal Case Notes, Copywriter.

Official-resource references. Evidence required: a citation log showing which participant-facing statements rely on official NDIS information and when the references were checked. Pass condition: links or citations support the specific statement and do not substitute for the provider's own service details.

Fail condition: outdated guidance is paraphrased without review or an official source is used to imply endorsement. Severity: medium. Owner: content governance lead. Corrective action: update the statement and supporting reference, or remove it if no longer applicable. Validation step: re-open the cited official source and verify the published wording against it. Tools: NDIS Website

A useful content program should answer concrete service-selection questions and make the next step clear without manufacturing urgency or implying availability that operations cannot support.

SIL vacancy information. Evidence required: a current operational source of truth for available properties or placements, eligibility notes, location details, and the person responsible for updates. Pass condition: published vacancy information matches what intake or housing staff can confirm and clearly states how a participant or referrer can enquire.

Fail condition: stale availability, vague claims that imply a vacancy, or a page updated only for search visibility without operational verification. Severity: critical when inaccurate information could mislead a participant.

Owner: housing or intake operations with content support. Corrective action: connect the page to an approved update process and remove unsupported availability claims. Validation step: compare the live page with the current internal vacancy record. Tools: Google Search Console, Housing Hub.

NDIS planning and process guides. Evidence required: source references, reviewer notes, and a scope statement showing what the provider can explain versus what requires independent or official guidance.

Pass condition: the guide helps readers prepare questions and understand the provider's process without giving individualized legal, funding, or medical advice. Fail condition: content states uncertain plan outcomes as certain or blurs provider information with official determinations.

Severity: high. Owner: content lead with quality or service review. Corrective action: narrow claims, cite appropriate official material, and separate educational information from provider-specific next steps.

Validation step: have the responsible reviewer compare the published guide with current approved information. Tools: AnswerThePublic, Semrush.

Long-tail service and referral queries. Evidence required: Search Console query data, internal referral questions, service descriptions, and capacity information. Pass condition: each target page addresses a real service, audience, location, or referral question that the provider can substantiate.

Fail condition: content targets attractive phrases that do not match actual service scope, registration, capacity, or participant needs. Severity: medium. Owner: SEO lead with service operations. Corrective action: retire mismatched targets and build pages around verified service decisions and frequently asked referral questions.

Validation step: compare target queries with on-page content and confirm the service team can fulfill the implied next step. Tools: Ahrefs, Mojo.

Person-centered language and claim control. Evidence required: editorial guidance, reviewer comments, and a sample of participant-facing pages. Pass condition: wording is respectful, specific, understandable, and avoids unsupported safety, quality, or outcome claims.

Fail condition: content is generic, stigmatizing, manipulative, or written to satisfy keywords at the expense of clarity. Severity: high. Owner: content lead with lived-experience or service review where appropriate.

Corrective action: rewrite around the participant's information need, preserve autonomy, and remove claims that cannot be evidenced. Validation step: complete a plain-language, tone, and claims review before publication. Tools: Grammarly, Internal Review

Provider identity check - Evidence required: current approved provider details. Pass condition: the footer and contact surfaces show the approved identifier consistently. Severity: high. Owner: web content lead.

Corrective action: correct mismatched identity information. Validation step: check the live templates after deployment. Estimated review effort: 15 mins

Google Business Profile accuracy check - Evidence required: current service and vacancy information approved by operations. Pass condition: the profile does not imply unsupported availability or services.

Severity: high. Owner: local marketing lead. Corrective action: update inaccurate profile content. Validation step: compare the live listing with the approved source record. Estimated review effort: 30 mins

Broken service-page check - Evidence required: crawl report showing 404 responses and the intended destination for each affected link. Pass condition: important participant and referral paths do not terminate unexpectedly.

Severity: technical health. Owner: web developer. Corrective action: restore the correct page, update the link, or apply an appropriate redirect based on the content decision. Validation step: recrawl the affected URLs. Estimated review effort: 1 hour

Accessibility smoke test - Evidence required: keyboard and assistive-technology notes for core navigation, forms, and contact actions. Pass condition: the tested journey is operable and understandable without relying on an accessibility overlay.

Severity: user experience. Owner: accessibility or web lead. Corrective action: repair the component or content issue found in testing. Validation step: repeat the same manual test path after the fix. Estimated review effort: 1 hour

• Generic disability imagery without context. Evidence required: an image inventory, licensing records, alt text, and editorial rationale. Pass condition: imagery is respectful, relevant, permitted for use, and does not misrepresent the provider's participants or services. Severity: medium. Owner: brand and content lead. Corrective action: replace misleading assets and rewrite alternative text around the image's actual purpose. Validation step: review the published page with accessibility and brand stakeholders.
• Stale service or registration information. Evidence required: the current approved service catalogue and registration records. Pass condition: public pages match what the provider can currently deliver and describe status precisely. Severity: critical. Owner: quality or operations lead. Corrective action: update or remove obsolete service claims. Validation step: compare the live site with the approved record after publication.
• Unverified local intent coverage. Evidence required: actual location, service-area, and intake records plus query data. Pass condition: local content describes genuine operations and useful location-specific information. Severity: high. Owner: local SEO lead with operations. Corrective action: consolidate nominal suburb pages and retain dedicated pages only where the provider can substantiate a real location or meaningful local service detail. Validation step: audit each local page against current operations.
• Weak internal pathways between services and the main authority resource. Evidence required: a crawl of priority service pages and the NDIS provider authority page. Pass condition: relevant pages link naturally where the relationship helps participants or referrers understand the service. Severity: medium. Owner: SEO and content leads. Corrective action: add descriptive links where context supports them and remove forced anchor text. Validation step: recrawl and manually test the resulting navigation path.