Understand the thing being transferred.

Digital asset due diligence begins when a buyer needs to check whether a proposed transaction matches the seller’s description. A domain, website, archive, lead system and audience may appear together in a presentation, but they can be owned through different accounts and governed by different contracts. We write an asset schedule that names each component, its current controller, the claimed right to transfer and the evidence available. A domain name cannot carry a newsletter list by implication; a site export does not transfer a third-party license automatically.

The review is organized around a concrete purchase decision. What is the buyer trying to acquire: recurring income, a customer acquisition channel, a relevant knowledge base, a domain identity or the ability to enter a category faster? That purpose determines which assumptions matter most. If a buyer wants a working lead platform, form routing and lawful use of past inquiries are critical. If the buyer mainly wants the domain and original research, the operator’s affiliate income may be secondary. We set scope and materiality before opening hundreds of files.

This service investigates digital, editorial and operational evidence within agreed access. It is different from a valuation exercise, which tests possible value conclusions, and from acquisition support, which compares transaction paths. Due diligence asks whether the underlying claims, assets and dependencies withstand inspection. Lawyers, accountants, tax advisers and specialist security testers address their respective legal, financial and technical judgments. Our report preserves facts and open questions they can use without pretending to replace their work.

A lead site with a compelling dashboard.

Suppose a buyer considers a regional home-services platform. The seller presents an established domain, hundreds of location pages, a form that routes requests to partners and reported monthly lead income. The homepage looks active; a dashboard shows many submissions. The buyer intends to operate the same system after purchase. At first glance the transaction appears to bundle traffic, content, a partner network and an automated route from inquiry to payment. Each element needs its own source and transfer check.

We request the registered domain details, hosting and code inventory, analytics property, form submission records, invoicing or payment evidence, partner arrangements, content provenance and a list of integrations. We compare the period of reported inquiries with payment and delivery records. A submitted form is not a sold lead; a paid invoice may relate to a different month or partner. If a test inquiry currently reaches the seller’s private inbox, that route must change and be verified under buyer control. We do not assume that partners who trust the seller will continue on identical terms with a new owner.

The review finds that several city pages share the same generic text, the main analytics property changed during the reported growth period and two important partner agreements are verbal. None of these facts automatically makes the asset worthless. They change what is known about traffic quality, content maintenance and recurring revenue. The buyer can request records, negotiate a transition, exclude unverifiable components or stop. We make that decision traceable by linking each finding to a source, its impact and the specific question that would resolve it.

Check reported performance against the same period.

A serious review aligns sources before comparing them. Analytics sessions, search clicks, form submissions, accepted leads, invoices and bank receipts are different stages of a funnel. Their dates can differ because a lead submitted in June might be sold or paid in July. We document those definitions and avoid declaring a contradiction simply because two systems count different events. We do flag unexplained gaps, duplicated records, changes in tracking and missing data that prevent a claim from being tested.

Access matters. A seller screenshot can suggest a question, but original exports or read-only access from the source system are preferable where appropriate and permitted. We note the property or account being inspected, coverage dates, filters and any known migration. A spike associated with an advertising campaign should not be presented as steady organic demand. If privacy limits access to person-level records, aggregate evidence and documented process may still support parts of the story, but the limit belongs in the report.

The same discipline applies to costs and obligations. Hosting, software, paid traffic, contractor hours, payment fees, refunds and the seller’s own operational work affect how an asset performs after transfer. A verbal commitment from one partner may not survive a sale. We identify what can be checked through authorized business records and what needs qualified accounting or legal examination. The objective is not to calculate a seductive single number; it is to establish which performance claims can be relied upon and which remain conditional.

An archive can be useful and still carry obligations.

Content rights must be examined separately from content quality. Who wrote the articles? Are photographs licensed for transfer or only for the seller’s account? Does a data feed permit use by a new owner? Are client stories approved for continued publication? We inventory the material that matters to the purchase thesis and flag rights requiring documentation or replacement. Public availability is not proof of ownership. If the seller cannot show permission, that component cannot be treated as fully transferable without further review.

The topical structure affects both utility and maintenance cost. We examine whether pages serve distinct user questions, whether important claims have dated sources, whether internal links lead to useful next steps and whether geographic or category templates repeat claims that cannot be supported locally. An archive with broad keyword coverage may still require substantial correction. Conversely, a smaller set of well-maintained research pages can hold meaningful value for a buyer with the right operating team. Neither page count nor an authority score substitutes for inspecting actual material.

We record what the buyer can keep, what needs expert review and what should not be assumed fit for reuse. This assessment is tied to the intended operating model: a platform continuing in the same category faces different work from a buyer redirecting the audience to a new service. We avoid promising that existing search rankings, links or user behavior will survive a change of owner or architecture. A sound topical map helps estimate the work after close; it is not proof of future visibility.

Try the critical journeys before ownership changes.

A technical inventory lists registrar and DNS, hosting, CMS and source code, user roles, backups, analytics, email routing, payment tools, APIs and third-party integrations. For each, we identify who controls the account and what must happen for the buyer to operate it. An admin password is not enough when billing, domain registration or license entitlement remains in a seller-controlled account. We note renewal dates, dependencies and the cost or disruption of replacing a component.

