I have spent some time networking over the past couple of years and I keep having the same conversation, they happen so often that I am starting to keep count.

These conversations are all with founders, marketing leads and managing directors across completely different sectors and all of them say we get our new business through referrals and networking and the website is just there so people can check we are real and credible.

And I get it. I understand why they think that. Because that is how it has always worked for them and when something works you do not question it. Someone introduces you, the prospect has a look at your site, they see that you have a proper business with real people behind it and then they pick up the phone. The website did not sell anything. It just confirmed what somebody else already told them.

The thing that surprises me is that these are not small companies, these are established businesses turning over millions of pounds every year, they have offices, they have teams sometimes in the hundreds and they have been around for years. 

But their entire new business pipeline depends on either the senior leaders spending endless time in breakfast meetings or evening drink networking and whether someone they already know happens to mention them to someone at the exact moment they need it. That is not a strategy that is hope.

What I find even more interesting is that most businesses do not measure the real cost of it such as the hours spent at networking events, the coffees, lunches and evening drinks, the lost time and the follow ups that do not go beyond the first conversation. If you sat down and worked out how much each new client costs you through referrals and networking compared to what a website that converts strangers could produce for you, I suspect that the reality of those numbers would be uncomfortable.

I am not saying referrals are bad for business or even the wrong strategy, referrals can be the best converting leads when they come in, all that I am saying is that if referrals are your only lead source channel then your growth is obviously capped at the size of your network and the generosity of the people in it. 

The problem is not that these businesses are doing networking it’s their mind-set that extends throughout the entire culture of the business which also includes their website that only works as the last step in their overall lead generation process. Their site is a validation tool when it should be a lead generation tool. I believe that It should be the thing that starts the relationship and not the thing that confirms it after someone else did all the work.

That is what we built at Ronins and it is the same approach I used at my previous agency where it was the commercial engine behind scaling from two million to twenty two million in six years. Every service page is a self contained landing page designed so that a complete stranger lands on it from Google, sees everything they need to know, and gets in touch. 

In my scenario the website does the networking for us, and the stranger makes the first introduction leaving our role to be the most intelligent and charming agency in the room to convert them from visitors into clients.

When I say every service gets its own web page I mean that literally. If you look at the Ronins site right now you will find a separate page for every single service we offer and each one of those pages is designed to do one job which is to take a complete stranger who just typed something into Google and give them every reason to get in touch before they click the back button.

The way most websites work is that someone lands on the homepage and then they have to figure out where to go next. They click into services, they click into a sub page, maybe they find something relevant and maybe they don’t and somewhere along that journey they either find what they were looking for or they give up and leave. 

That is how many websites are designed and developed and I think it is the single biggest reason why so many businesses do not get organic traffic to their site and as a result get almost no enquiries from anyone who does not already know them. The site is trying to tell a story with confusing navigation, unstructured user journeys is enough to frustrate users

What we do at Ronins is treat each service page as its own mini microsite. Someone searching for “AI consultancy” lands directly on our AI consultancy page. Someone searching for “WordPress agency” lands on a completely different page dedicated to the search intent with completely different case studies and completely different copy because they are completely different people with completely different problems. They never see each other’s pages and they do not need to because everything they need is right there on the one they landed on. Each page is built for a specific target audiencewith its own layout, its own images and its own proof points.

These visitors have never met anyone who has worked with our brand, never heard about us before, so we have to make that page work hard with our subject matter expertise, clear visual case studies and social proof this is not our first rodeo. This landing page needs to drive engagement, be clear in its messaging and offer intuitive ways of making contact without visitors having to search for it.

When someone lands on our web design page and sees that we restructured the entire Montreaux Homes website around how property buyers actually experience their homes, the site started converting better because of it, or they land on a page with a case study that reads that we found in a prospectus “the most exciting school in England” and used it to reshape the entire brand strategy, those stories do something that a capabilities section or a list of services never will. 

They leave the stranger with a feeling that these people have done this before and they understand what the issues I am dealing with. That is a better user experience than any amount of visual appeal or design elements could produce on their own.

Yes and before you say it, I know that the bounce rate conversation is rearing its ugly head, it always does but it’s a made up stat that I don’t believe in and our bounce rates on individual service pages are higher than what most people would consider healthy for a website. But that metric is misleading when the page is designed to be self contained and drive conversions as people land on one page with a specific search intent and showing them a different search intent feels wrong, 

The conversion rate from our pages is higher than most websites we see and we do a lot of CRO and SEO work for clients to achieve high search engine ranking. So high bounce rates do not automatically mean a poor user experience, sometimes they mean the page did exactly what it was supposed to do.

This is not something I invented at Ronins either. I used exactly the same approach at my previous agency and it was the single biggest reason we were able to scale from two million to twenty two million in revenue over six years. Every service had its own page, each page ranked for its own keywords in the search engine results, each page attracted its own strangers and converted them into clients who had never heard of us before they searched. When I sold that agency and started Ronins I did the exact same thing again because I already knew it worked and now I am watching it work a second time with a team of five people and no networking budget. Our website does the lead generation and we focus on being professional enough to close.

I get asked this a lot and the answer is simpler than people expect. A stranger will get in touch if they believe three things by the time they reach the bottom of the page. They need to see that you understand their problem and that you have solved it before, and lastly do you make it easy for them to make contact.

Most websites suffer from one or more of these, The copy tends to talk about the business instead of talking about the visitor’s situation. Then the case studies are all about the implementation not the business problem they solved and the contact form is buried on a separate page to confuse users and even then you have to prove your human with a CAPTCHA statement before you are even allowed to say hello.

For us at Ronins every service page follows the same structure and is designed this way deliberately. The first thing you see speaks directly to the search intent and then the situation which brought them there in the first place. We take the stance that if someone lands on our web design page they are not interested in hearing about our design process or our tools or how many years we have been in business. They want to know that we understand why their current website is not working and that we have fixed their problem before.

We ensure our case studies do the heavy lifting. I have already mentioned Montreaux Homes and Hurtwood House but every page across the site has its own set of case studies that are specific to that service and that target audience. The case studies are there to remove doubt and gain trust as we believe that a stranger reading about a project we delivered in their sector or with their kind of challenge starts to become curious at this point because they can see themselves in the story. That is what I believe builds trust and confidence with visitors, it’s not the design elements, a poor website design, visual appeal or a visually appealing homepage with a video that autoplays, they play a part but the users have to see we understand them more.

Then lastly across all our service line pages, I place the contact form at the bottom. It should be located on the samepage as the content as the moment someone decides they want to talk to you there should be seamless user experience between that decision and the action we want them to take. With every extra click you put between a visitor and a contact form is a chance for them to change their mind and I have seen enough session recordings and Google Analytics data over the years to know that happens, they decide to get in touch, they click to the contact page, something distracts them and they are gone. On a self contained landing page that does not happen because the form is already in front of them.

Responsive web design is important and I am not talking about whether the site is engaging on a mobile devices across different screen sizes. Its not just about how the site renders it’s also the user experience, this article is a long one and its a hell of a commitment to ask people in responsive design on a mobile phone to scroll for what feels like forever to get the end. We test mobile responsiveness across various screen sizes as a large percentage of the website visitors who find us through search engines are on their mobile phones.

The whole point is that I see website success is when a stranger should be able to land on a single page, understand that you know what you are doing, see proof that you have done it before and get in touch without any hesitation. If your website cannot do that for them then it is not a lead generation tool it is a brochure and you are back to relying on networking to fill your pipeline.

I have lost count of the number of businesses who come to us after spending a significant amount of money on a website redesign with web designers or web developers that did not change anything commercially. 

Yes the website looks better than it did before, yes the photography is nicer and the fonts are more modern and someone has added some animation and parallax scrolling. But after launch the enquiries are exactly where they were before and the agency cannot explain why.

The redesign changed how the website looked without changing what the website performed. 

I often see this with clients who come to us after a previous agency has already had a go and I see it when I talk to businesses at events who tell me they had their site redesigned last year and it has not made any difference. The website looks beautiful and it does not do anything. That is bad website design dressed up as good website design and it is everywhere. These are poorly designed websites not because they are ugly but because they were created without a commercial strategy behind them. The design problems are invisible to anyone who is only looking at how the site looks rather than what it does for users.

We are working with Korda at the moment who are the biggest fishing tackle wholesaler in the UK and Europe. Their site is functional and their brand is strong but nobody on the board could point at the website and say what that investment returned. It’s currently seems as a cost centre that everyone tolerates because that is what that website is supposed to be apparently. We are not redesigning, we are reshaping what the site could actually become and ultimately become a high performing business asset.

When I was at my previous agency we worked with Weber Shandwick who had sixteen separate WordPress websites across EMEA. Each office had created their own website independently with their own interpretation of the brand design and their own unique content. This leads to the costs of maintaining sixteen WordPress instances with no head office governance, no web accessibility guidelines or approved media libraries and content. We built a shared digital platform with components and multilingual content workflows and launched it within six months and it eventually grew to twenty four sites,

The problem was never that the individual sites looked bad, the problem was that nobody had look at the larger commercial picture and designed the system for every part of the business.

That is what I mean when I say web design is broken, It’s not that people are building ugly websites with bad website design elements. It is that the entire approach to web development starts in the wrong place. The conversation starts with what should it look like and what pages do we need when it should start with what does this site need to do commercially and how do we structure it so that strangers can find it through search engines and convert on it. If you start with the second question the design follows naturally.

If you start with the first question you end up with a site that looks great and performs like a brochure.

There is a simple way to work out whether your website is a lead generation tool or a digital business card and it takes about ten minutes in Google Analytics.

We look at where your traffic is coming from, and if the majority of your visitors are arriving through direct traffic and referrals that means people are typing your URL in or clicking a link someone sent them. They already know who you are. Your website is not finding new people it is confirming you exist for people who were already told about you. If organic search for your service lines is a small percentage of your overall traffic then strangers are not finding you and your website is not doing any commercial work on its own.

Then look at what happens when people land on your service pages. If you have got pages dedicated to the things you sell and nobody is landing on them from search engines then those pages are invisible. 

User behaviour is where it gets really interesting and this is something I would not encourage anyone reading this to spend time on, instead install a session recording tool if you do not have one already and watch what your users actually do on your site. have sat through hundreds of session recordings over the years across our own site and client sites to gain valuable insights and the gap between what businesses assume their visitors are doing and what they are actually doing is huge. 

User feedback is the other thing that most businesses never collect. You do not need a survey, just pay attention to what people say when they do get in touch. If every new enquiry starts with “I was referred by” and nobody ever says “I found you on Google or in the AI search engines” that tells you everything you need to know.

We went through exactly this process with Catch. When we built their platform we created a digital strategy that fisheries would link back to their Catch listings and over time that meant two things happened at once. The website started to build up enough authority through those backlinks that it started ranking above the individual fisheries in search engine rankings and at the same time every new fishery that signed up brought their own audience with them. Their traffic started to grow organically year after year because the digital strategy was the growth engine and through targeted improvements to the optimisation we were able to build a sustainable business for them.

I have built two agencies now and what’s been consistent across both of them is the belief that the website should start a relationship.

At Ronins we are a specialist boutique agency and do not have a dedicated business development team or anyone whose job it is to go to networking events and hand out cards and follow up with coffees. We still do this but it’s an add on to our job and we love the social side of this as much as anyone. 

Every single day strangers are finding our service pages through search engines, reading the case studies, seeing the work we have done for clients like them and getting in touch. Our job at that point is not to sell, it is to listen and be consultative and the easiest people to work with.

That is what I mean when I say the client makes the first move, we are not chasing anyone we are not cold emailing and we are not tapping up our mates for referrals. We thrive on the warm inbound from a complete stranger and it is the most valuable kind of lead a business can get because the person on the other end already believes you can help before you have even spoken to them.

I know there are people reading this who will say that their business is different and it wont work for them, oh boy how many times do I hear that story, That’s fine you don’t have to adopt this approach I’m happy to pick up the clients you are leaving on the table.

The relationship still matters and the human conversation is still super important, I am just saying that for me there is a better way to get to that conversation started than spending three evenings a week at networking events hoping the right person is in the room.

The businesses I have been talking to all year who tell me that their website is just for credibility are leaving this entire channel switched off. And every day it stays off a competitor who has worked this out is picking up the visitors and the enquiries and the clients that they will never even know they missed. You cannot measure what you never had but I can tell you from twenty years of doing this that the number is bigger than most people would be comfortable knowing.

If your site is only working when someone has already been introduced to you then your web design is not broken because it is ugly or outdated, It’s broken because it’s not a working asset helping you grow your business.

If someone handed me a business tomorrow with no website and no clients and told me to build it from scratch I would do exactly what I have done twice before. Yes I would still attend a few networking events as I would have time on my hands but I spend a lot of my energies in getting my favourite lead generation source working.

If you have read this far and you are thinking that sounds like our website then you are probably right. The good news is that it does not take a full rebuild to start fixing it and the even better news is that once you see the first enquiry come in through Google you will never look at your website the same way again.

Let’s Talk

Mobile devices dominates modern life. In the UK, the average person spends over three hours a day on their phone, most of that time inside apps. From social feeds to shopping baskets, mobile apps shape how we live, work, and buy.

But here’s the catch: while usage is higher than ever, so is the competition. App stores are saturated. Discovery is hard. Retention is even harder. And the average user spends 80% of their time in just a handful of favourites. App fatigue is real, and getting fiercer.

Still, I regularly meet founders and marketing leads who feel pressure to “have an app” because their competitors do, or because it signals innovation. But that’s rarely enough. A mobile app can be a brilliant asset, but only when it solves a specific problem, fits into people’s daily habits, and earns its place on a crowded home screen.

Im my career, I have built mobile apps that quite literally save lives (Grdian), support people with mental health issues (AiME), and reinvent how people engage with sport, retail, or smart devices. But we’ve also told ambitious founders notto build, because the value case wasn’t clear enough. We don’t chase launches. We chase outcomes.

This guide is the conversation I wish more businesses had before investing five or six figures. It explores where apps win, where they fail, and how AI is reshaping the space. It’s grounded in UK usage data, commercial thinking, and 15+ years of lived experience.

If you’re considering a mobile app, use this to sharpen your thinking, or drop me a line and I’ll help you sense, check the plan.

