Website Redesign Content Inventory Template

Outcome Summary

• Get a practical content inventory template you can use to decide what to keep, rewrite, remove, merge, or add before a redesign.
• Map every page to a clear job in the buyer journey so the new design supports conversion paths (not just aesthetics).
• Reduce scope creep by turning “we should update content” into a trackable, owner-assigned plan.

What Revamp Actually Does (Truth Block)

✅ does

• Generates an AI website redesign demo when you paste in a website URL.
• Produces a shareable live preview link you can use to align stakeholders on a direction.
• Accepts optional design preferences to steer the redesign output.
• Supports code export on paid plans.

❌ does not

• Guarantee performance, SEO, or conversion outcomes from the generated redesign.
• Replace discovery, content strategy, or stakeholder sign-off for what the site should say.
• Always work well for sites with complex functionality or specialized components (output can require refinement).

The Core Problem

• Redesigns fail quietly when pages “look modern” but the content doesn’t match what buyers need at each step.
• Teams redo work because nobody agreed on what content is in scope (and what gets cut).
• Important pages get missed: legacy landing pages, high-intent docs, PDFs, old campaign URLs, or support content.
• Writers can’t write efficiently because page purpose, primary CTA, and ownership aren’t defined.
• Stakeholders argue about opinions because there’s no shared system for deciding: keep vs rewrite vs remove.

Framework

Step A — Define the decision rules (before you list pages)

Write down a simple rule set you’ll apply consistently:

• What counts as “must keep” (legal, revenue-critical, customer help, top-of-funnel entry points)
• What counts as “rewrite” (right topic, wrong structure/message)
• What gets “merge” (duplicate topics split across pages)
• What gets “remove” (no clear audience intent, outdated, off-strategy)
• What you will “add” (missing pages needed for the buyer journey)

Step B — Build the inventory (the template)

Copy/paste this table into a doc, spreadsheet, or project tool.

URL / Asset	Page type	Audience intent	Buyer journey stage	Primary CTA	Key message (current)	Proof / credibility	Owner	Action	Notes / dependencies
								Keep / Rewrite / Merge / Remove / Add

Tips for filling it out (fast, not perfect):

• Treat PDFs, slide decks, and downloadable assets as first-class items.
• If a page has no clear “Audience intent” or “Primary CTA,” that’s a content strategy flag.

Step C — Map each item to a single job in the journey

Use a journey label that matches how your customers actually decide. Common labels:

• Problem exploration
• Solution comparison
• “Why us” validation
• Purchase / contact
• Onboarding / success

If a page tries to do multiple jobs, it usually becomes a candidate for Rewrite or Split (add a new page).

Step D — Add a “layout requirement” note (so design supports content)

For each page, write a short note in Notes / dependencies like:

• “Needs a comparison section, but avoid naming competitors”
• “Needs a sticky primary CTA”
• “Needs space for screenshots / gallery”
• “Needs a trust section: testimonials, logos, security notes”

This is where Revamp can help: generate a redesign demo for a key page type (like the homepage or a landing page) and use the live preview link to align on layout direction before writers finalize copy.

• Revamp home: revamp.dev
• Revamp app: app.revamp.dev

Step E — Turn actions into a content plan writers can execute

For each item marked Rewrite, add a lightweight brief:

• Who is it for?
• What question must it answer?
• What is the primary CTA?
• What proof must be included?
• What should be removed (fluff, jargon, outdated claims)?

Step F — Do a “merge/retire safety check” (before you delete anything)

Before you merge or remove pages:

• Confirm the page isn’t used in active campaigns, sales sequences, or help docs.
• Decide what the replacement page is (or what section absorbs the content).
• Add a redirect note (even if redirects are implemented later).

Step G — Review with stakeholders using decisions, not drafts

Run a review meeting that only approves:

• Action per item (Keep / Rewrite / Merge / Remove / Add)
• Owner per item
• Any hard requirements (legal approvals, brand constraints, claims that must be sourced)

Avoid wordsmithing in this meeting. That happens after the inventory decisions are locked.

Use Cases

