Interface and experience
Layouts, navigation and hierarchy reworked so the page reads clearly and the next step is always obvious.
Website redesign — Nepal
Website redesign from Nepalfor global businesses.
Soft Himalaya rebuilds dated websites into faster, clearer and more accessible ones — without losing the search visibility you already have. We work with teams in Nepal, the UK, Australia, the USA and Canada.
- Search migration planned
- Redirect mapping prepared before launch
- Measured speed
- Judged against Core Web Vitals, not adjectives
- Mobile-first
- Rebuilt for the devices your visitors use
- Global delivery
- Nepal, UK, Australia, USA and Canada
- Audit before opinion
- Audit before opinion
- Search value carried over
- Search value carried over
- Evidence over adjectives
- Evidence over adjectives
- Support after launch
- Support after launch
Where to start
Signs a redesign is worth considering.
Not every site needs rebuilding. These are the patterns that usually mean the current one is holding the business back rather than helping it.
- 01
The interface looks its age
Cluttered layouts, inconsistent spacing and dated graphics undercut credibility before a visitor reads a word.
- 02
Pages take too long to appear
Slow first loads are one of the most common reasons visitors leave before the content finishes rendering.
- 03
Mobile is an afterthought
Small tap targets, illegible text and awkward wrapping matter, because most traffic now arrives on a phone.
- 04
Traffic arrives but nothing happens
Visitors land and leave without enquiring. Usually the calls to action are unclear, buried or absent.
- 05
Search visibility is slipping
Missing structured data, weak internal linking and poor mobile handling all work against your rankings.
- 06
The site is hard to update
If publishing a page requires a developer, content goes stale — and a stale site steadily loses ground.
Our approach
What a redesign actually covers.
A redesign is not a new coat of paint over the same structure. These are the six areas we work through on a full rebuild.
Search structure
Sitemap hierarchy, metadata, canonical URLs, structured data and a 301 redirect map from every existing address.
Performance
Modern build output, right-sized images and a reviewed loading order, measured against Core Web Vitals.
Mobile behaviour
Grids that stack predictably, tap targets sized for thumbs, and layouts checked across real device widths.
Conversion paths
Journeys mapped end to end, with calls to action placed where intent is highest and form friction reduced.
Brand consistency
A typography scale, colour tokens and iconography applied consistently instead of page by page.
Before and after
What changes underneath.
The visible design is the part people notice. These are the structural differences that decide whether the new site performs better than the old one.
- Build
- Before: Theme or page builder carrying plugins the site no longer uses
- After: A compiled Next.js build that ships only the code each page needs
- Images
- Before: Full-size uploads served at whatever dimensions the browser requests
- After: Responsive sizes and modern formats, lazy-loaded below the fold
- Layout
- Before: Desktop layout squeezed down, with tap targets sized for a mouse
- After: Designed at mobile width first, then opened up for larger screens
- Search
- Before: Metadata filled in per page, with no structured data or redirect plan
- After: Generated metadata, JSON-LD, canonical URLs and a mapped 301 table
- Content edits
- Before: Copy changes require a developer and a deployment
- After: Editable content areas, so your team can publish without waiting
- Measurement
- Before: Analytics installed but unused, with no view of what converts
- After: Events defined for the actions that matter, reported after launch
Process
Eight steps from audit to launch.
Redesigns go wrong when the rebuild starts before anyone has measured the original. This order exists to prevent that.
- 01
Audit the current site
We record how the existing site performs — layout issues, drop-off points, device breakpoints and Core Web Vitals — so later decisions rest on measurements rather than impressions.
- 02
Research how people use it
Analytics and journey mapping show which paths matter, which pages earn traffic, and where visitors currently give up.
- 03
Design the interface
A design system and page layouts in Figma, shared as an interactive prototype so you can walk the flow before any code is written.
- 04
Plan the URL and redirect map
Every existing address is mapped to its new destination and 301 redirects are prepared. This is the step that protects the rankings you already hold.
- 05
Build the site
Next.js App Router and Tailwind, written as semantic, accessible markup with server rendering where it benefits the page.
- 06
Tune performance
Image handling, bundle size and loading order reviewed and re-measured, with the trade-offs behind each change explained.
- 07
Test and check accessibility
Cross-browser and responsive checks, plus keyboard navigation and WCAG AA contrast verification before anything ships.
- 08
Launch and verify
Deploy, confirm redirects resolve, submit sitemaps, watch Search Console for crawl errors, and report on the first weeks of live data.
The stack
What we build with.
We pick the stack to suit the project rather than the other way round. This is what we reach for most often on a redesign.
Frontend
Pre-rendered output so pages arrive quickly and stay interactive.
- Next.js 15 (App Router)
- React 19 server components
- Tailwind CSS v4
- TypeScript
Backend and data
Only where the project needs it — not every redesign does.
- Node.js / Express
- Laravel
- PostgreSQL / MongoDB
- REST and GraphQL
Measurement
The tools we use to check the work rather than assert it.
- Lighthouse
- Core Web Vitals field data
- Bundle analysis
- Cross-browser testing
Search and analytics
Set up during the build, not bolted on afterwards.
- JSON-LD structured data
- Generated metadata routes
- Google Analytics 4
- Search Console
Deliverables
What you receive.
Everything below is agreed in the scope before work starts, so there is no ambiguity about what lands at the end.
Design system and source files
Layered Figma files with colour tokens, a typography scale, component states and responsive mockups — yours to keep.
A responsive front end
Layouts verified across phone, tablet and desktop widths, with tap targets and reading sizes checked on real devices.
Search migration package
The 301 redirect table, metadata, XML sitemap and structured data (Service, FAQPage, Breadcrumb) applied and submitted.
Performance report
Before-and-after audit results for the pages that matter, with the remaining trade-offs written down rather than hidden.
Conversion paths
Calls to action, forms and navigation arranged around the journeys identified in research, with events defined for each.
Analytics and handover
GA4 configured with meaningful events, plus source code, access details and documentation for whoever maintains the site.
Pricing
Starting points, not fixed quotes.
Every redesign differs in page count, integrations, content and migration work. We review the current site and provide a written estimate for the agreed scope.
Marketing site refresh
For a small site that needs a clean, modern and properly responsive presentation.
- Up to 6 layout pages
- Next.js 15 App Router build
- Tailwind CSS v4 styling
- Metadata and sitemap setup
- Google Analytics 4 configuration
Full website redesign
Common scopeFor corporate sites and portfolios where search visibility and conversion both matter.
- Up to 15 layout pages
- Custom Figma UI and prototype
- Core Web Vitals tuning
- JSON-LD structured data
- 301 redirect mapping from existing URLs
- WCAG AA accessibility audit
- Lead capture forms
Complex migration
For platforms, stores and multi-system sites where a migration sits alongside the redesign.
- Unlimited page components
- UX research and persona work
- Content management system
- Custom analytics dashboards
- Iterative refinement rounds
- Interactive prototyping
- Legacy content and data migration
- Weekly engineering updates
Working together
A clear delivery relationship.
We do not publish anonymous quotes or invented percentage gains. These are the standards we hold ourselves to on every redesign instead.
A documented scope
Pages, features, integrations, responsibilities and milestones are agreed in writing before the rebuild starts.
Visibility while it matters
You review work at agreed milestones, so feedback arrives while decisions can still change the outcome.
A safe migration
Redirects, metadata and content are checked against the old site before launch, and monitored in Search Console afterwards.
Honest reporting
We report what the audits and analytics actually show after launch, including the parts that still need work.
Questions
Website redesign FAQs.
Start here
Tell us about the site you have.
Send the details below to open a pre-filled email. You can also reach us directly at info@softhimalaya.com.
- A review of the current site and what it is costing you
- Questions that help define the scope honestly
- A written next step if the project is a fit