← All posts Blog

Buying an Existing Website: My Step-by-Step Strategy

A step-by-step strategy for buying an existing website: analytics, SEO penalties, legal/IP risks, traffic, GEO, monetization, negotiation, deal terms and USD valuation.

Quick article contents
  1. Deal map
  2. What the seller is afraid of
  3. How to reach the owner
  4. What data to request first
  5. How to read audience behavior
  6. Traffic sources: what to check deeper
  7. Search queries and topic risk
  8. Geography: US, Russia and other markets
  9. Audience
  10. Content and top pages
  11. How to identify the project stage
  12. AMP, Turbo and technical factors
  13. Negotiation: how to reduce price with specifics
  14. How not to break the deal
  15. Fixing terms and transfer
  16. Advanced check: penalties, filters and collapse risk
  17. Legal and IP points before buying
  18. Red flags
  19. Final pre-purchase checklist
  20. Deal Agreement: what to write down to avoid problems
  21. Final takeaway: market multiples and where to find price-reduction arguments
  22. Initial Website Valuation Calculator for Negotiation
Main idea

Buying an existing website is not about finding a domain and sending money. A safe deal follows a sequence: contact → trust → simple data request → analytics check → evidence-based negotiation → written asset scope → secure transfer through escrow.

1. Deal map

StageGoalWhat to do
Initial contactFind the owner and get a reply.Show seriousness, use a clear but careful price anchor or range.
Data requestGet a basis for valuation.Start with screenshots or read-only access to GA4, Search Console, Yandex Metrica or ad dashboards.
NegotiationReduce price with facts.Do not just say “too expensive”. Use risks: traffic drops, weak monetization, seasonality, bots, dependence on one source.
Fixing termsLock the price and asset scope.Write down domain, files, database, CMS, analytics, social accounts, mailing lists, rights and seller support.
TransferReceive the asset safely.Money goes to escrow. Verify the transfer first, then release the payment.

2. What the seller is afraid of

Most sellers worry about three things: safety, money and time. The better you address these concerns, the easier it is to get data, negotiate and close.

  • Safety. Do not ask for passwords at the beginning. Ask for screenshots or read-only access. Offer escrow from the start.
  • Money. Show that you have a budget and are not just testing the market.
  • Time. Do not send a 40-question audit request in the first email. Make the first step easy.

3. How to reach the owner

Use Whois and historical Whois, emails on the site, contact forms, social accounts, group admins, comment sections, phone numbers, old page versions, domain mentions, old marketplace listings and public profiles. Hosting support is a last resort: do not ask for personal data; ask them to forward your message to the owner.

First message template

Hello,

I’m interested in [domain]. I buy websites in this niche and wanted to ask whether you would consider selling it.

Based on a quick preliminary check, I would be ready to discuss a deal around [amount/range], final price depending on a quick review of traffic, revenue and the asset scope. I am happy to use escrow.

If that sounds interesting, what would be easiest for the first step: screenshots from Google Analytics/Search Console/Yandex Metrica for the last 6–12 months or read-only access?

Best,
[Name]
[Phone]
[Profile / company]

4. What data to request first

It does not matter whether the site uses Yandex Metrica, Google Analytics, GA4, Search Console, server analytics or ad dashboards. The goal is the same: you need confirmed traffic dynamics, sources, revenue and audience quality.

BlockWhat to requestWhy it matters
Traffic6–12 months, ideally the full available history.To understand trend, seasonality, drops, spikes and dependence on one source.
SourcesSource summary for the last 3 months and earlier periods.Highlight all sources above 3% and check whether any previous source disappeared.
RevenueRevenue screenshots, payouts, expenses, ad networks and affiliate programs.Count net income, not promises.
SearchGoogle Search Console, Yandex Webmaster, queries, pages, countries and devices.Understand where organic traffic comes from and where ranking risk exists.
ContentTop pages, recent posts, update dates and authors.See whether the site depends on old content or new articles can also generate traffic.
TechnicalCMS, hosting, speed, uptime, plugins, backups, cron jobs.Estimate future migration and maintenance costs.
AssetsDomain, files, database, design, social accounts, channels, email list, source files.The price depends heavily on what is actually included.

