In short: before a redesign, prepare five things. Describe the problem as a customer task. Gather the product information. List the pages that already matter, so URLs and search visits are not lost. Put your brand material in one place. Agree the practical boundaries: platform, access, approvals and what can wait. You do not need a perfect brief: send your current site, the main problem, any evidence and your deadline.

A useful ecommerce website redesign starts with the things your customers need to understand. The design brief should explain what you sell, who buys it and where the current store makes their decision difficult.

For Skin Boutique Online, my role spans website design and optimisation, SEO, social content and ad creatives. That gives me a reason to look beyond the homepage: a product page, a search result and an ad all belong to the same buying journey.

Here is what I would ask you to prepare before we redesign a store.

Describe the problem in terms of a customer task

“The site feels dated” is a starting point. “Customers struggle to choose between these products” is a more useful brief. Other concrete problems might be a confusing mobile navigation, missing delivery information or an ad that sends people to a page about a different offer.

Choose one main goal for the first scope. It might be easier product discovery, a clearer product page or a better home for a new range. If you have analytics, support questions or customer feedback, bring them. They help distinguish a known problem from a design assumption.

Gather the product information

A designer needs more than product names and packshots. Prepare the facts a customer uses to make a choice:

  • Product descriptions, sizes, variants and current prices.
  • Images you have permission to use, including available detail shots.
  • Usage instructions and verified product claims.
  • Delivery, returns and availability information.
  • Common questions and the differences between similar products.

For skincare, suitability and usage need particular care. Provide approved wording and sources for claims. Design should make that information understandable without inventing advice or benefits. The same preparation applies to web design and content for skincare brands.

List the pages that already matter

Before changing URLs, make an inventory of product, category and editorial pages. Identify pages receiving search visits, campaign traffic or links from elsewhere. Search Console and your analytics can help with that inventory.

Some pages will stay, some will be rewritten and some may need redirects. Decide that deliberately. A redesign is a good moment to improve page titles, internal links and descriptions, but it should also preserve useful existing paths into the store.

Put your brand material in one place

Gather the logo files, typefaces, colours, photography and examples of current ads or social posts. Include examples you want to keep and ones that no longer feel right.

I want to see what happens before someone reaches the website. If an ad shows a particular product, offer and visual style, the destination page should continue that story. Looking at both together often reveals a problem that a homepage-only review would miss.

Agree the practical boundaries

Include your current platform, integrations, who can grant access and who approves the work. Separate launch requirements from later improvements. If a deadline depends on a campaign, say so at the start.

Also decide what happens after delivery: who changes products, maintains content and checks new pages? Those responsibilities affect both the build and any ongoing scope.

Make a working checklist with evidence, not only ticks

A tick is useful only when someone can say what was checked. For each item below, record an owner, the relevant page or document, the result and any unresolved issue. The evidence can be a tested URL, a screenshot of a state, an approved content file or a short note describing a completed task. Avoid turning the checklist into a document that says everything is done without showing what that means.

Use three statuses: ready, blocked and not applicable, with a reason for the last two. An item should not be marked ready because the team hopes it will work at launch. Where information is missing, identify who can supply it and which decision depends on it. The aim is a manageable release decision, not a perfect-looking spreadsheet.

StageOutput to reviewWho needs to understand it
DiscoveryCustomer tasks and known problemsOwner, designer and developer
InventoryExisting pages, content and integrationsContent and technical owners
PlanningURL decisions, scope and release dependenciesPerson approving the release
PreviewReal content and verified task outcomesOwner and reviewers
ReleaseCritical checks and a practical rollback planPerson publishing and responding
Follow-upIssues, observations and measurement limitsTeam maintaining the store

The roles can belong to one person in a small business. Naming them still helps. Someone has to approve a product claim, someone has to verify a redirect and someone has to decide whether a defect blocks publication. Do not leave those decisions implicit merely because the team is small.

