A new look can be valuable, but a redesign can also remove rankings, break forms, and hide the information customers use to decide. Treat the project as a business and information-architecture change—not a coat of paint.
1–3. Define why the site must change
- What is failing? Name the problem: weak leads, confusing navigation, slow mobile pages, outdated services, or hard editing.
- What must improve? Choose measurable outcomes such as more qualified forms or faster load time.
- What already works? Protect top pages, useful copy, backlinks, and conversion paths.
4–6. Clarify the audience and message
- Who is the primary visitor? Lead with the customer you serve most often.
- What do they need to know first? Service, fit, proof, process, and next step usually matter more than company history.
- What questions block action? Address timing, price approach, service area, and what happens after contact.
7–9. Protect search visibility
- Which URLs receive traffic or links? Keep them where possible.
- What needs a redirect? Map every retired URL to the closest useful replacement.
- Can search engines understand the structure? Use descriptive URLs, headings, internal links, and indexable content.
Google’s SEO Starter Guide recommends logical organization, descriptive URLs, helpful content, and relevant internal links.
10–12. Design the mobile decision path
- Can someone understand the offer without zooming?
- Are tap targets comfortable and forms easy to complete?
- Do menus, consent tools, chat, and accessibility controls avoid overlap?
Test real devices and narrow screens. A desktop mockup squeezed smaller is not a mobile design.
13–14. Set performance and accessibility targets
Google’s current Core Web Vitals guidance defines “good” field targets as Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint within 200 milliseconds, and Cumulative Layout Shift at or below 0.1 at the 75th percentile. See web.dev’s Web Vitals guide.
Use semantic headings, keyboard-friendly controls, visible focus, useful image alternatives, sufficient contrast, and reduced-motion support from the start.
15. Build a launch and rollback checklist
- Crawl old and new URLs
- Verify redirects, canonicals, sitemap, and robots rules
- Test forms, calls, bookings, email delivery, and thank-you pages
- Confirm analytics and consent behavior
- Check desktop, mobile, and common browsers
- Keep a restorable backup until post-launch checks pass
See Inkwell’s website design services for a conversion- and search-aware approach.
Common questions
How often should a business redesign its website?
There is no required schedule. Redesign when the site no longer supports the business, customers, technology, or measurable performance goals.
Will a redesign hurt SEO?
It can if useful content, URLs, internal links, metadata, or crawl access change without a migration plan. A tested redirect and verification plan reduces that risk.
Should a redesign be mobile-first?
Yes. Plan the smallest-screen decision path early, then expand the layout. This exposes content, navigation, form, and control conflicts before development is finished.
Information is educational and may change as platforms, laws, and market conditions change. Results depend on your offer, market, budget, competition, and follow-up.
Leave a Reply