5. How to read audience behavior

Do not value a site by visits alone. Two websites with the same traffic can have completely different value if one has engaged commercial users and the other has bots, random queries and weak engagement.

MetricBadAverageGoodGreat
Pages per visit1–1.21.2–1.41.4–22+
Time on siteunder 1 min1:00–1:301:30–3:003:00+
Bounce rateabove 12%9–12%6–9%below 6%
Time to renderover 3 sec2–3 sec1–2 secunder 1 sec
Filtered bots20%+10–20%5–10%below 5%

Adblock matters too. If more than 15% of the audience blocks ads, include this as a valuation discount, especially for display ad monetization.

6. Traffic sources: what to check deeper

  • Traffic structure. Look at the last 3 months and investigate every source above 3%.
  • Historical anomalies. Use the maximum analytics period and find sources that used to drive traffic but disappeared.
  • Referral sites. Check whether referrers include bot or traffic manipulation services.
  • Other owner sites. You can often find them through referrals, similar templates, similar monetization, common contacts or SEO tools.
  • Social media. If social channels drive meaningful traffic, they should be included in the deal or the price should go down.
  • Recommendation systems. If recommendation traffic disappeared, there may be a ban. If it is active, check clickbait, topic changes and misleading headlines.

7. Search queries and topic risk

Search queries should be checked not only in analytics but also in tools such as Ahrefs, Semrush, Serpstat, keys.so or the tools relevant to the target country. For US and English-language sites, the main focus is usually Google Search Console, Google organic traffic, US/CA/UK/AU geography and the commercial value of keywords.

  • medical, health, weight loss, beauty and pet health queries are sensitive to quality updates;
  • adult and borderline queries increase monetization and reputation risks;
  • seasonal queries, dates and events should not be valued by a peak month;
  • off-topic articles usually monetize worse and may indicate random traffic.

8. Geography: US, Russia and other markets

The old “75–90% Russia is normal” rule only fits Russian-language projects built for Russia/CIS. If you buy a US-focused site, the opposite is true: check the share of US and other Tier-1 traffic. If an English site has a large share of India, Pakistan, the Philippines or a random country mix, revenue per visitor can be much lower.

Practical rule

Value the site by target-country traffic, not total traffic. For a US project, 10,000 US visitors can be worth more than 50,000 visitors from low-RPM markets.

9. Audience

  • Age. For many content and commercial sites, the 25–55 audience should be the core. If it is too small, monetization may be weaker.
  • Gender. Check whether the audience matches the topic. In some niches a skew is normal; in others it signals random traffic.
  • Dynamics. Sudden changes by gender, age, country or device can indicate bots, purchased traffic or source changes.

10. Content and top pages

A good site should not depend on one or two pages. The wider the traffic distribution, the lower the risk of losing the asset after one update or one article drop.

  • Review top pages and whether they match the site topic.
  • Check whether the topics can be monetized.
  • Take the latest posts from the last month and see how they perform in search after 2–3 months.
Traffic by month 3 after publicationRating
under 30 visitorsbad
30–100average
100–200good
200+great

For US sites and narrow niches, adapt these thresholds. In an expensive commercial niche, lower traffic can still be valuable. In a broad informational niche, weak performance of new posts is a serious minus.

11. How to identify the project stage

Use the organic search traffic graph, not the seller’s description.

StageSignalValuation multiple
GrowthOrganic traffic is growing, new posts rank, no major drops.up to 18 months of income
PeakTraffic is high, but future growth is unclear.up to 10 months of income
StagnationTraffic is flat and growth points are limited.up to 12 months of income
DeclineTraffic is falling, new posts do not work, filters or updates may be involved.up to 6 months of income

Sharp drops must be explained. A drop to zero may be a disabled tracking code. A 30–90% drop is more often caused by filters, search updates, structural changes, technical errors or the loss of a traffic source.

12. AMP, Turbo and technical factors

If the site uses AMP, Turbo or similar technologies, overlay that condition on the search traffic graph and see when it was enabled and how it affected traffic. If it is active now, it may help traffic but reduce monetization — sometimes by up to 30% if users consume content outside the full site page.