Let’s start with the obvious: your customers live on their phones. In the UK, smartphone users now spend 3 to 4+ hours per day glued to their devices, and 80% of that time is spent in mobile apps, not web browsers. Globally, it’s even higher. Usage isn’t slowing down.

But here’s the problem: everyone knows that. App stores are now bloated ecosystems, Google Play hosts nearly 3 million apps, and Apple’s App Store isn’t far behind. In this environment, your app isn’t just competing with your direct rivals. It’s up against TikTok, WhatsApp, Amazon, Gmail, and Spotify for attention.

And attention is finite. The average person uses just nine apps a day, and around 30 per month. Launching a new app is like pitching a pop up shop in Times Square, you might be seen, but staying open is another story. One analysis estimates that only 1 in 1,000 new apps achieves any meaningful traction .

Despite that, in the mobile market, app downloads continue to grow. In 2025, global downloads are projected to hit 299 billion, with app revenue surpassing $935 billion. So the question isn’t whether apps are relevant. It’s whether your own mobile app would matter to your target audience in the moments that count.

This is why I tell every founder we work with: high usage doesn’t guarantee opportunity. It’s not about launching an app, it’s about earning a space in someone’s daily routine. And in 2025, that’s a far tougher brief than most realise.

Once you have a clear sense of your business goals, the next key step is gaining a detailed understanding of your target customers and Even with record-breaking screen time, users are deleting apps faster than ever. And it’s not because they’re short on storage, it’s because they’re short on patience.

Studies show that 71% of mobile users abandon a new app within 90 days . Worse still, many apps don’t even make it past the first week. One crash, and 45% of users will delete it immediately . That’s the bar now. Flaky UX? Confusing value? Annoying in app notifications? You’re gone.

This is the reality of app fatigue, a growing reluctance among users to install or keep apps that don’t instantly prove their worth. Most people aren’t excited to download “another app.” In fact, only 35% of smartphone users in the UK download even one new app per month . They’ve been burned too many times.

We saw this first-hand with the Catch app. Originally just a booking tool for anglers and fisheries, it’s since evolved into a fully-featured platform, session notes, AI fish recognition, blueprints, loyalty rewards, all in one intuitive experience. But features alone weren’t enough. We overhauled the UX to work seamlessly in bright outdoor conditions, reduced visual clutter, and made key actions (like logging catches) usable with one hand on the bank. The result? A 50% increase in subscriptions and growing loyalty, even in the off-season.

But even great design can’t fix a weak proposition. If your app doesn’t deliver daily utility or solve a specific pain, it won’t survive. Remember: users spend 80% of their mobile time in their top 3 apps . To make that shortlist, you need to be exceptional, not just functional.

So before writing a single line of code, ask: “Would someone miss this app if it vanished?” If the answer’s vague, you’re not ready to build.

Despite the pitfalls, there are moments when a mobile app is exactly the right move. The difference? Purpose. When an app solves a real problem in a way no other channel can, it earns its keep.

Let’s start with Catch. What began as a simple booking tool for fisheries is now a feature rich companion for anglers. Session notes, AI fish recognition, location blueprints, and loyalty rewards are all designed for real-world conditions: spotty reception, wet fingers, one-handed use. The app doesn’t just offer convenience, it becomes part of the fishing experience itself for their app users.

Apps work best when three things align:

If your service is accessed daily or weekly, an app can streamline that interaction. Think ecommerce, fitness, or food delivery. In fact, UK consumers who install a retailer’s app are up to 60% more likely to make repeat purchases .

In Mobile app development, native mobile apps are faster, smoother, and more responsive. They can cache data offline, use gestures, and integrate with device features like GPS, camera, and push notifications. That’s why brands in food, fragrance, and ecommerce are investing in app only experiences, think voice commands, smart device control, or one-tap reordering. These aren’t luxuries; they’re friction reducers that turn casual users into loyal ones.

The best apps adapt. Think of an app that remembers your fishing spots, suggests weather-based tactics, or nudges you when your favourite lake has a cancellation. These aren’t just features, they’re hooks. The kind that turn an app from a utility into a companion.

Apps also shine in customer loyalty programs and community-building, two things websites often struggle to execute with the same emotional impact.

So yes, mobile apps can drive retention, growth, and brand affinity, but only if they deliver unique value at high frequency. If your idea just duplicates your website, it’s not an app. It’s overhead.

One of the biggest mistakes I see founders make is copying what’s working in a different app marketplaces. Just because a B2C app drives huge downloads doesn’t mean a B2B audience will behave the same, or vice versa.

Consumer-facing apps dominate the download charts, retail, food delivery, entertainment, fitness. But they also churn users at brutal rates. On average, more than half of new B2C users uninstall an app within 30 days. In categories like gaming and dating, that figure can hit 60% or more.

The apps that survive tend to offer frequent, habitual utility, banking, news, messaging, shopping. UK users show strong long-term loyalty to apps like mobile banking (used weekly by millions), while travel, recipe, and one-time event apps get uninstalled fastest .

In contrast, B2B apps often serve fewer users, but they stick around longer. Productivity tools, internal dashboards, or booking platforms used in daily workflows tend to see much higher retention. Enterprise clients aren’t uninstalling Slack or Zoom after one login.

We saw this distinction in practice with Catch. While it’s a B2C platform at face value, its business-facing functionality for fishery owners (calendar, CRM, reports) behaves more like a B2B SaaS product, with higher stickiness and longer-term retention patterns .

Don’t just benchmark your idea against “top apps.” Benchmark it against user behaviour in your sector. Ask:

The context matters. Consumer audiences might download impulsively, but they’ll also delete ruthlessly. B2B users may require onboarding and sales effort, but once you’re in, you’re often embedded.

If, after thorough analysis, you decide moving forward with a mobile app is the right choice, consider an MVP (minimum viable product) Let’s be blunt, building a proper mobile app isn’t cheap. And it’s not just a “one-time” cost. A good app is a living, breathing product that needs to evolve alongside your users, your tech stack, and the platforms it runs on.

In the UK, a simple app that professionally built might start at £30,000–£50,000. Add user accounts, database integration, or payments and you’re quickly into the £80k–100k range. Custom backend? Cross-platform build? Expect six figures .

At Ronins, we’ve scoped apps for every shape and size, from quick MVPs to IoT-connected products. In each case, the real cost isn’t just in design or development. it’s in decision-making. What do you build now? What do you defer? Where’s the long-term value?

Apps aren’t “set and forget.” You’ll need:

Plus, if your app uses paid APIs (like maps, messaging, or AI), those costs scale with usage. Miss these during planning, and your margin disappears overnight.

This is the line item most founders ignore: distribution. Publishing an app is not the same as acquiring users. Unless you have a high-traffic web presence or an existing user base to migrate, you’ll likely need:

Even the best apps die in silence if no one knows they exist.

A few years ago, we worked with a large UK food outlet, The original UK app had been heavily invested in, but wasn’t fit for scale. Our advice? Rebuild from scratch. It wasn’t an easy conversation, but it was the right one. The reengineered app jumped from one star reviews to five, boosted engagement, and paid for itself in weeks .

That’s the difference between launching fast and launching right.

BThere’s a growing narrative in tech circles: Are we moving beyond apps altogether? With the rise of generative AI and digital assistants, some believe the future isn’t in launching yet another app, it’s in removing the need for one.

Think about it. Instead of opening a train app, you might just say, “Book me a return to Manchester tomorrow.” Instead of logging into a shopping app, you tell your AI assistant, “Reorder my usual groceries.” And it gets done, without you ever tapping an icon.

In 2025, tools like ChatGPT, Claude, and Google Gemini are already replacing multiple niche apps. One recent TechRadar article showed how ChatGPT now handles note-taking, translation, and scheduling, previously spread across three separate tools .

Users are trading app-juggling for simpler, voice- or text-driven interfaces. The goal? Less friction. More results.

If your app idea is single-function (e.g. a calorie tracker, basic translator, or static directory), there’s a good chance AI already does it, or soon will. And that’s a hard place to win attention.

But if your app does what general tools can’t, blend location data, real-world interaction, sensors, payments, community, or personalised workflows, you’re still in the game.

With Catch, for example, we embraced AI instead of fearing it. The app uses machine learning to auto-identify fish species and generate catch reports, saving anglers time while boosting their data accuracy. The AI is invisible, but it elevates the user experience.

The smartest move? Treat AI as a layer, not a threat.

Use it to:

In other words: Don’t compete with AI, build with it. Apps aren’t dead. But lazy, narrow-purpose ones? They’re living on borrowed time.

INot every business needs a mobile app. And sometimes, building one too soon, or for the wrong reasons, can cost more than it returns.

We’ve advised multiple founders to pause or pivot their app ambitions. Not because we’re anti-app, but because the proposition wasn’t clear enough, or the cost couldn’t be justified.

Here’s how to know when not to build:

If your app does the same thing as your responsive mobile site, just in a different wrapper, it’s not worth the overhead. Users won’t download it, let alone keep it. Instead, optimise your web experience. Improve speed. Shorten journeys. Add offline capabilities with PWAs (progressive web apps).

Apps live and die by frequency. If your existing customers only need your service once a year, an app is the wrong format. That’s why travel, recipe, and real estate apps have such high uninstall rates .

Why build a booking app if Calendly or Square Appointments covers 90% of your needs? Why launch a storefront if Shopify or Etsy already gives you reach and scale? Standalone apps only make sense when they offer a distinct experience or functionality that can’t be replicated.

If your product is still pre revenue or pre traction, a mobile app is often overkill. You’ll spend time and budget on something untested. Instead, consider a clickable prototype, a no code solution, or a lean MVP. See how people engage before you go build a full native app.

This one’s the killer. Competitor envy leads to poor decisions. Just because a rival built an app doesn’t mean it’s working, or that it’s right for your brand. Your digital strategy should serve your users, not your ego.

At Ronins, we helped one founder skip the app altogether and build a conversion-first web flow that tripled revenue. No downloads. No technical debt. Just smart delivery.

At this point, you’ve seen the data, the risks, and the upside. But how do you actually decide whether to invest in a mobile app?

Here’s a 5-point framework we use with founders before committing to code. Treat this like a sense-check before any budget gets signed off.

Ask: What specific user problem will the app solve, and does that problem already have a working solution elsewhere?

If your app just offers a “nicer way” to do something that already works via web, email, or WhatsApp, you’re unlikely to get traction. But if it genuinely removes friction, delivers faster outcomes, or gives the user superpowers, then it’s worth exploring.

Apps need to be habitual to succeed. Will users engage weekly, if not daily? Is there a repeat-use loop—like booking, tracking, managing, or sharing, that encourages return visits?

If your user might only need your service occasionally, an app could be overkill. That’s when mobile web or third-party integrations often win.

Does the app do something the web can’t? For example:

Catch is a great example here, fish recognition via camera, annotated blueprints, and hyperlocal weather data aren’t things you can easily offer in a browser .

What business result will the app drive, and how will you measure it? Will it:

No ROI = no runway. If the app’s success doesn’t move a core commercial metric, don’t build it yet.

Are you ready to maintain this app post-launch, fix bugs, ship updates, manage compatibility, support users, promote it, and evolve based on feedback?

If you’re not ready to treat it like a product team (not a project), wait. The graveyard is full of apps that were built but never properly supported.

If you can tick 4 or 5 of the boxes above, you might have a strong case for an app. If not, focus on delivering value through web, partnerships, or smarter UX instead. There’s more than one way to innovate.

Mobile is here to stay, but that doesn’t mean your business needs to live in the App Store.

Too many founders build apps because it sounds strategic. Because someone in the boardroom said, “We need one too.” But the truth is: users don’t care how you show up. They care about how easily you solve their problem.

At Ronins, we’ve built mobile apps that have saved lives, powered health tech, transformed brands, and scaled communities. But we’ve also told clients not to build, and they’ve thanked us later. Because the real risk isn’t launching late. It’s launching something nobody needs.

A great mobile app can deepen loyalty, unlock new revenue, and elevate your brand. But it only works when it delivers daily value, commercial outcomes, and a user experience that outperforms everything else.

So before you green-light an app, ask the hard questions. Sense-check the strategy. And if you need a second pair of eyes, we’re here.

Thinking about building an app, but unsure if it’s the right move?

Drop me a note. I’ll give you a straight answer.

It’s the first question most Surrey businesses ask after getting a quote:

“OK, but how long will it actually take?”

And the honest answer is: It depends. But not as much as some agencies make it sound. If you’re clear on what you need, move fast on approvals, and don’t try to reinvent the wheel mid way, most custom website without a lot of functionality can go live in 8 weeks, sometimes faster.

At Ronins, our recent projects for Surrey based clients have averaged between 6 and 10 weeks, depending on scope and how ready the client was with content. E-commerce builds take a little longer, simple brochure sites a little less.

But here’s the catch: “build time” isn’t just how long your developer takes.

It’s how long it takes you and your agency together to get from idea to launch. And that includes discovery, design sign-offs, content population, and testing.

So in this article, we’re breaking it down:

Website timelines don’t just depend on what you’re building, they depend on who you’re building it with and where. 

We looked at 10 recent projects we’ve delivered. Here’s the pattern:

The most common phrase people use to find us is “web design Surrey,” which reflects what most local businesses are actually searching when they’re ready to start a new project.

Face-to-face kickoffs, in-person workshops, quick WhatsApp sign-offs. These shave days or even weeks off the process compared to fully remote builds.

One Guildford-based client cut their project time in half by:

Their entire site went from kickoff to launch in under 6 weeks.

Every website project moves through the same four stages. Whether you’re a solo consultant or launching an e-commerce brand in Guildford, the shape stays the same , but the friction points change.

We’ve broken down each phase, who owns it, how long it typically takes, and what tends to delay it. Knowing where timelines slip is the first step to avoiding it.

Owner: Shared

Typical Duration: 1 week

Biggest Risk: Starting before the brief is nailed.

This is where we align on goals, users, pages, structure, and features. For Surrey builds, we often run this face-to-face, or via a fast-paced workshop on Zoom. Done well, it sets the tone for everything.

How to keep it tight:

Owner: Agency (with client feedback)

Typical Duration: 2 weeks

Biggest Risk: Endless feedback loops.

