Website rebuild checklist for Australian small businesses
A rebuild should preserve existing value while removing the limitations that prevent the website supporting customers and the business.
The short version
Before rebuilding, document the current website’s valuable pages, search queries, backlinks, analytics, forms, integrations, domains, and content ownership. Define the new customer journey and success measures, map old URLs to new destinations, test the production build, and monitor indexing and enquiries after launch.
Before design begins
A visual refresh is not enough if navigation, content, search intent, ownership, or integrations remain unclear. Establish why the rebuild is needed and which evidence will show improvement.
- Business goal and priority audiences
- Current analytics and Search Console exports
- High-value pages, queries, backlinks, and conversions
- Content inventory and ownership
- Brand, photography, legal, privacy, and accessibility needs
- Forms, CRM, booking, email, domain, and hosting access
Protect existing search value
Changing URLs without redirects can discard signals and send visitors to missing pages. Create an old-to-new URL map, preserve useful content, avoid redirect chains, update internal links, publish accurate canonicals, and submit the new sitemap.
Do not automatically migrate outdated, duplicated, or low-value content. Decide what should be retained, consolidated, rewritten, redirected, or removed based on customer and search evidence.
Production checks before launch
Test responsive layouts, keyboard access, forms, validation, links, social previews, metadata, structured data, analytics, performance, image dimensions, error pages, redirects, and ownership access. Confirm the production domain is indexable while staging or preview environments remain excluded.
Monitor after launch
Inspect important URLs in Search Console, watch indexing and crawl errors, verify redirects, compare organic landing pages, and test enquiries directly. Short-term ranking movement can occur after a migration; investigate material losses by query and page rather than making broad changes immediately.
Keep a dated launch record so later performance changes can be interpreted against deployments, campaigns, seasonality, and search updates.
Related questions
Will a website rebuild hurt SEO?
It can if valuable content, URLs, internal links, or technical signals are lost. A planned migration with redirects and monitoring reduces that risk, but rankings are never guaranteed.
Should the old website stay online during the rebuild?
Usually the existing production site stays live while the replacement is developed in a protected preview environment. The final switch should be planned with domain, redirect, form, and analytics checks.