For businesses whose current site no longer fits
Website redesign
A redesign should make the website easier to use and maintain without discarding useful content, URLs, or customer paths by accident.
Build your site01
What a website redesign can cover
Wild Logic can review an existing marketing website, plan a clearer structure, design and develop the replacement, and prepare the agreed launch and handoff work. The exact deliverables belong in the written scope.
Existing-site inventory
Identify public pages, content, images, forms, integrations, hosting, DNS, and account owners before deciding what stays, changes, or retires.
Responsive design and development
Rework the information hierarchy and page system for readable, usable phone, tablet, and desktop layouts.
Migration and launch planning
Define URL decisions, redirects, content movement, form and integration checks, account control, launch checks, and handoff responsibilities that are included in scope.
02
See a real project with changing content
Battle of the Buildings shows how an event website can remain useful after the event. Its structure includes results and a recap alongside event information. Austin Brower built the site under Battle Bound Branding LLC; this is an example of a design decision, not a claim of a measured redesign result.
03
Price the redesign around the work
A redesign estimate separates the Website Foundation, pages, and selected features from content preparation, migration requirements, third-party expenses, and any review-required custom work. The planning estimate is not a quote or agreement; we confirm the scope and price together before work begins.
Use the pricing guide to understand the fixed menu, then describe the current site and what must change so the redesign-specific work can be reviewed.
04
Does your site need a redesign or a few repairs?
An outdated service list, a failed form, or a confusing menu may need a targeted fix. A redesign may make sense when the structure no longer fits the business, routine updates are difficult, or customers cannot complete important tasks on a phone.
Where customers get stuck
Try finding a service, reading the price explanation, and contacting the business on a small screen. Record where the task breaks down.
Outdated content
Compare the current offering with the site. Identify obsolete pages, missing answers, and duplicated information.
Updates that are hard to make
List the updates your team avoids because the tools, access, or documentation are missing.
05
Start with discovery and an audit
Bring the current URL, a list of known problems, and the tasks the replacement site must support. Read-only access to available search and analytics reports can help identify pages worth preserving; reports are evidence, not a promise about future traffic.
The planning inventory should cover public URLs, content, images, forms, integrations, hosting, DNS, and account owners. Agree which items stay, change, or retire before agreeing on the scope of the redesign.
06
Move the content with a written URL map
Give every existing page a destination. Keep useful URLs when possible. When a URL must change, map it to the closest relevant replacement and use a permanent redirect. Sending every retired page to the homepage usually fails to answer the visitor's original question.
Update internal links, canonical URLs, and the sitemap to point to final destinations. Preserve important text, page titles, image descriptions, and useful downloads unless there is a reason to change them. Check that staging restrictions are removed from the production pages intended for search.
A migration plan reduces avoidable errors, but it cannot guarantee rankings or uninterrupted search traffic. Check Search Console after launch for crawl errors and unexpected canonical choices.
07
Test the design against real tasks
Responsive design needs readable text, usable controls, and a clear order of information at narrow widths. Keyboard navigation, visible focus, labeled forms, useful image descriptions, and reduced-motion behavior belong in the review.
Run through complete tasks: open a service page, follow a contact link, submit a test inquiry in an agreed test environment, and confirm its destination. Screenshots alone cannot establish that a website works.
08
Define the launch and handoff
Record a backup, rollback approach, launch checks, and who controls each account. Confirm that forms and email delivery still work after DNS or hosting changes. Agree who checks the site after launch and who will maintain it going forward.
Wild Logic keeps build costs, support by request, third-party expenses, and review-required scope separate. Describe your existing site and what needs to change so migration work can be included in the written scope.
Put the plan to work.
Configure a site without sharing your email, or bring your questions to a conversation.