We translate goals into visuals, wireframes, then full designs. This is where clients get excited (and sometimes indecisive). The faster you respond with clear, consolidated feedback, the faster we move.

How to keep it tight:

Owner: Agency + Client

Typical Duration: 4 weeks

Biggest Risk: Content delays.

This is the heavy lifting , building the site, setting up CMS, making it fast, responsive, and accessible. But the biggest blocker isn’t code, it’s content. If your copy and images aren’t ready, we can’t launch.

How to keep it tight:

Owner: Agency

Typical Duration: 1 week

Biggest Risk: Rushing the final mile.

This phase covers QA, mobile and browser checks, performance optimisation, search engine optimisation polish, and final tweaks. If you’ve planned well, this is smooth. If you haven’t, this is where bugs bite back.

How to keep it tight:

Not part of the core build, but should be scoped early. SEO, CRO, integrations, phase-2 features, these are sprints, not delays.

Here’s the truth: most delays aren’t technical. They’re human.

And in Surrey, where many of our clients are balancing a site build with running a growing business, the same traps come up again and again. The good news? They’re avoidable, if you know where to look.

The #1 killer. We can’t build a homepage without words. And we can’t populate your CMS if we’re waiting on product info, team bios, or service blurbs.

Fix it:

Design’s done. The build’s ready. But everything stalls waiting for approval, especially when multiple stakeholders are involved.

Symptoms:

Fix it:

Starts with “Can we just add…” and ends with a launch date that’s slipped by a month.

Scope creep happens when new features, extra pages, or unplanned integrations are added mid-way, without adjusting time or budget.

Fix it:

Too many opinions. No clear direction. Creative rounds spiral.

You lose time, and energy, trying to make everyone happy.

Fix it:

Final tweaks stretch into weeks. Everyone’s nervous about launching, or someone wants “just one more round of polish.”

Fix it:

In early 2024, a local clothing retailer approached us to take their business online. They had 50+ products, a loyal local customer base, and zero digital presence. Their brief was clear:

Timelines slip when you leave things loose. Want your website live in 8 weeks? Treat it like a real project, not a side task. That means clarity, momentum, and decision making discipline.

Here’s how Surrey businesses we work with launch on time, without stress:

Deadlines create momentum. When everyone knows the launch date, they work backwards from it.

This person approves copy, gives feedback on designs, and unblocks decisions. Without one, timelines get stuck in limbo.

If we’re writing it for you, great, we’ll start in parallel with design.

If not, aim to deliver final content by Week 3.

Slack threads, email chains, endless PDFs, they kill clarity.

We use JIRA, Figma, and Google Drive so everything stays in one place. You get version history, faster feedback, and fewer “where’s that file?” moments.

If you want extra features, great, let’s plan for them. But don’t hold up your go-live for something that can come in Phase 2.

We get these questions in nearly every discovery call. Here are the honest, unfluffed answers, so you know exactly what to expect.

Yes — massively.

If you deliver page copy, images, product info, and sign-off decisions early, you can shave 2–3 weeks off the build.

We’ve launched a WordPress website in under 5 weeks this way, but only when the client is highly organised, decisive, and responsive.

You’re not alone, most delays come from missing content.

You’ve got three options:

Either way, don’t wait. Content should start in Week 1.

Absolutely, and often, you should.

For example:

We bake it in.

If you’re switching domains or rebuilding an old site, we also handle 301 redirects so your rankings don’t tank.

Not strictly, but local often equals faster.

Surrey agencies:

If you want speed, clarity, and accountability, local helps.

In our experience:

If you avoid those, you’ll launch on time, or ahead.

A website isn’t finished when it goes live. It’s just ready to start working.

You’ve scoped it, built it, refined it, now it needs to earn its place in your business. That means:

At Ronins, we don’t vanish after go-live. We help Surrey businesses grow into their sites, not just launch them.

Whether you’re planning a fast brochure build, an e-commerce site, or a phased digital platform, here’s what matters most:

If that sounds like how you want to work, or you’ve just priced up a site and now want to talk timing, let’s have a proper conversation.

If you’re looking for expert web design Surrey web design Surrey with a clear process and reliable timelines, let’s talks a personal touch and provides real-world examples of how the tool has been beneficial, which can be persuasive for potential customers.

Let’s be honest, most business owners trying to budget for a new website get stuck in the same frustrating loop.

They Google “how much does web design cost in Surrey,” land on vague ballpark ranges, and leave with more questions than answers. Or worse, they receive three wildly different quotes from local web design agencies with little clarity on what’s actually included. One looks cheap but skimps on strategy. Another piles in buzzwords but no delivery metrics. The third? Already five figures before anything’s even built.

No wonder so many founders delay their digital projects, or rush them, only to redo them later.

This article exists to break that cycle.

We’re going beyond the “it depends” clichés to unpack the real cost of web design in Surrey in 2025, with actual pricing benchmarks, common hidden fees, and examples of what businesses actually get for their money. Whether you’re a founder commissioning your first custom build or a scale-up leader refactoring a site that no longer fits, this is written for you.

You’ll leave with a clear view of:

But more importantly, we’ll show why the better question isn’t just “what does it cost?”
It’s “what does it return?”

Because smart web design is never just about layout or code, it’s about building the digital core of your business. Get it right, and it becomes your best-performing salesperson, your top lead-gen asset, your growth platform.

This guide is here to help you make decisions with confidence, clarity, and zero fluff. Let’s get into it.

Let’s cut to it.

If you’re in Surrey and scoping a new site in 2025, the market will offer you everything from a £2k templated quick-fix to a £60k+ bespoke platform. Both might be fair. But most businesses don’t need extremes, they need clarity.

We’ve built enough websites across sectors, from SaaS to luxury retail, to know where the money actually goes. So here’s a reality check on what you’re likely to pay, and more importantly, what not to miss in the fine print.

These aren’t vanity prices, they reflect real world web developers and web design project scopes across Surrey in 2025. The lower end is often a solo freelance web designer using off-the-shelf templates. The upper end? A multi-disciplinary team mapping user journeys, building scalable architecture, and wiring in analytics, CRO, or even AI.

If you’re quoted less than £3k for a “custom” site, chances are it’s not really custom, it’s a template with your logo on top.

If it’s north of £30k and doesn’t come with a commercial roadmap or post-launch support, you’re probably paying for process, not outcomes.

Founders often tell us:
“We’ve had quotes ranging from £4k to £40k for the same brief. Are they all guessing?”

Not exactly.
They’re scoping through very different lenses, some cost based on output, others on outcomes.

A £5k job often covers just what you see: pages, images, a CMS login. A £50k+ project? That’s strategy, architecture, QA, integrations, governance, compliance, and the confidence it’ll perform.

Here’s the catch: most fast growing businesses don’t need a mega budget build, but they’ve outgrown budget templates too.

They need that middle ground: a smart, scalable site that gets them live quickly, converts now, and evolves later.

That’s where Ronins operates. We build lean, phased digital platforms that support growth, not just go live. That means:

The question isn’t just “How much will it cost?”
It’s “What’s behind that number?”

Most website designer quotes bundle a dozen invisible decisions into a single price tag. So unless you’ve built a site before, or interrogated a few quotes line by line, it’s hard to know what you’re actually paying for.

The biggest cost factor by far. Are you building a 10 or more page site with no integrations or a dynamic platform with logins, filtering, booking flows, or custom dashboards?

Every moving part adds development time, testing scope, and architectural planning. And complexity multiplies fast when third-party systems (like CRMs, ERPs, or payment gateways) are involved.

A common blind spot. You might think you have “most of the content already,” but is it written for SEO? Designed for conversion and to attract new customers? Structured to be reusable in other formats?

Time spent on:

…can easily account for 20–30% of your project cost if scoped properly. If it’s not in your quote, it’s likely assumed to be DIY.

This isn’t about developer ego, it’s about speed, SEO, and user retention.

It takes technical expertise to optimise for Core Web Vitals, mobile responsiveness, and loading time isn’t optional in 2025. Google cares. So do your users. So should your agency.

Cheap builds often skip:

The result? A slow, leaky site that tanks rankings and bounces users.

If your business operates in regulated markets (health, finance, education, government), compliance isn’t negotiable.

But even outside those, accessibility (WCAG 2.2), GDPR, cookie management, and basic user safety are increasingly standard.

The bit many agencies undervalue, or leave out entirely.

A proper discovery and UX strategy phase adds cost, but it saves even more in the long run by preventing expensive rebuilds, poor conversion, and team misalignment.

In short: if two quotes are wildly different, it’s rarely because one agency is “too expensive.”
It’s usually because they’re quoting for completely different things.

Not all websites are created equal, and neither are the budgets behind them.

Below are the 2025 price ranges we’re seeing across the Surrey market, drawn from agency quotes, competitor research, and anonymised Ronins projects. These aren’t theoretical, they reflect what businesses are actually spending on website design.

Let’s unpack what lives inside each range

Think: templated WordPress builds, limited customisation, and just enough polish to launch. Perfect for early stage ventures, small businesses needing a digital presence, but rarely conversion optimised, scalable, or built for growth.

Best for: solopreneurs, local service providers, pre product startups

This is the realistic starting point for scale-ups with traction.

These sites are typically:

Expect user-centric UX, clean CMS setup, and launch support, plus a foundation you can iterate from.

Best for: B2B service firms, funded startups, growing DTC brands

This is where most high-growth businesses land, especially those integrating CRMs, booking engines, gated content, or AI enhanced features.

What justifies the jump in cost:

Complex digital products that require:

These projects are rarely “websites” in the traditional sense—they’re platforms, often with internal and external users, dashboards, or live data integrations.

Best for: compliance led organisations scale-ups. government & public sector bodies

Many briefs fall into the £20–30k build zone, but start with £8–10k expectations based on outdated market perceptions or previous builds.

That’s not a problem, it’s a sign of ambition.

But if your expectations don’t flex to meet your goals, you risk getting stuck with the wrong partner, or worse, the wrong product.

On paper, your website quote might look complete.
But unless it’s itemised clearly, or you ask the right questions, you might be walking into a cost trap.

Here’s what often isn’t in the initial proposal, but almost always appears in the final invoice (or the second phase you didn’t realise you were agreeing to).

If your quote jumps straight into design without a discovery or UX phase, either:

At Ronins, we front-load discovery intentionally. A half-day workshop now saves weeks of rework later.

Not every site needs full WCAG compliance, but every site needs to be usable, and legally safe. If your build ignores accessibility or cookie compliance, expect post-launch fixes or legal exposure down the line.

Good agencies bake this in. Bad ones call it “a nice-to-have.”

Migrating hundreds of pages, blogs, or documents takes time, especially if URLs are changing. Without a proper redirect plan, your SEO rankings tank overnight.

Yet many agencies scope for “new build only,” and treat migration as a post-go-live add-on.

Poorly defined deliverables (e.g. “we’ll design up to 10 pages…”) or open-ended functionality (e.g. “basic CRM integration”) leave room for interpretation, and disputes.

You’ll often get hit with change requests, billed hourly, or pushed into a costly second phase.

Were you quoted for web hosting.

At Ronins, we lock down scope through clear acceptance criteria, phased roadmaps, and client-approved wireframes before we write a line of code.

No site stays “done.” If your quote ends at launch, what’s your plan for the next six months?

Without post-launch support, most businesses see slow declines, slower load times, stale content, rising bounce rates.

We recommend baking in at least a light-touch ongoing costs as a support retainer, especially during the first 90 days post-launch.

Let’s be clear: trimming cost doesn’t have to mean trimming ambition.

The most effective web builds aren’t the ones with the biggest budgets, they’re the ones that deploy those budgets intentionally. The trick isn’t to spend less. It’s to spend smart.

Here’s how to keep your website design costs commercially sharp, without compromising on quality, performance or long-term scalability.

It sounds counterintuitive to add a phase if you’re trying to save money. But discovery isn’t a “nice-to-have”, it’s your insurance policy against scope creep, UX mistakes, and stakeholder chaos.

Even a 1–2 day sprint with the right people can clarify:

You don’t need to launch with everything.

Instead of trying to bake every feature into v1, focus on what drives commercial value in the first 90 days. That might be:

Everything else? Phase it. You’ll make better decisions with live data anyway.

It’s tempting to go full custom, but sometimes the smartest move is a modular CMS or design system that’s:

We often use WordPress or headless CMSs paired with component based design to give clients flexibility without the technical debt.

Endless rounds of subjective feedback kill momentum and quietly drain your budget. Set boundaries early:

Not everything needs to go into the initial build.

Smart projects break into clear stages:

It’s not about being cautious, it’s about being strategic. You avoid budget blowout and stay agile as the business evolves.

Not all pricing models are created equal, and neither are the agencies behind them.

Some will pitch you a single flat fee. Others will bill by the hour. A few will tempt you with low monthly payments and zero upfront cost. Each model has its place. But each comes with trade-offs that most clients don’t see until they’re deep into delivery.

Let’s break it down.

How it works:
You agree a defined scope up front, and pay one fixed fee to deliver it. Sounds simple, and it can be, if the scope is watertight.

Pros:

Cons:

How it works:
You pay for the hours logged, simple as that. It’s common in dev-heavy builds where requirements are fluid or hard to define up front.

Pros:

Cons:

This model works best with retained partners or trusted long-term collaborators, not one-off vendors.

How it works:
Some agencies offer fully managed websites with no upfront fee, billed monthly like a phone plan.

Pros:

Cons:

If you’re building a platform to grow with, owning your tech stack matters.

At Ronins, we’ve designed our pricing to balance clarity with flexibility.

We don’t believe in bloated fixed fees, or open-ended hourly burn. Instead, we start with:

It’s a model built for founders who want control without compromise, and performance that scales with ambition.

By now, you’ve seen just how much nuance sits behind a website quote.

There’s no single “right” price. But there is a right range, based on your goals, your growth plans, and the commercial role your website needs to play.

If you’re a founder in Surrey looking to:

That number shouldn’t scare you, it should focus you.

Because if your website isn’t built to attract, convert, and evolve, it’s not infrastructure. It’s a holding page.

So, ask yourself:

If the answer to any of those is “not really,” then it’s time for a smarter investment. One that pays back in qualified leads, better conversion rates, and lower technical debt, not just nicer design.

