Why comparisons go wrong
Looking at other sites is useful. It shows what visitors in your field expect, which topics are covered, and where your own pages are thin. But a comparison is easy to misuse. A rival’s site shows only its public surface. You do not see its traffic, budget, history, staff, conversion rates or what it tried and removed. Drawing a firm conclusion such as “they rank above us because of their design” from outside information is usually guesswork.
A fair comparison is modest in what it claims. It asks “what can I observe, and what does it suggest I examine on my own site?” and stops there.
Choose the right peers
The first mistake is picking the wrong sites. The biggest name in your industry may not be a sensible benchmark for a small shop or local service. Consider three groups:
- Search competitors: sites that appear for the phrases you care about. These may differ from your business competitors, and they can include directories, publishers and forums.
- Business competitors: organizations that offer what you offer to the same kind of customer.
- Near-peers: sites of similar size, age and resources. These are often the most realistic reference point.
Aim for a handful, perhaps three to six, and write down why each one is on the list. If a site is on it only because it is famous, take it off.
Compare like with like
A comparison only makes sense when the things being compared are alike. Some examples of mismatches to avoid:
- A site with thousands of pages against one with fifty. Differences in content volume say little about quality.
- A site with years of history against a new one. Age affects how much of the web knows about a site.
- A national brand against a local business. They are usually answering different searches.
- A homepage against an article. Compare page types that serve the same purpose, such as one product page with another.
If you cannot find a comparable match, say so in your notes instead of forcing one.
What you can reasonably observe
From the outside, you can look at a good deal without special access:
- Content coverage: which topics, questions and formats they handle, and where you have content gaps they have filled, or the reverse.
- Page structure: how they organize categories and navigation, and how deep important pages sit.
- Page basics: how their titles and descriptions are written, how pages are laid out, and whether the content matches the likely search intent.
- Experience: how their pages feel on a phone, how fast they appear to load, whether pop-ups get in the way, and how clear their calls to action are. Your own device testing applies to their site as well.
- Trust signals: contact details, policies, authorship, reviews and how clearly the business is described.
Notes taken as a reader, not as an auditor, are often the most useful. Open their site as a visitor and note what makes a task easier or harder than on yours.
What you cannot observe
Be honest about the limits. You cannot see their actual visits, sales, rankings over time, search budget, internal tests or whether a feature was helpful or harmful. Third-party estimates of rival traffic and links exist, but they are modeled approximations, can be far from reality, and tend to be less reliable for smaller sites. Treat any such figure as a rough indication at best, and avoid presenting it as fact in a report.
You also cannot tell cause from correlation. If a rival has long articles and good visibility, the length may not be the reason. Many other things could explain it.
Turn observations into questions
The best output of a comparison is a list of questions about your own site, not a list of copycat tasks. For instance:
- They answer a question we do not. Should we, and do we have something useful to say?
- Their product pages show information we leave out. Do our customers need it?
- Their checkout has fewer steps. Where might our own process cause people to give up?
Each question can be tested or investigated using your own data, which will always be more relevant than another site’s surface.
Keep your own goals in view
Matching a competitor is not the same as serving your visitors. A rival may have features that do not suit your audience, or tactics that add risk, such as heavy use of automated or thin pages. Copying what looks like success can also copy their mistakes. Decide what your site is trying to achieve and compare only on measures tied to that aim.
Repeat sparingly
Competitors change, but you do not need to track them weekly. Checking a short list once or twice a year, or when you plan a major update, is usually enough. Record the date and what you noticed so you can see changes over time. Compare yourself most often with your own past: your own trend over twelve months says more about your progress than a snapshot of someone else’s site.
A simple template
For each peer, write down:
- Why it is a fair comparison (type, size, audience)
- Two or three things it does better, as you perceive them
- Two or three things you do better
- Questions this raises for your own site
- Anything you cannot judge from outside
Keep the template short, and keep the conclusions hedged. A fair comparison is a source of ideas to test, not a verdict.