An HVAC website redesign is worth considering when the current site prevents customers from understanding your services or reaching the right person, and a smaller repair cannot reasonably fix it. Start with the problem you can demonstrate. Keep useful pages and contact paths, then scope only the changes needed.
Should you keep, improve or rebuild the site?
- Keep it when service information is accurate, contact paths work and the office can receive and follow up on inquiries. If the gap is missed calls or an unowned inbox, assign the follow-up work first.
- Improve it when specific changes can solve the problem: clearer service-area copy, a usable form, a corrected phone link, better proof or a more reliable delivery destination.
- Consider a rebuild when the existing structure or maintenance burden blocks those changes. Ask for a concrete explanation of that limitation and compare the cost and risk of a targeted repair with the proposed rebuild.
The conversion-path diagnosis helps locate the gap. If a rebuild is justified, use the checks below with the agreed website scope. A redesign cannot guarantee preserved rankings or more inquiries.
1. Record what the current site does
Export URLs and available Search Console or analytics records. Add phone numbers, form destinations, service-area information and pages linked from directories or printed materials. Mark missing data as unknown instead of treating an untracked page as worthless.
For each page, record the question it answers and where that answer will appear in the new site. Preserve useful details without carrying over inaccurate copy. Word count alone does not establish quality or whether a page should survive.
Use the call-log audit worksheet (CSV) alongside available form records to understand the current handoff. Separate repeat attempts, unique inquiries and confirmed outcomes. If the source cannot be verified, mark it unknown instead of crediting the website for every call.
2. Build a URL and redirect map
Download the URL, redirect and owner worksheet (CSV). It includes one illustrative row and blank rows for your site.
- Old URL: /air-conditioning-repair/
- New URL: /ac-repair/ — only if that page replaces the same service and coverage information.
- Expected behavior: one permanent server redirect to a working page; links and canonical tags use the destination.
- Owner: the person responsible for checking the deployed redirect and contact action.
Keep an existing URL when there is no reason to change it. Do not send unrelated retired pages to the homepage. Google’s site-move guidance explains relevant mappings and redirect handling.
3. Rehearse the contact paths
- Check the business number and mobile dialer link.
- Test form errors, success messages and delivery using approved test records.
- Verify any booking link against the actual scheduling process.
- Keep emergency, price and availability statements aligned with the contractor’s rules.
- Confirm that the office can find each test inquiry and owns the next step.
The repair, replacement and maintenance examples provide three paths to rehearse. If missed-call text-back is included, review the message examples and required office actions against the contractor’s real coverage.
4. Keep measurement comparable
Record event names and definitions before the switch. Check that consent settings, call attribution and approved analytics still work. If a definition changes or tracking has a gap, document it in the comparison.
The measurement framework separates an inquiry from a booking and completed work. A before-and-after report should identify other changes, such as advertising, staffing or service coverage.
5. Agree the launch and recovery plan
- Choose a window when the owner and the person controlling hosting are available.
- Keep a restorable copy of the previous site and document how to restore it.
- Freeze the agreed URL map for final checks; reassess any late changes.
- Assign who checks the deployed site and who investigates failures.
Use the contractor’s records when choosing a quieter window. There is no universal safe month or fixed period in which rankings will recover.
6. Verify after the switch
Recheck protected URLs, redirects, forms, phone links, indexing directives, canonical tags and the sitemap on the deployed site. Monitor Search Console and available inquiry records against the saved baseline. Investigate broken routes or missing requests promptly; do not dismiss them as normal ranking movement.
Our dated release example shows the checks recorded for this website. It documents implementation verification, not a contractor’s conversion results.
What should the proposal commit to?
Ask for the pages being kept or changed, the contact paths being tested, the person who owns each acceptance check, and the access you receive at handover. Agree who supplies accurate service information and verifiable trust evidence. Separate work included at launch from ongoing maintenance and paid software.
Compare the written scope with the published package and cost breakdown. A proposal should explain which observed problem each change addresses, what counts as a working result and who resolves a failed launch check.