What should a rehab website build contract include?

2026-10-12

A rehab website build contract should define much more than page count and a launch date. It should explain what the agency will build, who owns it, how existing search visibility will be protected, and what happens when something needs fixing. For healthcare marketers comparing agencies, those details help separate a polished sales presentation from an accountable project plan.

The contract also needs to connect web design with technical SEO, local SEO, answer engine optimization (AEO), and generative engine optimization (GEO). A visually attractive website can still create problems if important pages disappear, inquiry tracking breaks, or search engines cannot access essential information.

Use the following checklist when evaluating a new website for rehab, detox, intensive outpatient programs (IOP), partial hospitalization programs (PHP), or residential programs. Many of the same questions apply to behavioral health, mental health, dental, med spa, and other healthcare websites.

1. Define the business goals and project boundaries

Start with a written statement of what the website is intended to support. That might include clearer program information, better location navigation, more useful admissions inquiries, or an improved foundation for ongoing rehab marketing. These are project objectives, not guarantees of rankings or lead volume.

The agreement should identify the organization, domains, locations, and programs included. If your organization operates multiple facilities or brands, do not assume that every location is covered by a proposal labeled a website redesign.

• The scope should name each included domain and explain whether subdomains or separate location websites are part of the project.
• The contract should identify which rehab, detox, IOP, PHP, and residential program pages will be created, revised, or migrated.
• The agreement should list exclusions, such as photography, paid software, ongoing content production, or post-launch PPC management.
• The project plan should distinguish website delivery from recurring SEO, AEO, GEO, and rehab lead generation work.

Ask each agency to explain how its proposed scope supports discovery and inquiry quality. A proposal that only lists design deliverables leaves important commercial questions unanswered.

2. Specify the sitemap, templates, and content responsibilities

A contract should include an approved sitemap or a clear process for developing one. Page counts alone are not enough. Twenty pages can mean twenty useful program and location resources, or a collection of thin pages with little differentiation.

Identify the page types the agency will build, including program pages, location pages, admissions information, team profiles, contact pages, and educational resources. Specify which templates are custom and which reuse a shared layout.

Content responsibilities need equal attention. The agreement should state who drafts copy, verifies business facts, supplies images, approves claims, and enters the final material into the website.

• Each page should have a defined purpose, intended audience, and internal linking role.
• The content scope should distinguish original writing from editing, migration, and basic formatting.
• The approval process should identify the people responsible for operational accuracy and compliance review.
• The contract should explain how outdated, duplicate, or unsupported content will be handled.

For SEO and AI search, useful content depends on accurate distinctions between programs, locations, and organizational responsibilities. The contract should not permit generic copy that presents every service or facility as interchangeable.

3. Make technical SEO and migration work explicit

A redesign can change URLs, navigation, metadata, and indexing behavior. The contract should describe how the agency will evaluate the existing site before making those changes. Preserving every old page is not always appropriate, but removing pages without review creates avoidable risk.

Require a pre-build inventory of important URLs, current search performance, existing redirects, and relevant technical issues. That inventory should inform the new architecture rather than appear as an unrelated audit delivered after launch.

• The agency should map changed URLs to relevant replacement pages and document permanent redirects.
• The build should include descriptive page titles, appropriate headings, canonical tags, and crawlable internal links.
• The launch checklist should cover XML sitemaps, robots directives, indexing settings, and broken links.
• The contract should define mobile and performance testing, including how significant template-level problems will be corrected.
• The agency should explain how staging environments will be kept out of search results without blocking the live site at launch.

Ask for specific deliverables rather than a single line promising an SEO-friendly website. Also clarify whether post-launch technical monitoring is included, how long it lasts, and who resolves migration defects.

4. Include realistic AEO and AI search requirements

AEO and AI search work should be described as practical implementation, not a promise that a platform will cite your organization. Google AI Overviews, ChatGPT, Perplexity, and Gemini use different systems, and a website contract cannot control their responses.

