A competitor’s website shows the result of decisions, but rarely the evidence, constraints, or commercial conditions behind them. You can see its navigation, wording, and features without knowing whether they work well. Copying the result can therefore bring another business’s assumptions into your project while leaving your own problem unresolved.
I would use competitor research to ask better questions and assess different ways of explaining an offer. The brief should then return to your audience, services, evidence, and operating capacity. That gives useful observations a role without allowing a neighbouring business to define what your website needs.
A prominent competitor may have a strong website, a weak one, or a mixture of both. The useful task is to distinguish what can be learned from what remains unknown. Appearance and reputation should not be treated as complete evidence of a successful customer journey.
Begin with a question worth investigating
Decide what the comparison should inform before collecting examples. You may want to understand how service suitability is explained, how evidence is presented, or what visitors are asked before making an enquiry. A defined question makes the review more useful than a search for impressive homepages.
Choose examples that offer different relevant approaches. If every reference uses the same presentation, one arrangement can appear inevitable without being appropriate. Include your own site in the comparison so the observations lead back to a decision about an actual gap.
Record the conditions of the review. A public page, a mobile navigation path, and a logged-in service reveal different information. Note what you could inspect and where access or functionality was outside scope. That prevents a partial observation from becoming a judgement about the entire business.
Keep the research manageable. The objective is enough evidence to inform a defined choice, not a catalogue of features.
Check whether the underlying businesses are comparable
Two organisations can serve the same sector while selling different engagements. A large provider may address procurement teams and complex buying processes. A personal consultancy may need a clearer route to one informed conversation. Similar visual styles do not establish equivalent customer needs.
Compare the actual offer, audience, and working arrangement. What must the reader understand before choosing? What happens after the contact action? Which information needs ongoing maintenance? These questions help identify whether a reference is relevant to your own project.
For an illustrative consultancy, copying an agency’s extensive services menu could fragment a focused offer. The agency may have distinct teams behind those categories while the consultant works across a connected problem. A useful comparison could still reveal how evidence is made understandable without justifying the same architecture.
Treat navigation as a statement about the business
Navigation looks like a design detail, but it expresses how a business expects people to understand its offer. A competitor may organise its services by industry sector because its teams, case studies, and sales process are structured that way. Your business may work across sectors with a few technical specialisms, and the same menu would hide the distinctions your visitors need.
A large menu can also create pressure to add a page for every service a competitor lists. That expands the offer on paper before anyone has confirmed that the business can or wants to deliver it. For an illustrative consultancy, a long services menu borrowed from an agency could fragment a focused offer, because the agency may have separate teams behind those categories while the consultant works across one connected problem.
I would start from the questions customers ask and the choices they need to make, then group pages around those tasks. Competitor navigation is useful for spotting familiar language and possible gaps. It should not decide the shape of your business.
Separate visible observations from performance claims
A long form is visible. Whether it improves qualification is a separate question requiring evidence. A prominent button can be observed without knowing how many suitable visitors use it. Keep those levels distinct in the research record.
A business’s demand can also reflect referrals, relationships, reputation, and wider marketing. A busy company can tolerate a difficult journey, while a well-designed site can still receive limited relevant traffic.
Search visibility needs the same care. A competitor ranking for an attractive query is evidence of what a search system currently shows for that query, not an instruction to copy its page. The visitor may want an explanation, a comparison, or a provider, and those tasks call for different pages. Adding a ranking guide’s headings to a service page could make it longer without helping anyone evaluate your services. My article on the searches a service page cannot win explains how to tell the difference.
Where evidence is unavailable, describe a hypothesis. You might investigate whether clearer scope information would help your visitors, rather than say another business has already proved the value of a layout. That keeps the proposed next step proportionate and testable.
Distinguish an expert review from user testing
Reviewing a website yourself can reveal likely strengths, gaps, and usability concerns. It does not establish how its entire audience behaves. Your familiarity with the industry and the task can make some information seem clearer than it would to a prospective customer.
Nielsen Norman Group’s guide to competitive usability evaluations distinguishes expert reviews from tests in which people perform tasks across designs. Those approaches produce different kinds of evidence. Name the method used rather than describing every inspection as user research.
If you need to learn about task performance, choose a proportionate study with realistic tasks and relevant participants. Avoid treating a favourable opinion of the appearance as equivalent to completing the intended journey. A prototype can help explore a decision, provided its limits remain clear.
The method should fit the uncertainty and the consequence of getting the decision wrong. A focused review may identify an obvious information gap, while a difficult interaction may deserve observation of actual use.
Read content as evidence of positioning
Examine what the competitor’s pages make clear and what they assume the reader already knows. Identify questions about suitability, scope, process, and the next step. These observations can help assess your own information without adopting another company’s voice or claims.
Prepare your content from the real offer and supporting evidence. Changing a name in another business’s wording does not explain your position. Nor should a strong-looking claim become yours unless the facts support it. Project examples, qualifications, and service promises need their own verification.
My article on auditing website content explains how purpose and overlap can guide these choices. Use competitor observations to identify questions, then assess whether an existing page should answer them before creating another destination.
Follow the journey around the component
Start from a realistic entry point and work towards the intended action. A visitor may arrive on an article or service page rather than the homepage. Consider the information available at each step and what the person needs before continuing.
A comparison table can look useful while leaving important conditions unexplained. A booking button can be easy to find while giving little indication of commitment or next steps. Review the surrounding explanation before treating the component itself as a solution.
For an illustrative audit service, readers may need to know whether fixes are included before choosing an option. Moving a button higher would not resolve that uncertainty. The information sequence deserves attention alongside its visual treatment.
My article on traffic without useful enquiries develops the complete journey. A copied visual feature may leave the source of friction untouched. The strongest recommendation should identify the obstacle and explain how the proposed change addresses it.
Examine the operating cost behind a feature
An interactive calculator, personalised dashboard, or complex comparison creates obligations beyond the visible screen. Its information needs an owner, its behaviour needs testing, and faults need a practical response. Another business may have systems or capacity your project does not require.
Before adding a similar feature, describe the task it supports and compare simpler alternatives. A clear explanation or appropriately designed form may be enough. A specialised tool becomes more credible when it answers an established need the simpler arrangement cannot meet.
Ask what happens when underlying information changes. Who updates the rules, reviews accuracy, and checks connected behaviour? An impressive launch can become a misleading experience if the business cannot maintain the feature. That cost belongs in the decision.
My article on website decisions before features explains why capability is not justification. The ability to reproduce a component, including with AI assistance, should not determine whether it enters the scope. The project needs a reason grounded in the audience and operating model.
Turn the research into an independent brief
Summarise useful observations, questions they raise, and requirements supported by your own evidence. Mark assumptions and include the conditions under which the observation was made. The designer should be able to understand why a reference matters without being told to recreate it.
Name the quality you want to explore: clearer hierarchy, easier comparison, more relevant evidence, or a dependable next step. Leave room for a design that fits your content and assets. A reference using elaborate photography may suggest a hierarchy principle without requiring imagery you do not possess.
Familiar conventions such as clear navigation, understandable buttons, and predictable forms reduce effort for visitors, and there is no need to avoid them. Reproducing another business’s distinctive typography, composition, photography, and tone is different. It can make your site read as a less confident version of the original, and it may communicate the wrong personality. Ask instead how formal the experience should feel, what must be understood immediately, and what someone should remember afterwards. Then translate a reference’s underlying principle into your own system rather than its surface.
My guide to briefing a web designer shows how to provide that context. Retain the distinction between preference and evidence. You can like a presentation without claiming it has been proven effective for your audience, and the designer can assess both honestly.
Test the recommendation and keep its limits visible
Define the behaviour the proposed change should improve and the checks needed afterwards. A revised service explanation can be reviewed for accuracy and understanding. A changed form needs functional verification as well as a suitable information sequence. Match the assessment to the claim.
Record what changed and why. Where possible, avoid bundling unrelated modifications that make later interpretation difficult. If several changes are necessary together, recognise that a subsequent outcome cannot easily be attributed to one component alone.
Assess meaningful evidence over a suitable period. Do not require every useful improvement to produce an immediate revenue increase, or label a change successful solely because the new page resembles the reference. The question remains whether your website serves its task more dependably.
If another site has prompted concern about your own, begin by identifying the actual weakness. Competitor research is useful when it leads to better questions, clearer information, and justified decisions. Sometimes the right decision will resemble a competitor’s solution, and sometimes it will be deliberately different. I would rather build a website that can explain its decisions than one that can only point to another site as justification. A modest improvement with a clear purpose can be stronger than a copied design with an impressive appearance and an unexplained operating cost.
If you have collected a folder of competitor references ahead of a redesign, get in touch. We can separate useful observations from untested assumptions and turn them into decisions that make sense for your business.