No matter what you spend, your site should deliver:

At Ronins, that’s the baseline. Because anything less is just noise.

If you’ve made it this far, you’re clearly not just shopping for the cheapest quote, you’re looking to make a smart, strategic decision.

That’s exactly where we come in.

At Ronins, we don’t do bloated builds, bloated timelines, or bloated promises. We do sharp discovery, phased delivery, and digital products that actually move the needle, whether that’s more leads, better conversion, or faster rollout.

We’ve worked with scale-ups, SMEs and ambitious brands across Surrey and beyond, building sites that don’t just look good but return investment, measurably and quickly.

If you’re planning your next move, we’d love to help you scope it properly, no pressure, no fluff.

See how our web design agency costs in Surrey stack up or book a 15-minute scoping call to talk through your brief.book a 15 minute scoping call to talk through your brief.

Because the right digital partner doesn’t just build websites.
They build momentum.

I taught myself to code on a Commodore 64 when I was about ten years old and one of the first things I built was a game inspired by Scramble, the side scrolling shooter, and I remember the feeling of getting it working was genuinely magical. That was over forty years ago and I have been building digital products ever since, through my first IT business, through twenty years at the agency I co-founded with two friends that was eventually acquired by Interpublic Group, and now at Ronins where we work with founders and enterprise teams from our base in London and Surrey.

In all that time the word bespoke has been misused more than almost any other word in this industry. What a lot of agencies are actually doing is buying a generic template, swapping in the client’s brand elements and colours and calling it custom web design. That is not bespoke website design, that is template customisation and the difference is considerable and more than most people realise until they end up living with the consequences.

A genuinely custom website is specifically designed and built from nothing for your business. The CMS is configured around how your site needs to be managed and your editing experience is created just for you. The front end reflects how your target audience thinks and searches and buys and every component exists because the web designers understood the problem before they started designing the solution.

Early in my career I used to lead with the technology as that was my training and background. But over time I realised that nobody buys a database, they buy what it does and the same is true for websites. Nobody needs a bespoke website, they need a site that works the way their business generates sales and leads and that their team can run without calling a developer every time they want to update the content. This is what separates a truly bespoke website from a generic template from an off the shelf market-place.

I remember when I was first introduced to Orbus Software project by a friend looks for a job there and we both looked at their site in the cafe numerous times and could not work out what the hell they did as the sites content was very technical and not easy to understand if your on the outside. Then when we pitched to replace their website our audit uncovered that the site was on Sitefinity with rigid page templates and an overwhelming number of layout options in the content management system. There were no guidelines and no documentation so every member of their content team was using it differently. 

I have also been on the other side of this as a customer too as earlier in my career I was Head of IT at the ISTD and Jon the Head of marketing and I had to create their first ever website, do we use a template or go for a custom design after all it was our first site for them.

I am not saying a template website is always the wrong call. For a small business that needs to get business online quickly and the budget is tight, a good template with someone who knows what they are doing can work fine and I have told people that to their face. But if someone is charging you for bespoke web development and what you are getting is a theme with your logo on it then that is a conversation worth having before you sign anything.

Most of what I see is when clients come to us with an off the shelf design that they have outgrown as someone bought a WordPress theme for fifty quid, and an agency customised it, sometime quite heavily to it cant be the core theme can no longer be upgraded and called it bespoke. But the underlying code is still someone else’s. We build our own bespoke WordPress themes from either our library of ACF blocks and customise the UI or design something completely unique from scratch for the client based on their budget at the time.

The version we build is slightly different because from the design system to the components, the CMS configuration and the client specific user journey all start from a blank canvas and are shaped around business needs and ambitions This obviously takes a little longer and it costs more and I will be honest about that in a later section, but it is also the reason our clients can run their sites themselves and its relevant for years, one of our clients still has the same site we custom designed for them 10 years ago and its holding its own.

I get asked this a lot by clients and my answer is sometimes not what people expect because I have been known to tell them not to go for a bespoke build. If they are a startup with a tight budget and a simple proposition and you just need to be visible while you work out if the idea has legs then a template based site is fine, I did exactly this when I started Ronins as a solo founder. I wanted to get online, test the market, learn what our customers actually want and go custom when I had market fit. 

But that is not most of the people who find us.

Most of the websites that I see that are underperforming are not ugly and they are not broken but there are tired and not bringing in the leads it once did or simply the company had rebranded and the website needs a refresh.

This is when the upfront cost of a bespoke site make sense because you are not just paying for a new website you are paying for business goals and something that grows alongside you.

I reminder Brightside who came to us, they are an IT services company and they wanted something that did not feel corporate, they needed warmth, a personality and a way of communicating to SMEs that IT can be a simple managed service. We performed some in depth research into who their ideal customer profile was and drafted a strategic approach for an engaging website that was designed to convert and be attractive to Google.

Another client CTFSI had a different problem, they build AI platforms for the financial sector and their technology is exceptional but their old site was awkward and hurting their chances for investment, We gave them a custom website design that made them look bigger then they were and would resonate with both their target audience and investor pitches.

So back to the key question of what is custom web design and is it worth it, this really depends on if you need your website to generate leads or selling products in an e-commerce store or you require bespoke features that need to handle workflow operations and integrate with third party systems. This is when we create a tailor made website just for you, so as your business grows and you want to add new features then having a bespoke site is worth the bespoke website cost.

I am not going to give you a six step process with a nice diagram because that is not how it works in practice. Every project is different and the process shapes itself around what we find when we start asking questions.

We always start with questions, lots of questions. I find that most clients come to us having already decided what they want built and half the time the brief is the problem not the solution. We had a private school come to us in Surrey asking for a new website and during the discovery we were going through their prospectus and found a phrase that the founder had written years ago without realising what he had. “The most exciting school in England.” Nobody had done anything with it. We used that to reshape the entire brand strategy and built everything around it and when we presented it back to him he stood up turned his back to the room and cried because we had captured his life’s work in a way he had never seen before. They did not need a bespoke design they needed someone to see what they already had.

That is what our discovery does and it is the part that most websites we come across seem to skip as everyone wants to see how it looks. I get it, designs are exciting and tangible and you can show them to your board. But if the strategy underneath is wrong then the design is just design and you will be redesigning it in a year.

The collaborative process we run is not complicated but it does require the client to engage as we need access to the people who understand the brand, the customers as well as the people who manage the content and the people who will be signing off the work. 

After discovery we move into user experience and user interface design before the development works begins. The people designing are highly experienced and understand what can be built in the content management system and whats fantasy. Jason our Creative Director has been with me for years and one thing I have instilled in him is to question everything, the brief, the client, our own process and push for better as that attitude runs through every bespoke build we do and the entire agency,

The web developers on our team write clean code without any redundant code from themes, plugins and frameworks. We have picked up enough projects from other agencies to know exactly the business impact from bloated code and heavily customised plugins or themes that can no longer be patched.If your platform can’t evolve, it’s already obsolete.

I am not going to give you a price list because a bespoke website cost depends on how so many factors and client specific features or functions.

But I know that is not that helpful if you are trying to work out whether your budget is enough, so I have put together some indicative fee ranges based on decades of experience and what we still deliver today.

When I was still running the agency we built before Ronins we did a project for a global consulting firm where we consolidated sixteen separate WordPress website from across the globe into one shared content management system with multilingual content, content editor workflows and a shared media library

The question that most clients want answered is whether the upfront cost is worth it compared to a cheaper templated solution and I understand why they ask and my answer is always yes something depends on it, such as product sales, lead generation or operational workflows between you and your customers and you can tinker with every element of the use journey without slowing down page speed and the user experience.

I always say to clients that I will never play games with your money and treat as if it was my own cash. If I think the budget does not match the ambition I will say so in the first conversation and help you find an alternative solution.

The easiest way to find out is to look at their other work is to goto their portfolio and open five or six of their client websites and if the layouts feel familiar and the structure is the same on most of them then they are recycling a theme regardless of what they are calling it. A genuinely bespoke web design project should look nothing like the last one they did as it should be built for a completely different business with different business goals and a different target audience.

Ask them what CMS they are recommending and why, as if the answer is the same for every client regardless of what the business needs then that tells you something. We often build on WordPress, Webflow, Sitefinity, Umbraco and custom software systems. A web design agency that only works on one platform is not necessarily a problem but if they cannot explain why that platform is right for your specific situation then the recommendation is about their comfort zone not your needs.

Also ask them about search engine optimisation, their track record in it and when it enters their overall delivery process. We structure every bespoke build so that the site is indexable to Google and the AI search engine LLMS from the moment it goes live to ensure your digital presence is found.

And finally ask them what happens after launch, do they provide support? do they monitor site performance? Do they help you iterate based on user behaviour data or do they hand over the site and move on. Its in the first few months after a site goes live are when you learn everything about what is working and what needs to change.

If the agency gets uncomfortable with any of those questions that tells you more than their pitch deck ever will.

If you have read all of this and you are still trying to work out where your project sits then the easiest thing to do is have a conversation. I can usually tell you within thirty minutes or so whether your budget and your ambition are in sync as I have been doing this for a long time.

Let’s talk

I’ve sat in too many rooms where “user feedback” meant the CEO asking their mate what they thought of the homepage.

Let’s be blunt: most teams don’t test. They ask. They guess. They ship. And they wonder why bounce rates climb, conversions stall, or onboarding flops.

Whether it’s a marketing website, customer portal, or web app, the principles hold: if you’re not observing real people trying to use what you’ve built, you’re building blind.

I’ve led product strategy for FTSE brands, global NGOs, and fast moving scale ups. And the biggest unlock, every time, is watching someone actually try to complete a task. It’s not about being surprised. It’s about being humbled. They don’t read your clever copy. They don’t click the shiny CTA. They do what makes sense to them. If it doesn’t work, that’s on us, not them.

When we rebuilt the National Extension College’s website, one round of moderated user testing surfaced a critical disconnect between their navigation model and how real users actually searched for solutions. Fixing that friction, plus a handful of targeted layout tweaks, dramatically improved content discovery and conversion quality. That’s what happens when you stop guessing.

If you want to conduct usability testing that actually improves outcomes, you need the right focus from the start. That means identifying clear goals, defining your target users, and running a pilot test to make sure your scenarios reflect real-life behaviours.

This article is a practical guide for leaders, designers and product owners who want to run a better user testing process, and build better web experiences. No fluff. No buzzwords. Just real ways to make your web presence work harder.

Most “user testing” isn’t testing, it’s opinion-chasing in disguise. A quick round of stakeholder feedback. A few Slack messages. Someone’s mate saying the homepage “feels a bit busy.”

But none of that tells you how users behave, or where they get stuck.

Real insight doesn’t come from opinions. It comes from watching real people in real scenarios, using a thoughtful user testing method. It’s about user behaviour, not boardroom preferences. It answers the hard, specific questions:

Did the user complete the task? Where did they hesitate? What did they expect but not find?

Over the years, I’ve seen this gap play out again and again. Product teams obsess over scroll depth, but miss that no one understood the CTA. Marketing teams run A/B tests while a broken user interface erodes trust. And customer portals go live with strong NPS scores, even though half of users never return.

Here’s the truth:

That difference is critical, especially across modern websites, SaaS tools, and internal portals.

To get real insight, you need to conduct user testing that shows not just where the problems are, but why they exist. A successful user testing process doesn’t just confirm the obvious, it uncovers the mental shortcuts, habits, and expectations your users bring to every session.

That’s where user research comes in. And it starts by choosing the right testing method, not just heat-maps or analytics, but live observation and task-based validation.

Because sometimes, watching a single user fumble through your best-designed page gives you more clarity than a thousand data points.

That’s not failure. That’s your next opportunity.

One of the biggest reasons a user test fails? The team doesn’t actually know what they’re testing. They show a few screens, ask if people “get it,” and walk away with a bunch of polite feedback and no idea what to fix.

User testing isn’t a vibe check. It’s a way to validate assumptions and uncover friction, fast. But only if you’re specific about what you want to learn.

That means asking better questions of the test participants from the start.

Instead of “is this clear?” ask:

These are sharp, measurable, outcome-tied questions. And they force clarity. On what matters. On who you’re testing with. On what success looks like.

Here’s how we approach it inside Ronins:

When we restructured the navigation for Orbus Software, we weren’t asking if it looked clean. We were testing if enterprise buyers could quickly find the product suite that matched their role. That insight didn’t just improve UX, it sharpened their value proposition and improved conversion quality .

The same applies whether you’re testing a hero layout or a customer portal’s billing flow. Vague testing gives you general feedback. Focused testing gives you insight you can act on next sprint.

So before you write a script or line up participants, ask yourself one thing:

What do I need to know, that only a real user can show me?

One-size-fits-all doesn’t work in user testing. The right approach depends entirely on what you’re testing, and why.

That’s why smart testing starts with segmentation, not just of users, but of interfaces.

Here, a usability test is about clarity, motivation, and conversion. Can users find what they came for? Does the message land? Is the CTA visible at the right moment, not just eventually?

When we launched the new Montreaux Homes site, we tested how prospective buyers searched developments by location. What looked elegant to us was skippable noise to users in a hurry. The fix? Sharpen search, declutter copy, and move CTAs above the fold. Result: stronger funnel, higher lead quality .

In apps, it’s about confidence, control, and flow. Do users understand what to do next? Can they complete a task without explanation? Are you surfacing what matters at the right time?

For the Catch app, we tested complex features like AI-powered catch reports and session blueprints. But the win came from small insights: anglers didn’t always trust the AI, so we added user verification steps and made the system explain itself better. Trust went up. So did adoption .

Portals demand frictionless functionality. Can users log in, update details, complete key workflows, and get out , fast? Errors here cost not just conversions, but support time, satisfaction scores, and retention.

Our work with Orbus revealed that different user groups navigated with totally different expectations , decision-makers skimmed, practitioners drilled. We restructured flows to match. Bounce rates dropped. Time on task improved. And sales teams had a clearer case to pitch from .

Don’t get hung up on the tools, Maze, Lookback, UserTesting, PlaybookUX, they’re all useful. What matters most is clarity: what are you testing, for whom, and why now?

Because the method doesn’t matter if the goal is muddy. But if the question’s clear? The right approach to conducting user testing practically chooses itself.

