Single listing
For one business with a selectable duration.
CHF99per listing
1 month
Excl. VAT.
- Publish 1 listing
- Anonymous or visible contact details
- Save as draft possible
Register free
No payment before publication.
Sell a website project
Sell a website project: prepare a clear listing on company.ch with location, guide price, revenue and handover. Choose open, discreet or anonymous visibility while private seller data stays protected.
Subscription
For regular sellers with several listings.
CHF99per month
3 active listings
Billed yearly. Excl. VAT.
- 3 active listings at the same time
- Anonymous or visible contact details
- Change package before publication
Register free
No payment before publication.
Sell a website project: verified traffic, search visibility, content and code rights, audience quality, revenue, platform dependence and maintenance workload
To sell a website project, make verified traffic, search visibility, content and code rights, audience quality, revenue, platform dependence and maintenance workload verifiable and show what a buyer can continue after completion. The offer should connect commercial performance with the contracts, people, assets and permissions that produce it.
Show the transferable value of a website project
Explain verified traffic, search visibility, content and code rights, audience quality, revenue, platform dependence and maintenance workload, the owner's current duties and the exact transaction perimeter. Historic results, current pipeline and forecasts should be separated so buyers can test what is recurring rather than relying on a headline turnover figure.
Prepare industry-specific records and evidence
Prepare analytics and search data over time, revenue and costs, domain ownership, code and content rights, backlink and penalty history, hosting, dependencies, privacy and maintenance records. Mark ownership, term, notice, transfer restrictions and any consent required; financial data and operating records should cover comparable periods.
Qualify buyers for the operating requirements
Publishers, digital operators and strategic buyers may fit when they can maintain content, technology, compliance and monetisation. Screen for the capabilities that protect continuity as well as available capital, and explain which skills can be transferred during an agreed induction. Do not publish user personal data, credentials, unpublished content, customer or advertiser contracts, security issues and private analytics access. Use anonymised segments, ranges and aggregate performance to support initial evaluation, then open identifying information only for a justified review step.
Transfer work, relationships and access safely
Transfer domain, hosting, repository, CMS, analytics, advertising or affiliate accounts, content files, licences and operating calendar with credentials rotated. Build a handover list for open work, responsible people, access, deadlines and introductions before the seller's availability reduces.
Related seller guidance for a website project
Compare the broader category or return to the main seller page: sell a company and IT & software.
Questions to resolve before selling a website project
How do I substantiate traffic quality, revenue and maintenance workload for my website project?
Show several comparable periods and evidence for verified traffic, search visibility, content and code rights, audience quality, revenue, platform dependence and maintenance workload. Reconcile financial claims with analytics and search data over time, revenue and costs, domain ownership, code and content rights, backlink and penalty history, hosting, dependencies, privacy and maintenance records and distinguish transferable performance from work or relationships that depend on the seller.
What domain, content, code, analytics, licence and monetisation records should be prepared?
A focused file should include analytics and search data over time, revenue and costs, domain ownership, code and content rights, backlink and penalty history, hosting, dependencies, privacy and maintenance records. Explain gaps and exceptions before they affect valuation, warranties or the timetable.
How should I disclose search dependence, platform risk and traffic tied to my personal brand?
Identify which parts of verified traffic, search visibility, content and code rights, audience quality, revenue, platform dependence and maintenance workload depend on the seller, individual employees, major customers, suppliers, premises or permissions. Quantify concentrations and explain which safeguards or transition steps can make the operation less dependent on them.
How can domains, accounts, publishing workflows and audience communication transfer safely?
Transfer domain, hosting, repository, CMS, analytics, advertising or affiliate accounts, content files, licences and operating calendar with credentials rotated. Test the transfer on real open work and record who owns every remaining exception after completion.