Audit an Addiction Treatment Website With Evidence, Severity, Ownership, and Verification

This audit is for marketing, digital, web, admissions, and operations teams that already have a live addiction treatment website and need to determine why search visibility, qualified inquiries, or program-page performance is not behaving as expected. It is also useful when evaluating prior agency work because the output is a documented baseline rather than a vendor opinion.

Evidence: Gather the current crawl, Google Search Console coverage and performance data, analytics or other approved inquiry measurement, current program and location inventories, Google Business Profile ownership information, structured-data test results, and a list of third-party forms, chat tools, scheduling tools, or CRM integrations. Keep screenshots or exports so later changes can be compared with the starting state.

Severity: Classify findings by user harm, privacy or regulatory review need, indexation impact, loss of access to important pages, conflict with current program facts, and effect on qualified inquiry paths. A cosmetic metadata issue should not outrank a broken admissions form or a blocked program page simply because it is easier to fix.

Owner: Assign search findings to SEO or web owners, program-content questions to content and clinical reviewers, intake-path defects to web and admissions teams, and privacy or regulatory questions to the people authorized to make those determinations. The source references 45 CFR Parts 160 and 164 and 42 CFR Part 2; those references require current verification before operational use. This audit cannot guarantee compliance, and responsible legal, medical, or regulatory reviewers remain required.

Corrective action: Define the smallest change that resolves the documented problem without expanding scope unnecessarily. Preserve a change log with the affected URL, evidence, decision, approver where applicable, and rollback information for higher-risk technical changes.

Validation: Re-test the exact condition that created the finding. Confirm the page can be crawled and indexed when intended, the content still matches the current program, inquiry paths reach the right team, and any privacy-sensitive implementation has been reviewed by the appropriate owner. If the website is still pre-launch or requires a build-first workflow, use the addiction treatment SEO hub for the broader supporting sequence rather than forcing a live-site diagnostic onto an unfinished site.

The audit should move from site access and indexation into page overlap, content quality, and trust-related implementation because later symptoms can be caused by earlier technical defects. Each layer below has its own evidence, severity test, owner, corrective action, and validation step.

Layer 1: Technical Access and Crawlability

Evidence: Compare a full crawl from Screaming Frog, Sitebulb, or Ahrefs Site Audit with the site's intended URL inventory. Record broken internal links, redirect chains, blocked pages, duplicate or missing metadata, Core Web Vitals concerns, and orphaned URLs. Severity: Highest when an important program, location, insurance, or admissions page cannot be reached, rendered, or indexed as intended. Owner: SEO and web development. Corrective action: Fix access, routing, canonical, internal-link, or template defects according to the evidence. Validation: Re-crawl the affected URLs and confirm that intended destinations, status codes, internal links, and rendered content now match the site plan.

Layer 2: Index Coverage and Search Eligibility

Evidence: Use Google Search Console Page indexing data and URL inspection on representative pages. Compare pages that are discovered, crawled, indexed, excluded, canonicalized elsewhere, or blocked with the URLs the organization actually wants searchable. Severity: High when a valid, useful page is unintentionally unavailable to search or when large sets of low-value URLs consume crawl attention. Owner: SEO with development support. Corrective action: Resolve the specific cause instead of assuming every non-indexed page needs more content. Validation: Recheck the corrected URL after Google has had an opportunity to process the change and confirm that the intended canonical and index state are reflected.

Layer 3: Program-Page Cannibalization

Evidence: Export indexed URLs and map the queries, impressions, clicks, internal links, and conversions associated with each page. Flag cases where IOP, PHP, detox, residential, insurance, or location pages compete for substantially the same intent. Severity: High when the wrong page repeatedly ranks, inquiry traffic is split across duplicative pages, or users land on content that does not match the service they searched for. Owner: SEO, content, and the program reviewer. Corrective action: Differentiate intent, consolidate redundant content, change internal links, or plan redirects only after link and conversion evidence is reviewed. Validation: Confirm the preferred page is crawlable, internally supported, factually current, and receiving the intended query coverage after changes.

Layer 4: High-Intent Content Quality

Evidence: Review the top 20 organic landing pages by clicks and add high-intent pages that may have little traffic but matter to admissions, such as insurance, payment, program, and location pages. Check factual accuracy, clinical review where needed, sourcing of health claims, authorship context, duplication, stale program information, and whether the page answers the actual user decision. Severity: Highest where inaccurate, unsupported, or incomplete information could mislead a patient or family. Owner: Content, clinical review, admissions, and SEO. Corrective action: Rewrite around verified service facts and user questions rather than adding length for its own sake. Validation: Re-review the published page against the approved source material and test the next action, such as calling, verifying insurance, or reaching admissions.

