How to Prepare Website Content Before a Redesign
A website redesign moves faster when the content is organized before design and development begin. This checklist helps a business decide what to keep, improve, combine, or remove while protecting the pages and systems that already matter.
A website redesign moves faster when the content is organized before design and development begin. This checklist helps a business decide what to keep, improve, combine, or remove while protecting the pages and systems that already matter.
Start with a complete content inventory
List the material that exists today before deciding what the new website needs. Include more than visible pages:
- Core pages: home, services, about, contact, location, and campaign pages
- Supporting content: articles, FAQs, case studies, testimonials, and downloadable files
- Media: logos, photographs, videos, icons, PDFs, and other brand assets
- Page details: URLs, titles, descriptions, headings, forms, and calls to action
- Connected systems: analytics, booking, payments, email, CRM, maps, and review links
A spreadsheet is usually enough. Give each item an owner, current URL, intended action, and approval status.
Decide what happens to every useful page
For each existing URL, choose a clear next step:
- Keep: the page is accurate and still serves a useful purpose
- Improve: the topic is useful, but the message, structure, or next step needs work
- Combine: multiple pages cover the same intent and would be clearer as one stronger page
- Remove: the page is outdated, unsupported, or no longer useful
Do not remove or rename an important URL without checking whether it receives search traffic, has external links, appears in printed material, or is used by a QR code. When a URL changes, record the correct redirect destination.
Clarify the audience and next action
Every page should answer three practical questions:
- Who is this page for?
- What should that person understand?
- What should they do next?
This keeps content decisions tied to the visitor journey instead of filling a template. A service page may lead to a consultation request, while a resource may lead to another guide or a relevant service overview.
Assign content ownership early
Name the person responsible for drafting, reviewing, and approving each page. One person may hold several roles on a small project, but the responsibilities should still be clear.
| Responsibility | Practical question |
|---|---|
| Content owner | Who confirms that the information is accurate? |
| Writer or editor | Who turns the information into clear website copy? |
| Approver | Who gives final approval before launch? |
| Technical owner | Who verifies forms, tracking, integrations, and redirects? |
Approval dates are useful because a redesign can stall when feedback arrives after layouts and development are already complete.
Prepare content for the new page structure
Organize copy around meaningful headings rather than long blocks of text. For each planned page, prepare:
- A clear page title and primary heading
- A short opening that explains the page's purpose
- Supporting sections in a logical order
- Specific calls to action
- Approved images with useful alternative text
- A proposed title and description for search and sharing
- Links to related pages that will exist at launch
Avoid linking to placeholder pages. Internal links should point to real canonical URLs, such as the website redesign service or the guide to choosing between a redesign and a rebuild.
Protect technical and operational dependencies
Content work affects more than copy. Review the systems attached to each page and record what must continue working:
- Form destinations and notification recipients
- Analytics and conversion events
- Booking, payment, CRM, and email integrations
- Structured data that matches visible page content
- Download links and media files
- QR codes, campaign links, and shared URLs
Test these items in staging before launch. A page should not be considered complete simply because its text and design look finished.
Set a review and migration sequence
A practical sequence is:
- Inventory the current site and connected assets.
- Decide what to keep, improve, combine, or remove.
- Confirm the new sitemap and page responsibilities.
- Draft and review content before final page assembly.
- Add approved content to staging.
- Test links, forms, tracking, mobile layouts, and accessibility basics.
- Confirm redirects and retained URLs before launch.
- Review the live site after deployment.
Use a simple readiness checklist
Before development depends on a page, confirm that it has:
- An approved purpose and audience
- A responsible owner and approver
- Final or clearly labeled draft copy
- Approved images and files
- Working internal-link destinations
- Documented form and integration requirements
- A keep, change, or redirect decision for the old URL
Preparing content this way reduces avoidable rework and gives the redesign a clearer foundation. If the larger project direction is still uncertain, start with Website Redesign vs. Rebuild: How to Choose before finalizing the content plan.