A website redesign should solve specific customer and business problems. A new color palette cannot repair unclear services, duplicate pages, weak calls to action, missing local proof, inaccessible forms, confusing navigation, slow mobile pages, unreliable tracking, or a publishing process nobody owns. Planning starts by identifying the audiences, tasks, evidence, content, systems, and measurable outcomes that the new experience must support.
The existing site contains valuable evidence. Search queries reveal how prospects describe their needs. Analytics show common entry pages and journeys. Sales and support teams know which questions delay decisions. Form and call data show which conversions matter. Content inventories expose duplication, stale claims, missing services, broken links, thin local pages, and articles that attract the wrong audience. A redesign roadmap turns that evidence into priorities before layouts are approved.
ALLMSP plans, designs, develops, launches, and maintains business websites for organizations in Lawrenceville, Suwanee, Gwinnett County, Metro Atlanta, and throughout Georgia. Our in-house team can handle content strategy, information architecture, responsive design, WordPress and Elementor development, accessibility, technical SEO, analytics, forms, hosting, security, migration, testing, training, and ongoing improvement.
Translate customer needs and business goals into a buildable redesign plan
- Define outcomes: Name the business result, customer task, baseline, target, evidence, owner, deadline, and constraint.
- Research the audience: Study customer questions, search language, devices, locations, accessibility needs, objections, and decision paths.
- Audit the current site: Inventory content, traffic, rankings, links, conversions, technology, integrations, risks, performance, and ownership.
- Design the structure: Organize services, industries, products, resources, locations, proof, and calls to action around visitor intent.
- Specify the system: Define templates, components, content fields, forms, tracking, security, hosting, accessibility, and publishing controls.
- Plan delivery: Sequence content, design, development, migration, redirects, testing, training, launch, stabilization, and improvement.
Define audiences, customer tasks, business outcomes, and evidence
Identify the people the site must serve and the situation that brings each one to it. A business owner comparing managed IT providers needs different evidence from an employee seeking support, a local buyer looking for computer repair, a marketing leader evaluating campaign services, or a customer researching a specific technology. Record each audience’s question, urgency, location, device, knowledge, objection, required proof, preferred contact path, and successful outcome. Include mobile, keyboard, low-vision, multilingual, and other needs that affect access and comprehension.
Set measurable outcomes without pretending the redesign controls every business result. Useful measures include qualified calls and forms, booked appointments, ecommerce completion, support deflection, search visibility for priority services, successful page journeys, engagement with proof, mobile performance, accessibility defects, publishing time, and lead-routing accuracy. Establish the current baseline, data quality, target, period, owner, and conditions that could influence each measure. A redesign cannot be evaluated fairly when conversion tracking changes at launch and the old baseline was never validated.
Interview sales, service, support, leadership, and content owners around real interactions. Gather questions prospects ask, reasons opportunities stall, misunderstandings that create support work, location concerns, trust requirements, pricing expectations, compliance needs, and services the site describes poorly. Review call recordings, tickets, search queries, form submissions, chat, reviews, proposals, and lost opportunities where authorized. Distinguish evidence from internal opinion and record decisions when stakeholders disagree.
- Audience record: Capture role, need, urgency, location, device, knowledge, accessibility, objection, proof, action, and desired outcome.
- Customer task: State what the visitor needs to find, understand, compare, trust, submit, buy, schedule, download, or resolve.
- Business measure: Define baseline, target, attribution limits, period, data source, owner, decision use, and possible outside influence.
- Sales evidence: Collect common questions, objections, decision criteria, proof requests, lost reasons, lead quality, and routing problems.
- Support evidence: Review repeated confusion, failed self-service, account and form problems, broken journeys, and missing instructions.
- Decision record: Document priorities, evidence, tradeoffs, assumptions, exclusions, owner, approval, and conditions for reconsideration.
Evidence-based goals keep the redesign centered on customers and operations rather than the personal preference of whoever comments last on a mockup.
Audit content, search visibility, analytics, technology, and risk
Crawl the current site and inventory every indexable URL, redirect, file, image, template, form, menu, structured-data type, language, and important external destination. Add page purpose, audience, owner, traffic, search impressions, queries, backlinks where available, conversions, assisted conversions, freshness, quality, duplication, accuracy, local relevance, accessibility, performance, and disposition. Decide whether each item will be kept, improved, consolidated, redirected, archived, or removed. Preserve useful material instead of rewriting everything merely because the design changes.
Validate analytics before using it. Confirm tag coverage, consent behavior, events, conversions, call tracking, form success, ecommerce, cross-domain measurement, internal traffic, referral exclusions, campaign parameters, and data retention. Review Search Console for indexed pages, queries, clicks, impressions, page performance, sitemap status, crawling, canonical selection, manual actions, and security issues. Identify high-value landing pages and inbound links that require special protection during migration.
Map the technical environment and its owners. Include CMS, theme, page builder, plugins, custom code, hosting, DNS, domains, certificates, CDN, firewall, email delivery, backups, repositories, deployment, forms, CRM, scheduling, payments, analytics, search, privacy tools, accessibility dependencies, and administrator access. Review support status, updates, licenses, data flows, security exposure, performance bottlenecks, and exit options. A redesign that ignores operational ownership often launches with a cleaner appearance and the same underlying fragility.
- URL inventory: Record purpose, owner, traffic, queries, links, conversions, quality, duplication, freshness, disposition, and redirect destination.
- Content evidence: Evaluate accuracy, usefulness, originality, proof, voice, local relevance, readability, media, accessibility, and next action.
- Search baseline: Capture index status, impressions, clicks, queries, landing pages, canonical behavior, sitemaps, errors, and valuable inbound links.
- Measurement baseline: Verify tags, consent, events, conversions, forms, calls, ecommerce, attribution, exclusions, retention, and reporting owners.
- Technology map: List platform, hosting, DNS, security, email, integrations, code, plugins, accounts, licenses, data, backups, and support.
- Risk register: Track unsupported software, single-person access, weak recovery, insecure forms, broken tracking, poor performance, and migration exposure.
The audit protects what already works, exposes what the redesign must repair, and prevents valuable search equity or conversion data from disappearing unnoticed.
Create the information architecture, component plan, roadmap, and acceptance model
Organize the site around understandable customer choices. Define the relationships among services, industries, products, locations, resources, case evidence, support, and contact paths. Use descriptive labels and avoid internal department names that customers do not recognize. Build a page map and navigation model, then test common tasks from search landing pages as well as the homepage. Every important page should have a distinct purpose, useful content, contextual internal links, appropriate proof, and a clear next step without forcing visitors back through the main menu.
Specify reusable templates and components from content needs. Define hero content, service summaries, comparison structures, process sections, product details, industry evidence, team or credential proof, FAQs, calls to action, forms, related resources, and local information. Document fields, responsive behavior, accessible semantics, image requirements, states, variants, and analytics events. Keep component choices limited enough to preserve consistency while allowing different services to communicate genuinely different information.
Build a phased roadmap with dependencies. Sequence discovery, content decisions, information architecture, visual system, prototypes, technical foundation, component development, content production, integrations, analytics, accessibility, performance, migration, redirects, quality assurance, stakeholder acceptance, training, launch, and stabilization. Assign owners, deliverables, entry criteria, acceptance criteria, budget, review windows, and change control. Reserve time for real content and device testing because placeholders hide layout, comprehension, and migration problems.
- Page map: Show page purpose, audience, parent, related content, customer task, primary action, proof, owner, and disposition.
- Navigation model: Test labels, hierarchy, depth, mobile behavior, keyboard access, search, breadcrumbs, and routes from landing pages.
- Component model: Define content fields, semantics, responsive rules, states, variants, media, accessibility, analytics, and usage guidance.
- Content plan: Assign source, writer, reviewer, expertise, proof, SEO intent, local context, media, due date, migration, and approval.
- Delivery roadmap: Sequence dependencies, owners, deliverables, reviews, decisions, testing, migration, launch, stabilization, and improvement.
- Acceptance model: Set functional, content, visual, responsive, accessible, performance, security, search, tracking, and operational criteria.
A complete roadmap lets design, content, development, marketing, IT, and leadership make coordinated decisions before the launch window becomes the planning process.
Business website redesign planning from ALLMSP
ALLMSP can research audiences, inventory content, analyze search and analytics, map customer journeys, design information architecture, create content and components, define requirements, build the roadmap, develop the site, migrate systems, launch safely, and improve performance through one in-house team.
We plan and deliver website redesigns for businesses in Lawrenceville, Suwanee, Gwinnett County, Metro Atlanta, and throughout Georgia, with local SEO and customer needs integrated naturally into the broader site strategy.
- Discover: Define customers, tasks, outcomes, measures, questions, proof, constraints, technology, ownership, and risk.
- Design: Build the page map, navigation, content model, visual system, components, prototypes, requirements, and acceptance tests.
- Deliver: Write, develop, integrate, migrate, redirect, test, train, launch, stabilize, measure, and improve the new experience.
Primary guidance for website redesign planning
Use current search, performance, and accessibility guidance while making decisions from the organization’s own customers, content, analytics, technology, and operating constraints.
- Google SEO Starter Guide. Emphasizes logical organization, useful original content, descriptive titles, clear links, and high-quality relevant images.
- Web Vitals. Defines user-centered performance measures that can inform redesign requirements and post-launch monitoring.
- W3C Planning and Managing Web Accessibility. Provides resources for integrating accessibility into planning, implementation, monitoring, and organizational practice.
- ALLMSP Web Design. Strategy, content, design, development, accessibility, SEO, analytics, hosting, maintenance, and conversion improvement.
Website redesign planning FAQs
What should a website redesign accomplish?
It should improve defined customer tasks and business outcomes such as qualified inquiries, purchases, support access, search visibility, accessibility, performance, publishing, and measurement.
Should every page be rewritten during a redesign?
No. Keep and improve useful accurate content. Consolidate duplication, replace weak material, redirect retired URLs, and preserve pages that already satisfy customers and search intent.
What belongs in a website content inventory?
Include URL, purpose, audience, owner, traffic, queries, links, conversions, accuracy, quality, freshness, duplication, media, accessibility, local relevance, and final disposition.
How should redesign goals be measured?
Define a reliable baseline, target, period, data source, owner, attribution limits, and the decision each measure will support before changing tracking.
How does local SEO fit a website redesign?
Map real service areas, local intent, customer evidence, location information, internal links, titles, content, business data, and conversion paths without repeating place names unnaturally.
Why test navigation from landing pages?
Many visitors arrive from search, advertisements, email, or direct links. They need useful next steps and context without returning to the homepage.
What technical systems should be reviewed?
Review CMS, hosting, DNS, security, backups, email, forms, CRM, payments, scheduling, analytics, search, plugins, code, accounts, licenses, and support.
When should accessibility be considered in a redesign?
Include accessibility in research, content, design, components, development, procurement, acceptance testing, publishing, and maintenance from the start.
Can ALLMSP handle a complete website redesign?
Yes. ALLMSP handles strategy, content, design, WordPress and Elementor development, SEO, accessibility, analytics, integrations, hosting, migration, testing, training, and support in house.
Where does ALLMSP provide website redesign services?
ALLMSP serves Lawrenceville, Suwanee, Gwinnett County, Metro Atlanta, and businesses throughout Georgia through local and remote delivery.
