Skip to main content
Website Planning10 min read

What to Prepare Before a Website Redesign: Scope, URLs, Integrations & Approvals

A practical, non-technical checklist for business owners to avoid budget overruns, preserve SEO rankings, and launch on time.

Published Updated Editorial policy ↗
REDESIGN PLANNING

Treat a redesign as a controlled migration.

A website redesign changes more than the visual layer. It can alter URLs, content, forms, analytics, integrations, hosting, and the path a visitor takes from a search result to an enquiry.

The safest plan connects each design decision to a business goal and gives every important part of the current site an explicit destination. That makes scope, approvals, testing, and launch responsibilities visible before production starts.

Choose one person who can approve scope, content, and launch decisions. Record who owns technical access, who reviews each page, and who can authorize a rollback.
CURRENT-STATE BASELINE

Record what works before changing it.

Start with the actions the website must support: calls, bookings, qualified enquiries, applications, purchases, or access to essential information. For each action, record the current page, form, destination system, responsible person, and how success is measured.

01 / GOALS

Business priorities

Name the services, audiences, regions, and conversion paths the redesigned site must make easier to understand.

02 / SEARCH

Organic baseline

Export important landing pages, queries, clicks, impressions, and index coverage from Search Console before URLs or content change.

03 / ENQUIRIES

Conversion baseline

Test form delivery, booking flows, phone links, and CRM records so the team knows what a successful handoff looks like.

04 / OWNERSHIP

Access and authority

Confirm control of the domain, DNS, hosting, CMS, analytics, email, repositories, and third-party accounts.

SITE INVENTORY

Give every existing page a decision.

Create an inventory of indexable URLs, navigation pages, campaign landing pages, files, images, forms, and embedded tools. Add the page purpose, target audience, traffic or backlink evidence, content owner, and proposed action.

Keep or improve

Retain pages that serve a clear audience or search need. Preserve useful subject coverage while improving structure, clarity, and conversion paths.

Merge, replace, or retire

Combine overlapping pages only when the new destination satisfies the same intent. Retire pages deliberately instead of allowing them to disappear during the build.

Do not judge importance from the navigation alone. An older page may receive valuable search traffic or external links even when it is difficult to find from the homepage.

URL MIGRATION

Map old URLs to their closest useful destination.

Build a redirect sheet with one row for every current URL and columns for its status, new destination, redirect requirement, canonical URL, and test result. When a URL changes permanently, use a server-side permanent redirect to the closest relevant replacement.

Google’s site-move guidance recommends preparing and testing the new site, creating an old-to-new URL map, updating internal signals, testing redirects, and submitting a new sitemap. Its redirect guidance explains that permanent redirects signal the preferred destination.

  • Avoid sending many unrelated old pages to the homepage.
  • Point internal links directly to final destinations instead of through redirect chains.
  • Update canonical tags, navigation, structured data, hreflang where used, and sitemap entries.
  • Keep redirects in place long enough for users, search engines, and external links to adopt the new URLs; Google recommends at least one year.

Where similar pages remain accessible, use a consistent canonical strategy. Google’s canonicalization documentation explains the signals used to identify the representative URL.

CONTENT OWNERSHIP

Plan the content work page by page.

For each page, name the audience, primary question, intended action, source material, writer, reviewer, and final approver. Mark legal, pricing, team, and service claims that require specialist review.

  1. Preserve proven subject coverage

    When a page already earns relevant visits or links, make sure the replacement still answers the same core need.

  2. Gather complete assets

    Collect original images, logos, biographies, downloadable files, usage permissions, and meaningful alternative text.

  3. Review in the actual layout

    Approve copy inside responsive templates so headings, calls to action, tables, and images can be assessed together.

  4. Set a change cutoff

    Agree when launch-critical content is frozen and route later ideas into a post-launch backlog.

INTEGRATION AUDIT

Trace every form and external service end to end.

List CRM connections, booking tools, email platforms, payment providers, maps, chat widgets, consent tools, analytics, advertising pixels, feeds, webhooks, and downloadable resources. For each one, record the account owner, access method, data collected, destination, failure notification, and test contact.

