Skip to content
THE STARTING POINT
Redesign when the underlying structure prevents the website from doing its job. Choose targeted updates when the platform and content model work but specific pages, messages, or interactions are weak. Start with evidence before replacing what already performs.
Separate appearance from function
A dated visual style can justify improvement, but it does not identify the highest-priority problem. List broken forms, confusing navigation, missing service details, editing limitations, and performance issues separately. Ask which problems prevent a customer or your team from completing a task.
For a San Jose professional service business, the essential task may be understanding the specialty and requesting a consultation. For a store, it may be finding and purchasing a product. Judge the current website against that task rather than a competitor's animation.
Inventory what should survive
Record important URLs, useful content, existing search traffic, and customer-facing integrations. Keep a copy of the current titles and descriptions. A redesign should not casually discard pages that already answer valuable questions.
Identify which layouts can be improved once and reused. If the same problem appears across every service page, a template update may solve it without replacing the whole site. Conversely, a system your staff cannot maintain may justify deeper work.
Choose a bounded first intervention
Pick one problem with a clear acceptance test. Rewrite an unclear service page, simplify navigation, or repair the inquiry flow. Observe the result before assuming the entire site needs rebuilding.
Do not confuse a short test with proof of a conversion lift. Traffic quality, seasonality, and small samples can affect results. Combine observed behavior with direct customer feedback and operational evidence.
Treat a rebuild as a migration
If URLs change, map old pages to relevant new destinations. Check internal links, metadata, indexability, forms, and mobile layouts. Google's site-move guidance emphasizes planning and monitoring; a visual launch is not the end of the work.
Keep the actual San Jose service information accurate. A redesign is an opportunity to explain whether you work remotely, visit customers, or receive visitors, without creating misleading office claims.
Approve outcomes, not screenshots
Before launch, complete the core journeys on a phone and desktop. Confirm that a real inquiry reaches the right person and that confirmations make sense. Give your team a simple editing handoff.
Use the matrix below to separate a design preference from a structural limitation. Commission the smallest scope that resolves the actual constraints, while preserving content and functions that already help customers.
A diagnostic before a redesign
Select three tasks: find the relevant service, understand its scope, and request contact. Ask an unfamiliar person to attempt them while describing what they expect. Record problems without coaching them through the interface.
If the failures cluster around one confusing page, start there. If navigation and templates consistently block the tasks, a broader redesign may be justified. This exercise does not replace analytics or accessibility review, but it creates concrete evidence that is more useful than simply saying the site feels old.
DECISION FRAMEWORK
Make the comparison clear.
| Consideration | Focus | Action |
|---|---|---|
| Unclear message | Targeted copy update | Test customer understanding |
| Repeated layout issue | Template improvement | Check all affected pages |
| Platform blocks required work | Consider rebuild | Document migration needs |
| Broken forms | Repair immediately | Test delivery end to end |
PUT IT TO WORK
Your working checklist.
Check each item as you prepare. Download the worksheet to add notes, owners, and deadlines. Entries on this page are temporary.
0 of 6 completed
COMMON QUESTIONS
A few details worth clarifying.
Will a redesign automatically improve SEO?
No. It can help or hurt depending on content, implementation, and migration. Preserve useful pages and verify the technical details.
Can we improve one page first?
Yes, when the problem is local to that page and the underlying platform works.
Further reading
Google: Site moves with URL changes ↗External references support platform or policy details. The planning frameworks and hypothetical examples are Adnetix editorial guidance, not market benchmarks.
FROM PLANNING TO EXECUTION
Bring us the problem.
We’ll help define the work.
Explore web design services or learn how we serve San Jose.
Talk about your project ↗