Website Acquisition Screening: Verify Traffic, Revenue, and Workload

A website listing can present three appealing figures: visitors, revenue, and hours of work. Each figure needs its own evidence, and the acquisition case depends on how they fit together. Traffic matters differently when it requires ongoing advertising. Revenue means something different before refunds and fulfillment. A short maintenance estimate may omit work performed by contractors or by the seller's other businesses.

Start with a defined operating model and a record of the assets included. The website screening framework covers the wider review. Here, the objective is to establish what the audience and financial records support, then identify the work and dependencies that a new operator would inherit.

Define the website and the reporting perimeter

List the domains, subdomains, content, code, accounts, contracts, and other items included in the proposed transaction. Match that list to the reporting systems. A report covering several sites cannot automatically establish the performance of the single site being sold. Ask for the method used to separate shared revenue, expenses, and staff time.

Choose a review period that captures the operating pattern you need to understand. Request monthly records across that period and retain the underlying exports where available. Record missing months and changes in systems. If the site has a short history, evaluate that shorter history explicitly rather than implying that it represents a full seasonal cycle.

Make traffic reports comparable before interpreting them

Google's Traffic acquisition report documentation explains that the GA4 report covers where new and returning users come from. Its session-scoped traffic dimensions describe sessions, including session source and medium. This provides a practical reason to record the exact report and dimension: a user acquisition view and a traffic acquisition view are not interchangeable evidence.

For every export, preserve the property identifier, date range, reporting time zone, filters, dimensions, and metric names. Confirm that the data covers the website in scope. Ask when tracking was installed or materially changed. If two periods use different measurement arrangements, document the discontinuity before drawing a growth or decline conclusion.

Prefer authorized access to inspect the underlying reports when available, supported by dated exports. If access is limited to screenshots, state that limitation and ask for enough surrounding context to identify the report. A screenshot can still be useful; the important question is which claim its visible scope permits you to assess.

Examine concentration by channel and page

Break the audience record into meaningful groups, such as acquisition channel, landing page, geography, and device. Compare each group's contribution across the review period. The purpose is to understand concentration and changes, not to label one channel universally better than another. A concentrated audience may fit the business, but the acquisition case should explain that reliance.

Connect the largest audience sources to the work or spending that supports them. For paid traffic, ask which campaigns and costs are included. For email, identify the list and sending arrangements in scope. For search traffic, examine the pages and topics supporting the case. The domain SEO screening guide develops the historical search review.

Investigate changes with an event record

For each material jump or drop, note the date and request an explanation tied to records. Possible questions include whether a campaign began, a page moved, tracking changed, or a temporary promotion ran. Keep the observed change separate from the proposed explanation. Agreement in timing is a reason to investigate a connection, not proof of the cause.

Check whether the activity appears in related records, such as orders or server reports, using matched periods and definitions. Differences should prompt reconciliation. They should not be silently averaged into a more convenient number. Document the explanation and identify which part remains uncertain after the comparison.

Reconcile revenue to the business being acquired

Start with the seller's claimed revenue and identify its components. These may include advertising, affiliate payments, subscriptions, product sales, or services. For each component, request the relevant platform statements and supporting transaction records. Match the receiving entity and account to the proposed asset perimeter, and isolate revenue that belongs to another business.

Do not expect recorded sales and received cash to match without examining timing. Construct a bridge showing the starting amount, deductions, retained amounts where applicable, and settlement dates. Mark unresolved differences. The result should make the seller's reported figure reproducible within the available evidence, without treating a spreadsheet label as its own proof.

Rebuild operating costs from the work required

List the recurring activities needed to deliver the current product: content production, editing, technical maintenance, hosting, customer support, advertising, fulfillment, administration, and any other material task. Match expenses to those activities. Where a cost is shared with the seller's other sites, request the allocation method and consider the standalone cost for a new operator.

Give owner labor a visible place in the model. Record time separately from cash expenses so you can compare operating choices without double counting. If the buyer would replace the seller's work with a contractor, use an identified planning estimate and explain what it covers. An omitted expense should remain visible until it is estimated or shown to be unnecessary.

Separate recurring maintenance from deferred work and transition tasks. A backlog of updates, documentation gaps, or a required migration belongs in the acquisition review even if it does not appear in the last month's expenses. Ask what would happen if this work were postponed and whether postponement changes the intended business model.

Verify workload through a practical walkthrough

Ask the seller to describe a normal operating week and an unusually demanding one. Then walk through representative tasks using authorized access or a demonstration. Identify the inputs, decisions, tools, and expected output. Compare the walkthrough with invoices, publishing records, support queues, or other relevant activity records.

Record who currently performs each task and whether that person's involvement is included after transfer. A process that depends on personal expertise needs a specific handover plan. Ask which exceptions consume the most time, how they are recognized, and where the instructions are kept. A checklist of routine tasks alone may leave the difficult work unexplained.

Map dependencies and transition conditions

Build an account and contract inventory. For every important service, determine whether the proposed transaction allows transfer, requires approval, or requires a new arrangement. Request the applicable terms and confirmation where needed. Do not infer that an account will move simply because its dashboard appears in the sale materials.

Set acceptance checks for the transition: access works, included content is available, essential workflows can run, and responsibilities are assigned. Identify a fallback for any dependency that must be replaced. Price that replacement into a scenario, and mark the case as conditional if the acquisition cannot operate as intended without it.

Separate the existing operation from proposed improvements

A seller may describe opportunities to add products, raise prices, or publish more content. Put these in a separate development scenario with their own costs, dependencies, and evidence requirements. They are ideas to evaluate, not additions to verified historical earnings. The acquisition case should show whether it depends on those changes succeeding.

Apply the same discipline to your own plans. If you expect to reduce workload through a different process, identify the implementation work and any tasks that still require judgment. Compare the existing operation, the transition period, and the proposed future operation separately so that an attractive future scenario does not erase the cost of reaching it.

Conclusion: connect the evidence before discussing value

Prepare a decision note with supported audience patterns, reconciled revenue, recurring costs, owner workload, and transition conditions. Apply the evidence-first method to distinguish observations from estimates. Then examine scenarios such as losing a major traffic source, replacing a shared contractor, or taking longer to complete the handover.

The review is complete when you can explain how the website attracts people, how that activity connects to recorded earnings, and what a new operator must do to sustain the operation. Those answers do not forecast future income. They establish a clearer basis for deciding whether further diligence or negotiation is justified.