WebOneWordA comparable-sales table can become misleading even when every price in it is accurately copied. The problem often lies in how the records were selected and interpreted.
Do not start with the highest headline
An exceptional transaction may involve a particular buyer, existing business or unusually strong name. Begin with a written comparison rule: extension, naming structure, meaning and date relevance. Then inspect the records that meet it, including the less spectacular ones.
A single attractive sale is not a market distribution. Neither is a list containing several reposts of the same report.
Keep price types and currencies separate
Seller asking prices, auction bids, installments and reported completed sales answer different questions. Put each in its own group. Preserve original currency and identify any conversion supplied by the source.
Applying today's exchange rate to an old transaction creates a new estimate, not the historical amount. Do not present it without an explicit method and date.
Check what the date describes
A report date may be later than the transaction. A marketplace observation date may not describe a sale at all. An undated record should remain undated rather than receiving the import date as an invented closing date.
Look for missing context
Read notes on included assets, broker attribution and verification. A domain-only transfer and a purchase of an operating website are not interchangeable comparisons.
Make the limitation visible
WebOneWord's related-sale matches provide reasons such as extension, structure and category. They are research candidates, not a valuation model. Use the source links and reject records whose context does not fit your decision.
A smaller, defensible peer group is usually more useful than a long list assembled only to support a preferred price.
Maintained by WebOneWord Team. Last reviewed: 2026-10-07.