Treating Local Search as a Listing Exercise Instead of a Location Accuracy Problem
Observable evidence: The website, Google Business Profile, directory records, and phone routing show conflicting business names, addresses, phone details, hours, service descriptions, or location information. Another warning sign is a collection of suburb pages that repeat generic copy even though the provider has no genuine location-specific information to offer there. The source version previously stated that the local pack captured 30 to 50 percent of local search clicks. Because no supporting source URL is present in this JSON, preserve that statement only as a historical, unreconciled figure rather than a verified benchmark.
Consequence: Participants, families, and referral partners may encounter contradictory information, while search systems receive weaker signals about which real-world entity and location a page represents. Weak local visibility cannot be assigned to a single profile activity without evidence.
Correction: Reconcile public business information against approved operational records. Keep service categories and descriptions factual, resolve duplicate or outdated profiles through the platform process, and create a dedicated location page only for a genuine location with useful local details such as contact information, accessibility information, services available there, or arrival instructions. Do not present posting frequency, map embeds, profile activity, or review-response behavior as guaranteed or official ranking factors.
Owner: Local operations or provider administration with SEO support.
Verification: Compare the live website, business profile, key directory records, and contact routing against the same approved source of truth. Confirm that each published location is genuine and that users can reach the intended team.
Severity: critical
Using Accessibility as an SEO Claim Instead of Testing Whether People Can Use the Site
Observable evidence: Keyboard users cannot reach important controls, visible focus is missing, images lack meaningful text alternatives where needed, headings are structurally confusing, contrast is difficult to read, forms do not expose useful labels or errors, or interactive components are unreliable with assistive technology. These are user-access problems first. Do not describe WCAG conformance, ARIA use, or any single accessibility technique as a documented automatic ranking factor.
Consequence: People with disability may be prevented from finding service information, understanding next steps, or completing an enquiry. The provider may also create avoidable brand and governance risk if public accessibility claims are stronger than the site can support.
Correction: Run an accessibility review against the site components and journeys that matter most, using automated checks only as one input. Repair semantic structure, keyboard operation, form labeling, error handling, text alternatives, focus behavior, and contrast where required, then have knowledgeable reviewers assess the result in context.
Owner: Web or product owner with an accessibility specialist and content owners.
Verification: Re-test priority journeys with keyboard-only navigation and representative assistive technology, document remaining limitations, and confirm that fixes work in the live environment rather than only in a test report.
Severity: high
Publishing Sensitive Disability or Health Content Without Accountable Review
Observable evidence: Articles about disability supports, health-related decisions, restrictive practices, behaviour support, therapy, risk, eligibility, funding, or participant outcomes have unclear authorship, generic credentials, stale claims, unsupported statements, or no way to identify who reviewed material changes. The prior version described weak content as being buried on page 5. Treat that phrase as an illustrative historical example, not a verified search outcome or proof of a Google penalty.
Consequence: Readers have less context for judging high-stakes information, corrections are harder to trace, and promotional language can be mistaken for professional guidance. It is not appropriate to claim that missing author attribution automatically triggers a ranking penalty.
Correction: Assign accountable authors and reviewers, publish accurate role or credential information when it is relevant, cite official or reliable sources that actually support material claims, and keep an editorial record for substantive updates. Separate service descriptions from medical, legal, regulatory, or funding interpretations that require specialist review.
Owner: Editorial lead with the responsible clinical, legal, regulatory, or operational reviewer for the topic.
Verification: Sample sensitive pages and trace each material claim to an appropriate source and review record. Confirm that author and reviewer details are accurate, current, and specific to the content rather than copied across pages as generic trust elements.
Severity: critical
Chasing Broad Keywords Instead of Mapping Real Participant and Referral Intent
Observable evidence: The content plan is dominated by broad terms such as NDIS provider or disability support, while specific services, genuine locations, eligibility questions, capacity information, and referral needs do not have clear destinations. The source version said long-tail terms could convert 2 to 3 times higher than broad terms. With no supporting source URL in the source JSON, treat that as a historical, unreconciled estimate rather than a benchmark or causal claim.
Consequence: The site can earn impressions for mixed-intent searches without helping a participant or referral partner decide whether the provider offers the relevant support. Teams may then mistake traffic growth for qualified demand.
Correction: Build a query-to-page map from services the provider actually delivers, questions people genuinely ask, and the location or availability details the organization can maintain accurately. Consolidate overlapping pages, give each important intent a clear destination, and avoid creating thin pages solely because a keyword tool lists a suburb or service variation.
Owner: SEO and service-content leads, with operational validation of service and location claims.
Verification: Compare target queries with page purpose, headings, body copy, internal links, Search Console data, and live service information. The correction passes when each priority page has a distinct factual purpose and no longer relies on vague audience or service language.
Severity: medium
Writing Only for Participants and Ignoring the Other People Who Research Providers
Observable evidence: Service pages address only the participant and omit practical information that plan nominees, families, support coordinators, plan managers, or other referral partners may need, such as service scope, eligibility boundaries, referral steps, contact pathways, capacity context, documentation expectations, or how to request further information. Another warning sign is assuming every intermediary has authority to approve or arrange the same thing.
Consequence: People supporting a participant may be unable to verify whether the provider is relevant before making contact, while unclear role language can create confusion about consent, decision-making, or funding processes.
Correction: Create audience-specific information only where there is a distinct documented need. Explain what the provider can answer, what information is required to progress an enquiry, and where privacy, consent, clinical, or funding questions need responsible review. Avoid claiming that a support coordinator, plan manager, or nominee can approve a service unless that statement is accurate in context.
Owner: Intake or referral operations with participant communications and compliance review as needed.
Verification: Review common enquiry themes, referral questions, internal site search, and page coverage without exposing participant information. Confirm that each audience page answers a real question and does not duplicate generic marketing copy.
Severity: high
Skipping the Questions People Ask Across the NDIS Decision Journey
Observable evidence: The site describes services but leaves important research gaps around how the support works, who it may be suitable for, what information is needed before an enquiry, how availability is communicated, what participants should prepare, and where official NDIS guidance should be consulted. Educational articles may exist, but they are disconnected from current service pages or contain outdated funding interpretations.
Consequence: Participants and supporters may leave the site to answer basic questions elsewhere, while staff receive enquiries that could have been clarified with accurate public information. Educational content should not be treated as evidence that the provider will rank better or win referrals.
Correction: Build a resource set around recurring participant and referral questions that the provider is qualified to answer. Link educational material to current service information, use official NDIS sources for rules or scheme explanations, date-sensitive guidance appropriately, and distinguish general education from advice about an individual's plan or needs.
Owner: Content or participant communications lead with the relevant service and regulatory reviewers.
Verification: Compare published resources with current enquiry themes, official source material, and live service information. Retire or correct pages that no longer match the scheme, the provider's operations, or the audience's decision needs.
Severity: medium
Measuring Traffic Without Verifying Enquiries, Referrals, and Data Quality
Observable evidence: Reporting celebrates sessions, impressions, or keyword movement while form submissions, calls, referral sources, duplicate leads, spam, intake outcomes, and attribution quality are not reconciled. The source version used a 50 percent traffic increase as an example of growth with flat participant intake. Treat that as an illustrative scenario, not a benchmark and not proof that search traffic caused or failed to cause intake.
Consequence: Marketing spend can be shifted on the basis of incomplete evidence, successful fixes can be overlooked, and teams may overstate ROI or participant acquisition without a defensible connection between search activity and real enquiries.
Correction: Define the events that matter, validate form and phone tracking, reconcile marketing events with intake records where lawful and appropriate, document attribution limits, and route privacy-sensitive measurement choices through responsible review. Do not assume call tracking or any analytics configuration is automatically suitable for participant information.
Owner: Marketing analytics with intake operations, privacy, and technical owners.
Verification: Test each tracked event, inspect duplicates and spam, compare analytics with operational records at an appropriate aggregate level, and document what can and cannot be attributed. Use changes in traffic, enquiries, and intake as separate signals rather than a guaranteed causal chain.
Severity: high
