---
title: Competitor Analysis
published: true
index: 30
tier: free
---

# Competitor Discovery and Page Comparison

Use this workflow to understand the audited business, select defensible competitors, compare equivalent public pages, and supply competitor evidence to applicable experience and supporting-lens checks.

## In this file

- [Build the target business profile](#build-the-target-business-profile)
- [Build the candidate set](#build-the-candidate-set)
- [Select the comparison set](#select-the-comparison-set)
- [Pair equivalent pages and states](#pair-equivalent-pages-and-states)
- [Compare the experience](#compare-the-experience)
- [Hand evidence to checks](#hand-evidence-to-checks)

## Build the target business profile

Resolve the target through the [operating contract](../core/operating-contract.md). Use, in descending order of authority:

1. user-provided business context and competitor URLs;
2. the current storefront and its public product, collection, policy, about, and content pages;
3. repository configuration, product data, and prior compatible reports;
4. public third-party descriptions only for facts the target does not establish itself.

Record:

- primary product categories and hero products;
- price bands, catalog breadth, markets, and sales channel;
- intended audience, use cases, and purchase occasions;
- brand positioning, voice, visual traits, and stated differentiators;
- primary conversion actions and important page templates;
- facts that remain unknown or conflict across sources.

Do not infer sensitive customer attributes or invent a positioning statement from visual style alone. Use no connected source other than the optional target-bound GitHub repository.

## Build the candidate set

Treat user-provided URLs as required candidates. Verify that each URL is reachable, identify the represented product/category and market, and classify it rather than assuming it is a direct competitor.

When public web discovery is available within the read-only audit:

1. Search current category, hero-product, use-case, price, audience, and substitute-product terms derived from the target profile.
2. Find brand-owned storefronts selling the same or substitutable products in the relevant market.
3. Gather current public evidence of category relevance and scale, such as product breadth, retail distribution, review volume, search prominence, reputable coverage, or clearly documented market presence.
4. Capture the public source, access date, and the exact claim it supports.
5. Keep discovery notes separate from page-comparison evidence.

Do not call a brand “largest,” “leading,” or “top” from familiarity or search rank alone. Use `high`, `medium`, or `low` selection confidence when scale evidence is incomplete.

## Select the comparison set

Rank candidates using:

| Dimension | Question |
| --- | --- |
| Product overlap | Does the brand sell the same product or solve the same use case? |
| Audience and positioning | Does it compete for a similar customer, occasion, aesthetic, or gift? |
| Price and channel | Is the purchase context reasonably comparable? |
| Market relevance | Does it sell in the target geography and current category? |
| Scale evidence | Is there current public evidence that it is an established benchmark? |
| Design usefulness | Are equivalent public pages reachable and sufficiently complete to compare? |

Select three to five brands by default:

- two or three direct product/category competitors;
- optionally one major substitute or adjacent lifestyle competitor;
- optionally one aspirational design benchmark with a clearly labeled weaker commercial overlap.

Prefer direct relevance over fame. Exclude marketplaces, resellers, inaccessible pages, stale brands, and brands whose only similarity is visual taste. Record why each selected and material excluded candidate was classified.

## Pair equivalent pages and states

Pair the target with the closest available competitor page by:

1. surface: homepage, collection/search, product page, cart, or content;
2. product/use case and customer decision;
3. price tier, variant complexity, availability, and market;
4. viewport and comparable state.

For product-page comparison, use the closest representative product rather than each brand's most dramatic page. Record product name, URL, price, market, access date, and important comparability limitations.

Use only public, anonymous, read-only states. Do not sign in, create accounts, submit forms, add reviews, complete purchases, or mutate a cart or checkout.

## Compare the experience

Capture the same desktop and mobile viewport sizes where practical. For each paired page, inspect:

- first viewport, page length, content order, and primary action position;
- navigation, product/category orientation, and choice density;
- composition, typography, spacing, imagery, motion, and responsive recomposition;
- product proof, media, specifications, benefits, objections, trust, reviews, policies, and brand story;
- loading, empty, error, unavailable, validation, sticky, drawer, and overlay states that are safely reachable;
- accessibility or performance differences only when directly measured through their owning checks.

Record observed facts before interpretation. Quantify positions, counts, dimensions, or content depth only with a declared method and comparable viewport. Preserve target strengths and distinctive brand choices as well as gaps.

A competitor pattern is inspiration evidence, not a requirement. Do not:

- recommend copying a competitor's layout, assets, copy, claims, trade dress, or interaction verbatim;
- assume a pattern converts better because a large brand uses it;
- add unsupported product, durability, sustainability, security, warranty, or performance claims;
- treat more content, more features, or greater visual similarity as inherently better;
- penalize a deliberate target difference that serves its audience or positioning.

## Hand evidence to checks

Attach the paired competitor URL, observed pattern, comparability limits and target observation to the existing selected Check's supporting context. Competitor behavior never substitutes for required target evidence or establishes conversion uplift.

Use the [check evaluation workflow](check-evaluation.md) for outcomes and the [reporting contract](../core/reporting-contract.md) for supported Issues. Do not select extra Checks, create a competitor coverage row or fail a Check merely because a competitor has an additional feature. Unavailable comparison pages are a supporting-evidence gap unless the selected Check genuinely requires them. Preserve relevant selection notes and comparisons in that Check's evidence or an external artifact.