Also check stability. Frequent downtime is a price discount, but sometimes it is a growth opportunity if you can fix it quickly after purchase.

13. Negotiation: how to reduce price with specifics

Real negotiation is not “please discount it”. Collect the data first, then show which risks require investment.

Weak pointQuestionNegotiation use
Few articlesHow many posts are published and how many actually get traffic?Future content investment is required.
No recent publishingHow often were articles published in the last 6–12 months?The site may be stagnant.
Traffic dropWas it caused by an update, migration or technical change?Organic decline is a strong discount argument.
One-time spikesWhere did the spikes come from and can they be repeated?Spikes should not be counted as stable revenue.
Weak monetizationWhat is the net monthly income after expenses?Value by average income, not the best month.
Incomplete asset packageWhat is included: domain, site, database, design, social accounts, channels?If assets are missing, the price should be lower.
Dependence on sellerWhat stops working without your involvement?You need a discount and post-sale support.

Soft negotiation formula

The project looks strong, especially in terms of [traffic/domain/content]. But the data shows a few issues: [drop/seasonality/weak monetization/technical costs]. Because of that, I cannot accept the current valuation in full.

Considering these risks, I can offer [X] with escrow and fast payment. If [social accounts/email list/support/design] are included, I can discuss [Y].

14. How not to break the deal

  • Do not attack the seller with only negatives. Start with the strengths.
  • Do not cut the price in half without a clear bridge.
  • Do not use general market fear as your only argument.
  • Leave room: “What is the minimum level you would consider?”
  • If the economics do not work, walk away calmly. A bad purchase costs more than a missed deal.

15. Fixing terms and transfer

Before payment, write down: price, currency, escrow fee, asset scope, transfer order, timelines, inspection period, seller support, what counts as successful delivery and what happens if something does not work.

Agreement confirmation template

Confirming the agreement to buy [domain]:
- price: [amount] USD;
- deal through [escrow/platform], fee paid by [party];
- included assets: domain, site files, database, CMS access, [social account/channel/email list/design/source files], analytics access and monetization instructions;
- seller transfers all listed assets within the escrow deal;
- buyer verifies the site and access within [period];
- after successful verification, buyer releases the payment.

Please confirm that everything is correct.

16. Advanced check: penalties, filters and collapse risk

Main verification rule

Do not value only current traffic. Value the trend. A one-time spike is not a stable asset. A sharp 30–90% drop needs a clear explanation: penalty, algorithm update, technical issue, removed tracking code or lost traffic source.

A penalty/filter is not the same as an algorithm update. A global update usually moves many sites in the niche and creates SERP volatility with rollbacks. A site-level filter usually hits one site, a group of pages or one traffic source. Match every major drop against Google updates, Search Console data, indexation history, site changes and competitors.

Risk groupWhat to checkPrice impact
Text/content qualityCopied text, thin articles, empty pages, query cannibalization, mass pages not built for real search demand.Discount: cleanup, rewriting, removals and reindexing will cost money.
Link profilePaid links, link spikes, spammy donors, aggressive anchors, manual actions in Google Search Console.High drop risk. Discount heavily or avoid the deal without a recovery plan.
Behavior and manipulationUnnatural spikes, bots, strange sources, sudden changes in depth/time/bounce rate, signs of behavioral manipulation.If traffic is artificial, the real asset value is lower than the calculator result.
Ads and mobile UXAggressive first-screen ads, push subscriptions, redirects, black ad networks, ads covering content, deceptive mobile behavior.Penalty risk, weak behavior signals and lower monetization after cleanup.
Adult/YMYL/risky topicsAdult, medical, health, weight loss, finance, legal topics, clickbait and content that does not answer the promise.For the US and Tier-1 markets the risk is higher: stronger trust and compliance requirements.
Associated sitesOther sites owned by the same person: same templates, monetization, authors, cross-links and analytics footprints.If the whole network is risky, buying one domain can bring network-level problems.

