Most people choose a website redesign agency by looking at portfolios. It is the worst available signal: every firm shows you its five best projects, and you cannot tell which ones actually performed. Meanwhile the decisions that determine whether your rebuild succeeds, who owns the code, whether anyone maps redirects, what happens the week after launch never come up until it is too late to negotiate.

If you are still deciding whether to rebuild, start with the signs it’s time to redesign your website. For process, cost, and timeline, see the website redesign playbook. This post assumes you have decided and now have to pick someone.

Choose a website redesign agency by scope and ownership, not by portfolio. The right partner runs a real discovery process, names an SEO migration plan with redirects, builds accessibility in rather than bolting it on, hands you full ownership of your domain, code, and content, and tells you plainly what happens after launch. Ask what is NOT in scope that single question separates honest proposals from optimistic ones.

Know which kind of partner you actually need

There are four realistic options, and the expensive mistake is buying the wrong category, not the wrong company.

DIY platforms (Squarespace, Wix, a WordPress theme you assemble yourself). Right for a small brochure site when someone on your team is capable and the site is not a primary revenue channel. Cheap in dollars, expensive in hours. It fails on the invisible things redirects, accessibility, structured data, because nothing prompts you to do them.

Freelancers. A strong freelance designer or developer is excellent value for a focused project, and you get the person you hired rather than the person who pitched. The limits are real: one skill set, one calendar, no bench. If your rebuild needs strategy, design, development, content, and SEO migration, a single freelancer is doing three of those badly. Some assemble a network, ask who is accountable when it breaks.

Boutique agencies (roughly 5–40 people). The usual fit for professional services firms, nonprofits, and mid-size manufacturers: multiple disciplines, with senior people still on the project. The risk is capacity, a small team with a big client can leave you waiting.

Large firms. Appropriate for complex builds, multi-site architectures, deep integrations, e-commerce at scale, portals. You are paying for process, governance, and redundancy, and you should get all three. The known failure mode is the pitch team you never see again. Meet the people doing the work before you sign.

Size is not quality. Match the partner to the complexity of the problem.

The questions that actually matter

Portfolio review takes twenty minutes. These questions take an hour and are worth more.

Ownership

• Who owns the domain, the DNS, and the hosting account? You do, in your own accounts. Agencies holding client domains is common and indefensible.
• Who owns the code, designs, and content when we’re done? Get it in writing: work made for hire, or a full assignment of rights on final payment.
• Can another firm maintain this site without you? If the honest answer is no, you have not bought a website. You have leased one.
• What CMS, and is it proprietary? Proprietary systems are not automatically wrong, but they change the deal. If leaving means rebuilding from scratch, price that risk now.

Process and scope

• Walk me through your discovery. You want specifics, stakeholder interviews, analytics review, competitive analysis, a documented output you sign off on. “We’ll hop on a call and get started” means you are paying them to guess.
• Who writes the content? The most under-scoped line item in this industry, and the leading cause of blown timelines. If the proposal assumes you will supply 40 pages of copy, decide out loud whether that is true.
• What is explicitly NOT in scope? A good partner has a clear answer ready. A weak one gets uncomfortable.
• How do change orders work? Scope will change. You want a written process, not a shrug.

SEO migration

• How do you handle redirects and preserve rankings? Look for a crawl of the current site before anything is designed, one-to-one redirect mapping, metadata and structured data carried over, and post-launch monitoring. Google’s guidance on 301 redirects and site moves is the baseline; a proposal vaguer than a public Google doc tells you something.
• Who is responsible if traffic drops after launch? The answer matters less than whether they have thought about it at all.

Accessibility

• Is accessibility included, or an add-on? The standard is WCAG 2.2, and Level AA is the practical target. Building to it during design costs a fraction of retrofitting after launch.
• How do you test it? “We run a scanner” is a partial answer, automated tools catch only a share of real issues. You want keyboard testing and manual review too. For what a commitment looks like in writing, see our accessibility policy.

After launch

• What happens in the 90 days after we go live? Monitoring, fixes, and a named person.
• Who edits the site day to day, and will you train them? If your team cannot publish a page without a ticket, you have rebuilt the problem you were escaping.
• What does ongoing support cost, and is it optional? Either answer is fine. Surprises are not.

Red flags

• No discovery. Anyone who quotes a firm price on the first call is quoting a template, not your project.
• Design-only, with no SEO plan. A beautiful site that loses half your organic traffic is a net loss you will feel for two years.
• No real answer on accessibility. It signals how they treat everything you cannot see in a comp.
• A locked proprietary CMS with no export path. Ask what leaving looks like. Watch the reaction.
• No post-launch plan. Launch is the middle of the project, not the end.
• Portfolio without outcomes. Pretty is not a result. Ask what happened to traffic and leads afterward.
• A price far below everyone else. Cheap redesigns are not cheap because someone found efficiency. Something got cut. Ask what.

How to compare proposals fairly

Three proposals arrive at $22,000, $48,000, and $91,000. They are not the same product, and your spreadsheet will lie to you unless you normalize them.

1. Line up scope, not price. One grid: discovery, IA, content (who writes it, how many pages), design, build, SEO migration, accessibility, QA, training, post-launch. Mark what each proposal actually includes. The cheap one usually has four blank rows.
2. Price the blanks. If content is excluded, that work still exists, you will do it, or pay for it later. Add your own estimate to their number.
3. Compare total cost of ownership. Year one plus two years of hosting, support, and edits. The platform that is cheapest to build is often the most expensive to keep.
4. Weight the team, not the pitch. Who does the work, and what share of their time is yours?
5. Check references your size and shape. A firm that builds for professional services firms understands partner review and long sales cycles. One that builds for nonprofits understands boards and program complexity. Ask past clients one question: what surprised you?
6. Ask every firm the same questions. Different answers to identical questions are the most honest comparison you will get.

The short version

The best partner asks about your business before showing you anything, tells you what is not included, and leaves you owning everything at the end. It may not have the prettiest portfolio. It will have the fewest surprises.

Want a second opinion on the proposals in front of you? Book a website redesign consult and we will read them with you honestly, including when someone else is the better fit. You can also see how we scope website design and development, or how a rebuild fits into a broader digital marketing strategy.

Frequently Asked Questions

What questions should I ask a website design agency? Ask who owns the domain, code, and content when the project ends; how they run discovery; who writes the content; how they handle redirects and preserve rankings; whether accessibility is included and how they test it; what happens in the 90 days after launch; who edits the site day to day; and what is explicitly not in scope. That last one is the most revealing.

Should I hire a freelancer or a website redesign agency? A freelancer is good value for a focused project with one main skill requirement, and you get the person you hired. An agency makes sense when the rebuild needs strategy, design, development, content, and SEO migration together, or when you cannot afford a single point of failure. Match the partner to the complexity, not to the logo.

How much should a website redesign cost? It depends far more on page count, who writes the content, and custom functionality than on design. Rather than chasing a number, normalize the proposals: line up scope item by item, price whatever is excluded, and add two years of hosting and support. A proposal that is dramatically cheaper is usually missing strategy, content, SEO migration, or QA.

What are the red flags when hiring a web design agency? No discovery process, a firm price quoted on the first call, design-only scope with no SEO or redirect plan, no clear answer on accessibility, a proprietary CMS with no export path, no post-launch support, and a portfolio with no outcomes attached. Any one of these is worth a hard question. Two is worth walking.

Who should own my website after the redesign? You should, the domain on your own registrar account, the hosting in your account, and full rights to the code, designs, and content in writing on final payment. The practical test is whether another firm could maintain the site without the one that built it. If not, you are leasing your website rather than owning it.