Which pages need to survive the redesign? Which addresses should stay? What happens to content you’re combining or removing? Settle those questions before approving new layouts.
A redesign can change which pages customers find, what those pages explain, and whether someone can still reach information they saved or bookmarked. The changes go beyond how the business looks online.
For a Denver business, a practical SEO plan ties those decisions to named people and specific checks.
1. Inventory pages by purpose, not just appearance
Start a shared list of current destinations: service pages, useful articles, project examples, contact and quote pages, and important downloadable resources. Don’t stop at the navigation menus. They aren’t a complete inventory.
For each page, record:
- What a visitor needs to learn or do there.
- Whether the information is accurate and still relevant.
- How people reach it, using available search reports, analytics, internal links, and known external references.
- Whether it contains something worth preserving, such as a useful explanation or approved project evidence.
Separate public informational pages from account, payment, and other utility destinations. Their purposes differ, so don’t automatically give them the same search treatment.
A low-traffic page might still answer an important pre-sale question. Use traffic as one input to the decision. Missing analytics is a reason to record uncertainty, not proof that a page has no value.
2. Give every page a clear decision
Use four working dispositions:
- Keep: The purpose and content remain useful. Preserve the address unless there is a specific reason to change it.
- Improve: Keep the page’s job while correcting or strengthening its content.
- Combine: Bring overlapping material into one destination that genuinely covers the relevant needs.
- Retire: Remove content that no longer has a useful or appropriate role.
Before approving a combined page, identify the details it must retain. “Combine” doesn’t give anyone permission to discard important material.
Carry forward verified business facts in location information. A redesign is not a reason to invent offices or create interchangeable city pages.
Blank page-decision worksheet
Copy this table into a shared document or spreadsheet, with one row per current destination.
- Current URL
- Buyer purpose
- Decision: keep, improve, combine, retire
- Replacement URL, if applicable
- Responsible person
- Expected response; check and evidence
- Recovery action and owner
Write down something a reviewer can check. “Replacement includes the approved service explanation” is more useful than “SEO checked.” Leave unresolved decisions visible so they don’t turn into accidental implementation choices.
For a changed or retired URL, record the expected response, how you’ll check it, and what would trigger recovery. Keep planned and completed checks as separate entries. Attach evidence only after a check has run. Identify the approved pre-change version of the content or mapping and who may restore it. Avoid a blanket database restore that could overwrite new inquiries or orders.
3. Map changed URLs to genuine equivalents
A new design doesn’t automatically require new URLs. When an address does change, document the old destination, its intended replacement, and why the replacement serves the same need.
Where an old URL has a relevant replacement, ask the technical lead to use a server-side permanent redirect, such as HTTP 301 or 308, and test that it reaches the final destination without an unnecessary redirect chain.
Several old pages can redirect to one genuinely consolidated page. If content is removed with no relevant replacement, return an HTTP 404 or 410 response rather than redirecting it to an unrelated homepage. Check that the replacement covers the relevant substance; loading successfully isn’t enough.
Update internal links to point directly to the final destinations. For the separate task of finding and correcting existing link failures, see how to diagnose broken website links.
Check the destination’s content as well as its response. A page can load successfully and still answer the wrong question.
4. Assign responsibilities before implementation
One person may hold several roles. Each responsibility still needs an owner.
| Role | Decision or check to own |
|---|---|
| Business owner | Confirm current offers, priorities, exclusions, and acceptable launch risks. |
| Content lead | Reconcile page decisions, preserve useful material, and obtain factual approval. |
| Developer | Implement routes, redirects, templates, and technical checks; explain recovery limits. |
| SEO reviewer | Review page mapping, search instructions, internal discovery, and the measurement plan. |
| Release owner | Confirm readiness, authorize the agreed changes, and coordinate recovery if needed. |
Agree on access early. The business should know who controls its domain, hosting, website, and search reporting. For Google services, review Google account permissions. Keep passwords out of the planning document.
If outside SEO support is part of the project, spell out who recommends changes, who implements them, and who verifies them. Don’t assume those are the same assignment.
5. Agree on launch checks and recovery limits
Review the redesigned site in protected staging before release. Keep staging protected while separately planning the public site’s access and indexing checks.
The launch checklist should cover:
- Content: Important explanations, approved facts, titles, and images survived the move.
- Routes: Retained URLs work; changed URLs follow the approved mapping; retired pages behave as intended.
- Search controls: Canonical addresses and indexing instructions match the intended public destinations. If the site uses a sitemap, keep it aligned with those destinations; sitemap inclusion does not guarantee crawling or indexing.
- Discovery: Menus, contextual links, article listings, and pagination lead to the right pages.
- Customer actions: Quote and contact paths work, with authorized delivery testing where appropriate.
- Usability: Key pages remain readable and usable on phones and desktops, including keyboard navigation.
A form appearing on screen is not proof that an inquiry reaches the right person. And a successful preview doesn’t prove that the published site has the same settings.
Before release, preserve recoverable copies of the relevant content and configuration. Name the person authorized to stop or reverse the change. Check whether restoration could overwrite new inquiries, orders, or other activity.
Pause for broken critical destinations, unintended indexing restrictions, or failed inquiry paths. Record smaller issues with owners. Don’t hide them behind a general “launch complete” label.
6. Check the released site and keep an issue log
Run the important checks again on the actual released site. Confirm destinations and customer journeys; don’t rely only on the staging checklist.
Keep a short issue log with the affected URL, observation date, evidence, responsible person, next action, and verification result. That way, a missing image won’t be confused with a redirect failure or a reporting delay.
Record the release date and keep a prelaunch baseline where available. Compare consistent reporting periods and page groups. Note other changes, including campaigns, seasonality, and tracking adjustments.
Track search visibility and inquiry quality separately. More visits do not necessarily mean more suitable projects. When data is sparse, a longer observation period may be more useful than an early verdict.
Set dates for technical follow-up and later performance review, but do not promise a ranking-recovery deadline.
Finish the page plan
Use the page inventory to record clear decisions, who is accountable, and evidence that the released site behaves as intended.
For a scoped discussion with CreativeMade, use the quote request or contact route. Share the current site, planned changes, known dependencies, and the decisions you need help resolving.