Access checklist

Domain registrar, DNS, hosting, CMS, code repository, analytics properties, tag manager, Search Console, transactional email, and vendor dashboards.

Flow checklist

Submission validation, consent state, spam handling, email delivery, CRM creation, notifications, thank-you page, and reporting event.

Use named accounts and appropriate access levels where possible. Do not pass shared production credentials through a content document or informal message thread.

MEASUREMENT PLAN

Define useful events before implementation.

Decide which actions matter, what event names and parameters describe them, where consent is required, and how the team will validate each event. Keep the plan small enough to maintain and specific enough to support real decisions.

Capture the pre-launch baseline for priority landing pages and conversion paths. After launch, compare like-for-like periods while accounting for seasonality, campaigns, and changes in demand. A redesign alone does not establish the cause of every movement.

ACCEPTANCE TESTING

Test the journeys that carry business risk.

EXPERIENCE

Responsive and accessible

Check keyboard use, focus, contrast, headings, labels, error messages, zoom, touch targets, and representative devices.

CONTENT

Complete and accurate

Review copy, images, downloads, contact details, policies, navigation, internal links, and page titles.

SEARCH

Crawlable and mapped

Verify status codes, redirects, canonicals, metadata, structured data, robots rules, noindex use, and XML sitemaps.

OPERATIONS

Delivered and observable

Submit every form, confirm downstream records and emails, verify consent behavior, and test alerts for failures.

Write acceptance criteria as observable results. “Contact form submission creates the expected CRM record and alerts the assigned owner” is testable; “forms work” is not.

LAUNCH CONTROL

Use a runbook with owners and a rollback path.

Before launch, back up the current site and data, lower DNS time-to-live when appropriate, document the deployment sequence, confirm who can make changes, and agree what conditions would trigger rollback.

  1. Release and verify

    Check the homepage, priority landing pages, old high-value URLs, forms, integrations, analytics, and certificate from the public site.

  2. Submit search signals

    Publish the final sitemap, verify robots and canonical signals, and monitor Search Console for crawl or index issues.

  3. Monitor the operating paths

    Watch error logs, broken links, redirect misses, form delivery, CRM records, page performance, and user feedback.

  4. Resolve from one launch log

    Record each issue, owner, priority, evidence, fix, and verification result so decisions remain visible.

Website redesign preparation checklist.

  • Define business goals, priority audiences, services, and conversion paths.
  • Export current search, analytics, enquiry, and performance baselines.
  • Inventory URLs, files, forms, integrations, and account ownership.
  • Assign every current URL a keep, merge, replace, or retire decision.
  • Prepare a one-to-one redirect map and test final destinations.
  • Name content writers, reviewers, approvers, and delivery dates.
  • Document measurable acceptance criteria for responsive behavior, accessibility, search, forms, and integrations.
  • Agree on backup, release, rollback, monitoring, and post-launch ownership.
COMMON QUESTIONS

Questions to settle before the redesign begins.

Should every old page be moved to the new site?

No. Each old URL should receive an explicit decision. Keep pages that still serve a useful need, merge genuine overlaps, redirect changed URLs to a relevant replacement, and return an appropriate response when no replacement exists.

Can a redesign guarantee that search traffic will not fall?

No. Search performance depends on many systems outside the project’s control. A complete inventory, relevant redirects, preserved content intent, consistent technical signals, and active monitoring reduce avoidable migration risk.

Who should approve the website?

Subject specialists can review their areas, but one accountable decision-maker should resolve conflicts and give final approval. Separate content approval from technical acceptance so neither is assumed.

What should be monitored immediately after launch?

Priority URLs, redirects, crawl and index signals, forms, integration records, email delivery, analytics events, errors, page performance, and feedback from staff who handle enquiries.

RELATED SERVICE

Business Website Redesign & Performance Optimization

We audit what already works, redesign the buying journey, improve performance, and plan the migration so valuable pages and search signals are protected.

Explore service →

Make your next move a clear one.

Tell us where your workflow gets stuck. Let’s explore what could work better.

Start a conversation ↗