Website Ownership Checklist: GitHub, Cloudflare, Domains and the Right to Leave

A website is easier to maintain when the business can tell exactly who owns each component. An agency may build the code, but you should not have to lose your web presence to change agencies. Begin the ownership conversation before design starts, not after a disagreement.

1. Domain, registrar and DNS

Confirm the legal or authorized business owner controls the registrar account, knows the renewal date and has a recovery method. Export existing DNS records before any transfer. Verify mail-related records, not just the website's A or CNAME record; breaking business email is a common risk during a rushed migration.

2. Source code and creative assets

Ask for a repository under a client-controlled GitHub organization where practical, with appropriate access. Include assets the client has rights to use, deployment scripts, dependency versions and a readable setup guide. A website being publicly visible is not the same as having a buildable copy of its code.

3. Hosting and deployments

Identify which Cloudflare account or other hosting account deploys the production site, what happens on a failed build, how to roll back and who can edit environment variables. Store secrets in an appropriate secret store, never in a public Markdown file or repository. Ensure you can deploy to a staging domain before changing DNS.

4. Forms, payments and bookings

Forms and booking widgets may route into third-party services. Document where submissions live, who receives alerts, retention or deletion policies, service fees and failure notifications. The same principle applies to payment processing and email delivery. A static site can still contain dynamic workflows, and those need real account owners.

5. SEO, accessibility and content workflows

Keep a list of canonical URLs, redirects, sitemap generation, search console ownership, analytics setup and a content approval workflow. Test the accessible experience after integrations are inserted. No score can replace manual review of key customer tasks.

6. Exit and support terms

The contract should explain the one-time build fee, recurring support fees, who pays which vendors, cancellation terms, ownership of delivered code and what happens during handoff. Optional maintenance can be valuable, but the business should understand exactly what it buys and should not depend on perpetual agency access to retain its public site.

Start with the right documents: FOURAK's development process, the Alaska website cost guide, and the local static website guides for Kenai, Homer, Seward and Anchorage. To discuss ownership before a new build, start a project.