Before design: confirm what must be preserved

1. Save a baseline of the important journeys

Choose a few tasks that matter to the business and record how the current site handles them. Include finding a product, comparing options, understanding delivery and completing the relevant purchase or enquiry flow. Record difficulties without declaring every old feature a mistake. The current store may already solve some tasks well, and the redesign should preserve that useful work.

  • Identify the intended customer and the reason for their visit.
  • Record representative desktop and mobile pages, including a difficult product.
  • Note where the person hesitates and what information is missing.
  • Separate observed problems from suggestions based only on personal preference.

Keep the baseline dated. Stock, campaigns and content change, so a screenshot without context can later misrepresent the starting point. If the available evidence is a small set of observations, label it that way rather than calling it a measured conversion problem.

2. Export or assemble the current URL inventory

Include products, collections, articles, service pages, information pages and useful campaign destinations. Compare the sitemap, a crawl and available search or analytics reports rather than assuming any one list is complete. Old links can still bring people even when the page is absent from the main menu.

  • Give each important URL a page type and a current purpose.
  • Note relevant traffic, links or business use where evidence is available.
  • Identify redirects and broken pages that already exist before the project.
  • Assign a content decision: keep, improve, combine or retire.

Keep the original inventory alongside the proposed version. It provides a reference for checking what changed and prevents an existing defect being attributed to the redesign without evidence. Do not include credentials or customer personal information in this ordinary project register.

3. Check product and content readiness

Pick representative complete examples before scaling the design. A product with several variants, a long name and detailed instructions will reveal gaps that a neat placeholder cannot. Decide who approves facts, claims, instructions and policy wording. A designer should not infer an approved benefit from an old image.

  • Prepare the exact content needed by each changed template.
  • Mark missing information and identify the person responsible for supplying it.
  • Confirm the right to use images, fonts, footage and other assets.
  • Keep approved source text separate from exploratory draft copy.

If the new structure uses additional fields, test a complete entry before filling the entire catalogue. Ask the person who will maintain it to perform the entry. An elegant content model is not ready if ordinary users cannot understand where the required information goes.

Before development: make the change plan reviewable

4. Make the old-to-new URL map

For every URL that changes or disappears, decide the closest relevant outcome. Some keep their address and receive better content. Some merge into a stronger equivalent. Others have no useful replacement. Do not automatically send every retired page to the homepage just to avoid seeing an error.

Google’s site-move guidance recommends preparing a URL mapping when addresses change. A visual redesign with stable URLs does not need to become a domain migration. Apply the mapping discipline to the changes you are actually making.

  • Record the old address, intended outcome and exact new destination.
  • Explain why the new destination matches the old visitor’s likely task.
  • Avoid unnecessary handle changes made only for a tidier-looking launch.
  • Have the content owner review the map before technical implementation.

The map is a decision document before it is a redirect file. Someone needs to judge relevance, not merely transform strings. Keep a separate note for changes that require a platform-specific solution rather than an ordinary redirect.

5. Inventory integrations and shared settings

List the tools that affect what customers see or what happens after an action. Examples can include reviews, search, product options, subscriptions where used, forms, email capture, analytics and operational integrations. The relevant list depends on the store; do not install a new tool just to fill a checklist category.

  • Record each integration’s purpose, owner and affected pages or tasks.
  • Identify theme-dependent elements and settings shared with the live business.
  • Note duplicate-looking tools that need investigation before any removal.
  • Define which changes can happen in preview and which need release coordination.

A draft theme does not isolate all product, navigation or application settings. Ask the developer to explain the boundaries. That prevents a well-intended preview edit from changing live behaviour before the owner has reviewed it.

6. Agree scope, approval and content ownership

