Key takeaways
Hire for results you can verify: preserved search traffic, speed, lead tracking and a site you own.
Ask for an old-to-new URL redirect map before any design work is approved.
Ask the designer to commit to Core Web Vitals targets on mobile: LCP 2.5s, INP 200ms, CLS 0.1.
Use WCAG 2.1 AA as your accessibility benchmark, even if the DOJ rule doesn't bind your private firm.
Insist you own your domain, content and analytics, so you can leave without losing everything.
Hire the person who can prove results you can check: your search traffic survives the move, the site loads fast on a phone, forms feed your pipeline, and you own everything at the end. Skip the beauty contest of portfolios. Ask for the redirect plan, the speed numbers, and your login details.
Most hiring guides are written by agencies selling the service, so they end up describing themselves. This one is written from the buyer's side. We build and run websites for established firms at AetherWeb, and we've seen what goes wrong when owners hire on looks alone. Here is what to demand, what to skip, and a checklist you can hand to whoever you hire.
Start with the job the site has to do
Before you talk to anyone, write down what the site must do. For most firms, the answer is leads. List the pages that bring in calls and form fills today, who should be finding them, and what you want a visitor to do next.
This matters because a designer who hears "make it look modern" will deliver something modern-looking. A designer who hears "keep the pages that bring in clients and make the contact path shorter" will plan differently. It also gives you a way to judge the result after launch.
One more view, and it's ours rather than a studied fact: cutting pages that rank loses traffic even when the redirects are perfect. Treat a redesign as a content decision, not just a visual one. Ask which pages the designer plans to remove and why.
Demand a redirect and URL plan
This is the check most owners never make, and it's where redesigns quietly lose traffic. If your new site changes URLs, every old address needs to point to its new equivalent. Google's guidance in its site move documentation is clear on how to do it, so ask your designer to show you the plan.
What a good redirect plan includes
A written map of old URLs to new URLs, built before launch.
Server-side permanent redirects (HTTP 301 or 308) rather than workarounds. Google says permanent redirects don't cause a loss in PageRank.
No blanket redirect of many old pages to the home page. Google warns that can confuse users and may be treated as a soft 404.
No long chains. Google advises keeping a chain to no more than 3 hops, with each old URL pointing straight at its final destination where possible.
Redirects kept for at least a year. Google's John Mueller made the same point, reported by Search Engine Journal on keeping redirects.
The type of redirect matters too. According to Google's redirects documentation, permanent redirects make Google show the new URL in results, while temporary ones (302, 303, 307) keep showing the source page. Google staff also said a 301 passes ranking signals and a 302 does not, as covered in this Search Engine Journal recap. If your designer says "we'll just redirect everything" and can't say how, press for details.
Set expectations honestly. Google says a medium-sized site can take a few weeks or more for new URLs to replace old ones in search results, and visibility may fluctuate in the meantime. A dip right after launch is normal. A dip that doesn't recover is a sign the map was wrong. Google also notes that people often redirect to wrong or non-existent URLs, so watch for spikes in "Not found" errors in Search Console.
A word on domains: if your redesign also moves you to a new domain, Google's Change of Address help page says combining that with a content and URL overhaul will probably cause some traffic loss. Keep your domain unless you have a strong reason to change it.
Ask for speed numbers, not promises
"Fast" means nothing until it has a number. Google's Core Web Vitals guidance on web.dev sets the targets: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less. These are measured at the 75th percentile of page loads, split by mobile and desktop, and a page passes only if all three are met.
So ask the designer to commit to those targets on mobile. Then ask to see field data from PageSpeed Insights or Search Console once the site is live, not just a lab test on a fast laptop. If they've never looked at those tools, that tells you something.
Ask about accessibility without the hype
Accessibility is often reduced to one vague bullet: "we follow WCAG." Be specific. The benchmark to name is WCAG 2.1 Level AA. The Justice Department's final rule under ADA Title II, summarized by the SBA Office of Advocacy, adopted that standard for state and local governments.
Be clear about who that binds. The rule covers public entities, not private firms. Law-firm commentary in the Consumer Financial Services Law Monitor says it doesn't change legal obligations for private businesses, and that the extension left the substantive requirements unchanged. An April 2026 interim rule, covered by Jackson Lewis, moved the deadlines to 26 April 2027 for larger entities and 26 April 2028 for smaller ones.
It matters more if you serve public-sector clients. The UNC School of Government notes the rule reaches content created by contractors, including private web developers. It also confirms WCAG 2.1 AA doesn't require Level AAA criteria, so the target is realistic. Even for a purely private firm, a site people can actually use is a better site. Ask your designer how they test for it.
Know what you will own at the end
This is our opinion, and we're not shy about it: traditional agencies often leave clients stuck. The site lives on their hosting, the logins are theirs, and leaving means starting over. Before you sign, get a written answer on each of these.
Your domain is registered in your name.
You have admin access to hosting and the content system.
You own your content, images and form data.
Analytics and Search Console are set up under your account.
You know exactly what happens to all of it if you leave.
We cover the domain question in keeping your domain when you switch designers, and the money side in subscription versus paying upfront. Both models can be fair. Neither is fair if you can't see the terms.
Plan for what happens after launch
A launch is the start. Someone has to host the site, patch it, change a team bio, add a service page and answer when something breaks. Ask who does that, how fast, and what it costs. Vague answers here become surprise invoices later.
Ask too what the site does with a lead once it arrives. A form that emails one person's inbox and gets forgotten isn't a lead system. Our AetherHub platform handles forms, contacts, blogs, events and web analytics in one place, and our Workflows send automated follow-up so nobody waits days for a reply. Whoever you hire should have a real answer for this, whatever tools they use.
Red flags when choosing a web designer
The scope is fuzzy: no page list, no deliverables, no end date.
They have no redirect plan, or say it's "handled automatically."
Nothing is tracked at launch: no form tracking, no analytics, no Search Console.
They won't promise you access to your own domain and accounts.
They sell "AI SEO" with no specifics about what they'll actually change.
They show you finished pages only after you've paid in full.
That last one is why we like the idea of seeing the work first. We explain how that works in what to ask about a free website redesign.
A website redesign checklist you can use
This list draws on Google's site move steps. Give it to whoever you hire and ask them to confirm each item.
Before launch
Inventory your current URLs, including images, videos, JavaScript and CSS files.
Build the old-to-new URL map.
Give each new page a self-referencing canonical tag.
Update internal links to point to the new URLs.
Remove any noindex rules added to the staging site.
Test the redirects before going live.
Launch day
Switch on the redirects.
Submit the new sitemap in Search Console.
Confirm forms deliver and analytics record visits.
Check the host can handle extra load. Google says it crawls a new site more heavily after a migration.
The first weeks
Watch Search Console for spikes in "Not found" errors and fix wrong redirects.
Expect a few weeks of fluctuation before rankings settle.
Check mobile speed against the Core Web Vitals targets.
Keep every redirect in place for at least a year.
Questions about AetherWeb
What is AetherWeb?
AetherWeb is a web design, marketing tools and custom app development company for established small and mid-sized businesses. We design, build, host and maintain websites on a subscription with a free redesign. We work with firms in San Diego, San Francisco and online.
What is AetherWeb web design?
It's our service for firms whose websites underperform. We redesign the site, host it, maintain it and connect it to tools for forms, contacts and follow-up. You can see our San Diego web design page for local details.
Is AetherWeb a web browser or a driver?
No. AetherWeb is a company that builds and runs business websites and marketing tools. It isn't a browser, a software driver or a testing tool.
Hire on proof, not polish
A good redesign protects the traffic you've earned, loads fast on a phone, works for the people who need it, and leaves you in control. Ask for the redirect map, the speed targets, the access list and the lead tracking. A designer who can't show them is selling decoration.
If you want to see how we'd handle yours, check our pricing or get in touch with us. We'll show you the redesign before you pay, and we'll answer every question on this list.
Sources
Site Moves and Migrations — Google Search Central
Google: Keep 301 Redirects In Place For A Year — Search Engine Journal
Redirects and Google Search — Google Search Central
Google Explains How Redirects Affect Ranking Signals — Search Engine Journal
Change of Address tool - Search Console Help — Google Search Console Help
Web Vitals | Articles | web.dev — Google web.dev
Justice Department Finalizes Rule Requiring State and Local Governments to Make their Websites Accessible — U.S. Small Business Administration Office of Advocacy
DOJ Extends Title II ADA Web Accessibility Rule Compliance Deadlines for State and Local Governments — Consumer Financial Services Law Monitor
DOJ Extends Public Entities' Compliance Deadline for ADA-Related Website Accessibility, But HHS's May 2026 Deadline Still Looms — Jackson Lewis
Understanding the New ADA Web Accessibility Requirements for State and Local Governments — UNC School of Government