Let’s get something clear: bad user testing starts with the wrong users. You can design the perfect script, test the right flows, even record beautiful highlight reels, but if you’re testing with people who’ll never use your product in the real world, your insights are worthless.

It’s not about sample size. It’s about relevance.

Yes, five users really can reveal 80% of the friction. But only if they reflect the user satisfaction, behaviours, expectations and context of your target audience.

The Catch app is a great example. Some of our early testers were digital-savvy, high-frequency anglers. They flew through the onboarding, but their feedback was useless for understanding friction points facing casual, tech-anxious users. Once we switched to testing with real weekend anglers on older Android devices, the insights were instant: button size, contrast, and flow order all needed work .

A good screener is like a filter for relevance. It lets you hand-pick testers who actually reflect your personas, not just whoever clicks fastest.

Include:

And always ask one open ended question: “Tell us about the last time you did [related task].” That answer tells you way more than a checkbox ever will.

No show rates are real. People get cold feet, forget, or flake. Always recruit more than you need, and if you’re running remote tests, build in a buffer.

Because when testing time comes, the worst-case scenario isn’t bugs. It’s silence.

This is where most tests fall apart. The setup is clean, the participant is qualified, and then they’re handed a task that reads like it came from an internal Jira ticket:

Nobody talks like that. Nobody thinks like that. And your user certainly doesn’t wake up hoping to “navigate to the knowledge hub.”

The point of user testing isn’t to validate whether your interface can be used. It’s to reveal whether it makes sense in the context of the user’s real goal.

Here’s what a strong test prompt looks like:

That’s realistic. Open ended. Anchored in intent, not instructions.

Whether you’re testing a landing page or a subscription flow, scenarios should feel like the user wrote them, not your product manager.

In the real world, users don’t follow your flow. They try to achieve an outcome. Your job is to watch what they do when they try.

That small shift turns testing from a checklist into a discovery process. You’ll learn where friction hides, where users hesitate, and where your language or layout isn’t doing the job.

No hints. No jargon. No safety nets.

The moment you tell someone “Use the search bar to find pricing,” you’ve already skipped past the insight: Would they have found pricing on their own? Would they even expect it to be under that label?

Design your tests like you’re setting up an experiment, one that uncovers what your users assume, expect, and miss.

Context matters.

One reason we’ve had success testing portals and web apps is because we bake that context into every script. If a user’s logging in to submit an urgent form, we don’t ask them to “explore the dashboard.” We ask them to get something done, then watch what slows them down.

Because that’s the gap you’re really trying to close:

What you thought was clear… and what the user actually experiences.

Watching five users struggle to complete a task is interesting. Changing the design so the next five fly through it? That’s valuable.

Too many teams treat user testing like a research phase. Something you do, write up, and file away. But the real power of testing shows up in how quickly you move from observation to implementation.

Right after testing, while it’s fresh, gather your team and answer three questions:

You don’t need a 40-page report. You need a list of things to fix, and a rough sense of priority.

Not all issues are equal. Some kill conversion. Others are just polish. Group them into three buckets:

If a user can’t find the sign-up button, that’s a blocker. If they find it but hate the label, that’s friction. If they don’t like the font? File it under “later.”

The fastest way to create change? Show people the footage.

When stakeholders see users struggle, priorities shift. Debates disappear. Everyone aligns faster.

That’s why we often cut short highlight reels, raw clips of real people getting confused, stuck, or saying “I don’t trust this.” It builds empathy. And momentum.

Not everything needs a redesign. Often, a single label change, a button move, or a tighter heading hierarchy solves the problem. Quick wins first.

Then plan for the deeper issues, workflow changes, new layouts, content rewrites. Log them. Assign owners. And most importantly: track whether the next version performs better.

Testing isn’t a one-and-done. The best teams bake it into their rhythm. Observe → Adjust → Re-test.

Every time we’ve tested a product, implemented changes, and looped back with users, the second round always feels smoother, because we’re not designing in a vacuum. We’re designing with real behaviour as our north star.

The biggest mistake? Treating user testing like a one-off milestone. Something you “tick off” before launch, and then forget until complaints start coming in.

The best-performing teams I’ve worked with treat testing like dev treats Git. It’s just part of the workflow.

If you’re running Agile, you already have the cadence. Use it.

This isn’t theory, we’ve done it. At Ronins, we often structure micro-tests one sprint ahead, using Figma prototypes or staging environments. That way, feedback lands early, before time and cost compound.

Add it to your workflow. Literally.

You wouldn’t ship without QA. So why ship without usability confirmation?

Testing doesn’t need to be the UX team’s private domain. Involve devs, PMs, even marketing leads. Get them to observe a session. Or watch a five-minute clip.

The more people see the struggle, the faster they’ll care about solving it. You shift from opinion-based debates to evidence-led delivery. Culture follows process.

You don’t need a “research department.” You need a lightweight playbook:

Keep it frictionless. The easier it is to test, the more often it’ll happen.

You don’t need to test everything, every week. But you do need to test the moments that matter:

These deserve the spotlight. So give them a cadence, quarterly, monthly, or around major releases.

Because the truth is: user needs evolve. And without testing, your product won’t.

Let’s wrap where this started: with the biggest lie in digital.

No, you know of them. You know what they’ve clicked, what they’ve said, where they’ve dropped off. But unless you’ve sat quietly and watched them try, fumble, hesitate, misread, overthink, you’re working with guesses, not truths.

And I get it. You’re close to the product. You care deeply. But that’s the problem.

You know too much. You’ve seen the Figma files. You’ve sat in the roadmap meetings. You’ve heard all the justifications.

Your user hasn’t.

They land cold. Scanning. Multitasking. Distracted. And if your site, app or portal doesn’t help them move, clearly, confidently, without unnecessary effort, they bounce. Not because they’re impatient. Because they’re human.

That’s what user testing gives you: not data, but clarity. A direct window into what real people need, expect, and miss.

So if you take one thing from this guide, let it be this:

That’s how websites convert.

That’s how SaaS sticks.

That’s how great products stay great.

And if you want help making that happen? You know where to find me.

Ready to stop guessing?

At Ronins, we help founders and digital leaders build websites, web apps and customer portals that actually work, because they’re shaped by what real users do, not what internal teams assume.

If you want to run smarter user tests, fix the right things, and build web experiences that drive results, let’s talk.

The voice and reading of this article were created with artificial intelligence.

Most digital projects don’t fail in development, they fail in discovery. Not because the team lacked skill, but because they started solving before they fully understood the problem. The website discovery phase isn’t overhead. It’s where clarity begins and confusion starts to die.

Clients often arrive saying, “We just need a better site,” but nine times out of ten, that’s not the real problem. It’s just the most visible one. A slow site, a dated look, poor conversion, these are symptoms. Discovery is where we figure out what’s actually broken underneath.

This isn’t about wireframes or sitemaps. It’s about asking hard questions before anyone opens Figma. What are you really trying to fix? What does success look like in plain English, not just in analytics dashboards? Who’s going to call this project a win, and what do they actually care about?

One founder described the process as “commercial therapy.” That’s about right. Discovery is the space to say what’s true, even if it makes the brief messy for a bit.

When we worked with Catch, the UK angling platform, they came in thinking about scale and booking flow. But once we unpacked it, the challenge was bigger: they weren’t just building a booking tool, they were shifting toward becoming an ecosystem for anglers. That single realisation reframed the entire product direction. The discovery phase didn’t just validate assumptions; it changed the business.

Too many teams skip this step because they’re eager to show progress. But speed without precision is noise. Discovery is the first step that gives every other step its meaning, and without it, you’re just building prettier problems.

Most briefs are clean. Too clean. They’re polished, rational, and often wrong, because they skip the messy middle where real understanding lives. The discovery process isn’t there to confirm what’s already assumed. It’s there to break it apart.

A good discovery isn’t polite. It questions everything: Why are you really redesigning? Who’s struggling with what? Where is time or money leaking from this system right now?

This is where we move from wish-lists to realities. We’re not just listening, we’re interrogating. We’re surfacing assumptions, exposing knowledge gaps, and reframing conversations around outcomes. Not features. Not opinions. Outcomes.

During one B2B discovery, the client was adamant that their homepage was the problem. But once we gathered information across teams, it became clear the real issue was buried deeper: they were answering the wrong questions for the wrong audience. That shift changed the entire content plan, and ultimately drove a better understanding of their funnel.

The key is not to treat discovery like a static checklist. You need to layer methods: heatmap analysis, stakeholder workshops, content audits, sales call transcripts, even a glance at how support tickets are tagged. Because each piece unlocks a different truth.

Great discovery uncovers user needs that don’t appear in spreadsheets. It picks up on user friction that’s been normalised. It connects disconnected pain points across teams. That’s where the gold is. You won’t find it in the brief, but you will find it if you ask better questions and sit with uncomfortable answers.

Because discovery isn’t about what the client wants, it’s about what the user actually needs, what the business can realistically deliver, and what it all has to achieve commercially. That’s the line we draw.

One of the most common points of failure in digital projects isn’t technology. It’s the wrong people making the wrong decisions at the wrong time. Or worse, right people, but too late.

The project team needs to be shaped at the start, not bolted on after discovery is done. That means getting the project manager, strategist, developer, content lead, and at least one voice of the user involved from day one. Waiting until wireframes are signed off is already too late.

The kickoff meeting isn’t just a formal start, it’s your pressure test. Can the team align around what success looks like? Are there conflicting expectations between marketing and product? Will tech constraints derail scope mid-sprint? These aren’t blockers later, they’re alignment issues now.

In a discovery project for a national property developer, we brought together stakeholders from marketing, sales and the board. On the surface, everyone wanted the same thing: more leads. But as the session unfolded, we uncovered that each team had a very different idea of who those leads should be.

Marketing was chasing volume through brand storytelling. Sales wanted qualified buyers already armed with financial data. And leadership wanted to attract joint venture partners. Same project, three competing goals.

That surfaced in a single face-to-face session. Without it, we’d have built a site optimised for click-throughs… while sales quietly starved. Instead, discovery became a tool for prioritisation. We redefined what a lead actually meant and tailored user journeys to support all three objectives, without cannibalising each other.

Every team member brings a lens. And those lenses only work if they’re present from the start. Developers catch edge cases that strategy might miss. Support teams highlight common UX drop-offs. Marketing sees where content falls short. Discovery is where those perspectives collide, and sharpen each other.

You don’t need everyone in every session. But you do need to design discovery around access, to insights, blockers, contradictions and commercial drivers. That’s the real work.

And when it’s done right? Everyone leaves with clarity. Not just what to build, but why it matters, who it’s for, and what success looks like when we get there.

Data is useful. But it’s not the brief. Google Analytics can show you bounce rates, most visited pages, or session duration, but it can’t tell you why people bounced. Or what they were actually hoping to find when they landed on the site.

In discovery, we look at analytics, heat-maps, scroll depth and traffic sources, but we never treat them in isolation. A spike in traffic to a blog post doesn’t mean that page is working. It could mean it’s misleadingly titled. Or over-indexing on one search term. Or worse, it’s ranking for something you don’t want to be known for.

Page views are interesting. But without context from sales teams, customer support, or product managers, they don’t give you anything actionable. Discovery is where we combine quantitative data with qualitative truth. That means asking teams what they hear on the phone. Where users are getting stuck. What’s not being said.

When we audited the current website for a healthcare project, the analytics showed the careers section was one of the most visited pages. On paper, that looked like success. But in interviews, the internal team revealed that it was mostly internal traffic, staff clicking through to find HR links that weren’t where they should be. The insight? It wasn’t a recruitment asset. It was a workaround for broken internal comms.

Discovery connects the numbers to reality. It stops you from building based on assumptions, or worse, optimising for vanity metrics. If you want to increase website traffic, great. But only if it’s the right traffic, with the right intent, heading toward the right outcomes.

That’s why we look at data. Not to confirm success. But to challenge it.

One of the easiest ways to waste a digital budget? Rebuilding what already exists, just with nicer fonts. A lot of businesses treat their current website like a template to be improved. But if you’re redesigning based on what’s already there, you’re not solving anything, you’re preserving the problem.

In discovery, we audit what’s live. But we’re not looking for what to keep, we’re looking for what to leave behind. What’s underperforming? What’s unclear? What’s been patched over too many times?

That starts with gaining insights from real use. What do users search for that they can’t find? What content gets traffic but never converts? What pages take up space but serve no measurable purpose? Every element, navigation, page hierarchy, search, is on trial.

We took this approach with Catch’s early public-facing site. On the surface, the structure made sense: location filters, lake listings, a few help articles. But when we ran a full analysis during the discovery phase, it became clear that most users were navigating via search, not structure. And the copy wasn’t written for anglers, it was written for Google.

The solution wasn’t just technical. It was editorial. We rebuilt the information architecture from scratch, restructured the content, and wrote in a voice anglers actually recognised. The result? A simplified flow, improved search performance, and a more intuitive, user-friendly product.

That’s why we build low fidelity wireframes during discovery, not to lock in design, but to pressure-test logic. We map what content belongs where, what needs to be merged or deleted, and what’s missing entirely.

Your current site is a lesson. Discovery is where you choose whether to learn from it, or repeat it.ck for a health and wellness website made the brand more relatable and trustworthy to its audience, leading to increased user engagement and loyalty.

That’s why discovery always includes a brutal but necessary step: defining what success actually looks like. Because if we don’t align around website goals now, we’ll argue about them later, when it’s more expensive, more political, and harder to fix.

Some teams want brand visibility. Others want sales-ready leads. Some want users to self-qualify. Others want them to convert fast. There’s no wrong answer, but there has to be one.

In a recent project for a SaaS platform, we uncovered three competing visions during discovery: marketing wanted form fills, product wanted trial sign-ups, and the CEO wanted analyst credibility. That tension wasn’t going away. So we mapped out how each of those outcomes could be served, but made sure only one was prioritised per section of the site. Discovery became the alignment tool, not just the insight phase.

We also look closely at business objectives and how they ladder into digital. Is this project about reducing support calls? Improving close rate? Launching in a new market? Discovery links those business-level needs to web outcomes that can actually be measured, whether that’s conversion rates, sales pipeline impact or content adoption.