Name the changed templates, the supplied content, the custom components and the parts that stay outside this release. Distinguish content migration from rewriting. Copying current descriptions is not the same task as researching and writing new ones. Make image production and product entry explicit where they are required.

  • Choose one person to consolidate feedback and confirm final decisions.
  • Identify who approves product claims and operational policies.
  • State which issues block launch and which can be scheduled afterwards.
  • Agree how a new request changes effort, sequence or the release date.

Write acceptance tasks in plain language. “The correct size reaches the cart” is easier to verify than “optimised purchase experience”. Include maintenance tasks such as editing a section or adding a product, because the owner needs a usable system after the launch presentation ends.

During the build: protect discovery and meaning

7. Compare page content and metadata

Review the actual preview output rather than only the product records in the admin. A different theme or template can change the visible heading, omit a content section or output different metadata while the underlying record looks unchanged. Check representative pages from each affected type.

  • Compare page titles, main headings and useful body content with the plan.
  • Confirm descriptions remain accurate and specific to the relevant page.
  • Check canonical targets, robots directives and intended public access.
  • Review relevant structured data against the information visible to customers.

Do not treat a title-length rule or a keyword count as the whole SEO review. The page should still answer the intended question. Record deliberate content removals so they can be assessed, rather than discovering later that useful explanations were dropped to make the layout shorter.

Follow the routes from the homepage and menus to the important categories and products. Test links from articles and guides too. A product that appears only after typing its name into the store’s search box has a different discovery path from one connected through the catalogue.

  • Use labels that describe the destination in the customer’s language.
  • Confirm important links reach the intended current page without unnecessary hops.
  • Check later collection pages and any load-more implementation.
  • Test search results and a no-result case with realistic customer queries.

Google’s ecommerce structure guidance explains the role of linked navigation in finding products. Keep the practical requirement visible: useful items should be reachable through understandable links. A new menu animation is secondary to having the right route and destination.

9. Verify redirects by visiting the source addresses

Entering a redirect is not sufficient evidence that it works. Visit representative old addresses and inspect the final destination. Check the actual page as well as the response: a technically successful redirect to the wrong product is still an unsuccessful customer journey.

  • Test the important old URLs and the planned replacement pages.
  • Avoid loops and unnecessary chains through several intermediate addresses.
  • Check links that contain relevant market or language paths where applicable.
  • Keep a result and an owner for every unresolved mapping issue.

For Shopify, the redirect documentation describes limitations, including that an active source page is not overridden by an ordinary URL redirect. Consult the current platform guidance and test the relevant case. A generic migration checklist cannot replace knowing what the chosen platform actually supports.

Before publication: test the business tasks

10. Complete the purchase or enquiry route

Use the store’s approved testing process for transactions. Do not improvise a live payment or send an unexpected customer message simply to tick a box. Agree who controls the test, what result is expected and how any test records will be handled.

  • Select representative variants and confirm the correct items in the cart.
  • Change quantities, remove an item and review totals and availability messages.
  • Check relevant discount and delivery conditions through the authorised process.
  • Verify forms, confirmation states and an appropriate failure route.

A company website needs the same discipline for enquiries. Test required fields, useful errors and receipt behaviour where authorised. A beautiful form that silently loses a message is not ready. Keep personal test details out of public screenshots and project reports.

11. Review mobile access, readability and performance

Use a real phone alongside browser tools. Check a narrow viewport, enlarged text, keyboard access and visible focus. Open menus, filters, galleries and forms. The important question is whether a person can understand and complete the task, not whether every screenshot matches one ideal screen width.

  • Keep important labels and controls available when text is increased.
  • Check image crops, long names and content that wraps unexpectedly.
  • Review layout movement and realistic loading with the actual media and apps.
  • Check essential content without relying on decorative motion or autoplay.

Performance work should preserve necessary functionality. A single lab score does not describe every user’s experience, and a fast empty theme demo does not validate a finished store. Record the tested pages and conditions so the comparison has meaning.

12. Rehearse ordinary maintenance

