A website redesign goes wrong most often before a designer opens Figma, because nobody wrote down what the old site contains, which pages earn their keep and how the new pages will be organised. The fix is three short documents made in a set order: a content inventory (every page you have, with a verdict on each), a sitemap (the pages you will have, in a hierarchy), and a redirect map (where every old address will send visitors). If you are comparing a web development company in Pune for a rebuild, ask to see this planning stage in their proposal. It usually takes days rather than weeks for a small-business site, and it prevents the expensive surprises: pages that quietly disappear, rankings that drop after launch, and a menu that mirrors your org chart instead of your customers' questions.
This guide is written for the owner or marketing lead of a business with an existing website, roughly 15 to 150 pages, who has decided that the site needs rebuilding or redesigning and wants to brief an agency properly. It walks through each document with a worked example, shows how to decide what to keep, merge, rewrite or retire, and lists the tests to run before launch. The time estimates are our working estimates from small-business projects, not an industry benchmark; treat them as a starting point for your own plan.
Why Planning Content Before Design Saves Money
Design tools reward starting with the look: a home page, a colour palette, a hero image. The trouble is that a layout designed around imaginary content breaks when real content arrives. A neat three-column "Our Services" block looks fine with three services and falls apart when the business actually offers eleven. A menu with five items has no room for the pages that customers use most. A clean, short product page template collides with product descriptions that are really three paragraphs and a table.
Planning content first also changes the quote you receive. A fixed-price proposal written without knowing the page count, the number of templates and the amount of content to migrate is a guess, and either you or the agency absorbs the error later. If you want to know how a rebuild is usually priced and what is typically included, our guide on whether to redesign or rebuild a website explains the difference and why the answer depends on the state of the current site rather than on its age.
There is also a search reason. Google's own guidance on site moves with URL changes says the important work is mapping old URLs to new ones and keeping the redirects in place (Google Search Central). You cannot map what you have not listed. The inventory is the list, and the redirect map is its output.
Step 1: Build a Content Inventory
A content inventory is a spreadsheet with one row per URL on the current site. It sounds dull and it is, but it is the single most useful piece of project paperwork, and it can be built in an afternoon for a small site.
How to collect the URLs
Start from three sources and merge them, because each one misses things the others catch:
- A crawl. A desktop crawler can list every page it can reach by following links from the home page. Free tiers of common crawling tools handle small sites. A crawl finds pages that exist but are not in your sitemap.
- Your XML sitemap. If the site has one at
/sitemap.xml, it lists the pages the CMS believes should be indexed. Pages in the sitemap but not found by the crawl are "orphans": live pages with no internal links pointing to them. - Google Search Console. The Performance report shows which pages received impressions and clicks in the last 16 months, and the Pages report shows which URLs Google has indexed or excluded. Export the pages list. Pages that appear in Search Console but not in your crawl are often old campaign pages or URLs from a previous version of the site.
Merge the three lists, remove duplicates, and you have your row list.
The columns that matter
Resist the urge to add thirty columns. These are enough:
- URL and page title (the visible title, not the title tag).
- Page type: home, service, product, article, contact, legal, other.
- Search impressions and clicks over the last 12 months, from Search Console.
- Inbound links: whether other websites link to this page. Most SEO tools can show a count; for a small site, even a yes or no is useful.
- Last meaningfully updated, if known.
- Owner: the person who can say whether the content is still accurate.
- Verdict: Keep, Merge, Rewrite, Retire. This column is the deliverable.
A worked example
Imagine a Pune interior-design studio with 62 pages. The crawl finds 58, the sitemap lists 51, Search Console shows 7 further URLs from an older theme. After merging there are 65 unique addresses. Sorting by impressions shows that eight pages account for nearly all organic traffic: the home page, three service pages, the "interior designer for 2BHK flats" page, two project pages and the contact page. Nineteen pages have no impressions at all and no inbound links: old offer pages, a "coming soon" page and a set of thin pages that each describe one wardrobe finish in two lines.
This is an illustrative example, not a client case. The point is the shape of the result, which is typical: a small number of pages doing most of the work, a long tail of pages doing nothing, and a handful of pages that Google knows about and the business has forgotten.
Step 2: Decide What to Keep, Merge, Rewrite or Retire
The verdict column is where judgment comes in. Use these rules rather than gut feel.
Keep a page when it answers a real question, is accurate, and either earns traffic or supports a conversion. Keep does not mean "do not touch"; it means the URL and the core content carry over, possibly with a refreshed layout.
Merge pages when several thin pages cover one topic. Those eleven wardrobe-finish pages become one good page titled for the topic, with a section per finish. The old URLs redirect to the new page. Google's guidance on helpful content asks whether a page gives a satisfying answer; one thorough page generally serves a visitor better than eleven fragments (Google Search Central).
Rewrite pages that rank or get traffic but are out of date, vague or badly structured. These are your quickest wins because the page already has visibility. Our article on finding striking-distance keywords in Search Console shows how to find the pages worth rewriting first.
Retire pages that serve no purpose: expired offers, duplicate test pages, staff who left. Retiring does not mean deleting without a trace. If a retired page has inbound links or past traffic, redirect it to the closest relevant page. If nothing relevant exists, a deliberate 404 or 410 is acceptable; the mistake is redirecting everything to the home page, which Google may treat as a soft 404.
Do not retire pages just because they are old
Age alone is not a reason. A service page written three years ago that still ranks and converts is an asset. Retire based on usefulness, traffic and links, not on the date in the footer.
Content gaps
While you are reviewing, note what is missing. If customers phone and ask about pricing, delivery areas, warranty or process, and no page answers those questions, add rows marked "New" to the inventory. These become the additions to the sitemap. A useful rule is that every question your sales team answers more than twice a week deserves a page or a section.
Step 3: Draft the New Sitemap
The sitemap here means the planned structure of the new site, not the XML file for search engines. It is a tree: home page at the top, main sections beneath it, pages beneath those.
Group by what visitors are trying to do
The most common structural mistake is organising a site around how the business is organised: "About", "Divisions", "Group Companies". Visitors organise their thinking around tasks and questions: "Can you do this for me?", "What does it cost?", "Have you done it before?", "How do I contact you?". Navigation that follows those questions is easier to use. Nielsen Norman Group's research on information architecture recommends testing grouping with real users rather than guessing, using methods such as card sorting and tree testing (NN/g on card sorting).
For a service business, a sound first-draft structure often looks like this:
- Home
- Services (one parent page, then one page per service)
- Work or Projects (a listing, then one page per project)
- About (story, team, credentials)
- Resources or Blog
- Contact
Treat this as a starting hypothesis, not a template to copy. A restaurant needs a menu and reservation page near the top; a manufacturer needs product categories and a quote request.
Keep the depth shallow
Aim for every important page to be reachable within three clicks of the home page. Deep nesting hides pages from visitors and weakens the signals that tell search engines the page matters. Our guide to internal linking, breadcrumbs and site architecture covers how to link between pages once the structure exists.
Plan the URL pattern now
Decide URL rules before anyone builds pages: lower case, hyphens between words, no dates in service URLs, short and descriptive. Google recommends simple, readable URLs and consistent structure (Google Search Central: URL structure). Where the existing URL is already clean, keep it. Every URL you keep unchanged is one fewer redirect to maintain.
Mark templates, not just pages
Alongside the tree, list the page templates the design will need: home, service page, project page, article, listing page, contact page, legal page. A typical small-business site needs between six and ten. The number of templates, more than the number of pages, drives design and development effort, because each template must be designed, built, tested on mobile and tested with real content. This is the number to ask your agency about.
Step 4: Write the Redirect Map
The redirect map pairs every old URL that has traffic, links or indexing with the new URL that replaces it. In practice it is two columns in a spreadsheet, and the developer turns it into server rules.
What to include
Include every old URL that is Keep, Merge or Retire-with-replacement from the inventory, plus any URL with inbound links from other sites, because those links carry value that a broken page throws away. Use permanent (301) redirects for permanent moves. Google confirms that server-side permanent redirects are the right way to signal that a page has moved (Google Search Central: redirects).
Redirect to the closest match
Each old URL should go to the most relevant new page, one to one where possible. Avoid chains (A to B to C), which slow pages and waste crawl effort. Where a URL changes twice over the project, point the original directly to the final destination.
Keep redirects for a long time
Google has said that for site moves, redirects should stay in place for at least a year, and longer where practical, because old URLs may keep receiving links and traffic (Google Search Central: site moves). If your agency says redirects will be removed after launch week, ask why.
If you want the longer technical treatment of what to monitor after a move, read how to migrate a website without losing SEO and fixing 404 errors, redirects and broken links.
Step 5: Brief Content for Each New Page
With the sitemap fixed, you can brief content page by page. A page brief is half a page and answers five things:
- Who is this page for, and what question are they asking?
- What should they do next: call, request a quote, book, read more?
- What proof belongs here: photographs, named projects with permission, certifications, reviews?
- Which existing content moves across and who owns the rewrite?
- Which search phrase is this page for, if any, and which other page should not target the same phrase?
The last point matters because two pages competing for the same query dilute each other. The inventory helps here: if two existing pages target the same phrase, one should be merged into the other.
Plan who writes what
Content is the usual cause of launch delays: designs are ready and the copy is not. Assign an owner and a date to each page brief, and decide early whether your agency writes the copy, you write it and they edit it, or you supply bullet points. Be realistic about your team's time. We have seen projects slip by weeks because the one person who knew the answers was also the busiest.
Step 6: Pre-Launch Checks Against the Plan
Before launch, test the new build against the three documents.
- Inventory check: every Keep, Merge and Rewrite row has a live equivalent page.
- Redirect test: take a sample of 30 to 50 old URLs, weighted towards the highest-traffic ones, and confirm each returns a 301 and lands on the intended page. For a larger site, test them all with a crawler in list mode.
- Sitemap check: the XML sitemap lists only live, indexable, canonical URLs, and it is submitted in Search Console.
- Indexing check: the staging site's "noindex" instruction and any password protection are removed on launch day, not before and not after. Our article on keeping a staging site out of Google's index explains the safe sequence.
- Title and description check: every page has a unique title and meta description. See our guide to title tags and meta descriptions.
- Analytics check: conversion tracking fires on the new forms and buttons.
After launch, watch Search Console for crawl errors and for pages dropping out of the index over the first four to eight weeks, and keep the inventory spreadsheet. It becomes the baseline for your next review.
How Long Does This Planning Take?
For a site of roughly 20 to 60 pages, our working estimate is one to two days to build and review the inventory, a day or two to draft the sitemap and templates with the agency, and a day to produce the redirect map. Expect more time if the site has many products, several languages or years of blog content. These are planning days, not build days, and they sit inside the project timeline rather than adding to it.
If an agency proposes to skip this stage, ask who will map the redirects and when. A good answer names a person and a deadline.
Frequently Asked Questions
What is a content inventory for a website?
A spreadsheet that lists every page on your current site with its address, type, traffic, links and a decision to keep, merge, rewrite or retire it. It is used to plan a redesign and to build the redirect map.
Do I need a sitemap before a website redesign?
Yes, a planned page structure is needed before design starts, because layouts and menus depend on how many pages and templates the site will have. This is separate from the XML sitemap file you submit to Google after launch.
How many pages should a small business website have?
There is no correct number. Include a page for each service, a contact page, proof of your work and answers to the questions customers ask repeatedly. Add pages when you have something useful to say, not to reach a target.
Will a redesign hurt my Google rankings?
It can if URLs change without redirects, content is cut carelessly or the site is accidentally blocked from indexing. Careful planning, 301 redirects and post-launch monitoring reduce the risk, but no agency can promise that rankings will not move.
Should I redirect all old pages to the home page?
No. Redirect each old page to the most relevant new page. Mass redirects to the home page lose the relevance of the original page and may be treated as soft 404 errors by Google.
Planning a Rebuild?
If you are planning a redesign and want the inventory, sitemap and redirect map done properly before any design begins, Govindani Infotech, a website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009, includes this planning stage in website projects. See our website creation services and SEO services, then contact us or call 092019 58274.
Sources:
- Google Search Central: Site moves with URL changes
- Google Search Central: Redirects and Google Search
- Google Search Central: URL structure best practices
- Google Search Central: Creating helpful, reliable, people-first content
- Nielsen Norman Group: Card sorting
About the author: written by the Govindani Infotech web development team in Pune.