Visible and hidden filters

  • Visible. Check Google Search Console: Manual Actions, Security Issues, indexing problems and sudden exclusions. For Yandex, check Webmaster warnings.
  • Hidden. There may be no message. Detect them through analytics: page drops, lost queries, one search engine collapsing, worse behavior metrics, update dates and competitor comparison.
  • No Google traffic from the start. For a US-focused project this is a major negative. If the site gets almost no Google traffic, find out whether it is new, poorly indexed, not trusted or already problematic.

Before you lock the final price

  • Request read-only access to Search Console/GA4 or screenshots for organic traffic, pages, countries and devices.
  • Compare drop dates with major Google updates and site changes.
  • Check manual actions, security issues, indexing problems and pages that disappeared from search.
  • Review top pages: make sure the whole site is not carried by 3–5 articles or one accidental query.
  • Audit mobile ads: first screen, pushes, redirects, clickbait and content overlap.
  • If AMP/Turbo or similar technology was used, understand what drove traffic and how much monetization was lost.

17. Legal and IP points before buying

For small and mid-size deals, escrow plus written asset scope is usually the practical minimum. For larger deals, use a contract where the subject is not just a “website”, but the domain plus every transferred resource.

What to checkSpecificsWhat to fix in the deal
Deal subjectDomain, files, database, CMS, design, texts, images, social accounts, channels, email list, analytics, ad accounts and instructions.List assets in escrow/messages. Anything not listed is hard to demand later.
Photos and imagesBest case: own assets or stock/licensed media. Unknown origin creates takedown and replacement risk.Seller confirms usage rights or you discount for replacing images.
VideoEmbedding from platforms is safer when embeds are allowed. Downloading and reuploading third-party video is risky.Clarify whether only embeds transfer or actual video rights are included.
Copied textAdding a source link does not automatically make copied content safe. In the US, DMCA claims can remove pages from search.Check uniqueness of top pages. If risky, discount for rewriting.
TrademarksDo not build around someone else’s brand without understanding the risk. For the US, check USPTO/brand queries; for key assets, consider your own trademark.Seller confirms no brand disputes; questionable brand domains should not be valued as safe assets.
User dataEmail lists, forms, cookies, analytics, subscriptions and leads. For US/EU/UK markets, consent, privacy policy and collection method matter.Transfer only legally collected data and confirm whether it can be used after the purchase.
Practical takeaway

Legal cleanliness is not paperwork for its own sake. It directly affects price: third-party photos, copied text, a questionable brand, a weak email-list history and risky ad formats should reduce the valuation or become a post-purchase cleanup budget.

18. Red flags

  • The seller refuses to show even traffic screenshots but asks for prepayment.
  • Revenue is confirmed only verbally.
  • The asset scope is unclear.
  • Traffic dropped and the explanation is vague.
  • The site depends on personal seller accounts that cannot be transferred.
  • Content is copied, risky or mass-generated without quality control.
  • The domain history includes spam, doorway pages, drastic topic changes or penalties.
  • The seller pushes for payment without proper verification.

19. Final pre-purchase checklist

Final rule

A good deal is not the one where you pressure the seller at any cost. A good deal is when price, risks, asset scope and transfer order are fixed so that after payment you own a working asset, not a list of promises.

Deal Agreement: what to write down to avoid problems

Even if the transaction goes through escrow, the key terms must be written down: in the contract, in the escrow deal description, or at least in a message thread that can be used if there is a dispute. For larger deals, use a separate agreement where the deal object is not just “the website”, but the domain plus every transferred asset.

What must be fixed in writing

  • Deal object: domain, site files, database, CMS, theme/template, design, texts, images, source files, analytics, social accounts, channels, email list, ad accounts and instructions.
  • Price and payment: amount in USD, who pays escrow/platform fees, when the money is deposited and when it is released to the seller.
  • Transfer order: what is transferred after escrow deposit, what is checked before release, and which accounts must become fully controlled by the buyer.
  • Inspection period: for example, 2–5 business days to check the domain, site, database, admin panel, analytics, monetization and extra assets.
  • Rights to materials: the seller confirms the right to transfer content, design, code, logos and other materials, and confirms there are no known third-party claims.
  • Accounts and recovery: after transfer, change emails, passwords, 2FA, phone numbers, account owners, DNS and registrar contacts.
  • Post-sale support: 7–30 days for questions about migration, CMS, monetization, ad blocks and old settings.
  • If something is missing: funds are not released until the issue is fixed, the price is reduced, or the deal is cancelled.