Useful requirements include clear question-and-answer sections, accurate organizational information, accessible text, and consistent descriptions of services and locations. These elements help make the website easier to interpret for people and automated systems.

• The agency should structure important answers so readers can understand them without searching through promotional copy.
• The website should display clear business names, location details, contact information, and service relationships.
• Structured data should match visible page content and use appropriate types, without unsupported claims.
• The content plan should identify where authorship, review information, and relevant source references are appropriate.

Ask what the agency means by GEO, LLM SEO, or AI SEO. The answer should describe concrete tasks and limitations. Adding an acronym to a proposal does not establish a deliverable, and no structured data implementation guarantees inclusion in an AI-generated answer.

5. Document local SEO and location accuracy

For organizations serving specific communities, the contract should explain how location information will appear across the website. Each location page should reflect a real facility or legitimate business presence, with accurate contact details and information relevant to that location.

If Google Business Profile optimization is included, identify the profiles involved, the work covered, and the access arrangements. Website development and profile management are separate responsibilities unless the agreement explicitly connects them.

• The agency should confirm which address, phone number, hours, and location names belong on each page.
• Location pages should use relevant internal links rather than rely on disconnected pages created only to target cities.
• The contract should identify who approves changes to business profiles and who retains primary ownership.
• Any call tracking setup should preserve a clear plan for consistent business information and accurate attribution.

The same discipline applies to mental health offices, dental practices, and med spas. Accurate location details support local search and can reduce ambiguity when answer engines describe where an organization operates.

6. Clarify ownership, account access, and portability

Ownership provisions deserve close attention before a deposit is paid. Your organization should understand which assets it owns after payment, which components are licensed, and what access remains available if the agency relationship ends.

The contract should address the domain, hosting account, content management system, design files, written content, images, analytics properties, and custom code. Third-party software may have separate license terms that limit transfer or require ongoing payments.

• The agreement should state who controls domain registration and who can authorize DNS changes.
• Your organization should have appropriate administrative access to the website and its business-owned measurement accounts.
• The agency should identify proprietary components, paid plugins, and any restrictions on moving the site.
• The exit process should specify which files, credentials, documentation, and backups will be supplied.

Account ownership affects SEO continuity as well as operational control. Losing access to historical reporting or search data can make future audits and agency transitions harder. Ask for a written handoff procedure, not simply verbal reassurance that everything belongs to you.

7. Set privacy and compliance-aware review responsibilities

Healthcare websites need a deliberate approach to forms, tracking, security, and public-facing claims. A contract should assign responsibilities and review checkpoints rather than make broad statements that the finished site is automatically compliant.

HIPAA, FTC requirements, state rules, and relevant platform policies may affect particular website features or marketing activities. Have qualified legal and compliance advisers evaluate requirements for your organization. Agency practices and contract language are not substitutes for legal advice.

• The agreement should identify every form, its purpose, the requested fields, and where submitted information is sent.
• The project should document analytics, advertising tags, embedded tools, and other third-party integrations for review.
• The contract should identify who supplies and approves privacy notices, consent language, and required disclosures.
• The agency should explain access controls, update responsibilities, backups, and the process for reporting security concerns.

If LegitScript considerations are relevant to your marketing plans, clarify who handles related requirements and approvals. Do not treat a website build, an SEO engagement, or an agency relationship as certification. Compliance-aware planning also means avoiding unsupported claims in copy and structured data.

8. Define conversion paths and measurement

Conversion rate optimization should focus on making legitimate next steps clear. Visitors should be able to find contact information, understand which location they are contacting, and use inquiry forms without unnecessary confusion. The contract should list the paths being designed and tested.

Measurement needs similar specificity. A form submission, phone click, connected call, and qualified admissions inquiry are different events. Treating them as interchangeable can make reporting difficult to interpret.

• The measurement plan should define each conversion event and explain how it will be tested.
• The agency should distinguish website activity from admissions outcomes that require separate operational data.
• The scope should identify analytics and reporting access, dashboard deliverables, and reporting frequency.
• Any connection between website forms and internal systems should include field mapping, error handling, and responsibility for testing.

