Inventory the site before designing the replacement

A redesign can hide a content problem behind a new visual system. The pages may look better while still repeating the same message, burying important details, or sending visitors through an unclear path.

Start with a complete inventory of the pages that matter. Record the URL, title, page purpose, audience, owner, performance context, and recommended next action.

A content audit identifies what exists, how it performs, what it needs to do, and whether it belongs in the redesigned site. Without an audit, teams often recreate outdated pages, lose useful search traffic, and discover missing content after the interface is already built. The audit turns redesign from a visual reset into a controlled content migration.

The process should combine quantitative and qualitative review. Analytics can show traffic, engagement, and conversions, but they cannot determine whether a page is accurate, on-brand, accessible, or strategically necessary. Editorial judgment and stakeholder knowledge remain essential.

Build a complete inventory. Crawl the site and combine the results with CMS exports, analytics, Search Console, downloadable files, forms, and pages that are not linked in navigation. Include URL, title, content type, owner, status, traffic, backlinks, and proposed action.

Evaluate page purpose. State the audience, task, and business goal for each page. If no one can explain why a page exists, decide whether its content should be merged, archived, redirected, or removed. A page should earn its place in the new structure.

Give every page a job

A page should earn its place in the site by helping someone do something. It might introduce a service, answer a buying question, document a process, build trust through work samples, or support an existing client.

When several pages do the same job poorly, merge them. When a key task has no page at all, create one. This is how the content model becomes clearer before the interface is designed.

Identify duplication and gaps. Group pages covering the same topic and compare which one is strongest. At the same time, note questions and journeys the site does not answer. This prevents the redesign from preserving unnecessary repetition while still missing important content.

Plan migration and redirects. Map every retained or removed URL to its future destination. Preserve valuable titles, copy, structured data, and internal links where appropriate. Redirects should lead to the closest relevant page, not automatically to the homepage.

A common mistake is judging only by pageviews. A low-traffic policy, support, or conversion page may still be essential. Evaluate strategic function alongside traffic.

Find duplication before it becomes a migration problem

Duplicate content often appears when a business grows quickly. Old service pages, campaign landing pages, blog posts, and product descriptions can compete with one another or create conflicting information.

An audit makes those overlaps visible. You can decide which page should become the canonical version, which should redirect, and which needs a new angle instead of another rewrite of the same topic.

A common mistake is waiting until design is complete. Content length, hierarchy, and relationships affect component design. Audit findings should shape wireframes and CMS models before high-fidelity work.

A content audit gives the redesign a reliable foundation. Inventory everything, define page jobs, combine performance data with editorial judgment, and plan redirects before launch. The result is a smaller, clearer, and more maintainable site rather than a new interface wrapped around old problems.

Add ownership and review dates to the audit before migration begins. A page without an owner tends to become outdated again, even when the redesign improves it. Assign responsibility for product information, policies, staff biographies, campaign pages, and evergreen articles. Then define a realistic review cycle. Content governance is not separate from UX because stale or contradictory information directly changes whether visitors can trust and complete a task.

Design the future maintenance model too

A content audit should not end at launch. It should define who updates key pages, how new content fits into the site structure, which fields belong in the CMS, and how the team checks for stale information.

That is what keeps a new site from becoming an old site with a newer interface. The goal is a system that remains understandable after the first redesign presentation is over.

A practical way to carry the article forward is to build a complete inventory, evaluate page purpose, identify duplication and gaps, and plan migration and redirects. The evidence should appear in the content inventory, sitemap, interface states, responsive behavior, accessibility checks, and complete user journeys.

Before finalizing the decision, check for two risks: judging only by pageviews and waiting until design is complete. A final review should test the experience with real content, small screens, keyboard navigation, slow connections, and the exact actions visitors need to complete.

Continue reading Explore QART.Studio and Plan Your Website Before Figma: Sitemap, Content, and Navigation.