Website redesign agencies: compare design, URL migration and launch responsibilities

By Studio Swing | Provider information reviewed 25 October 2026

On this page
  1. 01Which redesign provider fits your project?
  2. 02Studio Swing
  3. 03Lounge Lizard
  4. 04Huemor
  5. 05Trajectory
  6. 06Bop Design
  7. 07Give every candidate the same migration example
  8. 08Compare planning, launch and monitoring as separate responsibilities
  9. 09Choose the scope before comparing the quote

Studio Swing publishes this comparison and sells website redesign services. We put ourselves first to make that commercial interest clear. The order is not a ranking. Public service descriptions establish what each provider offers; they do not independently prove delivery quality or results. Fit recommendations below are our editorial judgment.

Choose a redesign agency by asking who will take responsibility for the existing website as well as the new one. Your proposal should cover valuable content, old addresses, the new design, implementation, launch checks and the period after launch. A content transfer, an approved design and a tested URL migration are separate deliverables.

This comparison looks at Studio Swing, Lounge Lizard, Huemor, Trajectory and Bop Design. It is a selected group of useful alternatives, not an exhaustive market survey. The providers differ in scope, and the reviewed alternatives skew towards US businesses. Confirm availability in your country, contracting terms and the required platform before commissioning anyone. Trajectory's public positioning is US-focused; international acceptance is unconfirmed.

Which redesign provider fits your project?

ProviderReason to investigateMigration question to settle
Studio SwingA page-by-page redesign plan with old-address mapping and a baselineWhat tests, recovery arrangements and observation after launch will this scope include?
Lounge LizardBrand and structural change, with design-only or implementation engagementsWho implements and tests the documented migration requirements?
HuemorMessaging, copy, design and development in a coordinated rebuildDoes the migration scope cover old URLs as well as data transfer?
TrajectoryContent-led delivery with redirects and transition planning named at launchWho completes and checks the full old-address inventory?
Bop DesignA B2B WordPress rebuild with content and messaging workCan the proposal establish the migration responsibilities missing from the reviewed page?

For every candidate, ask for a comparable example of the planning and test records you will receive. We have not inspected a completed migration register or independently tested a migration by any provider in this list, including ourselves. The table describes reasons to investigate, rather than verified performance differences.

Studio Swing: decide what stays before changing the website

Our redesign service starts by finding what is holding the website back. If an unclear offer, a broken form or another focused repair explains the problem, we recommend that work. A full redesign should earn its place in the scope.

When redesign is appropriate, we give each page a decision: keep, improve, merge or retire. Our offer includes a page plan, a map of old addresses, a record of key numbers before launch, and a website built to the agreed scope. We check old-address destinations, key pages, forms, search settings, content and links before launch.

The public offer states that your domain and accounts remain yours and that files, logins, Content Management System (CMS) access and documentation are handed over. Third-party licences keep their own terms. Search monitoring and care after launch are separately agreed. Our fictional original concepts demonstrate design thinking; they are not completed client migrations or evidence of preserved traffic.

Consider us when: you want content decisions, design, implementation and old-address planning coordinated in one written scope.

Ask us: which URLs and systems are covered, what evidence will demonstrate the checks, and who handles problems after launch? Request a tested example if migration execution is a decisive selection criterion. This article's fictional register below is an illustration, not that evidence.

Lounge Lizard: migration requirements tied to the engagement

Lounge Lizard's web-design page describes reviewing organic landing pages, URLs, content hierarchy and internal links before structural changes. It documents redirect, canonical and sitemap requirements. Where implementation is included, its launch QA covers crawlability, indexability, canonical tags, sitemap behavior and redirect requirements. Design-only work passes requirements to the implementation team. Lounge Lizard web design.

Consider Lounge Lizard when: a redesign must coordinate brand, multiple audiences and technical requirements, or your development team needs a design handover.

Ask Lounge Lizard: does the proposal cover implementation and testing, or requirements for another team? Ask who signs off the URL map and who owns launch recovery and observation. Contractual ownership, the complete mapping deliverable and support entitlements still need confirmation. A design-only engagement needs a separately named implementation owner.

Huemor: a coordinated rebuild with migration scope to clarify

Huemor's redesign offer combines strategy, messaging, copy, design, development and integrations. The listed deliverables include data entry and migration, technical SEO, analytics and goal setup, editor guidelines, design/development ownership on completion, and two weeks of post-launch support. Those are provider-stated terms to confirm in the proposal. Huemor redesign services.

Consider Huemor when: the website needs coordinated work across its message, content, design and technical build.

Ask Huemor: does data migration include an old-to-new URL register and redirect implementation? Ask about canonicals, sitemap checks, the baseline, test evidence and monitoring. Confirm ownership exceptions, third-party licences, account control and support beyond the initial period. Moving content between systems does not establish what happens when someone follows an old link.

Trajectory: redirects within a content-led launch process

Trajectory describes developing structure and content together, building an editable site and training the client team. Its launch process explicitly names analytics setup, old-site redirects, testing and a transition plan. Trajectory's process.

Consider Trajectory when: content development and an editable business website are central to the redesign, subject to location and project fit. Its company website describes US delivery; buyers elsewhere should confirm availability first.