Short sample clause

The seller transfers the project [domain.com] to the buyer, including: the domain, website files, database, CMS access, theme/template, design, texts, images, analytics, monetization instructions, and [social accounts / channel / email list / other assets].

The deal price is $[amount]. Payment is made through [escrow/platform]. Funds are released to the seller only after all listed assets are transferred and the buyer checks their functionality within [inspection period].

The seller confirms that they have the right to transfer the listed assets and that they are not aware of third-party claims related to the domain, content, design, code or materials. If any listed asset is not transferred or access does not work, the buyer may refuse release of funds until the issue is fixed or agree on a price reduction.

This does not replace a lawyer for large transactions, but it prevents the main mistake: buying “a website” without a precise list of what is actually being transferred.

Download website purchase agreement template (.DOCX)

Final takeaway: market multiples and where to find price-reduction arguments

Sellers often try to price websites at around 18–20× monthly income. You may also see listings at 25–30×, but that only makes sense for strong assets: stable growth, clear monetization, clean history, traffic spread across many pages, and new content that still gains traction.

The buyer’s job is not to force a discount for the sake of it. The goal is to find real factors that reduce value and avoid risky projects that only look good because the top-line traffic number is high.

  • Traffic depends on 1–10 pages. If most visits come from a few URLs, one ranking drop can destroy the whole project economics.
  • The rest of the site is almost dead. A large index is not value by itself. What matters is how many pages actually bring traffic and revenue.
  • Traffic is seasonal. Do not value the site using its best month. Normalize traffic to an average month and use that in negotiation.
  • New articles do not work. If fresh content does not gain traffic after 2–3 months, the project may be stagnating, affected by a hidden filter, or missing a working content model.
  • There are one-off spikes. Viral posts, one-time recommendation traffic, news hype or paid traffic should not be priced as stable monthly traffic.
  • There are drops, filters or dependency on one source. Any drop in Google Search Console, GA4 or another analytics tool must be explained before the final price. No explanation means a lower offer or no deal.
  • Some assets are not included. If the seller keeps social accounts, email lists, channels, source files, ad accounts or analytics, the price should be lower.

A practical negotiation rule: the seller may ask 18–20× monthly income, but the buyer should pay a full multiple only for a stable asset. Traffic concentration, seasonality, weak new content, drops or legal/SEO risks are not minor details; they are direct reasons to lower the price.

Initial USD valuation

Initial Website Valuation Calculator for Negotiation

This is a fast first-offer calculation based on the table formula: traffic × organic share × revenue per visitor × project-stage multiplier. It is not the final deal price; it helps you choose the first number to offer after getting basic analytics.

Negotiation number

Enter the numbers and calculate. The result will show the first negotiation anchor.

How this calculation works

Formula: monthly traffic × organic search share × revenue per visitor = expected monthly income. Then the income is multiplied by the project-stage multiplier.

  1. Monthly traffic comes from GA4, Search Console, Yandex Metrica or another analytics source. It is not the final truth; it is the starting number for a first-pass valuation.
  2. Organic search share prevents overpaying for one-off spikes, social traffic, paid traffic or low-quality referrals. If exact data is missing, you can temporarily use 90%.
  3. Seasonality normalizes the number: if the current month is 20% above the average month, the calculator divides traffic by 1.2; if the site is not seasonal, use 0%.
  4. Revenue per visitor should be net or as close to net as possible. For the first offer, use a conservative value.
  5. The project stage sets the multiplier: 18 — growth, 10 — peak, 12 — stagnation, 6 — decline/dying. The weaker the trend, the lower the valuation ceiling.
  6. Sellers often ask 18–20× monthly income, and listings can reach 25–30×. This calculator is not the seller’s dream price; it is a first-pass negotiation range.
  7. The minimum valuation is the first negotiation anchor. The average valuation is the working range. The maximum valuation is the ceiling; go above it only when the extra assets are strong.