From there, we define the desired outcomes of the website. That includes not just what users do, but how they feel. Reassured? Curious? Confident enough to take the next step?

Discovery is where we kill off features-for-feature’s-sake thinking. Every page, every module, every call-to-action has to earn its place. And by the time the first layout hits the screen, the team already knows what that screen is there to achieve.

Without that clarity, projects drift. With it, they perform.

Most personas are too polite. They’re filled with vague hopes and soft attributes like “motivated by convenience” or “tech-savvy.” But good discovery doesn’t create fictional users, it introduces you to the real ones.

This is where user interviews, behaviour data and frontline feedback all collide. We don’t start with stock-photo demographics, we start with friction. What are users trying to do but can’t? What workarounds have they created? What’s their real intent behind that bounce?

At Ronins, we’ve had projects where the target audience on paper was miles away from the one that actually used the product. In one healthcare case, the client was designing content for first-time users, but it was repeat users who drove most interaction. That insight shifted the tone of the site from explanatory to supportive, and dramatically improved engagement.

During the Catch discovery phase, we went deep on identifying different user personas. Not just ‘anglers’ as a block, but nuanced groups: solo hobbyists, family day-trippers, competition fishers, even night anglers booking around shift patterns. Each had different needs, motivations, and tolerance for complexity.

User behaviour told us where they clicked. But talking to them told us why they stopped. That led to clearer journeys, shorter forms, and content that didn’t just inform, it anticipated.

We also mapped the conversion funnel with these audiences in mind. What’s the minimum amount of information a new user needs before they’re ready to act? What builds trust fastest? What disrupts it?

Discovery isn’t about guessing who your users are. It’s about listening, validating, and giving those users a site that fits their context, not just your brand’s. Because when you get that right, conversion isn’t something you chase. It’s something that happens.

Discovery is where we map problems. Design is where we solve them. But if that bridge is broken, everything unravels, wireframes go off-piste, dev sprints derail, and the “final product” ends up answering a question no one’s asking.

That’s why we treat the design process as an extension of discovery, not the start of something new, but the continuation of something already understood.

We don’t launch into visuals. We begin with structure. What does the site need to do, and in what order? That means translating insights into content hierarchy, journeys, and functional flow. Which page needs to reassure? Which one needs to convert? Which should load fastest?

And just as importantly, what needs to be left out?

The development process starts here too, long before code. Tech choices, third-party integrations, platform constraints, SEO implications, hosting decisions… they all need early visibility. Otherwise, someone will suggest a CMS that can’t handle multilingual content, or a design interaction that breaks accessibility.

One example: on a recent project involving booking logic across international time zones, discovery surfaced a technical requirement we might have otherwise missed, calendar slots had to flex dynamically based on user location and the fishery’s own management tools. That insight changed how the dev team approached the architecture, days before anything was committed to code.

This is also where we define functionality. Not in vague “we want a cool dashboard” language, but in use-case terms. What action needs to happen? What does the user expect to see? What happens next?

Everything we design is anchored to outcomes. And every outcome is validated during discovery, not invented in isolation.

When that process is tight, delivery runs lean. There’s less double-handling. Fewer misfires. And far more confidence, on both sides of the table.

Founders often come in thinking discovery slows things down. In reality, it’s the fastest route to a site that works. Why? Because it prevents guesswork, reversals, and six rounds of “can we just tweak the homepage?” after launch.

When done well, discovery helps generate leads earlier, because we’re designing for the right buyer journey, with the right friction removed. The site gets to work faster, because the guesswork’s already handled.

Take the Ronins project for a large education provider. Their existing site looked clean, but lead flow was weak. In discovery, we uncovered that course content was too deep in the structure, and their sign-up form was 11 fields too long. We redesigned their lead funnel around user priority, not organisational hierarchy, and they saw double-digit growth in sign-ups within 60 days of launch. The site didn’t just look better, it sold harder.

That’s the hidden power of discovery. It doesn’t just set up the design. It defines how you acquire, qualify, and convert attention into business.

It also saves internal energy. Clear briefs mean faster stakeholder sign-off. Aligned goals mean less back-and-forth in QA. And when you’ve had tough discussions early, you don’t get political surprises at the eleventh hour.

Discovery links every element, copy, UX, SEO, tech stack, back to a measurable outcome. More qualified leads. Higher engagement. Shorter sales cycles. Increased trust.

If you want a site that functions properly, performs commercially, and builds momentum, not friction, then discovery isn’t the expensive phase. It’s the high-leverage one.

By the end of a well-run discovery, the client often looks relieved. Not because the site is built yet, but because, for the first time, they can see the shape of it. The risks are visible. The unknowns are named. The next steps feel real, not theoretical.

When you get this phase right, it sets the tone for everything. Approvals go faster. Decision making gets easier. The client stops reacting and starts leading. Not because we sold them something clever, but because we helped them see clearly.

We’ve had CEOs tell us, “This is the first time I’ve felt confident briefing our board on the website.” Not because the homepage was finished. But because they could finally articulate the why behind the what.

One senior leader described it like this: “Before discovery, we had content. After discovery, we had conviction.”

And that’s really the goal. Not just to produce a plan, but to build shared belief. Because a confident team delivers better work. A clear client is a better collaborator. And a well-defined problem? That’s half the solution.

The biggest compliment we get isn’t about the code or the visuals, it’s when a client says, “That session changed how we think.” That’s when we know it worked. That’s when discovery paid for itself.

If you’re planning a new website, product, or digital platform, and you’re serious about getting it right, let’s start with a conversation. Not a quote. Not a pitch. Just clarity.

Because once you know what’s really needed, everything else moves faster, sharper, and with far less friction.

Drop me a message or connect on LinkedIn. Let’s see what your real brief might be.

Whilst we have taken great care in creating this article, the voice and reading were artificial intelligence-assisted.

WordPress is an indispensable platform in my web development toolkit, offering unparalleled versatility for creating dynamic and scalable websites. 

Its user-friendly nature and extensive customisation options through themes and plugins for WordPress make it a prime choice for digital professionals seeking to craft compelling online experiences.

Plugins are the lifeblood of WordPress, enhancing its base functionality in myriad ways. My approach emphasises selecting plugins that excel in functionality, ease of use, reliability, and innovation. These tools are vital for tailoring websites to specific operational needs, enhancing everything from performance and security to user engagement and SEO.

As we explore my best WordPress plugins, I focus on those significantly improving the website or CMS experience. The following are my favourites: free WordPress plugins or premium WordPress plugins. 

Ensuring robust website security is not just about protecting data; it’s about safeguarding users’ trust in digital platforms. In my pursuit of creating secure and resilient websites, I’ve come to rely on two pivotal plugins: Wordfence Security and Sucuri. These tools are not mere add-ons but essential fortifications that shield against the myriad threats on the internet.

Incorporating Wordfence Security and Sucuri into a website’s security strategy represents a comprehensive approach to safeguarding digital assets.

Optimising website performance has led me to employ three essential tools: WP Rocket, Smush, and Cloudflare. These plugins and services work in concert to ensure that websites are fast, efficient, and resilient against the challenges of the online environment. I think WP Rocket is the best WordPress plugin I have found so far, and it’s easily worth getting the paid version.

Leveraging WP Rocket, Smush, and Cloudflare has been pivotal in my strategy to ensure that websites not only meet but exceed performance expectations. 

My approach towards maximising SEO and marketing efforts focuses on leveraging tools that enhance search engine rankings and optimise marketing strategies. Among these tools, Rank Math SEO, MonsterInsights, and OptinMonster have been instrumental in achieving these objectives, each offering unique features to boost online presence and conversion rates.

Incorporating Rank Math SEO, MonsterInsights, and OptinMonster into a website’s marketing and SEO strategies represents a holistic approach to digital growth. These tools enhance the site’s search engine performance and provide the insights and capabilities needed to refine marketing efforts and increase conversions. 

The integrity and dynamism of a website’s content play a pivotal role in attracting and retaining audiences. To this end, I have found that a strategic combination of content management and social integration tools is essential. Akismet, Jetpack, and Revive Old Posts are three plugins that stand out for their ability to enhance content quality, ensure security, and leverage social media to amplify reach.

Employing Akismet, Jetpack, and Revive Old Posts has enabled me to effectively enhance websites’ content management and social integration aspects. These plugins ensure the quality and security of the website’s content and amplify its reach and engagement through strategic social media practices. 

Enhancing a website’s functionality is crucial for reaching a wider audience and providing a more personalised user experience. Tools such as WPML, Gravity Forms, and Advanced Custom Fields (ACF) play a role in this enhancement, offering capabilities that extend beyond WordPress’s core functionalities to meet users’ diverse needs worldwide.

Implementing WPML, Gravity Forms, and Advanced Custom Fields into a WordPress site significantly improves its functionality, making it more accessible, interactive, and tailored to the diverse needs of a global audience. 

For developers, optimising a website’s behind-the-scenes functionality is as important as enhancing its front-end user experience. Query Monitor and WP-Optimise are indispensable tools, offering capabilities that improve site performance, debugging, and maintenance.

Employing these specialised tools significantly contributes to developing and maintaining high-performing, user-friendly websites. Whether enhancing functionality for users around the globe, customising content displays, or optimising the site’s performance and debugging processes.

Exploring my best WordPress plugins illuminates their potential to transform a WordPress website significantly. The selection and integration of the right tools can propel a digital platform from merely functional to genuinely outstanding. These plugins, each serving a unique purpose—from enhancing user experience and bolstering security to optimising performance and extending functionality—demonstrate the capability to meet and exceed an excellent user experience.

Digital strategists, website owners, and developers must stay abreast of the latest tools and technologies. The plugins discussed here are at the forefront of my WordPress development, offering innovative solutions to refine and enhance online presence and operational efficiency. Whether it’s reaching a global audience, creating advanced forms, managing custom data, or ensuring optimal website performance, these tools provide the means to achieve a more inclusive, dynamic, and high-performing digital environment.

These resources can serve as a starting point for deepening your understanding of WordPress plugins and how they can be leveraged to enhance your website’s performance, security, and user experience.

“It looks incredible.”

And here’s the thing: we’d seen it before.

When speed trumps substance and dev workflows chase convenience, businesses unknowingly take on an SEO debt, a hidden cost that quietly compounds with every “efficient” choice.

Modern web development makes it dangerously easy to build something that looks exceptional but performs poorly in search.

It’s not malicious. It’s often not even careless. It’s just a byproduct of teams optimising for the wrong outcome, shipping, not surfacing.

This is where search engine optimisation (SEO) must stop being a post-launch patch and start being a principle baked into development culture.

Your site doesn’t exist in a vacuum. It exists in an ecosystem shaped by search engines, user intent, and algorithmic interpretation. If your content isn’t structured to be seen, parsed, and indexed, it’s effectively silent.

Google doesn’t care how clever your animations are. It cares whether your site answers the query, fast, cleanly, and clearly.

That’s why SEO best practices in web development aren’t optional extras. They’re foundational pillars that impact:

And when they’re ignored, everything else suffers: rankings, reach, revenue.

Google’s ranking systems increasingly lean into E-E-A-T, Experience, Expertise, Authoritativeness, and Trustworthiness. And while content is core to that, your technical integrity is its enabler.

E-E-A-T isn’t just about what you say. It’s about how reliably you say it, and whether it shows up at all.

That’s the question founders ask, right after spending tens of thousands on a gorgeous new site that Google barely acknowledges. The answer? It was built for the user’s eye, not the crawler’s logic.

In the sprint to launch, many web development teams optimise for internal velocity: frameworks they know, components they can reuse, plugins that speed things up. But the invisible consequence is often this: Google doesn’t see what the user sees.

And if Google can’t see it, it won’t rank it.

This is where the hidden SEO cost really starts to show. Here’s what typically goes wrong under the hood:

Your search engine rankings don’t just depend on having great content. They depend on how, and when, that content is delivered.

“It’s not just about what loads. It’s about what loads first, and what Google sees without asking.”

Let’s break it down.

The developer is focused on usability, animation, and speed for the end-user. The search engine is focused on parsing, hierarchy, and indexability. The two aren’t in conflict, but they aren’t automatically aligned either.

And when developer convenience becomes the guiding light, technical SEO best practices are often left behind.

Things like server-side rendering, semantic markup, and accessible image alt text fall by the wayside in favour of faster deployments and cleaner codebases. But that trade-off can be brutal. What you gain in speed, you lose in search visibility, and with it, the organic traffic that drives growth.

If your own website isn’t structured with SEO in mind from the first sprint, you’re not just delaying performance, you’re handing the advantage to other websites with less impressive builds but better optimisation. A few hours of extra setup can mean the difference between silence and search results.

Because if the structure doesn’t make sense to a crawler, it doesn’t matter how good the content is. Google won’t rank what it can’t understand.

And that’s not just a technical problem. It’s a business one.

“We built it in Next.js, so why can’t anyone find it?”

That question lands more often than it should. The new site looks great. The devs are proud. The interface is slick and the performance metrics are green. But Google is still quiet. No uplift. No discovery. No movement.

And that’s because most modern build stacks prioritise the developer’s experience, not the search engine’s.

Most JavaScript-heavy sites ship content dynamically, after the page loads. That means crawlers often hit an empty or incomplete HTML shell. The real substance, the stuff users see, is hidden behind layers of JavaScript that Google may not fully render, especially on a second crawl pass.

It’s not that search engines can’t crawl JavaScript. It’s that they don’t always wait around to try.

So what you end up with is a web application that looks flawless to a user on their browser, but looks like one page of vague code to a crawler.

And if it looks like one page, it gets treated like one page.

This is especially true with Single Page Applications. Without server-side rendering or proper hydration, internal routing isn’t crawlable. You might have 100 screens, but search engines only see one URL. And when that happens, your pages vanish from the search engine results.

Even the basics go missing. Page titles. Meta descriptions. Anchor text. Structured headings. All the things that tell Google what each page is about and where to place it in its index—they’re often rendered too late, or not at all.

Developer-focused tools often create unintended consequences:

In theory, these builds are modular, efficient, and “up to date.” But in practice, they confuse crawlers, fragment internal linking, and introduce duplicate content across versions of the same page.

The cost isn’t just technical. It’s commercial. Sites built this way often attract fewer users, lose their organic traffic edge, and rely more heavily on paid media to fill the gap.

