In this piece · 15 sections
- An APA buys selected assets, not a vague “website”
- Asset purchase vs. stock purchase: why website deals default to assets
- Build the asset schedule before negotiating boilerplate
- Confirm that every promised asset can transfer
- Define assumed and excluded liabilities
- Tie price to an allocation and payment mechanics
- Make closing conditions observable
- Use representations, covenants, and remedies deliberately
- Address customer data and privacy as a transfer condition
- Put transition support in a separate schedule
- How the APA affects website value
- Caveats
- Frequently asked questions
- Continue through the RSW silos
- Anchor the agreement to a defensible value
An APA buys selected assets, not a vague “website”
A website business may include a domain, hosting account, software, database, content library, brand, customer relationships, email list, contracts, inventory, receivables, analytics history, and operating documentation. It may also include obligations the buyer does not want.
An APA lets the parties identify assets and liabilities selectively. That differs from buying equity in the entity that owns them, where the entity generally continues with its history. The right structure depends on the parties, jurisdiction, contracts, taxes, licenses, and risk allocation.
The IRS explains in Publication 544 that the sale of a business is ordinarily treated as the sale of separate assets. Each asset is classified and its gain or loss considered separately. That tax principle is one reason “$500,000 for the website” is not enough detail for a real agreement.
Many deals begin with a non-binding letter of intent (LOI) that sets a price range, exclusivity period, and timeline before either party pays for due diligence or legal drafting. An LOI is a negotiating framework, not the enforceable contract. The asset purchase agreement and its schedules are what actually bind the parties and can be relied on to force performance.
Asset purchase vs. stock purchase: why website deals default to assets
Buyers of a website business generally choose between two transaction structures. In a stock purchase, the buyer acquires ownership of the legal entity itself — its full history of contracts, tax positions, and both known and unknown liabilities — and the deal is usually documented as a stock purchase agreement rather than an APA.
In an asset purchase, the buyer selects specific assets and specific liabilities from that entity, while everything left off the schedules stays with the seller.
Most website acquisitions use the asset purchase structure. A seller's operating entity is often a thin LLC or sole proprietorship with little independent value once the domain, code, and traffic are separated from it, and buyers generally prefer not to inherit an entity's undisclosed obligations along with its business.
A stock purchase can still make sense when a key contract, platform account, or license is not assignable and only survives inside the existing legal entity — trading one transfer problem for a different diligence burden. For a plain-language definition of the underlying terms, Cornell Law School's Legal Information Institute maintains a glossary entry on asset purchase agreements.
The IRS treats the two structures differently for tax purposes, and the choice affects which party bears successor-liability risk. Tax and legal advisers, not habit, should decide which structure fits a specific business transaction.
Build the asset schedule before negotiating boilerplate
The acquired-assets schedule should list specific assets concretely enough that someone who did not negotiate the deal could complete the transfer. Typical categories include:
- domain names, registrar accounts, DNS zones, and certificates;
- source code, repositories, databases, deployment workflows, and documentation;
- articles, graphics, video, product data, and editorial calendars;
- trademarks, trade names, logos, copyrights, trade secrets, and other owned intangible assets;
- customer lists, customer contracts, subscriber records, vendor records, and other operational records, subject to applicable law;
- assignable licenses, affiliate relationships, supplier contracts, and advertising agreements;
- social accounts, analytics properties, support systems, and business email;
- physical inventory or equipment, if any;
- prepaid expenses, deposits, accounts receivable, or cash if specifically included; and
- goodwill and going-concern value.
List excluded assets just as carefully. A seller may retain cash, tax records, personal devices, unrelated brands, personal email, or other businesses in the same entity. Silence creates disputes.
Flippa’s sample website sale agreement is useful as a first-party marketplace example because its asset definitions include domain names, third-party agreements, brands, trademarks, and business records. It also illustrates closing deliverables, consents, encumbrances, and warranties.
For a longer, more formal example at much greater length, the SEC's EDGAR system hosts a filed asset purchase agreement from a public-company transaction that schedules the same categories in fuller legal detail. Neither is a universal form.
Confirm that every promised asset can transfer
Ownership and transferability are different questions. A seller might own custom code but use a cloud, payment, advertising, or app-store account that cannot be assigned. A theme or font license may cover the seller but not a buyer. An affiliate or supplier agreement may require consent. An undisclosed lien, an unreleased security interest, or a pending dispute can also block a clean transfer of title even when ownership itself is not contested.
For every scheduled asset, record:
1. current legal owner; 2. account holder and administrator; 3. transfer method; 4. required third-party consent; 5. expected transfer date; 6. replacement plan if transfer is prohibited; and 7. evidence the buyer will use to accept it.
Contractor-created code and content deserve special attention. Ask for signed intellectual-property assignments. The U.S. Copyright Office explains that a copyright transfer includes assignments and exclusive licenses, and 17 U.S.C. §204 generally requires a signed writing for a valid transfer of copyright ownership.
For trademarks, the USPTO assignment guidance states that a business-sale trademark assignment must include the associated goodwill. Recording an assignment updates federal ownership records but does not repair a defective underlying transfer.

