When pricing domains for end users, one yardstick which I have found useful is to use Google's Traffic Estimator to get a rough idea what the budget would be to run ads on that exact phrase. While not a precise measure due to the number of factors that ultimately determine a given advertiser's CPC, having the general recommended budget range handy is especially useful when pitching an exact match domain to a company that is on the first page for ads, but not in natural SERPs.
In the last few months I have closed several end user sales based mainly around this metric -- the estimated annual AdWords budget vs. what I am asking for the domain, with a discount applied to the domain since the AdWords ad is basically "buying one's way to the front" while the domain name is not guaranteed to put them there.
Prospects for this particular pitch are: Companies that are on the second and third page of the SERPs for that domain's keyphrase, but not the first; companies that are on the first page of related phrases, but not for the domain's keyphrase; and companies that are showing on AdWords and on the ads on the domain's parking page (I always take a screenshot and provide it in my sales material.)
Frank
In the last few months I have closed several end user sales based mainly around this metric -- the estimated annual AdWords budget vs. what I am asking for the domain, with a discount applied to the domain since the AdWords ad is basically "buying one's way to the front" while the domain name is not guaranteed to put them there.
Prospects for this particular pitch are: Companies that are on the second and third page of the SERPs for that domain's keyphrase, but not the first; companies that are on the first page of related phrases, but not for the domain's keyphrase; and companies that are showing on AdWords and on the ads on the domain's parking page (I always take a screenshot and provide it in my sales material.)
Frank




