Conflicting Local Listings and Residence Information
Observable evidence: The residence name, operating address, phone number, website destination, hours, or location status differs between Google Business Profile, Bing, Yelp, relevant directories, and the website. The source previously associated the Map Pack with 30 to 50 percent of local clicks, but no supporting source URL is present here, so that range should be treated as a previously published observation requiring source reconciliation.
Consequence: Families, prospective residents, referral contacts, and search platforms can encounter conflicting information about which residence is real or how to reach it. That can reduce confidence and create local discovery problems, but it does not prove an automatic ranking penalty.
Correction: Establish one approved source of truth for the residence name, genuine address, phone number, website, and other public details. Correct material discrepancies on relevant profiles and directories, and do not create listings or location pages for nominal markets without a genuine residence and useful location-specific information.
Owner: The residence administrator or operations owner should approve factual location data, with the local SEO owner responsible for reconciliation.
Verification: Compare the live website and major profiles after changes, confirm that people can reach the correct residence, and document remaining duplicates or unresolved records.
Example: The source previously described an Austin residence losing a top 3 map position while an old address remained on three minor health directories. Treat that example as historical and unverified here rather than evidence that the address conflict caused the position change.
Severity: critical
Publishing Recovery Content Without Clear Accountability
Observable evidence: Sensitive recovery content has no named author or reviewer, staff biographies do not explain relevant roles, or the website uses generic authority language without identifying who is responsible for the information. E-E-A-T can support quality review, but it should not be described as a penalty filter or a single ranking switch.
Consequence: Families and prospective residents may have less information for judging who created the content, what experience supports it, and whether the page describes housing, peer support, clinical services, or general education accurately.
Correction: Add truthful authorship or review information where it genuinely applies. Describe staff roles, lived experience, professional qualifications, certifications, and responsibilities accurately without implying treatment authority or clinical credentials that the person or residence does not hold.
Owner: The content owner maintains attribution, while the appropriate residence leader, clinician, peer-support professional, legal reviewer, or regulatory reviewer checks claims within their actual scope.
Verification: Review representative recovery, policy, house-rule, and education pages and confirm that visible authorship or review information matches current records and the claims being made.
Example: The source previously recorded a 40 percent traffic increase after adding a team section with profile links. No supporting source URL is present, so preserve the value only as an internal historical observation rather than evidence that the biographies caused the increase.
Severity: high
Targeting Broad Addiction Terms Instead of Residence-Level Intent
Observable evidence: The website prioritizes broad addiction or recovery keywords even though the actual offering is sober living housing and support. Important pages may fail to explain location, resident profile, house structure, amenities, rules, eligibility, or other details people need when considering a residence.
Consequence: The site can attract poorly matched traffic or compete for queries whose intent belongs to treatment providers, government resources, national directories, or informational publishers. That creates measurement noise and makes it harder to judge whether search visibility supports real residence inquiries.
Correction: Build pages around genuine residence attributes and actual search intent, using plain language that accurately explains who the home serves and what it provides. Do not imply detoxification, treatment, clinical services, or guaranteed recovery outcomes unless those claims are factually and legally supportable.
Owner: The SEO or content lead maps query intent, while operations verifies that each described amenity, resident requirement, location, and service is real.
Verification: Compare Search Console queries, landing pages, inquiry themes, and actual residence operations to confirm that traffic is becoming more relevant rather than merely larger.
Example: The source previously associated an executive sober living query with a 15 percent increase in qualified admissions. Without supporting methodology, treat the value as an internal observation and do not infer causality.
Severity: medium
Mobile and Technical Friction on Critical User Paths
Observable evidence: House pages load slowly, large images delay rendering, phone or form controls fail on mobile, text shifts while loading, or important pages are blocked, duplicated, redirected incorrectly, or omitted from the index. Core Web Vitals can help diagnose performance, but no individual metric guarantees rankings.
Consequence: A family member or prospective resident may abandon the site, contact the wrong location, or fail to reach important eligibility and house information. Technical defects can also prevent crawlers from reliably accessing or understanding priority pages.
Correction: Compress and size media appropriately, reduce unnecessary scripts, repair crawl and indexation defects, test contact controls, and maintain secure HTTPS delivery. Do not describe mobile-first indexing or performance metrics as a direct penalty system.
Owner: The developer owns technical remediation, while design and content owners are responsible for page weight, interaction clarity, and visible contact information.
Verification: Test representative mobile devices, crawl the site, inspect Search Console coverage, and complete the contact path manually after deployment.
Example: The source recorded a residence website moving from 6 seconds to 1.5 seconds alongside a 20 percent increase in mobile rankings. No supporting source URL is present, so treat the comparison as historical observation rather than proof that speed caused the ranking change.
Severity: critical
Making Unverified Certification or Compliance Claims
Observable evidence: The website displays accreditation, licensing, certification, LegitScript, NARR, state-level, or other trust claims without current documentation, or presents a third-party status as an organic ranking requirement. Requirements can differ by state, advertising platform, certification program, referral source, and residence type.
Consequence: Families and referral partners may rely on inaccurate information when evaluating the residence. Unsupported claims can create legal, regulatory, reputational, or platform risk even when they were originally added for marketing purposes. Search benefit should not be assumed.
Correction: Publish only current, verifiable statuses the residence actually holds, explain what each status means in plain language, and use logos or badges only when permitted and factually accurate. Do not present certification display as a guaranteed authority or ranking tactic.
Owner: The residence operator owns factual status records; responsible legal, compliance, or program reviewers confirm statements within their scope; marketing publishes only approved wording.
Verification: Reconcile every public certification or compliance statement against current records and the applicable program or regulator, then remove expired, ambiguous, or unsupported language.
Example: The source described a Florida residence whose rankings stabilized after a NARR badge was added during a core update. With no supporting source URL, that remains an observational example rather than evidence of causation.
Severity: high
Thin House Information and Weak Internal Navigation
Observable evidence: The website contains only basic house, gallery, and contact information, or individual residence pages repeat generic copy without useful differences. Educational resources may exist but fail to link logically to house policies, eligibility, admissions information, contact routes, or the /industry/health/sober-living page.
Consequence: Users may be unable to answer basic decision questions, while crawlers receive weak contextual information about how the site's topics and residence pages relate. Dwell time should not be treated as a direct ranking factor, and internal links should not be described as a guaranteed transfer of rankings.
Correction: Add useful, non-duplicative information about genuine houses, policies, amenities, resident expectations, location, costs or financial disclosures where appropriate, and common questions. Link related pages contextually so people can move from education to the relevant residence or contact step.
Owner: Content owns structure and internal links; operations verifies residence facts; the appropriate reviewer checks sensitive recovery or policy statements.
Verification: Crawl the site for orphaned pages, manually follow important user journeys, and confirm that each house page contains genuinely residence-specific or location-specific information.
Example: The source previously reported that a FAQ hub with 20 detailed answers increased organic site depth by 3 pages per session. Treat those values as an unverified historical measurement, not a universal benchmark or causal result.
Severity: medium
Optimizing Traffic Without Verifying the Contact Experience
Observable evidence: Phone numbers are difficult to find, mobile tap targets fail, forms request unnecessary sensitive information, contact options do not state availability accurately, or structured data conflicts with visible address and phone information.
Consequence: Relevant traffic can arrive without a usable next step, so the residence cannot distinguish a visibility problem from a contact-path problem. Bed occupancy should not be used as a direct SEO metric because availability, eligibility, price, referrals, seasonality, and other operational factors also matter.
Correction: Make contact options clear and accessible, minimize unnecessary data collection, confirm that public phone and address information match the visible page, and use LocalBusiness structured data only when it accurately describes the entity and content shown to users. Markup does not guarantee richer search display or higher rankings.
Owner: Operations owns contact accuracy and response process; the developer owns interaction and markup; privacy or legal reviewers should assess sensitive information collection where applicable.
Verification: Complete the mobile call and form journeys, inspect the rendered structured data, and compare inquiry quality before and after corrections without assigning causality from a single change.
Example: The source recorded a 25 percent increase in phone inquiries after a sticky mobile call control was added. No supporting methodology is present, so treat the value as an internal observation rather than a guaranteed outcome.
Severity: high