Define assumed and excluded liabilities
Assets can carry obligations. The agreement should state which liabilities the buyer assumes and which remain with the seller. Examples include customer refunds, chargebacks, gift cards, prepaid subscriptions, accrued contractor bills, taxes, privacy claims, warranties, pending disputes, and obligations under assigned contracts.
A buyer should connect the liability schedule to due diligence, not to the seller's summary of it. Due diligence is what turns these categories from a checklist into evidence: verifying bank deposits against reported revenue, confirming that recurring charges match subscriber counts, and requesting the underlying contracts rather than a description of them.
What due diligence actually finds — not what the seller represents — should drive what lands on the assumed- and excluded-liability schedules.
If the seller received annual subscription payments before closing, the buyer may owe service after closing without receiving the original cash. That economic burden can affect working capital, purchase price, or the allocation between the parties. The schedule should also state whether assets transfer free and clear of liens and whether the seller's accounts receivable are included in the deal or retained.
Representations are not a substitute for disclosure. The seller’s schedules should identify exceptions to statements about ownership, authority, financial records, intellectual property, contracts, compliance, litigation, taxes, employees, and data security. A disclosed problem can be priced and assigned. A hidden problem becomes a post-closing dispute.
Tie price to an allocation and payment mechanics
The purchase and sale of a website business is only as good as the price mechanics behind it. The APA should state the total consideration and its components: cash at closing, escrow holdback, seller note, earnout, retained working capital, assumed liabilities, or other consideration. Define payment terms — timing, conditions, interest, offsets — and what happens if a contingent amount changes.
When goodwill or going-concern value may attach to a group of business assets, the IRS says the buyer and seller generally use Form 8594. The Form 8594 instructions require reporting total consideration and allocation across asset classes, and may require supplemental filings if consideration later changes.
The parties may have different tax preferences, but inconsistent reporting creates risk. Agree on the purchase price allocation in the document or a signed schedule and have tax advisers review it before signing. Do not invent an allocation after closing.
For valuation, the allocation also tells an economic story. Tangible assets, identifiable intellectual property, contracts, customer relationships, and residual goodwill do not have identical lives or risks. The purchase price should still reconcile to the operating earnings and durability the buyer verified.
Make closing conditions observable
“Seller transfers the site” is not an acceptance test. Closing conditions should state what must be delivered and how completion is confirmed.
A website closing checklist may require:
- buyer receipt of registrar control and domain transfer confirmation;
- repository ownership plus a tested production deployment;
- database, storage, backups, encryption keys, and documentation;
- buyer-admin access to hosting, DNS, monitoring, analytics, email, commerce, and support;
- assigned contracts and required consents;
- trademark and copyright assignment documents;
- business and financial records;
- credential rotation and removal of unauthorized access;
- a successful transaction through the customer journey; and
- release instructions for escrow funds.
Separate signing from closing when conditions take time. The agreement may be signed before consents, financing, or account replacements are complete. Between signing and closing, the seller typically covenants to operate the business in the ordinary course and to notify the buyer of any material adverse changes before the deal completes. State when risk, revenue, expenses, and control shift.
Use representations, covenants, and remedies deliberately
Representations describe facts, covenants require actions, and remedies define the consequence of breach. Together they are usually labeled the agreement's representations and warranties, and a single unsupported warranty can carry as much post-closing risk as an entire liability schedule left blank.
For example, the seller may represent that it owns the scheduled code, covenant to deliver the repository and assist with deployment, and agree to a defined remedy if an undisclosed ownership claim appears. The buyer may represent that it has authority and funds, covenant to maintain confidentiality, and agree to close when conditions are satisfied.
Remedy design may include escrow holdbacks, indemnification, liability caps, baskets, survival periods, specific performance, termination rights, or insurance. The correct package depends on deal size and risk. Overly broad language is not automatically better; it can make the agreement hard to negotiate or enforce.
Negotiate these terms and conditions with each side's own legal counsel before signing, and define a dispute resolution process — negotiation, mediation, or arbitration — for disagreements that survive closing.