Layer 5: Structured Data and Trust-Related Implementation

Evidence: Test implemented markup with Google's Rich Results Test and a schema validator, then compare the markup with visible page content. Review LocalBusiness or MedicalOrganization facts where applicable and BreadcrumbList markup where used. Severity: High when structured data contains false business facts, broken URLs, or conflicts with the visible page; lower when an optional property is simply absent. Owner: SEO and development, with compliance or clinical review if the encoded information is sensitive. Corrective action: Correct or remove inaccurate markup rather than adding unsupported properties. Validation: Re-run the validator and manually confirm that every retained property matches visible, current information. Google no longer shows FAQ rich results, and valid markup does not guarantee display or ranking.

Evidence: Build a URL-to-intent map for detox, residential, PHP, IOP, outpatient, insurance, payment, and genuine location pages. Use Search Console query data, internal-link destinations, page titles, conversion paths, and any approved call or form attribution. Preserve existing path examples when reviewing overlap, including /iop/, /programs/intensive-outpatient/, /detox/, and /locations/[city]/detox/. The purpose is to identify when different URLs are trying to answer the same user decision.

Severity: Treat overlap as more serious when the wrong page ranks for a high-intent query, multiple URLs alternate unpredictably, a weaker page receives qualified traffic that should reach a more complete page, or duplicated content creates confusion about the actual program. Thin insurance or payment content is higher severity when it omits current verification steps, accepted plan information the organization is authorized to publish, cost or payment context, or a clear route to admissions.

Owner: SEO should own the query and URL analysis. Content and admissions should verify the user journey and operational facts. Clinical or compliance reviewers should review sensitive treatment, insurance, or financial claims where the organization requires it.

Corrective action: Do not delete pages automatically. If consolidation is supported by the evidence, choose the preferred destination, preserve useful information, review inbound links and internal links, and use a 301 redirect only when the old URL should permanently resolve to the new one. If both pages serve different intents, make the distinction explicit in headings, copy, navigation, and internal links. For thin insurance content, replace the placeholder pattern with verified information about the facility's actual verification process and the next step a caller should take. The source described 150-word placeholders as a common example; treat that as an observational description, not a minimum-content rule.

Validation: Re-crawl the affected URL set, confirm redirects and canonicals behave as planned, verify that no important links point to retired pages, and monitor which URL receives the target query after Google processes the changes. For insurance and payment pages, have the responsible operational owner confirm that the published process is still current and test the contact path from a mobile device.

This audit stage identifies technical evidence that requires review; it does not decide whether a specific form, analytics setup, CRM, chat tool, or workflow is legally compliant.

Evidence: Inventory every intake, contact, insurance, chat, scheduling, and form-confirmation flow. Record which scripts load, where submitted values can appear, whether transport uses HTTPS, what third parties receive events, and whether the organization has current documentation for those integrations.

Contact and Intake Implementations

The source references HIPAA Privacy and Security Rules at 45 CFR Parts 160 and 164 and substance-use-disorder record requirements at 42 CFR Part 2; verify current applicability with the responsible reviewers instead of treating the citation as an SEO conclusion. Severity: Escalate immediately when sensitive values appear in URLs, logs, analytics payloads, or tools that have not been approved for the workflow, or when a form transmits over HTTP. Owner: Web development and the organization's privacy, security, compliance, and legal owners. Corrective action: Stop unnecessary collection or transmission, move sensitive data handling into approved systems, correct transport and tracking configuration, and document the change. Validation: Re-test the full form journey with approved test data and confirm that sensitive values do not appear in prohibited destinations or public URLs.

Structured Data Review

Evidence: Validate every implemented schema type and compare values with visible content, current facility facts, and live URLs. Check LocalBusiness data, MedicalOrganization data, BreadcrumbList paths, and any retained FAQPage markup. The source notes May 2026 as the point when the prior FAQ rich-result feature was removed and uses a 404 error as an example of a broken referenced URL; do not present FAQPage as a current Google rich-result opportunity. Severity: Prioritize false business facts, broken breadcrumb destinations, or markup that describes content not visible on the page. Owner: SEO and development, with content or regulatory review where the marked-up fact is sensitive. Corrective action: Correct, simplify, or remove invalid markup. Validation: Re-run the validators and manually compare the final markup with the rendered page and current business records.

