Before changing a small business homepage, preserve evidence of what visitors, search engines, assistive technologies, and business systems currently receive. Save the live response and rendered experience, not only a design file. Record copy, metadata, links, forms, analytics definitions, search status, accessibility, performance, integrations, ownership, and a rollback package.
Capture the current public page
Save the canonical URL, HTTP status, response headers, rendered HTML, source HTML, desktop and mobile screenshots, structured data, title, meta description, canonical tag, robots directives, language, headings, text, image URLs, alt text, navigation, footer, contact details, hours, service area, calls to action, disclosures, and privacy links. Record the capture time and viewport.
Use a nonproduction copy for form testing. Preserve field names, required states, consent language, confirmation behavior, routing destination, and error handling with invented submissions. Do not place real customer data in screenshots, logs, or a public issue tracker.
Preserve search and traffic evidence
Google's Search Console overview describes page and query performance, indexing, sitemaps, URL Inspection, security issues, and Core Web Vitals evidence. Export a dated baseline for the homepage and relevant queries when access permits. Record the property, date range, filters, time zone, clicks, impressions, and affected URL rather than a cropped chart with no context.
Use URL Inspection to capture current index status and loaded-resource observations. Keep sitemap and indexing evidence, but do not claim that a search position or traffic change was caused by one homepage edit without appropriate analysis. Analytics and Search Console measure different things.
Keep ownership and integration evidence
Inventory the domain registrar, DNS, host, content system, repository, deployment service, form processor, email sender, analytics, Search Console, business profile, appointment system, payment links, consent tool, and monitoring. Record accountable owners, roles, recovery routes, and configuration references without copying passwords, tokens, private keys, or recovery codes.
Map every homepage link and integration. Check telephone, email, directions, social profiles, booking, forms, downloads, product pages, structured data, and campaign parameters. Record third-party scripts and consent categories because a visual redesign can silently remove measurement or add unapproved tracking.
Prepare URL and rollback evidence
If URLs may change, Google's site-move guidance recommends a URL mapping, testing, permanent redirects, updated canonical annotations and internal links, and monitoring both old and new URLs. It also recommends changing one major element at a time when practical. Preserve the old-to-new map and a list of important inbound links.
Even when the homepage URL stays the same, keep the exact prior build or deployable artifact, configuration version, content export, asset inventory, database backup where relevant, and restoration instructions. Define the rollback trigger before launch, such as broken forms, unavailable contact paths, severe accessibility regression, security failure, or incorrect business information.
Build an acceptance matrix
Record critical visitor journeys: understand the business, confirm service area or location, find hours, contact the business, request an appointment, reach a product or service, read disclosures, and use the page with keyboard and screen reader. For each, store expected result, device and browser, test data, observed result, evidence, owner, and retest.
Compare performance using the same conditions and enough samples. Check status codes, redirects, canonical, robots, sitemap, structured data, headings, accessible names, focus order, contrast, reflow, images, links, forms, consent, analytics events, and error monitoring. A visual approval does not replace functional evidence.
Close the change responsibly
Keep launch authorization, deploy time, version identifier, live verification, post-launch monitoring, incidents, corrections, and final acceptance. Protect the previous evidence according to retention and privacy needs. Do not change domain ownership, DNS, billing, sender security, or account permissions merely to complete the homepage change.
The evidence set is complete when another authorized person can reproduce the old state, understand what changed, verify the new live page, identify any search or analytics baseline, and execute a tested rollback. Preserve facts and recoverability, not unnecessary personal data or a promise that rankings will improve.
Sources
- Get started with Search Console — Google Search Central
- Site Moves and Migrations — Google Search Central