Address customer data and privacy as a transfer condition
Customer data is not ordinary inventory. Before transferring it, identify what was collected, why, under what notice or consent, where it is stored, which processors receive it, and whether a sale or change of control affects permitted use.
The APA should assign responsibility for notices, consents, security incidents, retention, deletion, and post-closing requests. The buyer should not assume that owning the database means unrestricted use. Privacy obligations vary by jurisdiction and business model, so counsel should review this section.
Put transition support in a separate schedule
Even a well-documented website may need seller help after closing. Define the hours, services, communication channel, response expectations, duration, fees, exclusions, and escalation path. Avoid “reasonable support” without a boundary.
Support might include vendor introductions, deployment walkthroughs, billing explanations, content workflows, incident response, or customer handoffs. It should not quietly become unlimited free labor or ongoing operational dependence. If the business cannot run without the seller after the stated period, that is a valuation risk the buyer should address before signing.
How the APA affects website value
A strong agreement does not create earnings, but it protects the buyer’s ability to receive what those earnings depend on. Complete schedules reduce uncertainty around ownership, transfer, liabilities, and continuity. That can support a tighter value range and a cleaner close.
The inverse is also true. If critical contracts cannot transfer, code ownership is undocumented, analytics sit in personal accounts, or customer obligations are unclear, the buyer should model replacement cost and disruption. Deal documentation exposes value gaps that a headline multiple hides.
Caveats
Asset purchases can trigger tax, employment, privacy, intellectual-property, licensing, bulk-sale, successor-liability, and regulatory issues. The applicable rules differ by jurisdiction and deal structure. Platform sample agreements and the SEC example above are not substitutes for tailored advice. Nothing in this article creates an attorney-client relationship, and no template should be signed without review by the buyer's and seller's own qualified legal counsel.
This article is educational only.

Frequently asked questions
What is the most important part of a website APA?
The asset, excluded-asset, liability, and closing schedules. They determine what actually transfers and what proof constitutes delivery.
Who prepares the asset purchase agreement?
Practice varies, but the buyer's attorney commonly drafts the first version, since the buyer is best positioned to define the specific assets, schedules, and closing conditions it needs. The seller and its counsel then negotiate revisions. Either party may start the draft; what matters is that both sides review the final version with their own qualified counsel before signing.
Do you need a bill of sale in addition to an asset purchase agreement?
Often, yes. The APA is the master agreement; a short bill of sale, assignment, or transfer document may still be required for a specific asset class — tangible equipment, or, in some jurisdictions, domain and IP registrations. Ask counsel which ancillary documents the specific asset schedule requires.
Can I write my own asset purchase agreement?
Templates and marketplace examples, including the ones referenced above, can help you understand the categories involved, but a self-drafted agreement carries real risk on a business asset sale. A missed consent requirement, an unscheduled liability, or a missing disclosure can be expensive to unwind after closing. Have qualified counsel draft or review the final agreement.
Does buying the domain mean I own the website content?
No. Domain ownership, copyright, code rights, trademarks, data, and contracts are separate assets and should be transferred explicitly.
Who files IRS Form 8594?
The IRS states that both buyer and seller may have filing obligations when a qualifying group of business assets is transferred and goodwill or going-concern value may attach. Ask a tax professional about the transaction.
Can a payment or advertising account be sold?
It depends on the provider’s current terms and account structure. If assignment is prohibited, the buyer may need a replacement and a migration plan.
Is the Flippa agreement a legal template for every sale?
No. It is a useful marketplace example showing common categories. Actual terms should reflect the deal and jurisdiction.
Continue through the RSW silos
The complete website-selling guide supplies the transaction sequence. Use the guides to working capital in a website sale, earnouts, owner involvement and transferability, and deferred revenue to identify schedules the agreement may need.
The domain-appraisal tool provides a separate baseline when a domain is one of the transferred assets.
Anchor the agreement to a defensible value
An APA works best when the price and schedules describe the same asset. Run a Real Site Worth valuation before final negotiations, then reconcile the range with the assets, liabilities, transfer gaps, and verified earnings written into the deal.
Keep moving through the Selling websites silo
Transaction-focused pieces covering prep, marketplaces, fees, and sale mechanics.
- DealsWebsite Broker & Marketplace Fees Compared: What Selling Actually Costs

- DealsFlippa vs Empire Flippers: where your website actually sells best

- DealsEmpire Flippers vs Motion Invest: which broker fits your site's size

- Growth & multiplesHow to Increase Website Value Before Sale: The 5-Move Value-Gap Roadmap

- Growth & multiplesDoes an email list add to your website's sale value?

- MethodDeferred revenue in a website or SaaS sale: who owns the unfinished obligation