An audit can surface 40 issues without telling the team what should happen next. The useful output is a queue in which every finding has evidence, severity, owner, corrective action, and a validation test.

Evidence: Attach the affected URL, crawl or Search Console evidence, user-path impact, current traffic or inquiry data, and any dependency on clinical, privacy, legal, or operational review. Score only what the team can support from the available evidence.

• Estimated impact can use a 1-5 scale, where 5 represents the most material effect within this site's own context.
• Estimated effort can use a 1-5 scale, where 5 represents the hardest correction for this team.

Severity: High-severity findings are those that block intended pages, break inquiry paths, publish materially incorrect facility information, expose sensitive data for review, or misdirect high-intent users. Lower-severity findings can remain scheduled when they do not create immediate user, regulatory-review, or search-access problems.

Immediate Queue Examples

• Incorrect structured data on a location page can be scored impact: 4, effort: 2 when the business fact is wrong and the correction is contained.
• An intended page blocked by robots.txt can be scored impact: 5, effort: 1 when the block is accidental and the page is otherwise ready for search.
• An intake form missing HTTPS can be scored impact: 5, effort: 2 and should also be escalated through the organization's privacy and security process.
• Duplicate title tags across program pages can be scored impact: 3, effort: 2 when they contribute to unclear page differentiation but do not block access.

Planned Remediation Examples

• Program consolidation that requires 301 redirects can be scored impact: 5, effort: 4 when the URL map, link profile, and conversion path all need coordinated changes.
• Thin insurance or payment pages can be scored impact: 4, effort: 4 when factual development and review are substantial.
• Internal-link gaps that isolate important program pages can be scored impact: 4, effort: 3 when the content already exists but navigation and contextual links need restructuring.

Monitor or Schedule Examples

• Core Web Vitals work beyond the passing threshold can be scored impact: 2-3, effort: 3-5 depending on the actual field data and template constraints.
• Additional service-level schema can be scored impact: 2, effort: 3 when visible content is already clear and the markup is optional.
• Image alt-text cleanup can be scored impact: 1-2, effort: 2 when the main accessibility and content issues have already been addressed.

Owner: The audit lead owns prioritization, but remediation owners should be assigned by discipline: development, content, admissions, analytics, clinical review, or compliance. Corrective action: Work from the highest-severity evidence rather than applying the example scores mechanically. A page responsible for 80% of measured organic leads deserves different treatment from a similar page receiving 12 visits per month. If the audit produces more than 20 distinct problem categories, simplify the backlog into root causes before commissioning more work.

Validation: Close a finding only when the original evidence has been re-tested and the expected technical or content state is confirmed. If the team needs a second-level diagnostic, use the existing professional SEO audit option for treatment centers as the natural supporting path rather than treating the score itself as proof of business impact.

Evidence: Start with site size, architecture history, number of locations, migration history, rendering complexity, tracking quality, and whether previous changes are documented. A self-audit can be productive for a site under 100 pages when the URL structure is straightforward, ownership is clear, and there has been no major unexplained performance change.

Severity: Escalate the diagnostic when the cause cannot be isolated safely with the available evidence. Examples include layered redirects and canonicals from prior agency work, multi-location cannibalization, JavaScript rendering problems, undocumented migrations, or a material traffic decline such as 30%+ over a rolling 12-month period. The percentage is a previously published threshold example, not a universal trigger or proof of a search penalty.

Owner: An internal SEO or web owner can run the initial diagnostic. A specialist may be appropriate when the issue crosses development, migration, analytics, information architecture, or multi-location systems that the internal team cannot verify confidently. Privacy, clinical, legal, and regulatory review responsibilities remain with the organization's authorized reviewers regardless of who performs the SEO work.

Corrective action: If outside help is used, require a diagnostic that explains root causes, affected URLs, severity, dependencies, recommended changes, and how each correction will be validated. Do not accept a raw crawl export as a complete audit. For major migrations, include redirect mapping, canonical review, crawl comparison, analytics continuity, and pre-launch validation before the new site replaces the current one.

Validation: Compare the delivered findings with the site's actual data and confirm that proposed actions map to measurable problems. After implementation, re-run the crawl, Search Console checks, structured-data tests, and inquiry-path validation. A 150-line spreadsheet can be useful evidence, but without prioritization, ownership, and retesting criteria it is still only an inventory, not a completed diagnostic.