Have the receiving person add or edit a representative product, replace a campaign image and update a reusable section. This is a usability test for the editing system. Watch where they hesitate instead of assuming an explanation in the handover will solve every confusing control.

  • Explain which settings affect one item and which affect a shared template.
  • Check optional empty fields and a realistic long-content example.
  • Identify custom work and the relevant app or theme dependencies.
  • Agree who checks future updates and who handles later requests.

Shopify’s theme updating guidance notes the need to review app compatibility and code customisations when updating. Include an understandable update process in the handover rather than treating launch as the end of technical responsibility.

Release day: keep the decision small and explicit

13. Confirm readiness and the release window

Gather the unresolved issues and classify them by actual effect. A broken buying control is different from a photograph scheduled for improvement. Name who approves publication, who performs immediate checks and who is available to respond. Avoid a release window that leaves nobody able to investigate a problem.

  • Freeze unrelated changes while the release is being checked.
  • Confirm the exact version or theme that has passed review.
  • Make the approved URL and integration changes in the agreed sequence.
  • Record the release time and all changes outside the theme itself.

A readiness decision should be concrete enough to revisit. “Everything looks fine” is not a useful record if a problem appears later. Keep the critical checks short enough to repeat on the live site immediately after publication.

14. Keep a rollback plan for the actual scope

Save a known working reference and explain how to restore it. Returning to an old theme does not automatically undo product edits, redirects, navigation changes or app settings. The plan needs to include those shared parts where the release changed them.

  • Identify the condition that would justify stopping or reversing the release.
  • Name the person authorised to make that decision.
  • Record which changes require a separate restoration step.
  • Confirm how customers and the team can continue if a problem is found.

Do not practise destructive recovery against the live store without authorisation. Review the procedure safely and make the necessary references available. The purpose is a calm response to a real problem, not an invitation to reverse everything for a minor visual issue.

15. Repeat critical checks on the public site

After publication, visit the real public URLs rather than relying only on the preview. Confirm the intended pages are accessible and the important routes work. Check that temporary restrictions intended for development did not become public robots rules or access barriers.

  • Reach the main collections, products and supporting information pages.
  • Select an option and verify the corresponding cart behaviour.
  • Open important old URLs and confirm their intended destinations.
  • Verify authorised form and measurement checks without creating unintended sends.

Log a defect with the URL, action, expected result and actual result. That is more actionable than a message saying the site is broken. Prioritise customer-blocking failures and avoid changing unrelated details while diagnosing them.

After launch: interpret what changed carefully

The first review is functional: does the published site behave as approved? The next is about the original problem: can customers make the intended decision more easily? Those questions need different evidence. Do not wait for a long analytics report to fix a broken control, and do not claim a sales improvement from a handful of successful tests.

Compare relevant landing pages and buying steps where measurement is available. Keep the underlying counts beside rates. Record campaigns, pricing, availability, tracking changes and seasonal events that could alter the comparison. Before-and-after movement does not isolate the effect of a redesign. A small store may need more time and a more cautious conclusion.

Maintain an issue log with a next step. A missing instruction belongs to the content owner, a lost option state to development, and an unclear category may need both. The log should help the next useful change rather than become an unprioritised list of every preference anyone mentions.

A worked hypothetical release file

Imagine a fictional store combining two similar collections while introducing a clearer product template. This example describes the documents I would expect, not a real client result. The release file would contain the old collection addresses, the chosen surviving destination, the reason it serves both groups of visitors and a check of the products it includes.

The product template would have approved content, a difficult variant example and an empty optional-field example. The integration list would identify the review and form tools affected by the theme. The acceptance record would show the selected product arriving correctly in the cart and the old collection address reaching the intended useful page.

The rollback note would separate the theme change from the collection and redirect changes. The follow-up note would record the release date, which pages were affected and what else changed in the business. That is a reviewable project record. It is more useful than a folder containing only attractive before-and-after images and an unsupported claim that the new design will increase sales.