And that’s avoidable, if you design your stack to work for search engines from day one.

Because in modern web development, the stack you choose isn’t just a dev decision. It’s a visibility decision. It’s a revenue decision. It’s a search engine optimisation decision.

“It looks like a dream. But it ranks like a disaster.”

When sites are designed to impress stakeholders, not search engines, you get image-heavy homepages, zero crawlable text, and UX that wins awards but loses customers. The end result? A search engine sees the shell, not the story.

Designers love clean, minimal interfaces. Developers love shipping with reusable components. The result is often a homepage with three lines of text and a carousel of high-res images. No structured headings. No unique titles. No context for crawlers.

What looks polished to a user is often unreadable to search engines.

This is where technical SEO gets undermined by aesthetics. We’ve seen it first-hand. A client comes to us with a visually stunning new website, and a 30% drop in organic traffic. No image alt text. No semantic layout. No meaningful anchor text in the nav.

Google saw a glossy brochure. Not a website.

When Orbus came to us, their old site was cluttered, template bound, and visually tired. But it ranked. Their new redesign, however, had stalled. Pages weren’t performing. Search traffic had dipped. They’d swapped function for beauty, and the index paid the price.

We rebuilt it with purpose. A component-based design system that made content easy to structure. Clear headers. Search-focused landing pages. A flexible CMS that respected internal linking and metadata hierarchy.

The result? A visually elevated brand presence and a measurable improvement in organic reach. The work looked great, but more importantly, it worked.

Here’s what gets skipped in most builds:

This is where founders and content teams need to push back.

It’s not enough to showcase a strong visual identity. You have to provide real, indexable content. That means creating content for both human visitors and search engines, without compromise.

When we redesigned the Catch app landing pages, every section had a job to do. Real screenshots. Searchable captions. Structured HTML. Contextual FAQs optimised for different keywords and long-tail queries. We didn’t just highlight new features, we made sure Google could index them properly.

That approach helped Catch rank for highly specific fishing terms, even with a relatively new domain name. Traffic increased by 32% after launch. More importantly, those pages converted, because users weren’t just wowed by visuals. They found what they were looking for.

Design isn’t the enemy of SEO. But done carelessly, it can undermine everything good content tries to do.

“If it looks good but Google can’t read it, it’s decoration, not strategy.”

“We launched. We indexed. We didn’t climb.”

That’s the quiet frustration you hear from teams who tick the SEO basics, then still watch competitors overtake them. More often than not, the issue isn’t content or even links. It’s missing metadata. And it’s shockingly common in modern builds.

Titles, meta descriptions, canonical tags, structured data, these aren’t optional. They’re the language search engines read before they even consider ranking your content.

But in JavaScript-led workflows or CMS-heavy sites, metadata gets pushed down the list. Injected too late. Left to plugins. Or worse, duplicated across every page.

That’s when Google starts to guess. And when Google guesses, you don’t get higher rankings—you get irrelevant ones.

It only takes a few of these for search engines to hesitate. And when they do, your visibility flatlines.

When we started working with Korda, their organic footprint didn’t reflect the strength of their brand. They were well known among anglers. But their pages weren’t performing, despite great content and a loyal audience.

The issue? Metadata gaps and conflicting signals.

Product pages had overlapping titles. Important categories were missing meta descriptions. Canonical tags were inconsistent. And their internal link structure was shallow.

We fixed it at the foundations, clean titles, unique descriptions, content-aligned headings, and tighter internal pathways. Then layered in structured data to help with product visibility and FAQ appearance.

Within months, they saw a significant uplift in organic traffic and improved click-through rates across key product lines. They didn’t need new content. They just needed to give Google the right signals.

If you treat meta tags like admin, or hand them off to a CMS plugin, you’re missing a major opportunity. These are the fields that shape how your pages appear in search results. How users interpret them. And whether they click.

That means:

And if your team is creating new pages, rolling out features, or changing templates, someone needs to own that layer. Because if no one’s in charge of metadata, your site’s future rankings are a gamble.

“Good metadata is like good manners. It doesn’t guarantee you’ll be invited in, but without it, don’t expect a warm welcome.”

“It’s live. It’s indexed. But it’s nowhere.”

That’s what founders say when they check Google Search Console, see their new pages marked as discovered, and still wonder why they’re not showing up in meaningful search results.

The truth? Just because a page exists doesn’t mean it will perform. And in most modern builds, the visibility gap isn’t content, it’s connection.

Here’s what usually happens.

You launch a new section. The pages are up. They work. They’re technically indexable. But no one linked to them from the homepage. There’s no sitemap update. Internal links are sparse or buried inside JavaScript components. So Google crawls… and stops short.

This is how orphan pages are born, content that has no internal links pointing to it. No context. No authority passed from elsewhere on the site. To Google, these pages might as well be floating in space.

And that space is getting crowded.

Search engines rely on structured connections to understand your site. They follow links. They map hierarchy. They infer relevance.

When your internal linking is shallow or inconsistent, you’re not just slowing crawl rate, you’re weakening every page’s chance of ranking.

Some of the most common breakdowns:

And when this happens, Google may technically index the URL, but it won’t prioritise it. In practical terms, it might as well be invisible.

One of the biggest myths in SEO is assuming Search Console tells the whole story. It doesn’t. It tells you if a page is known, but not how it’s weighted. That’s why you can have dozens of indexed URLs and still see no uplift in rankings or traffic.

Use Search Console as a starting point, not a reassurance. Then dig deeper. Look at impression data. Look at which queries you’re appearing for. If your page is getting shown but not clicked, it might be a metadata issue. If it’s not appearing at all, it’s almost always structural.

This is why every new section of your website should come with three things:

And if you’re launching features or pages across different systems or CMS layers, make sure your technical SEO strategy still unifies them. Otherwise, your most valuable content will keep disappearing into the void.

“It’s a WordPress site, so SEO should be fine, right?”

That’s the assumption. And it’s a dangerous one.

WordPress powers over 40% of the web. It’s flexible, fast to deploy, and has a plugin for everything. But that same ease is what makes it easy to overlook the basics. Most WordPress sites aren’t underperforming because of the platform, they’re underperforming because no one took control of it.

Out of the box, WordPress ships with SEO vulnerabilities:

The myth is that WordPress takes care of SEO for you. In reality, you need to take control, or risk building a beautifully useless brochure.

Most basic sites we audit have the same issues:

And while content teams might be focused on writing blog posts, no one’s asking the bigger question: How is this site actually structured for search?

That question rarely gets asked. Because the tools feel like they’re doing the job. But visibility doesn’t come from installing plugins. It comes from intentional structure, connected pages, and properly configured metadata.

A few pounds spent on good plugins is fine. But the real investment is in how you use them. WordPress software gives you control—but it won’t take responsibility for you.

If you want more organic traffic, start by asking:

We’ve seen clients invest in design, content, and speed, only to realise they’re leaking traffic through duplicated slugs, conflicting canonicals, and thousands of thin pages they never knew were indexable.

The fix? Audit what’s live. Prune what’s unnecessary. Rebuild structure where needed. Then maintain it like you would any other system that affects revenue.

Because whether you’re running a personal blog or a global business, WordPress doesn’t rank websites. Google does.Implementing structured data is a continuous learning process that requires patience and experimentation.

“It works perfectly on mobile, until you check the rankings.”

That line should set off alarms. Because in the rush to go responsive, too many teams forget that mobile UX and mobile SEO are not the same thing. A site can look incredible on a phone and still deliver zero value to Google.

And that disconnect is costing businesses more than they realise.

We’ve seen it repeatedly: mobile sites that are fast, swipeable, and conversion-optimised, yet somehow invisible in the search results. Why? Because the development decisions that improve usability often block crawlers, strip content, or delay critical rendering.

Here’s what typically goes wrong:

These might sound like UX issues, but they have direct SEO impact. Poor usability on mobile affects your Core Web Vitals scores. And in Google’s eyes, those are ranking signals. If your page shifts around, lags behind user interaction, or hides too much content behind gestures, your visibility drops.

Google’s mobile-first indexing means your mobile site is your site. It’s the version that gets crawled. It’s the structure Google uses to determine relevance, layout, and crawl depth. So if you’ve stripped content for speed, or hidden key product descriptions to tidy up the design, you’ve also stripped your SEO performance.

This matters most when:

And Google doesn’t wait.

Good mobile SEO is about prioritising the content that matters, and making sure it loads first, fast, and fully. That means:

These aren’t just best practices, they’re part of how Google decides what pages rank. And if you’re not measuring how your mobile decisions impact search visibility, you’re flying blind.

The intention is always good. Hide complexity. Remove friction. Make the UI as clean and conversion-focused as possible. But if the price of that polish is lost visibility, the return isn’t worth it.

Mobile optimisation done without search in mind is just design theatre. You might win on engagement, for the 1 in 100 people who land. But without mobile SEO foundations, the other 99 never show up at all.

It’s a classic case of good intent, bad implementation. You build features to support a wider audience: regional pages, filters by location, translations for new markets. But instead of gaining reach, you lose it. And the culprit isn’t the content, it’s the structure.

Most localisation issues come down to one thing: SEO signals spread too thin, or sent in too many directions.

Here’s what typically goes wrong:

From Google’s perspective, domain names matter. So do page structure, content uniqueness, and internal linking. If you’ve got five versions of the same landing page in different languages, but no clear canonical version, no hreflang, and minimal content variation, you’ve just created five pages competing with each other.

And they’ll all lose.

We’ve seen brands invest heavily in going multilingual, only to watch rankings plateau. The issue? They translated words, but not structure. Or worse, they rolled out translated URLs with no indexable content, just images and links.

If your French version of a page hides key copy behind interactions, lacks metadata in the native language, or fails to signal its relationship to the English version, Google has no way of knowing they’re connected.

And if you’ve layered this across multiple languages without a clear SEO framework, you haven’t just added complexity, you’ve diluted your visibility.

Location based content needs clarity. Too often, companies spin up region-specific pages (UK, US, Europe, etc.) with identical product descriptions, identical structure, and no clear differentiator. So Google picks one. Or none.

If you want those pages to perform, you need:

You also need internal links that help users (and crawlers) find those pages naturally, not just in a dropdown, but as contextual anchors elsewhere on the site.

Supporting multiple languages, physical location filters, and region-specific experiences is absolutely worth doing. But only when it’s done with a clear plan.

That means:

Search engines reward clarity. They penalise confusion. And if your localisation creates more of the latter, your best work may never see the light of search.

“It was faster to build this way.”

That’s the refrain you hear when things go quiet. When rankings stall, traffic dries up, and the site, despite looking polished, fails to perform in search. The build was quick. The code was clean. But the opportunity was missed.

This is the cost of convenience. And it’s rarely paid by the developer. It’s paid by the business. In lost visibility. In lower conversion rates. In paid traffic that now has to compensate for organic failure.

And here’s the hard truth: most of those decisions are avoidable.

You don’t have to choose between speed and structure, UX and indexability, modern frameworks and proper visibility. But you do have to be intentional. Because search performance isn’t something you bolt on later, it’s something you build in from the start.

If you’re a founder, product owner, or marketing lead, it’s not your job to write the code. But it is your job to demand clarity.

Ask the uncomfortable questions:

If your agency, dev team or CMS vendor can’t give you straight answers to those questions, don’t move forward. Because if you do, the hidden cost will land on your balance sheet.

If this article has made you rethink your current site, or your next build, here’s what I’d recommend:

And if you’re about to launch a new product, site, or feature?

Let’s talk before you do.

If you’d like a fresh pair of eyes on your site, or want to make sure your next build doesn’t bury your SEO, drop me a message. I’m always up for a straight conversation.

Implementing SEO changes is a critical process that demands a collaborative effort between SEO specialists and developers. This collaboration Google Search Central. JavaScript SEO Basics .https://developers.google.com/search/docs/crawling-indexing/javascript

Web.dev (Google). Core Web Vitals Overview .https://web.dev/vitals/

Google Search Central. Localized Versions: hreflang .https://developers.google.com/search/docs/specialty/international/localized-versions

Google Search Console Help. URL Inspection Tool & Index Coverage Reports. https://support.google.com/webmasters/answer/9012289

Ahrefs. Why Your Page Isn’t Ranking .https://ahrefs.com/blog/why-your-page-isnt-ranking/

Yoast SEO. SEO for JavaScript Websites. https://yoast.com/javascript-seo/

Moz. Canonicalization Best Practices .https://moz.com/learn/seo/canonicalization

Search Engine Journal. How Google Handles Duplicate Content .https://www.searchenginejournal.com/duplicate-content-google/

Smashing Magazine. Lazy Loading and SEO .https://www.smashingmagazine.com/2021/06/lazy-loading-seo/

Aleyda Solis. JavaScript SEO Auditing Checklist. https://www.aleydasolis.com/en/search-engine-optimization/javascript-seo/

I still remember the anxiety that I went through when I needed to update our website back in 2006. 

The UI was starting to feel a little dated, and as an agency, we were expected to be at the cutting edge of what was possible to sell to our clients. I had some good search engine rankings, which brought revenue to the agency. My fears were what would happen to my pipeline. We had bills and wages to pay, and the pressure I felt was not insignificant to my much younger self then.

I’m sharing my experience and observations on this topic in this article as I have done this a few hundred times since. I’ll mention real cases, detail pitfalls, and highlight success stories. I aim to give a practical view of how a fresh look can affect SEO performance.

I’ve seen clients improve their website’s search engine rankings soon after launching a redesigned website. I’ve also watched some slips in ranking because they neglected certain technical factors. For me, the key is balancing a pleasing style with solid search practices. If you’re worried about dropping off page one, I get it. I’ve been there, too, and I’m happy to help where possible.

Redesigning a website can mean different things to different people. Sometimes, it’s just changing a few colour schemes or adding new graphics. In other cases, it involves a total rebuild, from code structure to page names to the content on each page.

When discussing a site makeover, I think about something bigger than changing the font and header image. If you only swap a few colours, you won’t upset your SEO results too much. But if you switch platforms, move pages around, or shift your entire navigation menu, search engines might treat your new setup almost like a fresh website.

