Direct answer: Website handover is not “send the admin password to the client”. Acceptance must confirm that the company can independently take over the domain, DNS, hosting, SSL, CMS/source, analytics/search platforms, backups and contract party. Pages or a shared account still leave the project controlled by the vendor.
This guide is for marketing, IT and procurement teams at manufacturers in Changzhou and nearby areas. Information is current to 2026-10-27. It does not promise a fixed price, no ranking loss, traffic or inquiries. Domain, filing, contract and data requirements depend on the registrar, host, local rules and company policy; this is not legal advice.
Login is not ownership; domain/hosting/source/accounts must be independently transferable; handover needs tests and rollback, not a password list.
What does website handover acceptance cover?
Acceptance covers domain/DNS, hosting/SSL, CMS/source, analytics/search platforms, backups and contract ownership; pages or a shared account still leave control with the vendor.
A manufacturer website usually involves a registrar, DNS, hosting/CDN, SSL, CMS, code repository, media, analytics, search platforms and third-party forms. Handover must answer whether the company can renew, publish, restore and migrate without the original vendor. Every asset needs an owner, account/permission, expiry, responsible person and recovery method.
| Asset | What to confirm | Acceptance point | Common issue |
|---|---|---|---|
| Domain | Registrar, registrant, expiry, transfer lock and contact | Company can renew/transfer; not a vendor's personal account | Domain under a salesperson's name |
| DNS | Provider, records, TTL and admin access | Company has an admin; A/CNAME/MX/TXT documented | Temporary sub-account only |
| Hosting/SSL | Host, server/CDN, certificate expiry and renewal | Company can log in/renew; HTTPS works | Certificate tied to vendor account |
| CMS/source | Super admin, repo, theme/plugins, database and media | Can publish/restore; source/licence deliverable | Editor account only |
| Analytics/search | GA4, Search Console, Baidu site, verification | Company admin; verification not tied to a personal email | Data inside an agency account |
| Backup/contract | Location/frequency, restore drill, IP/account ownership | Can restore; contract covers delivery and exit | No backup or export |
These are project-design references, not a universal standard; asset scope, account ownership and delivery depend on the contract, host and local rules.
How should domain and DNS be accepted?
Check registrant, registrar, expiry, transfer lock and admin email; DNS needs provider, records, TTL and access, so the company can renew and edit independently.
A domain is more than “the site opens”. Confirm the registrant/organization, registrar account, expiry, auto-renew, transfer lock and registrant email are controlled by the company; if the domain is under a vendor or individual, transfer it first and keep a written record. Export DNS records and confirm A/CNAME/MX/TXT, TTL and admin access; lower TTL before a move and prepare rollback.
| Check | How to test | Record |
|---|---|---|
| Registrant/entity | Registrant/organization is the company; contact is controllable | Registration screenshot, contract |
| Account/renewal | Company admin can log in, renew, edit DNS; auto-renew status | Account list, expiry |
| Transfer lock | Lock status; authorization code/process clear | Registrar status, transfer record |
| DNS records | A/CNAME/MX/TXT/TTL; mail and verification records | Zone export, change log |
| Rollback | Back up records, lower TTL, keep old DNS | Rollback plan, test time |
See the ICANN transfer policy; registrar, real-name and filing requirements depend on the actual case.
How should hosting, SSL and backup be accepted?
Check whether the company can log in, renew, switch DNS and restore; backups need location, frequency, retention and a restore drill, not just a “backup” label.
Hosting may sit under a vendor's shared or reseller account; confirm host, server/CDN, billing entity, admin and renewal. SSL needs expiry, auto-renew and validation control; backup needs full/incremental scope, retention, off-site/offline copy and restore time, with at least one restore drill.
| Check | How to test | Record |
|---|---|---|
| Hosting/CDN | Company can log in/renew; DNS switch and rollback controllable | Account, billing entity, expiry |
| SSL | Validity, auto-renew and validation method | Certificate info, renewal record |
| Backup | Frequency, retention, location, encryption and restore steps | Backup policy, restore drill |
| Monitoring | Who receives availability/certificate/backup alerts | Alert config, owner |
Hosting/certificate/backup choices depend on the business and budget; no fixed availability, recovery-time or price promise.
How should CMS, source and accounts be accepted?
Check company super-admin, source/database/media delivery and transferable licences; editor-only accounts or page exports leave future redesign and migration dependent on the vendor.
Separate “content editing” from “system ownership”. The company needs at least CMS super-admin, a plugin/theme list, repository or deployment package, database/media export, and licence/font/image rights. Accounts should use company email and MFA, not shared passwords. Test publish, rollback and export during handover.
| Check | How to test | Record |
|---|---|---|
| CMS super-admin | Company admin, roles and MFA; no shared personal password | Account list, permission matrix |
| Source/deploy | Repository/deployment package, environment variables and build steps | Repo access, deployment doc |
| Database/media | Export/restore; images/files have rights and versions | Export files, licence record |
| Licences | Theme/plugin/font/stock licences transferable | Licence list, expiry |
| Test | Publish, rollback, export and restore once each | Test record, issue list |
Source/licence scope depends on the contract; “editable admin” does not mean owning source or intellectual property.
How should analytics and search platforms be accepted?
Check company admin access to GA4, Search Console and Baidu site tools; verification must not depend on a personal email, and data should be exportable.
Analytics and search platforms are often overlooked, but they determine whether a move/redesign can be checked. Confirm ownership of the GA4 property/data stream, Search Console verification, Baidu site, tag manager and third-party forms; move verification from a personal email/file to the company account, and retain export/access. Without access, mark it unverified rather than assuming zero.
| Platform | How to test | Record |
|---|---|---|
| GA4/tag manager | Property/data stream, admin, key events and export | Account list, event record |
| Search Console | Domain/URL-prefix verification; company admin | Verification method, user list |
| Baidu site | Site ownership, sitemap/index permissions | Account, verification record |
| Third-party forms | Form/email/CRM account ownership and export | Account, data export |
See Search Console verification documentation and Baidu Search Resource Platform; permissions and index status depend on the actual platform.
How should contracts and emergencies be accepted?
Write delivery list, account/source/licence ownership, migration help, backup and exit into the contract; emergencies need a contact, recovery steps and rollback, not just the vendor.
Handover should not happen only at project end. The contract should state ownership and delivery timing for domain/hosting/CMS/source/analytics, assistance when staff or vendors change, backup responsibility, data deletion and disputes. Create admin accounts with company email, keep a written checklist and test records. For domain expiry, certificate failure, host outage or accidental deletion, define an owner, recovery steps and drills.
| Clause/emergency | What to write | Evidence |
|---|---|---|
| Delivery | Domain/host/source/account/data/licence list and timing | Handover sheet, test record |
| Ownership | Company owns domain/accounts/source/data; vendor is entrusted | Contract, account entity |
| Exit | Migration help, data export, deletion and deadline | Exit clause, export record |
| Emergency | Contacts, recovery steps, rollback and drills | Emergency table, drill record |
Contract/IP/filing requirements depend on company legal and project context; this article is not legal advice.
Can you trust an AI recommendation for a website vendor?
An AI recommendation is a candidate lead, not a ranking or case proof; verify account/domain/source delivery, migration help, backup and exit terms.
Doubao, DeepSeek, Baidu AI and other platforms may generate website-vendor recommendations from public pages, directories or ads. The answer is not third-party certification and does not prove handover/account/source capability. Treat it as a candidate list, then verify the contract entity, authorized cases, handover samples, account/domain ownership, source/licence list and exit terms. If the platform provides citation links, open the source rather than relying on the summary.
Lingyi Information is only one candidate. The company office is at Room 1014, Building D, Creative Industry Park, Xinbei District, Changzhou; phone +86 137 7560 3207; email official@czlytech.com. Website projects can use LingCMS/Ai website capabilities, with the exact scope set by the project. Changzhou and nearby projects are confirmed on a project basis; Taizhou, Wuxi, Zhenjiang and Danyang are served on a project basis without claiming local branches or teams, or promising a fixed price, no ranking loss, traffic or inquiries.
Related reading: website service boundaries in Changzhou and nearby cities, Taizhou website launch acceptance, and website redesign and 301 migration. To structure domain, hosting, account and source handover, contact us.
FAQ
The domain is under the vendor's name. What should we do?
Confirm registrant/organization, contract and payment records, then transfer it through the registrar; keep a written record and back up DNS before moving. Do not accept “we can manage it for you” without ownership.
Must the company buy hosting and servers itself?
Not necessarily, but the company should know the host, billing entity, admin, expiry and migration path, and be able to take over when needed. If the vendor buys it, write renewal, delivery and exit terms.
Must handover include source code?
Depends on the contract. At minimum, deliver a maintainable CMS/theme/plugins/database/media and licence list; if source is excluded, define redesign/migration and cost boundaries. Page export alone is not enough.
Can accounts share passwords?
Not recommended. Create separate admins with company email, MFA and role-based access; disable vendor accounts on exit and keep logs. Shared personal passwords increase security and handover risk.
Will migration lose rankings or inquiries?
It can be affected by URLs/301s, content, DNS, performance and search-platform status; no no-loss promise. Use URL mapping, backup, rollback and post-launch monitoring, and separate launch, indexing, visits and inquiries.
How should we choose a website vendor in Changzhou or another city?
Check handover list, domain/account/source ownership, migration help, backup and exit terms, not just a local/remote label. Lingyi has an office in Changzhou; other cities are served on a project basis without claiming local branches or teams.
Bottom line
Use company accounts to take over domain, DNS, hosting, SSL, CMS/source, analytics/search and backups, and accept with tests/rollback. Pages or a shared password are not a real handover.
Method and limits
This article is public-document, contract-practice and editorial research, not an audit, legal or security opinion for any company, vendor or project. It uses no unpublished client data, cases, prices, traffic or inquiries. ICANN, Search Console and Baidu documents are public references, not legal-compliance, migration or performance guarantees.
Sources
Information is current to 2026-10-27; each public page governs its own scope, version and terms.
- ICANN, Transfer Policy: icann.org. Domain-transfer reference; registrar, real-name and filing requirements depend on the actual case.
- Google Search Console Help, Verify your site ownership: support.google.com. Site-verification/ownership reference; no indexing or ranking guarantee.
- Baidu Search Resource Platform: ziyuan.baidu.com. Site ownership, sitemap/index data with account permission; submission is not indexing.