Redesign when your site fails on mobile, loads slowly, contradicts your current business, or you can’t update it without a developer. Most Chicago and Chicagoland redesigns we’ve done — for businesses in Naperville, Aurora, Lockport, Oak Park, Lincoln Park, and the Loop — run $4,000–$15,000 and take 3–8 weeks. The biggest SEO risk isn’t redesigning — it’s redesigning without a 301 redirect map, content preservation plan, and pre-launch staging-to-production checklist. Done right, a redesign improves rankings; done wrong, it can tank them in days. We cover the cost side in how much a website costs in Chicago.
Signs It’s Time to Redesign
A website doesn’t need to be old to be a liability. Some sites are a problem the week they launch. The question isn’t “how old is it?” — it’s “is it doing its job?”
It doesn’t work on mobile
If your site isn’t responsive — if text is tiny, menus require pinch-and-zoom, or buttons are too small to tap on a phone — you’re losing a significant share of your visitors immediately. Google’s mobile-first indexing means your mobile site is your site, from Google’s perspective. A poor mobile experience directly suppresses your search rankings.
It loads slowly
A site that takes more than 3 seconds to load on a mobile connection loses roughly 50% of visitors before they see anything. If your Core Web Vitals scores are red, that’s a ranking suppression signal and a daily conversion loss. Slow sites are often symptoms of platform problems (bloated WordPress installs, unoptimized images, render-blocking scripts) that can’t be fixed without a rebuild.
It doesn’t reflect who you are now
If your website shows services you no longer offer, photos that are 5+ years old, an old phone number, or pricing from a different era — it’s actively hurting you. A prospect who finds conflicting information between your site and your GBP will move on. Outdated sites signal a business that may not be reliable.
You’re embarrassed to send people to it
This one is simple. If you hesitate before sharing your URL in an email — if you preface it with “the site is a little outdated, but…” — you already know the answer. A website you’re not confident sharing is a website that’s costing you business.
Your competitors look significantly better
Visit your top three competitors’ websites. If theirs are clearly more professional, better organized, and more trust-building than yours, some percentage of the customers you should be winning are going to them instead. In competitive markets like Chicago, website quality is a meaningful factor in who gets hired.
You can’t update it yourself
If making a simple text change requires emailing a developer and waiting three days, you have a process problem that’s preventing you from keeping your site current. A properly built site with a CMS, or a static site where a non-technical user can update key content, is worth the investment.
The SEO Risk of a Redesign
Website redesigns are one of the most common causes of sudden organic traffic loss. Done carelessly, a redesign can wipe out years of ranking progress in a matter of days. This happens most often when:
- URL structures change without 301 redirects from old URLs to new ones
- Title tags and meta descriptions are reset to generic defaults
- Existing content is removed or significantly reduced
- Structured data (schema markup) is stripped out
- The site is relaunched with broken internal links
- A staging environment is accidentally left with a noindex tag that gets pushed to production
Every one of these is avoidable with proper planning. The risk of redesign isn’t inherent to the process — it’s a result of not doing the SEO migration work that should accompany any structural change to a site.
Protecting Your Rankings
| Phase | What to do |
|---|---|
| Before redesign | Export all URLs from GSC (Coverage + Performance reports). Record top-ranking pages and the keywords they rank for. Export inbound links from Ahrefs / Moz / Bing Webmaster Tools. Save a Screaming Frog crawl of the current site capturing all URLs, title tags, H1s, meta descriptions, and schema. |
| During redesign | Map every old URL → new URL with 301 redirects. Preserve or improve existing title tags and meta descriptions. Maintain or expand content currently generating search traffic. Re-implement all structured data on the new site. Lock the staging site behind robots.txt or HTTP auth so Google can’t index it. |
| At launch | Verify robots.txt and meta robots tags don’t block production. Submit the new sitemap to Search Console. Request indexing on key pages via URL Inspection. |
| Post-launch (90 days) | Monitor GSC for crawl errors weekly. Track organic traffic against pre-launch baseline. Spot-check redirects with Google’s URL Inspection tool. Watch Core Web Vitals — redesigns often improve speed, sometimes regress it. |
The staging site risk most agencies miss
A common cause of post-redesign SEO disasters: the staging site was built with a “noindex” tag to prevent Google from indexing the in-progress site. When the site went live, no one removed the noindex tag. Google crawled the new site, saw “noindex,” and deindexed everything. Always verify the robots meta tag is removed before launching.
Redesign vs. Rebuild: What’s the Difference?
These terms get used interchangeably but describe very different scopes:
Redesign
A redesign changes the visual appearance and UX of an existing site without changing the underlying technology stack. The URL structure stays the same, the CMS stays the same, and most of the content is preserved. A redesign is appropriate when the platform is sound but the visual design is dated.
Rebuild
A rebuild changes the underlying platform, architecture, and often the URL structure. It’s appropriate when the current platform is the problem — a slow WordPress site on shared hosting, a custom CMS that no one can maintain, or a site builder like Wix or Squarespace that has hit its ceiling. Rebuilds carry more SEO migration risk but also deliver more significant performance improvements.
For most Chicago businesses with 3–5 year old websites, a rebuild is more appropriate than a redesign because the platform problems (WordPress bloat, plugin conflicts, shared hosting) can’t be solved by a visual update.
What to Keep from Your Old Site
Not everything on your current site is worth rebuilding. But some things should be preserved regardless of how you feel about the current design:
- Content that ranks: Any page that appears in your Google Search Console performance report with impressions or clicks is generating search value. Keep that content, improve it if possible, don’t remove it.
- URL structure (where possible): If your current URL structure is logical (/services/roofing, /blog/post-title), keep it. Changing URL structure requires redirect work and carries ranking risk.
- Inbound links: Pages with inbound links from other sites have accumulated authority. Redirect these to their equivalent pages on the new site. Losing that link equity through a broken redirect is a direct ranking loss.
- Google Analytics history: Connect the new site to the same GA4 property to preserve historical data. A new property means losing your baseline and starting blind.
Redesign Timeline and Process
A well-run website redesign for a Chicago small business (5–15 pages, standard services, no complex integrations) takes approximately 3 weeks from kickoff to launch. Here’s the sequence:
- Week 1: Discovery, SEO baseline audit, content inventory, sitemap/architecture planning, design kickoff
- Week 2: Design mockups in Figma, client review and approval, development begins on approved designs
- Week 3: Development completion, redirect mapping, QA, pre-launch SEO checklist, launch
- Post-launch: Search Console submission, 301 redirect verification, 30-day monitoring
Larger projects with more complex integrations (booking systems, client portals, custom calculators) take 4–8 weeks. The timeline shouldn’t be rushed — particularly the pre-launch checklist. An hour of QA before launch prevents weeks of cleanup after.
How to Measure Redesign Success
A redesign succeeds or fails based on business outcomes, not how good the design looks.
The metrics that matter:
- Organic traffic: Did it hold through the transition (no SEO drop) and is it growing 3–6 months post-launch?
- Conversion rate: Are more visitors becoming leads? Compare form submissions and phone calls before vs. after.
- Page speed: Did Core Web Vitals improve? Track LCP, INP, and CLS via Google Search Console.
- Bounce rate and engagement: Are visitors staying longer and viewing more pages? (GA4 engagement rate replaces the old bounce rate metric.)
Set a 90-day post-launch review date and pull these metrics against your pre-launch baseline. The redesign should show improvement across all four within 90 days — if it doesn’t, there are specific issues to diagnose, not a reason to abandon the project.
Redesign Already Tanked Your Rankings? Recovery Steps
If you launched a redesign in the last 60 days and your organic traffic dropped 30%+, this is recoverable but requires an immediate, ordered diagnostic. Don’t make additional changes until you’ve worked through this.
1. Check the noindex tag and robots.txt
The most common cause of post-launch ranking collapse: a noindex meta tag or Disallow: / in robots.txt was carried over from staging. View source on your homepage and search for “noindex.” Visit yourdomain.com/robots.txt. If either blocks crawlers, fix immediately and request reindexing in Search Console — recovery typically begins within 1–2 weeks.
2. Verify every old URL has a working 301 redirect
Pull your pre-launch URL list (you exported it from Search Console, right?) and run it through Screaming Frog as a list import against your new domain. Anything returning 404 instead of 301 is a redirect that didn’t get implemented. Add the missing redirects, then resubmit the affected pages to Search Console.
3. Compare content before vs. after
Pull your pre-launch crawl of titles, H1s, body text. Compare to the new site. If pages are 50%+ shorter than they were, you lost content that was driving rankings. The fix is restoring or replacing that content. This is the second most common cause of post-redesign drops.
4. Verify schema markup migrated
Pull a Rich Results Test on key pages. If your old site had LocalBusiness, Service, FAQPage, or Article schema and the new site doesn’t, you’ve lost rich-result eligibility. Re-implement schema before doing anything else.
5. Check Search Console manual actions
Open Search Console → Manual Actions. Rare but possible — a thin-content or doorway-page penalty can hit a redesign that consolidated too many pages or duplicated content during migration.
If you’re working with the agency that did the redesign and they’re unable to diagnose this in 48 hours, that’s a quality signal — covered in our guide on choosing a Chicago digital agency. For an independent diagnostic, we offer a free SEO audit that includes a redesign post-mortem.
Ready to rebuild your Chicago business website?
We handle the full rebuild in three weeks — design, SEO migration, redirect mapping, analytics, launch. What’s included:
- Pre-rebuild SEO audit so we don’t lose what’s already ranking
- 301 redirect mapping from every old URL to the right new one
- LocalBusiness, Service, and FAQPage schema baked in across the rebuild
- Google Search Console + GA4 + call tracking wired before launch
- 30-day post-launch monitoring — we watch impressions and rankings daily
No WordPress, no plugins, no surprises. Fixed price, three-week timeline.
