01
Review and prioritise
Start with the current pages, business goal and reported friction. Review available analytics or search data with permission, then separate useful changes from a redesign for its own sake.
Website redesign & migration services
Keep the good. Rethink the rest.
Your business has moved forward. Has your website? Give it a clearer story, a more useful mobile experience and a considered next chapter—without rebuilding the parts that already work.
A fresh perspective. One point of contact.Work directly with Ali, with a clear written scope.
A NEW DIRECTION, WITH A PLANSTUDY / 01
Lumenfold · personal case study
- Review before rebuilding
- A scope you can understand
- Staging before the switch
- A documented handover
THE RIGHT AMOUNT OF CHANGENot every website
Not every website
needs a new beginning.
Website redesign for small businesses starts with a better question: what needs to change, and what should stay?
01Refresh what you haveThe foundation works. The experience needs attention.
Your pages, platform and content are still useful. Focus on the things getting in the way: unclear sections, inconsistent styling, mobile layouts or an awkward enquiry flow.
- Retain the useful structure
- Improve selected pages and journeys
- Test the changes that matter
02Rethink the websiteThe business has changed. The site needs to catch up.
When the editor, navigation and design all pull in the wrong direction, plan a more complete rebuild. Start from the content and routes worth keeping—not an empty screen.
- Inventory pages and useful content
- Agree a new design and editing workflow
- Review a working staging version
03Move to a better fitA platform change, with the details accounted for.
Changing CMS or hosting is more than moving a homepage. Review export limits, media, forms, redirects and account responsibilities, then agree a controlled release.
- Check what transfers and what needs rebuilding
- Map content, URLs and integrations
- Plan the switch and a rollback path
Still deciding? Read when a redesign is worth considering, or review the signs a website journey needs attention.
A COHERENT CHANGE, NOT A COSMETIC PATCHBeyond a new look.
Beyond a new look.
A more useful website.
Design, content and the technical details belong in the same plan. These are the workstreams we can agree together.
02
Structure and content
Keep useful pages and clarify how people find services, proof and contact details. Agree which copy stays, which needs editing and who supplies or approves new content.
03
A clearer visual identity
Bring typography, spacing, imagery and page layouts into one consistent direction. Build responsive interfaces with readable content, accessible controls and an obvious next step.
04
An editable foundation
Rework the existing WordPress build where sensible, or review a new CMS or frontend when the requirements justify it. Editing, plugins and integration compatibility stay part of the scope.
05
URLs and migration checks
Preserve appropriate URLs and map changed pages to relevant destinations. Check redirects, metadata, canonicals, internal links, images, downloads and the sitemap—not just the homepage.
06
Release and handover
Review a protected staging version, agree backups and rollback, and test the important journeys before switching. Confirm the live result and document editing, ownership and follow-up responsibilities.
REDESIGN & SEO MIGRATIONChange the experience.
Change the experience.
Account for every move.
A new design does not require new URLs. Keep the useful ones. When addresses must change, map them to relevant destinations and verify the routes—not just the visual result.
- Inventory important pages, images and downloads
- Check redirects, canonicals and internal links
- Review index settings and the new sitemap
- Agree who monitors issues after launch
A ROUTE FOR EVERY IMPORTANT PAGESAMPLE MAP
KEEP THE ADDRESS
/about/aboutSame URL, refreshed pageMAP THE CHANGE
/old-service/services/new-serviceRelevant permanent redirectREVIEW REMOVALS
/retired-offerNo replacement?An appropriate 404 or 410
A protected preview
Keep staging behind access controls. Noindex is not privacy protection. Use test data and prevent real payments, emails and production webhooks during review.
A way back
Back up files and data, agree the rollback steps, and account for orders or enquiries received during the change. Do not overwrite newer live data with an old copy.
More than the website
DNS, email records, forms and integrations need named owners. A hosting move should not silently replace mail settings or disconnect a business workflow.
Careful planning reduces avoidable migration problems. Rankings can still fluctuate after significant changes; no traffic, ranking or zero-downtime guarantee.
CHARACTER WITH A PURPOSEA direction that feels
A direction that feels
like your business.
Completed personal case studies, presented with representative interface artwork—not application screenshots, client redesigns or measured before-and-after improvements.
Completed personal case study
Make the next step feel obvious.
A completed personal creative-studio website combining an original visual identity with focused service content and a clear project-enquiry journey.
Lumenfold Studio
Completed personal case study
Give a familiar business more character.
A completed personal painting-services website combining original interior artwork, clear service categories and a focused estimate-enquiry experience.
Huefield PaintingMy primary professional experience is WordPress and PHP. These independent projects are separate from agency work; private client code, data and screenshots are not reused.
Meet your developerPrefer actual project screenshots? View the Softora Guide case study.
A BETTER WEBSITE, IN CLEAR STEPSNo disappearing act.
No disappearing act.
A process you can follow.
A written plan, purposeful review points and a working preview. Direct collaboration without a sales-to-development handoff.
See the website launch checklist- 01
Understand the starting point
Share your URL, goals and what is not working. Review the existing content and technical constraints before choosing a refresh, rebuild or migration.
- 02
Plan what changes—and what stays
Agree the page list, content responsibilities, visual direction and any URL or data changes. The scope, quote and review points are written down.
- 03
Build away from the live site
Work through a protected preview, review the design and test mobile layouts and important journeys. Keep real customer email, payments and production integrations out of tests.
- 04
Launch with a checklist
Confirm approval, backup and rollback, then release the agreed changes. Recheck the live site, redirects and submissions, and define who monitors issues afterward.
PRICE THE WORK THAT MATTERSThe right scope.
The right scope.
Then the right quote.
Some websites need a focused refresh. Others need a bigger change. Agree what is included before making the commitment.
A focused refresh
A defined set of improvementsFor a workable site that needs a clearer presentation or a few specific fixes.
- Existing platform and useful pages retained
- Agreed layouts, copy or journey changes
- Checks for the affected areas
A considered rebuild
A complete written project scopeFor a site whose structure, editor or design no longer supports the business.
- Page inventory and content plan
- Responsive design and CMS build
- Staging review, launch and handover
A platform migration
Review the move before the quoteFor a change of CMS or hosting with content, URLs and integrations to account for.
- Source/destination capability review
- Content, media and URL mapping
- Data, DNS and rollback responsibilities
Redesign pricing follows the agreed changes: page count, existing content, design, CMS, integrations and migration work. A written quote defines review rounds, responsibilities, acceptance checks and support. Hosting, domains, licences and other provider charges are separate unless included. A website URL starts the conversation; it is not enough for a final price or a complete technical audit.
BEFORE THE NEXT CHAPTERWhat stays?
What stays?
What changes?
The practical questions about cost, content, search visibility and the switch.
Ask about your existing siteDo I need a full redesign or just a few fixes?
Not every issue needs a rebuild. If your platform and content are useful, targeted layout, navigation, form or performance work may be enough. A broader redesign makes sense when several connected problems cannot be addressed well within the existing structure.
Can you redesign a WordPress website?
Yes. WordPress and PHP are my primary professional experience. That includes Elementor, ACF and WooCommerce. We review what can be reused, plugin compatibility and the editing workflow before deciding whether to refresh the current build or replace it.
Will I lose my Google rankings during a redesign?
Rankings cannot be guaranteed. Keeping useful content and URLs, mapping relevant redirects and checking index settings can reduce avoidable migration problems. Significant changes can still cause fluctuations while Google recrawls and reassesses the site. We agree what to monitor after launch.
Can I keep my domain name and business email?
Usually a redesign can keep the same domain; changing the design does not require changing the name. If hosting or DNS is changing, email records and the responsible provider must be checked separately. Do not replace DNS records without accounting for the existing mail setup.
Can you move my site from Wix, Squarespace or another platform?
A move starts with a review of what the old platform can export and what must be rebuilt. Content, media, forms, URLs, products and integrations have different migration limits. We confirm the destination and practical scope before promising a full transfer.
Can you migrate WordPress to Next.js?
I can review a scoped migration when a custom frontend fits the requirements. Next.js work uses AI-assisted implementation and testing and starts with a technical fit review. A conventional WordPress rebuild can be simpler to maintain; the new stack is not automatically better.
Will the current website stay online while you work?
The usual approach is to build on protected staging while the live site remains available. The final switch is planned around the platform and integrations, with backups and a rollback path. Downtime or uninterrupted transactions cannot be guaranteed without reviewing the specific setup.
Who supplies the copy, images and existing content?
We agree content responsibilities before the build. Existing useful material can be retained or reorganised; new copywriting, photography, licensed assets and large migrations are separate unless listed. You approve business claims and confirm permission to use supplied content.
How much does a website redesign cost, and how long does it take?
The scope determines both: pages, design complexity, content readiness, platform changes, integrations and review rounds. Send your current URL, priorities, target date and budget. A reviewed proposal explains the price, milestones and dependencies rather than a generic fixed deadline.
What happens after launch?
The handover covers agreed files and access, editing notes and the completed checks. Support hours, response targets, exclusions and any monitoring are defined in writing. Ongoing maintenance and new features are separate unless explicitly included; access granted for the project can then be reviewed or revoked.
START WITH WHAT YOU HAVEYour website’s next chapter
Your website’s next chapter
starts with a conversation.
Send the URL and tell me what no longer fits. I’ll review the direction and explain the next step in writing.