Website Redesign Companies: What to Look For Before You Sign

The single question that separates competent website redesign companies from expensive ones is whether they inventory your existing URLs and their traffic before anyone opens a design tool. A firm that opens with a design concept is selling you a new website. A firm that opens with a crawl export and a Search Console pull is protecting the one you already have. Everything else — portfolio, process deck, timeline — is downstream of that.

Redesigns are the single most expensive way to lose organic traffic, and the loss is almost always introduced before launch by decisions nobody flagged as risky.

The price signal is unusually loud here

Measured in Google Keyword Planner (geo Canada, English, August 2026): website redesign companies gets only 50 searches/month, but carries a top-of-page bid range of $24.17 to $120.64 — the highest cost-per-click in the entire keyword set we pulled for this market. website redesign agency is 70/month. website redesign near me is 1,000/month.

Fifty searches a month and $120 a click means firms are willing to pay roughly $2,400 for a hundred visitors, because a signed redesign contract is worth tens of thousands. It also means the people bidding hardest are, structurally, the people with the largest sales overhead. That's not a reason to avoid them — it is a reason to insist that what you're buying is engineering discipline and not a pitch.

Checkpoint 1: Do they inventory before they design?

A redesign proposal that arrives without any of the following has not looked at your site:

• A full crawl of existing URLs, with status codes
• A Search Console export of pages by clicks and impressions, 12 months
• A list of the pages that actually earn traffic, ranked
• A list of external sites linking to specific URLs

Ask directly: "How many URLs does my current site have, and which twenty get the most organic clicks?" If they can't answer before the proposal, the redesign will be scoped on aesthetics.

For TravelDesign By Lisa, the platform was 834 URLs across three languages. Roughly 2,300 technical defects had to be cleared. You cannot scope that from a screenshot of the homepage.

Checkpoint 2: Is a redirect map a named line item in the contract?

You don't need to know how a redirect map is built. You need to know whether one is a deliverable with your name on it — a document handed to you, in a format you can read, listing every old address and where it now goes.

The vendor-evaluation version of this question is short: "Is the redirect map in the statement of work, and do I get a copy?"

The three answers, ranked:

1. "Yes — it's a deliverable, you review it before we launch." This firm has lost traffic on a migration before and changed how they work.
2. "Yes, the dev team handles that." Possibly fine, but it is not scoped, not reviewable, and not chargeable to anyone if it's wrong.
3. "We'll set up redirects if anything breaks." Reactive. By the time something visibly breaks, the pages have already dropped out of the index.

One tell worth knowing: if a proposal describes the redirect work as pointing "old pages to the new homepage," that's a firm that intends to do it quickly rather than correctly. It reads as a shortcut to Google as much as it does to you.

The mechanics of doing this properly are their job, not yours — how we scope a redesign covers the sequence we follow.

Checkpoint 3: Do they decide keep vs. rebuild, page by page — in writing?

"Redesign" is sold as one decision. It is actually one decision per page, and the difference between firms is whether those decisions are written down where you can veto them.

Ask to see the page-level plan before design starts. Each existing page should be marked keep, rebuild, merge, or retire, with a reason. What you're evaluating is not their taste — it's whether they made the call deliberately or by default.

Named failure mode — content amputation. The new design is cleaner, so a 1,500-word service page becomes 300 words of elegant headline. Google ranked the 1,500 words. It is the failure mode clients accidentally ask for, because the short version looks better in the mockup, and a firm that has been burned by it will warn you before you approve the design. One that hasn't will happily build what you approved.

Second named failure mode — the launch checklist that doesn't exist. Development sites are routinely blocked from search indexing, and the block sometimes travels to production. Ask a single question: "Can I see your pre-launch checklist?" You are not auditing the checklist. You are finding out whether there is one. A firm that has to write it for you is doing your migration as its first.

Checkpoint 4: Is there a before/after measurement plan with dates on it?

A redesign without a baseline is unfalsifiable. Before launch, someone should export:

• GSC clicks, impressions, average position — 12 months, by page and by query
• Core Web Vitals field data for the top templates
• Conversion counts for whatever your conversion is

Then compare the same 28-day window post-launch against the equivalent pre-launch window, with a named review date in the contract. Ask: "What date do we sit down and compare, and what do you do if it's down?" A firm with an answer has done this before.

Performance is part of that baseline and it's measurable rather than arguable. On Lisa's platform, mobile Lighthouse showed CLS of 0.00 and Best Practices at 100 (Chrome Lighthouse, August 2026). On NAVTRL/Stalkr, a client build, 31 routes shipped in 19 days at 98/100/100 with a perfect agentic-navigation score. Those are numbers a client can verify themselves, which is the whole point of quoting them. If you want the mechanics behind those metrics, our Core Web Vitals guide covers them.

What separates firms on the commercial side

| Signal | Reassuring | Concerning | | --- | --- | --- | | Discovery | Crawl + GSC pull before quoting | Mood board before quoting | | Redirect map | Named deliverable, reviewable | "Handled by the dev team" | | CMS | You can edit pages after launch | Edits go through them, billed hourly | | Ownership | Domain, repo, hosting in your accounts | Site lives on their proprietary platform | | Post-launch | Fixed review date, agreed metrics | "Let us know if anything breaks" | | SEO sequencing | Built into the redesign | "We'll do SEO after launch" |

That last row deserves emphasis. "We'll handle SEO after launch" is the most expensive sentence in this industry. Fixing an unmapped URL structure after three months of 404s costs several times what mapping it correctly would have cost, and some of the lost external links never come back.

When a redesign is the wrong purchase

Honestly: often.

• If traffic is fine and conversion is not, you have a messaging and layout problem, and a redesign priced for a full rebuild is a very expensive way to test new copy.
• If the site is slow and dated but structurally sound, website maintenance and a performance pass may get you 80% of the outcome for a fraction of the cost.
• If the real complaint is "I can't update it myself", that's a CMS problem, not a design problem.
• If you're rebranding, do the brand work first. Redesigning around a brand that changes in six months means paying twice.

Our own approach to scoping this is on website redesign, design work generally on web design Montréal, and realistic Canadian budget ranges on website cost in Canada.

Getting a comparable quote

The reason redesign quotes are hard to compare is that they describe different work in the same words. The fix is to make every firm respond to the same written brief: current URL count, top pages, what must be kept, what must be measured, who owns what at the end.

If you'd rather just describe your situation and get that written back to you: stillawake.studio/start. You describe it in writing, you get a written scope in return — no sales call. Use it as a benchmark against the quotes you already have.