A website brings together content, accounts, people, and customer activity. Its review should connect audience records with earnings evidence and the work required to keep the business running. Begin by defining exactly what the proposed transaction includes and matching that scope to the reports provided. Then examine how traffic is acquired, how recorded revenue becomes received cash, and which responsibilities would move to a new operator. The aim is a documented operating picture that supports further diligence and makes transition work visible.
What to examine
Preserve the reporting property, dates, filters, dimensions, and metric definitions before comparing periods. Break the audience into channels and pages, then investigate concentration and changes. Connect the largest sources with the campaigns, publishing work, or other activity required to maintain the operation the seller describes.
Identify every income component and match it to the website being sold. Compare platform statements, adjustments, payment records, and the operating ledger using aligned periods. Build an explanation for timing differences and deductions. Keep discrepancies visible rather than accepting a monthly total without its records.
List tasks, owner judgment, contractor involvement, and accounts. Separate continuing expenses from transition work and a backlog of maintenance. Determine which relationships or services can move with the transaction and which need replacement. The operating case should identify who will perform each activity after handover.
A practical review sequence
List the domains, content, software, accounts, and contracts included in the sale. Match that list with the reports describing performance. Where systems cover several businesses, request the method used to separate this website’s revenue, expenses, audience activity, and staff time.
Collect comparable audience exports and revenue records for the review period. Preserve definitions and note gaps or measurement changes. Reconcile the seller’s figures to their components, then record which conclusions are supported and which require another source or an explanation.
Examine a representative operating week and the exceptions that demand attention. Match the walkthrough with task records, invoices, or activity evidence. Identify undocumented expertise and shared resources. Estimate a new operator’s requirements separately from the seller’s arrangement rather than assuming they will match.
Create acceptance checks for transferred assets and workflows. Model replacement costs and a longer handover where those are uncertainties. Keep proposed improvements separate from historical earnings, and state whether the acquisition case requires those improvements to succeed before the operation fits its purpose.
Primary-source context: Google Analytics Help: GA4 Traffic acquisition report. Use it alongside the asset-specific records relevant to your review.
Questions to resolve
A screenshot can establish what a report displayed within its scope. Record the property, dates, filters, and metrics needed for interpretation. Examine authorized underlying reports and retain exports. If access remains limited, describe the limitation and the claims it prevents you from checking.
Record the tasks and time separately from cash expenses. Then examine how the operator would perform that work. If a contractor estimate is used, state its coverage and assumptions. Avoid omitting owner work because it was not paid through the expense ledger.
The review needs an asset list, an owner for each task, and evidence that essential workflows can operate in the receiving arrangement. Record dependencies requiring approval or replacement. Any condition that remains unresolved should stay attached to the decision rather than disappear into the timetable.
Read the Lab
A website acquisition needs three connected reviews: audience evidence, earnings evidence, and the work required to keep operating. Learn how to reconcile the records, identify dependencies, and make the transition assumptions visible before discussing value.
Read the guide: Website Acquisition Screening: Verify Traffic, Revenue, and WorkloadA domain’s search history needs context before it can support an acquisition case. Review historical uses, inspect backlink samples, separate observations from penalty assumptions, and test whether the planned project works without promised search benefits.
Read the guide: How to Screen a Domain’s SEO History and Backlink RiskRelated screening lenses
Questions worth asking
Explore a new asset class or suggest a topic for the Lab.
