Changing web designers is less dangerous than most business owners assume. The traffic loss that scares people away from a switch almost always traces back to a short list of avoidable mistakes: broken URLs, missing redirects, dropped tracking, or a launch that happens while nobody is watching. Handle those and the move is usually quiet in the best sense. Search engines see the same pages, visitors land in the same places, and the only thing that changes is who answers your emails.
Indianapolis has a deep bench of designers. National firm directories list full-service agencies based in the city, Yelp results reach nearby communities such as Fishers, and local Reddit threads regularly collect recommendations from business owners who have already been through this. That depth is good news for your options and a reason to slow down for a week. The handoff deserves a written plan rather than a handshake.
Start With a Full Inventory of What You Own
Before you interview anyone, open a document and list every account, file, and access point connected to the current site. Designers change; ownership should not. The most common cause of a stalled migration is not a technical bug but a former vendor holding a login nobody else has.
Your inventory should cover:
- The domain name, plus the registrar account it sits in and the renewal date
- The hosting account and the control panel credentials
- The DNS provider, which may or may not be the same company as the registrar
- The content management system, its admin logins, and any licensed plugins or themes
- Analytics, Search Console, and tag manager accounts with admin rights confirmed
- Google Business Profile access, if a local listing drives calls or visits
- Form submissions, CRM connections, and any booking or chat tools
- Email accounts and inboxes tied to the domain
- Ad accounts and the conversion tracking that feeds them
- Original image files, fonts, and brand assets
Confirm that admin access actually works for each item rather than trusting a password list. Where access sits with a departing vendor, request it in writing and early, while the relationship is still civil.
Capture an SEO Baseline Before Anyone Touches the Site
You cannot prove you preserved traffic unless you measured it first. Pull a snapshot of the current site's search and analytics performance in the week before the redesign disappears, and store it somewhere your new designer can see. Screenshots are fine; exported files are better.
| What to record | Where it lives | Why it matters later |
|---|---|---|
| Number of indexed pages | Search Console pages report | Reveals whether pages silently dropped out after launch |
| Organic sessions and conversions over 12 months | Analytics | Gives you a seasonally fair comparison, not a one week panic check |
| Top landing pages by organic entry | Analytics | These URLs must exist or redirect after the switch |
| Queries and pages with impressions | Search Console performance report | Shows which pages earn visibility even without many clicks |
| Core Web Vitals status | Search Console experience reports | Establishes whether the new build is faster or slower |
| Backlink profile snapshot | Any backlink tool or exported report | Confirms that links still reach live pages after the move |
Add a plain list of the keywords the business actually cares about and their current positions. That list is your sanity check for months three and four, after the launch excitement fades and someone asks whether the redesign worked.
Make the URL Map the Center of the Handoff
Every page that currently earns traffic needs a destination on the new site. Export all known URLs, mark each as keep, redirect, or retire, and match it to the new structure. Pages that stay identical keep their exact address. Pages that move get a permanent 301 redirect to the closest equivalent, never to the homepage by default.
Retiring a page is a decision with consequences. If a page has links from other sites or steady organic entrances, keep it and refresh the content rather than deleting it. If it truly must go, redirect it to a relevant parent page instead of letting it return a 404. Ask your new designer for the finished redirect map before launch and skim it yourself. You know your old URLs better than anyone on the project.
Choosing the Right Local Indianapolis Partner
Local matters in practical ways. A studio in your time zone answers a Tuesday morning message before lunch, and one that works with central Indiana businesses has likely seen your competitive set already. It also makes sitting down with someone in person possible when a decision is complicated.
The local market spans a wide range. National directories and Yelp listings show full-service agencies offering design, development, and digital marketing under one roof, alongside smaller shops and freelancers. Publicly posted pricing in the Indianapolis area ranges from low entry-level packages with hosting bundled in up to full-service agency engagements, so ask directly what a scope includes rather than estimating from a homepage number. Reddit's r/indianapolis threads asking for local recommendations are a useful source of names, but treat them as a starting list and verify current work in the wild before you shortlist.
Questions to Ask Before You Sign
- Who owns the hosting, domain, and code when the project ends, and will I have admin access from day one?
- How do you handle redirects and URL preservation, and can I see the redirect map before launch?
- What does your launch process look like, including staging, testing, and a rollback plan?
- What happens to my current analytics, tracking tags, and ad conversions during the switch?
- What do you charge for ongoing maintenance, and what is covered?
A designer who answers these without flinching is a designer who has done migrations before. Vague answers about access and redirects are the clearest warning sign in the entire conversation.
Protect the Technical Foundations That Carry Rankings
Traffic rarely disappears because a design changed. It disappears because something underneath broke. Insist that the new build keeps clean, crawlable HTML, includes an accurate XML sitemap, uses a correct robots file, and serves every page over HTTPS. Confirm that title tags, headings, and internal links carry over rather than being replaced with generic copy.
Performance deserves the same scrutiny. Speed and Core Web Vitals affect both rankings and paid campaign results, so compare the new site against the baseline you recorded, on mobile first. A design that looks sharper but loads slower is a downgrade dressed up as progress, especially for businesses sending paid traffic to a landing page.
Move Domains, DNS and Email Deliberately
Keep the domain where it is unless there is a real reason to transfer it. Registrar transfers take time, and combining one with a site launch multiplies the ways a launch day can go wrong. Changing nameservers is enough for most migrations.
Email is the piece people forget. If inboxes are tied to the domain, verify the new DNS records before the switch and send test messages both ways afterward. Keep the old hosting account alive and paid for a couple of weeks after launch. It costs little and gives you a fallback if something surfaces late.
Plan the Launch Window and a Rollback
Pick a low traffic window, ideally early in the week so you have working days to respond to anything odd. Before the switch, take a full backup of the old site and database, confirm the new site works on a staging address, and decide in advance who has authority to roll back and what would trigger it.
On launch day, work through a short checklist: point DNS, verify HTTPS, load key pages on mobile and desktop, submit the sitemap, spot check redirects on the highest traffic old URLs, test every form and phone link, confirm analytics and conversion tags are firing, and check that the Google Business Profile link still resolves.
Watch the First 30 Days Closely
Expect minor ranking movement. Search engines need to recrawl and reprocess the site, and short term fluctuation is normal. What you are looking for is a pattern, not a single day's number. Check organic entrances to your top pages, indexed page count, crawl errors, and conversion volume weekly for the first month, then move to a monthly review.
If a page that used to earn traffic stops earning it entirely, look for a 404, a redirect pointing somewhere irrelevant, or a page that lost its optimized title and body copy. Those are fixable in an afternoon when you catch them early. The same problem left for three months can cost a meaningful share of the year's leads.
Frequently Asked Questions
Will I lose search rankings if I change web designers?
Not if the URL structure, content, and technical foundations survive the move. Rankings drop when pages 404, redirects are missing, or tracking disappears. A switch done with an inventory, a baseline snapshot, and a redirect map usually holds position. Expect small fluctuations during recrawling and judge results over four to eight weeks instead of a single day.
How long before I can tell whether the migration worked?
Give it at least four weeks. Search engines need time to recrawl the site and process the new version, and analytics data needs enough volume to show a trend. Check your top landing pages weekly during that window, then compare against the baseline over a full quarter for a fair seasonal read.
Who should own the domain and hosting after the switch?
You should. Register the domain and hosting accounts in the business name, not the designer's, and keep admin access yourself. Vendors can be given editor or manager permissions without becoming the owner. Ask for this in writing before work begins, and confirm each login works rather than accepting a password list.
Should the new site launch on the same domain?
Yes. Keep the domain that already has history, links, and search visibility. Launching on a fresh domain restarts almost everything and puts your existing traffic at risk for no benefit. If a rebrand requires a new name, run it as a separate, carefully planned redirect project rather than folding it into the redesign.
Can I keep my current content during a redesign?
Keep the content that earns traffic and rewrite the rest. The pages sitting at the top of your organic entrances should carry over with their headings, copy, and internal links intact. New visual design does not require new words everywhere. Stripping proven content during a redesign is one of the most common ways businesses lose visibility they had already paid for.
A designer switch is a project with a beginning, a launch, and a short monitoring period, and the businesses that come through it with traffic intact are the ones that treated the handoff as seriously as the design. Build the inventory, record the baseline, map every URL, and watch the numbers for a month. Do those four things and the change becomes administrative instead of risky, which is exactly what you want from a move like this.