Targeting Benefit Language Without Verifying What the Facility Can Actually Support
Observable evidence includes search impressions for TRICARE or VA Community Care language that lead to pages with vague, outdated, or unsupported statements about coverage, referrals, eligibility, or network participation. The problem is not simply that broad addiction terms are competitive. It is that veterans and families using benefit-related language may reach a page that does not clearly explain what the facility can verify, what requires an intake conversation, and what should be confirmed with the relevant payer or program. The correction belongs jointly to SEO, intake, operations, and the reviewer responsible for benefit claims. Rewrite the page around the exact questions users ask, distinguish service availability from insurance status, and remove language that implies approval or guaranteed coverage. Verify the fix by checking the live copy, current program information, search queries, and whether intake staff give answers consistent with the page.
Consequence: Unclear benefit language can attract mismatched inquiries, create avoidable intake friction, and weaken reader trust when the search promise and the facility's actual status do not align.
Fix: Build or revise benefit-related content only where the facility has accurate information to publish. Assign an operations or intake owner to confirm the facts, a qualified reviewer to check regulated or health-adjacent language, and an SEO owner to map the verified information to real query intent. Recheck the page whenever participation, referral requirements, or coverage language changes.
Example: A facility may appear for a Phoenix-area TRICARE query yet provide only a generic insurance paragraph. A stronger page would state the facility's verified status, explain what the intake team can confirm, and avoid implying that a search phrase or payer reference guarantees eligibility or admission.
Severity: critical
Treating Proximity to VA or Military Locations as a Substitute for Genuine Local Relevance
Observable evidence includes location pages that mention VA medical centers, military installations, or surrounding cities even when the facility has no genuine location-specific information to add. Another signal is a Google Business Profile or public directory listing whose address, service details, or categories do not match the real facility. Proximity can matter to users, but a map reference, repeated landmark name, or location phrase should not be presented as a guaranteed ranking mechanism. The correction belongs to local SEO and operations: document where the facility is actually located, which areas it legitimately serves, and what useful local information can be verified. Create a dedicated location page only for a genuine location with substantive local details. Verify through the live profile, on-site contact information, relevant local search results, and first-party inquiry data.
Consequence: Manufactured or inaccurate local relevance can confuse veterans and referral sources, create inconsistent business information, and leave genuine location questions unanswered.
Fix: Audit the website and local profiles against verified facility records. Keep names, addresses, phones, hours, and service information accurate. Where local pages are warranted, explain the real location, access considerations, and verified service context rather than repeating nearby landmark names for search coverage.
Example: A San Diego facility can describe its actual location and practical access information when that helps prospective patients or referral partners. It should not imply an affiliation with a nearby military or VA institution merely because that institution appears in local searches.
Severity: high
Publishing Generic Health Content That Does Not Match Veteran-Specific Questions
Observable evidence includes service pages or articles that could be placed on any addiction-treatment website without changing the substance. They may mention veterans in headings while leaving important questions about program fit, staff qualifications, referral pathways, co-occurring needs, military culture, or transition concerns unanswered. The correction is not to add more military terminology. Content owners and appropriate clinical reviewers should identify what the facility can accurately explain, support medical statements with suitable sources, make authorship and review responsibility transparent, and remove unsupported generalizations about veterans. SEO can then organize the verified material around the search questions that the page is meant to answer. Verify the correction by comparing the page with actual service information, reviewer sign-off, query intent, and reader pathways to appropriate next steps.
Consequence: Generic or thin material can leave users without the information needed to evaluate the facility and can make the site's expertise difficult to assess.
Fix: Replace interchangeable copy with specific, reviewed explanations of the facility's real services, limitations, staff expertise, referral process, and relevant veteran-focused considerations. Use medical and military terminology only when it is accurate, necessary, and understandable to the intended reader.
Example: A broad alcohol article can be less useful than a carefully reviewed page explaining how the facility evaluates and supports veterans who present with alcohol-related concerns alongside service-connected experiences, provided every clinical statement reflects the facility's real capabilities.
Severity: high
Treating E-E-A-T as a Checklist Instead of Making Health Claims Verifiable
Observable evidence includes anonymous clinical articles, staff pages without meaningful qualifications, unsupported treatment claims, unclear ownership, missing review responsibility, or accreditation and licensing language that cannot be reconciled with current records. E-E-A-T is a quality concept, not a switch that can be turned on with schema markup or an author box. The correction belongs to editorial, clinical, compliance, and technical owners working together. Identify which claims require professional review, show who wrote or reviewed health content when appropriate, cite reliable support where needed, keep facility and credential information current, and ensure any structured data matches visible page content. Verify by auditing the rendered page, source support, staff information, and the current status of any regulated credential or accreditation mentioned.
Consequence: Readers may be unable to judge who is responsible for important health information, and unsupported or stale claims can create trust, legal, regulatory, or quality risks.
Fix: Create a documented review process for patient-facing health content. Publish accurate author and reviewer information where appropriate, reconcile credentials with current records, support medical claims with suitable sources, and use structured data only when it truthfully represents visible entities and content. Do not treat markup as a ranking guarantee.
Example: A staff directory that merely lists names provides less verification value than profiles that accurately explain relevant roles and qualifications. Publishing external identifiers is not automatically required; the facility should disclose only information that is appropriate, current, and permitted.
Severity: critical
Creating Mobile Inquiry Friction and Then Misdiagnosing It as a Ranking Problem
Observable evidence includes a page that takes more than 3 seconds to become usable in the team's own test conditions, an intake form with 15 fields before a person can ask a basic question, hidden contact controls, broken tap targets, or unclear privacy expectations. These are usability and conversion problems first. They should not be described as proof that a particular engagement metric directly controls rankings. The correction belongs to product, engineering, intake, privacy, and marketing owners. Reduce unnecessary steps, make contact choices understandable, ensure the form collects only information the organization is prepared to handle appropriately, and test real mobile journeys. Verify with device testing, form completion checks, call routing, accessibility review, privacy review, and first-party abandonment data.
Consequence: People who are trying to understand services or contact the facility may abandon the process, submit incomplete information, or choose another option because the inquiry path is confusing or unreliable.
Fix: Improve mobile performance and Core Web Vitals where they identify real technical issues, simplify the inquiry path, keep important contact options visible, and review every requested form field for necessity and appropriate handling. Do not promise that a usability change will produce a specific ranking or intake outcome.
Example: A mobile page with a 3-field initial inquiry form and an accurately staffed 24/7 contact option can reduce unnecessary friction when those claims and operations are real. A long, multi-step path with unclear buttons may create avoidable abandonment even if the page is otherwise search-optimized.
Severity: high
Measuring Success Through Branded Visibility While Ignoring Non-Branded Service Discovery
Observable evidence includes reports dominated by searches for the facility name while service, program, condition, benefit, and location queries remain weak or unmapped. Branded visibility matters, but it does not show whether people who do not already know the organization can discover accurate information about relevant services. The correction belongs to SEO, content, clinical review, and analytics owners. Separate branded from non-branded performance, map legitimate service topics to pages, and confirm that each page reflects services the facility actually provides. Verify with query-level Search Console data, landing-page performance, qualified inquiry sources, and periodic content review rather than assuming that more keyword coverage automatically means better patient acquisition.
Consequence: The organization can mistake existing brand demand for broader discovery growth and may overlook important service questions that veterans and families use during research.
Fix: Build topical coverage from verified services and real user questions, not from a generic keyword inventory. Assign clinical or operational reviewers to confirm service descriptions and an analytics owner to separate branded demand from new non-branded discovery.
Example: Instead of relying only on searches for the facility name, a center can develop reviewed pages around the veteran-focused services it genuinely provides and the locations it genuinely operates, then measure whether those pages attract relevant non-branded inquiries.
Severity: medium
Leaving Conflicting Facility Information Across Relevant Public Profiles
Observable evidence includes different names, addresses, phone numbers, hours, URLs, or service descriptions across the facility website, Google Business Profile, treatment directories, professional listings, or other relevant public sources. The practical risk is user confusion: a veteran, family member, or referral source may call an outdated number or question whether a listing represents the same facility. Do not treat directory presence or citation consistency as a guaranteed ranking factor. The correction belongs to local SEO and operations, with a designated owner for source-of-truth business data. Inventory relevant profiles, correct verified information, and document which listing cannot be edited directly. Verify by checking the live listings and testing the contact details rather than relying only on a citation tool.
Consequence: Conflicting public information can reduce confidence, send users to outdated contact channels, and make local data harder for the organization itself to govern.
Fix: Maintain a source-of-truth record for the facility's public business information and audit relevant profiles against it. Correct only verified details, keep duplicate or legacy listings documented, and prioritize sources that real patients, families, and referral partners are likely to use.
Example: If a facility changes its phone number but an older veteran-oriented directory still shows the previous contact, the operations owner should document the discrepancy, request a correction where possible, and confirm that the website and primary profiles display the current number.
Severity: medium