Ask Trajectory: which sources create the old-address inventory, who decides what stays or merges, and how is every mapped destination checked? Confirm contractual ownership, account access, hosting portability, support and observation after launch. Naming redirects in a process is useful; the proposal must still establish coverage and responsibility.

Bop Design: a conditional option for a B2B WordPress rebuild

Bop Design's service page describes custom B2B design, content, messaging, copywriting and development, with an exclusively WordPress website-design focus. Its process runs from discovery through content and SEO to development and launch. The reviewed page does not establish a migration-specific specification. Bop Design B2B website services.

Consider Bop Design when: you need a WordPress B2B rebuild and content work is a substantial part of the project.

Ask Bop Design: can your proposal specify the old-URL inventory, page decisions, mapping, implementation, destination checks and observation? Confirm ownership, handover and support separately. Until those answers are in scope, treat it as a conditional redesign candidate. An unestablished detail on a reviewed page does not prove the provider cannot supply it.

Give every candidate the same migration example

Consider a fictional engineering consultancy replacing an older website. Two service pages overlap, one useful page needs better writing, a retired event has no replacement, and an existing PDF remains in use. These are invented requirements, not a client project, provider proposal or test result.

Use this register to ask each candidate how its process handles the same decisions:

Existing addressContent decisionExpected destination and behaviorEvidence to request
/services/inspection/KeepSame address, useful page, HTTP 200Response and content check; no redirect to itself
/services/testing/Improve the copySame address, revised page, HTTP 200Confirm address retention alongside content review
/commercial-testing/Merge with testing301 to /services/testing/, then HTTP 200Response, final destination and relevance check
/events/old-open-day/Retire with no useful equivalentHTTP 404 or 410 with helpful navigationActual response status, rather than a message on an HTTP 200 page
/downloads/inspection-guide.pdfKeep the useful documentSame document address, HTTP 200Document opens and internal links still work

The decision to keep or improve content does not require a URL change. A merged page needs a relevant destination. A retired page without a useful equivalent may need a proper missing or gone response. Google's migration guidance covers URL mapping, testing redirects, avoiding irrelevant homepage redirects and checking canonical and indexing settings. It also warns that rankings can fluctuate during a move. Google Search Central: site moves.

For Studio Swing, ask to see the proposed page plan and test record. For Lounge Lizard, establish which team implements the requirements. For Huemor, establish whether the migration includes this URL work. For Trajectory, clarify inventory and check coverage. For Bop Design, establish migration scope before accepting a general rebuild proposal. Each provider should be able to explain how it would resolve the example without promising unchanged rankings.

This register only illustrates address decisions. A real scope may also need product and customer data, image addresses, language versions, old domains, app behavior or third-party integrations. List those separately so the URL map does not become a substitute for the rest of the move.

Compare planning, launch and monitoring as separate responsibilities

A proposal becomes easier to assess when it names a deliverable, its owner and the acceptance evidence. Send the same questions to each shortlisted provider:

ResponsibilityWhat the proposal should establish
Existing-site inventoryWhich pages, documents, address variants and historical sources are covered? Who checks for omissions?
Content decisionsWho approves keep, improve, merge and retire decisions, including relevant replacements?
ImplementationWho configures redirects and updates links, canonicals and the sitemap? Who controls the necessary accounts?
Launch acceptanceWhich checks run on staging and again on the public site? Who records results and fixes exceptions?
MeasurementWhat is recorded before launch, which enquiries or sales actions are checked, and who can access the accounts?
RecoveryWhat is backed up, who can restore it, and how are new submissions or orders handled if recovery is needed?
ObservationWho reviews problems after launch, for how long, and how are findings assigned and resolved?
HandoverWhich files, credentials, records, licences and instructions does the client receive?

A useful baseline describes comparable periods and definitions. If the enquiry form or tracking changes, the provider should explain how that affects before-and-after comparisons. More recorded events alone do not prove more enquiries. Agree which business actions matter and who verifies that they reach the intended destination.

Migration ownership also includes access after launch. If redirects live on an old host or domain, establish who keeps that service available and renews it. Ask how the redirect rules and records move when hosting or support changes. A handover that leaves a necessary account inaccessible creates a practical dependency even if you own the new design.

For a detailed planning sequence, read planning a website redesign. If a site has already launched and visits have fallen, start with traffic dropped after a redesign. That diagnosis is a different buying situation from choosing a new design partner.

Choose the scope before comparing the quote

A visual refresh that retains its pages and addresses may need less migration work than a platform, domain and content restructure. Tell each provider what is changing and what must continue working. Ask it to separate planning, writing, design, implementation, migration, testing, handover and ongoing work in the quote.

If the design is already approved and your team can implement it, a design handover may be sufficient. If the old site has many valuable pages or the move affects a store, ask for a specialist migration plan and comparable test evidence. If a broken form or unclear offer explains the problem, commission the repair that addresses it.

No provider selection removes the uncertainty of search traffic or business results. Choose a team whose written responsibilities, evidence and handover fit the work you actually need.

To discuss Studio Swing's redesign service, share your current website, what is not working and any systems or addresses that must carry over. We agree the scope and quote before work starts.

Discuss your project.