Agency pitching a redesign while keeping scope controlled

• Scenario: A client asks for a redesign, but content is scattered and stakeholders disagree.
• Recommended approach: Build the inventory, mark actions, then generate a Revamp redesign demo for the homepage and a representative landing page to show layout direction while content owners finalize rewrites.
• Common mistake: Showing polished mockups before agreeing what content is being kept or cut—this creates rework and scope tension.

Founder modernizing a marketing site without losing conversions

• Scenario: The site looks outdated, but some pages are quietly driving signups.
• Recommended approach: Inventory everything, map high-intent pages to “purchase/contact” jobs, and add layout requirements so the redesign preserves the conversion path.
• Common mistake: Treating redesign as a visual refresh and discovering late that core pages lack clear CTAs.

Team cleaning up legacy pages after years of launches

• Scenario: Multiple product announcements created duplicates and outdated promises.
• Recommended approach: Use “Merge” decisions to consolidate topics into canonical pages and mark old pages for retirement with replacement targets.
• Common mistake: Deleting pages without deciding where that intent should land in the new structure.

Decision Checklist

• Can you state the primary conversion path you want the redesign to support (in plain language)?
• Does every page in the inventory have a clear audience intent and a single “job” in the buyer journey?
• Have you assigned an owner for each rewrite (and a reviewer who can actually approve it)?
• Are “Keep” pages truly current (claims, product screenshots, positioning), or are they just familiar?
• Do you have a plan for merges (what becomes canonical, what content moves, what gets retired)?
• Have you noted layout requirements so design and content don’t fight each other?
• Did you include non-page assets (PDFs, decks, downloadable guides) that affect the buyer journey?

Constraints

• Some content lives outside your CMS (docs platforms, support tools, embedded widgets), which complicates inventory and ownership.
• Dynamic or personalized pages can’t be evaluated like static pages; you may need representative variants.
• Stakeholders may disagree on success criteria; without decision rules, “inventory” turns into endless debate.
• Old pages may still be referenced externally (partners, communities, past PR), so retirement needs a plan.
• Regulated industries often require extra review steps and careful handling of claims.

Practical Example (Illustrative)

Scenario: You’re redesigning a SaaS homepage plus key landing pages.

A simple decision path you can apply to each page:

• If the page has high-intent traffic or is used in sales → Keep the URL, then decide Rewrite vs Light refresh.
• If the topic matters but you have multiple near-duplicates → pick one canonical page → Merge the rest into it.
• If the page has no clear audience intent and no place in the journey → Remove (but first note a replacement target if needed).
• If you notice a journey gap (e.g., no page that answers “Why switch?”) → Add a page and write a brief.

Where Revamp fits in this workflow:

• Generate a redesign demo for the homepage layout direction.
• Share the live preview link internally to align stakeholders on structure.
• Use your inventory “layout requirement” notes to guide what content blocks must exist in the redesigned page.

FAQ

What’s the difference between a content inventory and a content audit?

A content inventory is the list (what exists, where it lives, who owns it, what action it gets). An audit is the evaluation (quality, message fit, journey fit, proof, and what needs to change). Most redesigns need both, but inventory comes first.

Should I inventory blog posts for a redesign?

Yes—at least at a high level. Blogs often act as entry points to the buyer journey, and outdated posts can contradict new positioning. If you can’t deeply audit every post, at minimum tag posts by topic, intent, and whether they should be refreshed, merged, or retired.

How do I handle duplicate pages created by campaigns?

Choose a canonical page for the intent, merge the best content into it, and mark the rest for retirement. Note dependencies (ad destinations, email links, sales collateral) so nothing breaks.

Who should own the content inventory?

Typically a content strategist, marketing lead, or PMM owns the decisions, while writers and subject-matter experts own execution. If nobody owns decisions, the inventory becomes a spreadsheet without outcomes.

Does this template cover redirects and SEO?

It supports redirect planning by capturing merge/remove decisions and replacement targets. Implementation details (redirect rules, technical SEO validation) usually live in a separate technical checklist tied to the final IA and URL plan.