Questions before starting the checklist

Do I need everything ready before contacting a designer?

No. Bring the current site, the main problem and whatever evidence exists. The checklist helps identify missing inputs and responsibilities; it is not an entry exam. A focused discovery stage can produce the inventory and a sensible scope before the full design begins.

Does every redesign require new URLs?

No. Keep useful stable addresses when the content and purpose remain the same. URL changes add planning and verification. Make them because the information structure genuinely needs to change, not because a new visual design feels as if it should have new handles too.

Can a deadline be agreed before content is ready?

A provisional plan can be discussed, but dependencies should remain visible. If approved claims, images or product data are missing, say which stages depend on them. An optimistic date is not a substitute for assigning responsibility and deciding what can sensibly be released first.

Adapt the release checklist to a company website

A company website replaces the cart with a different set of important actions. A prospective customer might need to understand a service, check relevant evidence, identify who is behind the business and send a useful enquiry. Map that route with the same care as a purchase. A service page that looks polished but does not explain what is included can still prevent a qualified enquiry.

Start the inventory with services, projects, articles, contact pages and useful campaign destinations. Record which pages answer which questions. An old service address may receive links from proposals or partner websites even if it has little recent search traffic. Before merging it, decide where a visitor with that original expectation should go. Do not move every retired service to an unrelated contact form merely because the form is the final commercial action.

The content readiness check should include the actual scope, relevant evidence, approved company information and an understandable next step. Keep contributions and results distinct. A case study can explain what was designed or built without inventing a commercial outcome. If there is no approved testimonial, do not create one to fill the space in the layout. Mark the missing evidence and use accurate project information instead.

For forms, agree what information is genuinely needed to begin a conversation. Explain required fields, privacy information and what happens after submission. Test validation, the confirmation and the approved receipt path. A contact action may also involve a booking tool or a direct email route; include those actual dependencies in the integration list and check their destinations.

Search protection remains relevant. Compare the service titles, descriptive content, project links and intended indexable pages. A new visual template should not silently remove the explanation that made the old page useful. If the service itself changed, reflect that honestly and make the URL decision deliberately. The objective is clarity for the prospective client, not preserving outdated promises just because a page once received visits.

The post-launch review can combine relevant landing behaviour, completed enquiry events where properly measured and the quality of questions received. Avoid collecting or publishing personal enquiry details in the audit. A small number of contacts does not support a sweeping claim about a design’s effect. The useful question is whether the intended person can understand the service and take the right next step with fewer unresolved questions.

What if a page has no meaningful replacement?

Record that decision instead of inventing an irrelevant destination. Explain the situation clearly to someone arriving on an old link and offer reasonable navigation where appropriate. The exact technical response should follow the platform and the intended content outcome. A redirect exists to help someone reach the relevant replacement; it is not a universal method for hiding every retired page from the release checklist.

What should the review evidence leave out?

Keep the evidence focused on the task. A screenshot can show a correct cart state without exposing a customer’s address, order history or payment details. A form test can record a received result without copying a real enquiry into a public report. Use appropriate test data and the agreed access process. Where a reviewer needs sensitive operational information, provide it through the authorised channel rather than placing it in the ordinary redesign folder.

The project record should help another person understand what was verified and what remains uncertain. It does not need every raw export or every piece of data available in the account. Keep useful summaries, representative examples and references to the approved source. This makes the handover easier to use as well as easier to maintain.

The same preparation helps a company website

For Growth Frontier, I designed and built the company website from scratch and handled indexing and SEO. A B2B site needs its own version of the same inputs: a clear service, an audience, evidence and a useful next action. Product specifications become service details; the purchase path becomes the path to an inquiry.

You do not need a perfect brief. Send your current site, the main problem, any available evidence and your deadline. We can define the rest through the web design and SEO scope. If the store is on Shopify, how a Shopify redesign works covers the same preparation step by step.