Website redesign services should improve the customer journey without breaking useful content, search visibility, analytics or everyday publishing. The safest engagement begins with a current-site baseline, makes explicit keep-change-retire decisions, separates design from engineering responsibility, maps every changed URL and turns launch quality into testable acceptance criteria.
The short answer: redesign the system, not only the screens
A website redesign affects more than the home page. It can change navigation, content, conversion paths, templates, forms, integrations, tracking, search signals, accessibility and the way your team publishes after launch. A polished visual direction can still fail if an important service page disappears, a form stops sending leads, the mobile menu traps keyboard users or the new CMS makes routine updates harder.
Treat the work as a controlled change to a live business system. Define the business problem first, preserve what already performs, prototype the highest-risk journeys, give every page and URL a decision, and assign an owner to each launch dependency. The provider should make those decisions visible before multiplying the design across dozens of pages.
Decide whether you need a refresh, redesign or rebuild
Teams often use redesign as a catch-all word. The delivery model changes sharply depending on whether the structure and technology remain sound. Diagnose the constraint before requesting a quote. Otherwise, one provider may price a visual reskin while another prices research, content, development, migration and launch support, making the proposals impossible to compare.
| Current problem | Likely response | What should stay stable |
|---|---|---|
| Brand or visual layer feels dated | Focused visual and component refresh | URLs, content structure, functionality and analytics |
| Navigation and page journeys confuse buyers | Information architecture and UX redesign | Valuable content, ranking URLs and working integrations |
| CMS or front end blocks publishing and performance | Rebuild or replatform with migration | Business logic, data, search equity and measurement |
| One campaign needs a clearer conversion path | Dedicated landing page | The wider site unless evidence supports broader change |
| Offer, audience or positioning has changed | Strategy, messaging and redesign | Proven assets that still serve the new direction |
Create a baseline before anyone redraws the home page
Capture the current state while it is still observable. Export crawlable URLs, page titles, metadata, canonicals, status codes, internal links, sitemap entries, top landing pages, organic queries, conversions, form paths, analytics events, integrations and important downloads. Add mobile behavior, page speed evidence, accessibility issues, support questions and the content your sales team uses most often.
- Business goal, audience and primary action for each important journey.
- Current URL, content owner, traffic or business value and intended decision.
- Forms, payments, search, CRM, consent, email and other integrations.
- Templates, components, breakpoints and recurring content types.
- Search Console, analytics, tag manager, domain, hosting and CMS ownership.
- Accessibility target, browser and device support, privacy and security constraints.
- Known technical debt, campaign deadlines, content freezes and launch dependencies.
Turn the content inventory into explicit page decisions
Give every current page one status: keep, improve, merge, redirect or retire. Then record its target audience, search intent, primary action, evidence, owner and destination URL. This prevents teams from treating migration as copying old paragraphs into a new template, but it also protects useful pages from being deleted because they look less important in a design review.
| Decision | Use it when | Required control |
|---|---|---|
| Keep | The page already serves its audience and purpose | Preserve URL, intent, core content and measurement |
| Improve | The intent is valid but clarity or conversion is weak | Document what changes and the expected user outcome |
| Merge | Several pages compete for the same job | Choose one useful destination and consolidate evidence |
| Redirect | A URL changes or content moves | Map the old URL directly to the closest relevant new URL |
| Retire | The content has no continuing user or business value | Confirm links, campaigns, files and support references are handled |
Protect search visibility with a URL migration plan
Keep valuable URLs when their purpose remains the same. When a URL must change, map the old address to the closest relevant new destination and use a server-side permanent redirect. Google's current site-move guidance recommends preparing the new site, building an old-to-new URL map, implementing redirects, updating canonicals and internal links, submitting the new sitemap and monitoring both old and new URLs.
Do not send every retired page to the home page. Google notes that irrelevant bulk redirects can be treated as soft 404s. Avoid redirect chains, update links to point directly to the final destination, carry required structured data and metadata forward, remove temporary noindex rules at launch, and test robots rules before the release. Keep the redirect register after launch so future teams know why each route moved.
A redesign should make intentional changes visible. Hidden URL, content and tracking changes are where launch risk accumulates.
PitchWorx website-redesign principle
Design journeys, components and responsive states together
Start with the pages that contain the most uncertainty or business value: the home page, primary service or product page, pricing, a proof page, a content template and the main conversion flow. Use real content. Show default, hover, focus, error, empty, loading and success states where relevant. Include mobile navigation, long labels, tables, media, forms and consent patterns before approving a component as reusable.
| Area | Design evidence | Launch test |
|---|---|---|
| Navigation | Priority journeys, labels and responsive pattern | Keyboard, touch, current state and deep-link behavior |
| Content | Real headings, proof, media and long-copy cases | Migration completeness, hierarchy and ownership |
| Forms | Labels, help, errors, success and consent | Submission, routing, analytics and recovery |
| Components | Variants, states, spacing and content limits | Cross-browser behavior and CMS authoring |
| Performance | Media budgets and interaction choices | Representative page measurements on production |
| Accessibility | Contrast, focus, reflow and semantic intent | Automated checks plus manual keyboard and screen-reader review |
Make accessibility a design and implementation requirement
Choose an accessibility target in the brief and name who tests it. The W3C WCAG 2.2 quick reference states a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text at Level AA. Its reflow criterion expects ordinary content to remain usable at a width equivalent to 320 CSS pixels without two-dimensional scrolling, apart from content such as complex data tables that genuinely needs it.
Separate visual design, development and launch ownership
Ask every provider to mark each responsibility as included, client-owned, partner-owned or excluded. Visual design, UX research, copywriting, CMS architecture, front-end development, backend work, integrations, content entry, redirects, analytics, accessibility testing, hosting, security, deployment and post-launch support are different workstreams. A vague promise to deliver a website leaves the highest-risk boundaries unresolved.
Current provider pages illustrate the difference. ManyPixels says its web service delivers responsive, developer-ready Figma files but does not include UX research, prototyping or coding. PitchWorx can design responsive marketing pages and continue into development for eligible marketing surfaces. Custom backend engineering, hosting, complex integrations and production infrastructure require separate scope or the client's technical team. Confirm the exact boundary before work starts.
- Who owns discovery, audience evidence, sitemap and user-flow decisions?
- Who writes, supplies, migrates and approves page content and metadata?
- Who builds components, templates, integrations and CMS fields?
- Who creates, implements and tests the redirect map?
- Who validates forms, consent, analytics events and lead routing?
- Who controls domains, DNS, hosting, deployment access and rollback?
- Who fixes defects after launch, for how long and under what service level?
Use a staged approval and launch sequence
- Approve the problem statement, audiences, measures and current-site baseline.
- Approve the content and URL inventory with keep, improve, merge, redirect or retire decisions.
- Approve the sitemap, key journeys and content model before high-fidelity visual production.
- Test the design system on representative pages, mobile states and difficult content.
- Build or hand off components with documented states, CMS fields and acceptance criteria.
- Populate real content and complete redirects, metadata, analytics and integration work on staging.
- Run content, functional, browser, mobile, accessibility, performance and search QA.
- Freeze changes, back up the current site, confirm rollback and assign one launch decision owner.
- Release, run immediate smoke tests, submit the sitemap and monitor errors, leads and search behavior.
Do not let a calendar date become the only definition of ready. The launch gate should list critical pages, forms, payments, navigation, search, downloads, redirects, canonicals, robots rules, sitemap, analytics, consent, accessibility checks, backups and rollback. Record the expected result and the person authorized to accept it. Defer launch if a critical route has no owner or recovery plan.
Monitor the redesigned site after release
The first production review should happen immediately, not at the end of a reporting month. Crawl the live site, test priority redirects and forms, inspect analytics events, check canonical and robots output, review the sitemap, verify important structured data, and compare the baseline with live behavior. Watch server errors, missing assets, broken links, indexing changes and lead quality as well as headline traffic.
Compare website redesign prices only after normalizing scope
Page count alone does not price a redesign. Cost changes with research, content, templates, integrations, CMS work, migration, languages, accessibility, testing and support. Huemor's current first-party cost guide publishes $10,000 to $40,000 for freelancer-led work and $50,000 to $250,000 or more for specialized agencies. Those are that provider's planning ranges, not a universal market average or a quote for your site.
PitchWorx Creative Assist is currently $699 per month with two active requests, unlimited queued requests and revisions, unlimited team members, editable source files where applicable, stock images and icons, senior review on every output, no long-term contract and cancellation at any time. The web design subscription cost guide explains the model and scope boundaries. Most everyday requests target about 72 hours. A multi-page redesign should be sequenced into discovery, representative templates, components, page production and QA rather than treated as one everyday request.
The subscription can suit teams that already own business strategy, content decisions and technical access, and need ongoing design plus eligible marketing-page development. It may not replace a specialist engagement when the work requires deep user research, a complex replatform, custom backend engineering, high-risk integrations, security architecture or continuous hosting operations. Compare the same workstreams, owners and acceptance tests before comparing prices.
Questions to ask a website redesign provider
- What evidence will you collect before recommending structural changes?
- Which pages, templates, content types, languages and breakpoints are included?
- How will you preserve useful URLs, content, metadata, internal links and structured data?
- Who owns copy, content entry, redirects, analytics, development and deployment?
- Which component states and responsive cases will the design system cover?
- What accessibility target and manual test process will you use?
- How will forms, integrations, consent and analytics be tested end to end?
- What editable files, code, licenses, documentation and training will we receive?
- What is the launch, rollback and post-launch defect process?
- Which exclusions or third-party costs could change the schedule or price?
Website redesign launch checklist
- Business goals, audiences and priority journeys have measurable acceptance criteria.
- Every current URL has a keep, improve, merge, redirect or retire decision.
- Priority content, proof, metadata, internal links and downloads are accounted for.
- The sitemap and navigation work for users, search and everyday publishing.
- Representative pages cover desktop, mobile, long content and interaction states.
- Forms, integrations, analytics, consent and lead routing pass production-like tests.
- Accessibility checks include manual keyboard, focus, reflow and content review.
- Redirects, canonicals, robots rules, sitemap and structured data are ready and tested.
- Domains, DNS, hosting, deployment, backup and rollback have named owners.
- The team receives editable files, component guidance, credentials and update instructions.
- Launch-day smoke tests and post-launch monitoring have owners and response thresholds.
Website redesign services FAQs
What do website redesign services include?
A complete engagement may include a current-site audit, analytics and search baseline, audience and journey work, content inventory, information architecture, wireframes, responsive visual design, a component system, copy or content migration, development, redirects, analytics, accessibility and performance testing, launch and support. Providers package these differently, so the proposal should mark each workstream as included, client-owned, partner-owned or excluded.
How much do website redesign services cost?
Cost depends on scope, not the redesign label. Page and template count, research, copy, CMS work, integrations, migration, languages, accessibility, testing and support all matter. Supplier-published ranges vary widely because the work is not equivalent. PitchWorx Creative Assist is currently $699 per month with two active requests, while complex engineering or infrastructure may require a separate quote or specialist team.
How long does a website redesign take?
Timing depends on content readiness, decision access, number of unique templates, development scope, integrations, migration risk and testing. Ask for milestones covering baseline, inventory, information architecture, representative designs, components, build, population, QA, launch and monitoring. A visual refresh can move faster than a content-heavy replatform. Fast screen delivery is not the same as a safe live launch.
Will a website redesign hurt SEO?
A redesign can create search risk when valuable content, URLs, metadata, internal links, canonicals, structured data or crawl access change without a plan. Preserve useful URLs where possible, map every necessary change, implement direct permanent redirects, update internal links and the sitemap, and monitor Search Console and analytics after launch. Some temporary fluctuation can occur during a significant move as Google recrawls the site.
Should we keep the same URLs during a redesign?
Keep a URL when the page's purpose and content remain materially the same and the address still works. Change it only for a clear information-architecture, platform or consolidation reason. When it changes, map the old URL directly to the closest relevant new destination, update internal links and canonicals, avoid redirect chains and keep the mapping as a maintained launch record.
Does website redesign include development?
Sometimes. Some providers deliver visual files only, while others include front-end build, CMS work, integrations and deployment. PitchWorx can continue approved marketing-page designs into eligible development work. Custom backend engineering, complex integrations, hosting and production infrastructure need separate scope or the client's technical team. Require written ownership for design, code, content entry, redirects, testing and launch.
What should we provide to a redesign partner?
Provide business goals, priority audiences, analytics and Search Console access, current URL and content exports, conversion paths, brand files, legal and compliance requirements, integrations, technical constraints, device and browser needs, accessibility target, examples, deadlines and named owners. Also share what already works. A redesign brief should protect valuable evidence, not only list what stakeholders dislike.
What files and access should we receive at handoff?
Request editable design files, component and content guidance, image and font licenses, export assets, source code where included, repository and deployment access, CMS credentials, domain and analytics ownership, redirect register, test results, environment notes, backup and rollback instructions, training and a known-defects list. No essential business account should remain accessible only through the provider's login.
One subscription does all of this
A redesign creates a connected production queue: inventory findings become new page structures, structures become responsive templates, templates become reusable components, and launch needs graphics, presentations, campaign assets, social creative and follow-up pages. PitchWorx keeps that work moving under Creative Assist for $699 per month with two active requests and senior review on every output. Start with the highest-risk page template and its migration checklist. Explore the web design service.