Privacy review should happen before tracking is enabled. Reporting should support decisions about SEO, AEO, and rehab marketing without collecting unnecessary sensitive information. Avoid contracts that promise lead quality while leaving the definition and measurement method unspecified.

9. Establish accessibility, usability, and acceptance criteria

A contract should explain what makes the website ready for acceptance. A subjective statement that the site looks good is not a reliable standard. Define the browsers, devices, templates, and user journeys that will be checked before launch.

Accessibility requirements should identify the intended standard, testing approach, and remediation process. Automated scans alone do not evaluate every issue. Your organization should also understand whether manual checks and third-party review are included or separately priced.

• Testing should cover navigation, readable content, keyboard interaction, form labels, and understandable error messages.
• The agency should verify phone links, contact forms, location links, and confirmation messages across supported devices.
• The agreement should define the difference between a defect and a new feature request.
• The acceptance process should provide a review window and a method for recording unresolved issues.

Usability also supports search-oriented content. Clear headings and accessible text help visitors understand a page quickly, while reducing reliance on images or interactive elements that may obscure essential business information.

10. Put timelines, revisions, and payment milestones in writing

A useful timeline shows dependencies, not just a target launch date. Content approvals, access to existing systems, legal review, and integration decisions can all affect delivery. The contract should specify what happens when either party misses a dependency.

Revisions should be defined by stage. Clarify how many review rounds are included for architecture, design, copy, and development. Also explain how feedback is consolidated when several stakeholders participate.

• Payment milestones should correspond to identifiable deliverables or agreed project stages.
• The agreement should describe how change requests are priced and approved before additional work begins.
• The timeline should include client review periods and the consequences of delayed approvals.
• The contract should address cancellation, paused projects, and payment for completed work.

For agency comparisons, request the full expected cost of ownership. Hosting, software licenses, maintenance, ongoing SEO, and content updates may sit outside the build fee. A premium proposal can be appropriate, but its inclusions should be clear enough to evaluate against other offers.

11. Require a launch plan and post-launch handoff

Launch is a coordinated process, not simply publishing a new design. The agreement should identify who controls the launch decision, who makes technical changes, and who checks the live website immediately afterward.

A written plan should include a current backup, a rollback approach, redirect verification, live form testing, and checks for accidental indexing restrictions. It should also identify how urgent launch issues are reported and prioritized.

• The agency should deliver documentation for routine content updates and essential website settings.
• The handoff should include approved credentials, asset files, and a list of recurring software costs.
• The contract should specify the defect warranty period and distinguish it from ongoing maintenance.
• Post-launch reporting should identify technical issues and available search signals without promising a fixed ranking timeline.

Confirm who maintains the website after handoff. If the build agency is not handling ongoing technical SEO or content strategy, the next team needs enough documentation to manage the site without reverse-engineering the project.

12. Compare agencies by accountability, not vocabulary

When asking what should a rehab website build contract include, look for a connected plan: accurate content, understandable architecture, measurable inquiry paths, ownership protections, and a documented launch process. Strong proposals explain both deliverables and limitations.

Ask each agency to walk through one program page and one location page. Have it explain the content requirements, internal links, technical checks, conversion path, and AEO considerations. This reveals more than a long list of SEO terms.

SCALZ.AI offers premium, custom, done-for-you rehab marketing, with web design, addiction treatment SEO, technical SEO, content strategy, AEO, and GEO scoped to the needs of the engagement. Explore the SCALZ.AI rehab marketing agency service when comparing how agencies connect a website build with ongoing search work.

Before signing, make sure every important promise appears in the agreement or an attached scope. If you want to discuss a website project and its search requirements, call 407-954-8800 or review SCALZ.AI's rehab marketing approach. A clear scope gives your team a practical basis for evaluating the work.

Call 407-954-8800 to talk through next steps.