Web systems
What to check before redesigning a business website
A redesign is most valuable when it solves a business problem—not when it simply replaces one visual style with another.
A practical website-readiness review covering positioning, content, customer journeys, measurement, accessibility, and technical ownership.
Start with the decision the site must improve
Write down the customer decision the website should make easier. For a service company, that may be deciding whether the company understands the job, serves the right market, and is credible enough to contact. For a product company, it may be understanding fit, value, and the next step. This becomes the standard for judging the sitemap, copy, proof, and calls to action.
Separate business readiness from design readiness
Business readiness means the audience, offers, markets, priorities, growth plans, and internal owners are reasonably clear. Design readiness means the content, references, photography, brand materials, integrations, and approval process are available. A project can begin before everything is finished, but the missing pieces should be visible so they can be planned instead of discovered late.
Map the customer path, not only the page list
A page list says what exists. A customer path explains why someone arrives, what they need to understand, what doubt must be resolved, and what action should follow. Review paths for first-time visitors, returning prospects, current customers, job candidates, and any other audience that materially affects the business.
Preserve what already works
Before changing URLs or copy, review search queries, indexed pages, referring links, conversions, form quality, and the pages sales teams actually use. A redesign should protect valuable equity through deliberate redirects, content migration, and measurement continuity. Visual improvement is not worth avoidable loss of discovery or operational utility.
Define ownership after launch
Decide who can change content, who reviews inquiries, who owns technical access, and how the company will evaluate the site. A website is healthier when domain, hosting, analytics, source files, and credentials have clear owners. Launch is the beginning of evidence, not the end of the project.
Use a focused first-look, then verify deeply
Automated checks can reveal missing titles, descriptions, mobile settings, canonical links, structured data, and obvious accessibility gaps. They cannot replace customer research, manual accessibility testing, performance profiling, analytics review, or a full crawl. Use quick signals to prioritize the next responsible review.
Turn your context into a practical starting point.
Build a focused project brief on this device, then carry it into a conversation only when you choose.
Build a project brief →