Testing is scoped and authorized. We can follow selected public routes and buyer-permitted workflows: submit a test inquiry, inspect where it arrives, check a key purchase or verification path and confirm that a backup can be accessed. We log the environment, date and result. A working form during inspection may still fail after DNS or email changes, so the transfer checklist includes a retest. Formal security testing requires separate permission, methods and qualified specialists; a successful workflow test does not certify that the website is secure.

The exit plan matters as much as the current setup. Which accounts must be created for the buyer? Can data be exported in a useful format? What breaks if the seller revokes an API key? Are plugins, photos or proprietary integrations bound to the seller’s subscription? We assign each dependency a transfer action or an explicit exclusion. A buyer should understand both what works today and what must work without the seller tomorrow.

Turn discoveries into deal questions.

The final issue register distinguishes confirmed facts, seller statements, unavailable evidence and contradictory records. Each material finding names the affected asset or claim, the source, why it matters, the request that could resolve it and the person responsible for acting. Missing information is not automatically evidence of misconduct; sometimes it can be produced after a request. A documented contradiction is different and must be investigated. We state the distinction plainly so that a decision meeting does not turn uncertainty into either certainty or accusation.

The buyer can act on findings in several ways: request more evidence, change the assets included, revise the integration plan, ask advisers to address a contractual or compliance point, negotiate terms or leave the deal. We do not silently decide that any one of these follows from a colored risk label. A materiality judgment depends on the buyer’s purpose. An old photo license may be inexpensive to replace on a domain-focused deal; a nontransferable primary data feed may undermine a business that depends on its comparison tool.

The handover usually includes an asset schedule, evidence register, selected performance reconciliation, content and route inventory, critical dependencies and prioritized open questions. It identifies the sample reviewed and what remained outside scope. A report that checks a handful of pages cannot claim the entire archive has clean rights or accurate sources. That limitation makes the work more useful to transaction professionals and the future operating team.

The lead platform under a buyer’s control.

Return to the home-services platform. Before the seller grants access, the buyer agrees what must be true to operate the acquisition: control the domain, receive inquiries, contact willing partners, maintain the published service information and reconcile reported lead sales. The first data request asks for the same six-month period across analytics, form logs, invoices and payment records. The form log includes tests and spam, so raw submission volume is not a revenue figure. We label those entries and explain any remaining mismatch.

Next we inspect account control. The domain is registered to the seller’s company, which can transfer it, but the form plugin and email delivery service are billed through a personal account. The buyer requests a migration path and a test sending messages to a buyer-controlled address. An automation using a seller-owned API key is documented as a dependency, not presented as a permanent buyer asset. A staging or agreed test process shows whether a lead can travel through the route without exposing real customer information unnecessarily.

The editorial sample includes the highest-traffic city pages, pages receiving inquiries and a selection of low-traffic templates. Several pages describe coverage areas that no partner currently serves. This is not just a search issue: a visitor could submit a request the network cannot fulfill. We identify the relevant pages and request current partner coverage records. The seller can correct the statements before close, or the buyer can include a clearly estimated remediation queue in its operating plan. We do not presume the sample describes every page.

Payment reconciliation shows that one large partner accounted for a substantial portion of reported income during the review period. The buyer asks whether the arrangement is documented and whether the partner intends to continue. The answer cannot be inferred from a positive relationship story. If the partner has no transfer obligation, the buyer models the scenario without that income and discusses transition terms with advisers. This is an acquisition-relevant uncertainty, not a judgment about the seller’s motives.

The buyer now has three choices. Proceed with the full platform after specified evidence and transfer tests; purchase only the domain, code and selected original pages while rebuilding the partner network; or pause. The report lists what is included in each route and which open questions remain. If the full purchase proceeds, the domain and key accounts move to buyer control, form and email delivery are retested and the partner and content queues are assigned. Acceptance is recorded against tasks, not against the seller’s presentation.

After closing, an unexpected fall in inquiries could be caused by a routing error, changed demand, tracking changes or lost partner coverage. The baseline established during due diligence helps the operator investigate without immediately blaming one factor. The buyer can compare the same journey, source and period, then update the issue register. Careful pre-purchase work therefore supports both negotiation and the first months of responsible operation.

One more issue deserves its own decision: personal data. The fact that a seller has stored past inquiries does not automatically tell a buyer whether they may receive, retain or contact those people after transfer. We inventory the data categories and how they are used, identify where privacy notices and agreements may matter, and ask the parties’ qualified privacy advisers to determine the lawful transfer and permitted future use. The buyer may decide to acquire the domain and system without historical inquiry records. In that case, the asset schedule and any analysis of audience value must reflect the narrower deal.

The issue log is written for action rather than drama. A row marked “not provided” names the record requested and the deadline relevant to the transaction. A row marked “contradicted” identifies the two sources and the difference between them. A tested route records what was done and under whose access. If the seller fixes a form after the first test, we preserve both observations and retest the repaired path. This prevents a late change from silently erasing an earlier concern or leaving a known problem unexamined.

Finally, we distinguish a stop condition from ordinary integration work. A missing right to transfer the domain threatens the intended purchase itself. A dated article that needs a new citation may be a manageable editorial task. The buyer defines materiality in light of its plan and advisers’ input. The report supplies the evidence and consequences so those choices can be made deliberately, before an irreversible handover.