Chicago Website Redesign Guide: Plan, Migrate, Launch

Treat a redesign as a controlled migration, not a new coat of paint. The current site contains business information, indexed URLs, backlinks, analytics history, form behavior, and content that customers may already use. The redesign should identify what earns its place before anything is removed.

Refresh, rebuild, or redesign?

A full rebuild carries the most migration risk. It should not be the default answer when a focused refresh can fix the problem.

Start with evidence from the current site

Record the baseline before changing navigation, copy, forms, URLs, or tracking. Use at least the last twelve months when the business has seasonal demand. Mark any analytics configuration changes that make periods difficult to compare.

Search evidence

• Export Google Search Console pages and queries
• Mark pages with clicks, impressions, high-value queries, and external links
• Export indexed and non-indexed URLs
• Save the submitted sitemap and robots.txt
• Crawl titles, descriptions, canonicals, headings, status codes, and internal links

Business evidence

• List the forms, calls, bookings, purchases, and other actions that count as leads
• Record conversion rates by landing page where tracking is reliable
• Identify pages used by sales, support, recruiting, and existing customers
• Collect common questions from emails, calls, proposals, and reviews

Technical evidence

• List the CMS, hosting, forms, analytics, CRM, email, booking, and payment systems
• Record domain, DNS, hosting, Search Console, Analytics, and Business Profile ownership
• Test mobile navigation, keyboard navigation, forms, and common browsers
• Run PageSpeed Insights on the homepage and the main organic landing pages

Decide what each page must do

Give every proposed page a purpose, primary audience, search intent, and next action. Pages without a distinct job often become duplicate service pages or city pages with swapped place names.

Build the URL migration map before development ends

Put every current URL in a spreadsheet or database and assign one outcome: keep, update in place, redirect to a close replacement, or remove with a 404/410 when no replacement exists. Do not send every retired page to the homepage.

Google recommends permanent server-side redirects for moved URLs and warns against irrelevant redirects that can be treated as soft 404s. Read Google's redirect guidance and site-move checklist before launch.

Migration-map fields

• Old URL
• Current status code
• Search clicks and impressions
• Known backlinks
• New URL or removal decision
• Redirect status
• Internal links updated
• Post-launch verification result

Protect the tracking setup

Write the measurement plan before launch. Name the events, conversion conditions, thank-you states, phone tracking rules, consent behavior, and test cases. A redesigned form that sends email but no longer records a conversion creates a false traffic problem in the reports.

Keep Google Analytics and Search Console in business-controlled accounts. Annotate the launch date and any event-definition changes. Test analytics in a production-like environment without sending test leads into live sales workflows where possible.

Use a launch checklist

Content and on-page checks

• One descriptive H1 per page
• Unique titles and descriptions for indexable pages
• Self-referencing canonical URLs
• Accurate business names, addresses, phone numbers, prices, and dates
• Useful alt text for informative images
• No placeholder copy, sample reviews, or unsupported claims

Crawl and index checks

• Robots.txt permits required pages and assets
• The XML sitemap contains only canonical 200-status URLs
• Redirects use one hop and point to relevant replacements
• No important page has a noindex directive
• Internal navigation and content links use final URLs
• Structured data matches the visible page

Functional checks

• Forms deliver the right information to the right destination
• Phone, email, booking, payment, and account actions work
• Analytics and agreed conversion events record correctly
• Keyboard focus, labels, error messages, and contrast are usable
• Mobile navigation works at common viewport sizes
• 404 and server-error pages behave as expected

What to do after launch

1. Crawl the production site and compare it with the migration map.
2. Submit the canonical sitemap once in Google Search Console and Bing Webmaster Tools.
3. Inspect the homepage and the highest-value changed pages.
4. Check forms, calls, and analytics with real production tests.
5. Watch 404s, redirect errors, indexing changes, organic landing pages, and conversions.
6. Fix migration defects before adding new redesign features.

Do not request indexing for every URL repeatedly. Submit the corrected sitemap, inspect the priority pages, and let the crawl signals stay consistent.

Redesign pricing at Intuico Digital

Intuico's custom website builds start at $2,500 plus a care plan. A redesign quote depends on the existing page count, content migration, integrations, design scope, and search-preservation work. Small sites that fit a preset design may qualify for a managed monthly plan instead. The pricing guide lists the current plan details and first-year totals.

Send the current URL and required changes through the project form. The first useful deliverable is a written recommendation: refresh, partial rebuild, or full redesign.