One of my first clients, a local department store in the village where I grew up, decided to modernise its web presence. They moved from a basic HTML site to a full content management system. This gave them new features but also changed most of their URLs. As we are changing a lot of URLs, I knew that unless we utilised 301 redirects from the old page to the new page, they would see a drop in traffic and, subsequently, rankings. Adding 301 redirects is a tedious job, and nobody really puts their hand up for it, but it is necessary and will save you time and money later on.

I usually check the size of the redesign before I predict any effect on search engine optimisation. There’s a big difference between a small facelift and a rebuild from scratch. 

Search engines rely on structured data to determine what your site is about and how pages link. They look at your navigation menu, URLs, and internal linking style. That’s why any significant changes in your layout can affect your ranking.

I’m convinced that site architecture is like the skeleton of a house. Without a clear blueprint, your pages can end up scattered. Search crawlers might have trouble discovering your new structure. You could rank well for a while, but if you move everything around without caution, you might puzzle both bots and human visitors.

I’ve worked on a blog that wanted to group all posts by date rather than topic. They hoped it would look more streamlined. This led to confusion because users were used to browsing by category. As they added more articles to the blog, the older articles were pushed onto pages 3, 4, 5, etc., and this constant change and increased number of clicks the users needed to perform to find the content were detrimental.

This is why we created the content hub approach you are reading about. All content is clearly signposted, grouped, and doesn’t move around. The benefit to the reader’s use experience and the crawler’s accessibility cannot be underestimated. 

I like to keep the main categories logical and limit the depth of pages. Nothing should be buried too far in subfolders. If I want users to find something quickly, I keep these essential web pages within two or three clicks from the homepage. 

Existing content often builds the backbone of your site’s credibility on search engines. Blog posts, product pages, service descriptions, and other written resources can become magnets for visitors. If you discard them all in a redesign, you risk wasting months or years of SEO efforts.

Before I perform a site redesign, I ask the SEO team to perform a quick content audit, which includes the following:-

Creating a spreadsheet of all the site’s pages lets you quickly see what content is working and what you need to decide about.

I often remove pages that do nothing for traffic but rescue articles with promise. If I see a piece that ranks on page two for a decent keyword, I’ll rewrite it for clarity, add more relevant details, and watch it climb to page one.

This is a process I go through for each of my SEO clients when we approach a new website. It’s not quick, but it’s necessary to maintain those valuable search engine results.

Switching links can be a huge deal. If you overhaul your site’s structure, your old links could suddenly lead to pages that do not exist and give a 404 error. This is why I get uneasy seeing random new URLs unrelated to the old ones.

Broken links annoy visitors and search engines alike. A user clicks on a Google result, lands on a 404 error, and quickly leaves. This can reduce your site’s overall credibility in the eyes of a search engine. It also frustrates anyone who used to visit your pages from external blogs, social media, or email newsletters.

To avoid this, I carefully plan my redirect map. If the new site replaces a page that used to live at /services/web-design with a page at /services/site-design, I’ll put a 301 redirect in place so that Google and users automatically land on the correct new page. A 301 redirect tells search engines that the old page has a permanent new home.

I am currently working with one client who is running a booking platform similar to Airbnb but for fisheries. I performed an SEO analysis of their website and analysed their keyword rankings. I discovered that 90% of their search traffic came from fishery brand terms. However, the URLs for these profiles were not user-friendly, and we are currently considering what we can do to the existing site to make them user-friendly while maintaining SEO rankings. The answer will likely be 301 redirects, but we look at all options.

At our agency, in 2016, we saw mobile users overtake desktop users for the first time; this was backed up in October of that year when Stat Counter released their study. An article can be found here: https://techcrunch.com/2016/11/01/mobile-internet-use-passes-desktop-for-the-first-time-study-finds/?t

On July 5, 2024, Google officially dropped its desktop crawler in favour of a mobile-first approach, so the importance of having a mobile site changed forever. 

Mobile page speed and user engagement are now more important than ever before. So many times have I created an article or new web page and been so proud of it on my desktop that it is only when I check it on my mobile device that I realise it could be way more friendly.

Slow sites push people away. If you’ve ever tried to load a page on your phone and spent ten seconds waiting, you’ve felt that frustration. That frustration leads to back-button clicks, which can hurt your ranking. To reduce page load time, I often compress images, remove unnecessary scripts, use a content delivery network (CDN) and implement caching.

It’s tempting to revise everything during a redesigning process, including tags, meta descriptions, and headings. Sometimes, though, your existing tags are already doing well. I prefer to keep high-performing titles intact. But if I see outdated or irrelevant wording, I’ll rewrite it.

Title tags remain one of the strongest signals to search engines. Meta descriptions may not directly change rank, but they can boost click-through rates if written well. I like to maintain the same primary keyword focus so I don’t accidentally lose the momentum that page had built.

Header tags (H1, H2, H3) guide readers and search bots through your content. Poorly structured headings make it tough for people to skim and for crawlers to understand. If a redesign changes the look of headings, that’s fine, but I never sacrifice their logical order.

Structured data is another factor—markup for FAQs, Locations, Products, reviews, recipes, or events can help you appear with rich snippets in search results. If you lose that markup during a code rebuild, you might miss out on those eye-catching extras in Google’s listings.

I prefer to do a thorough check right before the launch. I’ll compare the old site’s headings, tags, and structured data to the new site’s. If I spot anything missing or misaligned, I fix it quickly. That small effort can protect the search presence you built over time.

I have realised that a visitor’s experience directly links to search ranking. If users can’t find what they need, they leave in frustration. That short session length signals potential problems for Google. You are probably reading this on Google Chrome, which is reporting all of your behaviour back to Google to help influence its rankings. How long did you spend on the page, how far down the page did you reach, what elements did you engage with, etc? I believe the strong user engagement signals are a way of bubbling up the content the audience relates to the most.

During a redesign, I pay close attention to the main navigation menu. It should be clear where each link takes you. I avoid burying crucial pages under several layers of submenus. I also want my calls to action to be visible and straightforward.

Readability counts as well. Huge blocks of text can overwhelm. I prefer shorter paragraphs, bullet points, and a few visuals. That approach is friendly for visitors and search bots that parse page structure. I hope we live this advice as you read this and other articles on our site.

backlinks links pointing to your pages can do wonders for search standing. When you revise your site, those inbound links might suddenly send people to missing pages unless you set up proper redirects. That can hurt your credibility and link equity.

I regularly check my clients’ backlink profiles with tools like Ahrefs or SEMrush. I see which pages draw strong inbound links. Then, I protect those pages’ URLs or map them carefully if we change them. We might lose valuable traffic and credibility if high-value pages disappear without any redirects.

If you change your business name or domain, the risks rise even further. You want to let your affiliates and partners know you have a new address. They can update their links. Meanwhile, you should keep a redirect chain from old addresses to the new site. That way, the flow of authority remains intact.

A redesign shouldn’t be guesswork. I rely heavily on tracking tools to measure what happens to my traffic after I switch over. Google Analytics is my go-to for user behaviour, and Google Search Console helps me see how impressions and clicks shift over time.

I like to set benchmarks. Before the redesign, I noted my baseline metrics: average search position, bounce rate, organic sessions, and conversion rate. Then, once the new site is live, I track those metrics daily or weekly. If I spot a sudden drop in a specific area, I investigate.

I am currently working with a wholesaler of goods in the fishing tackle sector who changed their domain name in 2023. While every best practice was undertaken to preserve ranking, it still took them a year to return to the traffic levels before.

I also monitor mobile performance and site speed metrics right after launch. Sometimes, a fancy redesign can be code-heavy. If load times spike, visitors may leave quickly. I can fix any issues early by staying alert and reducing ranking damage.

A redesign is a process, not a one-time event. If I see signals of trouble, I pivot. That’s how I’ve saved clients from deeper ranking slides.

One of the biggest pitfalls is forgetting about technical SEO. I’ve seen a site launch with beautiful images and neat text without proper meta tags or headings. Sometimes, people skip the alt text on images. That might not sound major, but search engines care about these signals.

Another trap is ignoring user input after the redesign. I always watch the site’s analytics and listen to feedback. If visitors say something’s hard to find, that’s my cue to rearrange or rename it. If a redesign confuses customers, they leave. That bounce can drag down your ranking.

There’s also the risk of slower page speed. Some new themes come with bulky scripts and heavy plugins, which are easy to miss if you look at your local version. I test speeds on real devices, not just in my developer environment.

I also avoid launching a new site without solid testing. I run staging environments where I can spot broken links. I do my best to confirm that the main features work across desktop and mobile. This approach has saved me from pushing out code that breaks fundamental pages. 

A final pitfall involves ignoring a step-by-step plan. If you switch everything in one day, you might struggle to find and fix what caused a problem. I prefer a phased approach, especially for large sites. If something goes wrong, you only have to backtrack on a small part rather than the entire redesign.

My advice would be meaningless if I did not practice what I preached, so it would be remiss of me to use this section to discuss my agency’s site.

At Ronins, we started off using Google PPC to generate instant leads. However, this was getting more expensive as more and more people saw PPC as a means of instant gratification, and the spending was unsustainable for our situation at the time. (For example, we spent £30k a month on PPC at my last agency; I have heard this has tripled in the last couple of years.)

So, we started an SEO strategy to supplement our lead generation while networking like crazy. We redesigned our website from an off-the-shelf template into a custom build on WordPress using ACF blocks, ruthlessly focusing on user experience, indexability, and page speed. 

We did not have any organic traffic to worry about, and with the help of tools like aHrefs, we quickly learnt that we were creating articles without performing any keyword research. In effect, we were publishing and preying.

We set about building out our content hub, where this article is found. We started again from scratch; each article was re-written, new images were found, and we even added Spotify to our articles so that our audience could listen to them over reading. We gave our users a choice.

This felt like a never-ending trudge of article writing without any traffic. In fact, it took about 6 months to see something and about a year to see any real tangible benefits. The good thing about writing good-quality articles is that their impacts compound over time, unlike PPC, where it’s like a tap turning it off, and the traffic stops.

Yes, we have made mistakes along the way. We are only human. Yes, Google has changed the rules a few times, too, as it dealt with the tsunami of AI-generated content flooding the internet. But you only learn from failure, not success, and that line from the 2005 movie Batman Returns, “Why do we fall, Bruce? So we can pick ourselves up,” is so true when you engage with search engine optimisation.

We are now starting our third year of SEO and regularly appear on the first pages for our service pages locally. A few are on the first page nationally / globally. We need to keep up the cadence of articles and perform regular monitoring and maintenance, and the compound effect will take care of itself.

Over time, I’ve created a personal list of tasks that I check whenever I’m revamping a site. Here’s the rundown:

This is the structure I follow. It’s served me well across various projects.

I think a website redesign is an opportunity, not an automatic liability. A fresh look can attract new visitors, increase conversions, and show you’re evolving. But it’s essential to go about it in a measured way.

In my experience, panic only results from a lack of planning. You might lose ground if you tackle a redesign without mapping your key pages, checking your existing SEO signals, or preparing for mobile responsiveness. Fear of losing rank shouldn’t stop you from modernising your online presence.

I weigh the pros and cons. If my site runs on old code, has poor user experience, or fails on mobile screens, then clinging to my current rank might hold me back in the long run. I’d instead take the leap, do it carefully, and come out ahead. Yes, there might be a temporary dip in rank, but if the result is a faster, more logical site, there’s a good chance you’ll climb again.

Balancing design and function is key. I see them as partners rather than enemies. I recommend always letting the user experience drive the technology and stealing a phrase from the 1999 movie Field of Dreams: ” If you built it, they will come.”

Q1: Will my rankings always drop right after a redesign?

I’ve found that a small dip in traffic can happen while Google re-crawls your site. That doesn’t always mean a permanent drop. If you’ve taken care of redirects, kept valuable content, and ensured mobile speed, you’ll likely bounce back or move higher.

Q2: Do I need a new domain name for a redesign?

In my opinion, switching domains only makes sense if you’re rebranding. Otherwise, keep your existing domain. Changing it creates extra work with redirects, and it can temporarily unsettle your authority in search.

Q3: Can I maintain my old URLs even if the design changes?

Yes, you often can. The design or platform might look and function differently, but you can keep the same URL structure. This helps preserve links, though it depends on how drastically you’re rebuilding.

Q4: Is a complete content overhaul always needed?

I don’t think so. Some redesigns may only need slight content updates. If a page is already performing well, keep its core intact. Add new info or refresh outdated sections rather than starting from scratch.

Q5: Won’t a new fancy theme automatically fix my SEO issues?

A nice template can help with layout and responsiveness, but SEO depends on more factors—titles, headings, site speed, redirects, and quality content matter too. A theme alone won’t carry your ranking.

Q6: Should I pause my marketing campaigns until my new site is live?

I’d only pause them if your site has serious technical issues or if visitors will encounter broken pages during the transition. Otherwise, you can continue marketing while you carefully implement changes.

Q7: Will a faster site guarantee a page-one rank?

Speed is a major ranking factor, but it’s one part of the bigger puzzle. A lightning-fast site needs relevant content, quality links, and user-friendly navigation to reach and hold top spots.

Many people assume a redesign always crushes their ranking. In my view, it’s more about the details. If you handle things properly, you can keep or improve your position. A redesign is a chance to refine your approach rather than reset everything.

So, does a website redesign affect your search rankings? In my view, the impact can be positive or negative. It’s how you approach it.

A site refresh can help you adopt modern design principles, speed up load times, and refine your content, which can win you more attention from search engines. But a sloppy overhaul that breaks old links deletes valuable content or ignores mobile experience can cost you dearly.

The best approach is to treat your redesign like a journey, not a quick fix. Start by auditing your content. Protect or map your most powerful pages. Prepare for URL changes. Watch your data after launch. If you see problems, don’t panic; address them as soon as possible.

I like to remind people that a short-term drop can happen, even if you do everything right. Google may need time to adjust to your new structure. But you should regain momentum if you’ve retained your best material, used proper redirects, and improved speed and mobile use. Often, you’ll end up better off than you were before.

I hope my stories and observations have offered clear, direct advice. A well-planned redesign can keep your visitors happy and your ranking safe. Don’t fear a fresh look. Embrace it with a careful plan, and you’ll likely see stronger performance in the end.

Thanks for reading, and good luck with your changes!