A small business homepage handoff should show who controls the site, what the page is meant to accomplish, how to verify it, and how to recover from a bad change. Include the current owner, approved editors, hosting and publishing path, page purpose, important content blocks, measurement tools, unresolved issues, and the last known-good evidence.
Record control without exposing secrets
List the organization or account that owns the domain, hosting service, content system, analytics property, and search tools. Name the responsible role and the approved recovery contact, but do not put passwords, recovery codes, private keys, or billing details in the handoff. Link to the organization-approved credential vault or owner process.
Search Console distinguishes owners from users, and only owners can grant permissions to others. Its documentation also says a property needs at least one verified owner for users to retain access. Record the verified ownership method, current owner role, delegated users, and who can safely change them. See Google's Search Console permissions guide.
Explain what the homepage must do
Write a one-sentence purpose and identify the primary audience and primary action. Inventory the visible business name, service summary, location or service area, hours if applicable, contact path, navigation, legal links, and any disclosed promotion. Mark which statements are approved facts and which need review. Include links to the source for claims that can change, such as hours or service availability.
Preserve accessible structure
Record the intended page title, main heading, section headings, link wording, and meaningful alternative text. The W3C Web Accessibility Initiative advises informative unique page titles and headings that convey meaning and structure. Its writing accessibility tips provide a stable review checklist for the handoff. Note known keyboard, contrast, motion, form-label, or screen-reader issues instead of describing the page as accessible without evidence.
Include the publishing and verification path
Write the exact approved sequence from draft to preview to production. Identify who reviews content, who can publish, where deployment evidence is stored, and how the live page is checked after a change. Record the canonical URL, expected redirects, sitemap ownership, analytics identifiers, and search-property name without including secret tokens. Preserve a screenshot or content hash of the last known-good homepage and the date it was observed live.
List dependencies and current risk
Name forms, calendars, maps, booking tools, product links, third-party scripts, and external assets the homepage depends on. For each one, record its owner, purpose, renewal or review point, and what a failure looks like. Separate broken items from enhancements. A handoff should not turn an unverified idea into a required feature.
Test the handoff
Ask the recipient to locate the source, create a reversible preview edit, verify the page title and headings, follow the main contact path, confirm analytics ownership, and explain the rollback path. The handoff is ready when another authorized person can verify and maintain the homepage without guessing or receiving unnecessary access.
Sources
- Managing owners, users, and permissions — Google
- Writing for Web Accessibility - Tips for Getting Started — W3C Web Accessibility Initiative
- How to transition a team off of a project — Digital.gov