A live website is not proof that your business controls it. Many owners discover the gap only when they want to change agencies, the original developer stops answering calls, or a renewal reminder lands in someone else’s inbox. At that point the domain may sit in a freelancer’s personal registrar account, the hosting may run on an agency reseller server, the only WordPress Administrator may be the developer, and Google Search Console may have one verified owner who left two years ago.
This guide is a practical handover workflow for Indian business owners and managers who are:
- Accepting a newly built website from a developer or agency.
- Switching from one agency or freelancer to another.
- Recovering control after a developer has left.
- Tidying up access before an employee who managed the site moves on.
It focuses on what you can check yourself, in what order, and what “control” actually means for each system. It is not legal advice, and it does not assume any particular agency’s process. Product menus change, so follow the labels you see in each dashboard.
What “control” means, in one sentence per system
Before collecting passwords, agree on the outcome. Shared passwords are not a handover. Control means your business holds the top-level role in an account it owns, and outside helpers hold named, removable access.
| System | Your business should hold | Outside helpers should hold |
|---|---|---|
| Domain registration | Registrant record and the registrar account | Optional delegated access, if the registrar supports it |
| DNS | Admin access wherever DNS is actually hosted | Named user access, or none |
| Hosting / cloud | The account, billing and top-level admin | Limited user or SFTP/SSH credentials you can revoke |
| WordPress | At least one Administrator account owned by the business | Lower roles where possible, or a separate Administrator you can remove |
| Google Search Console | At least one verified owner from the business | Full or restricted user, or delegated owner if genuinely needed |
| Google Analytics | Administrator role at account level | Editor or viewer roles at the level they need |
| Google Business Profile | Primary owner | Manager |
| Business email | Super-admin of the email service | None, unless they support it |
The rest of this guide turns that table into checks.
Order matters: secure the foundations first
Work from the systems that can lock you out of everything else toward the systems that depend on them.
- Domain registrar account and registrant details. Whoever controls the domain can redirect the website and email.
- DNS. DNS decides where the site, email and verification records point.
- Business email. Password resets for most other accounts go to email.
- Hosting and backups. Without hosting access you cannot restore the site.
- WordPress Administrator access.
- Search Console, Analytics, Tag Manager and Business Profile.
- Payment, messaging and other integrations.
- Documents, licences and the final access clean-up.
If you only have one afternoon, finish steps 1 to 4. They are the hardest to recover later.
Step 1: Domain name — check the registrant, not a screenshot
Log in to the registrar yourself, or have the developer share their screen while you read the record. Check:
- Registrant name and organisation. Is it your business, or the developer’s name or company?
- Registrant and admin email. Is it a mailbox your business controls permanently, not a staff member’s personal Gmail?
- Registrar account owner. Even if the registrant is correct, the domain may sit inside the developer’s registrar account.
- Expiry date and auto-renew. Who pays, and to which card?
- Transfer lock status and where to get the transfer code. Most registrars show a lock setting and a way to request the authorisation code (often called an auth code or EPP code).
Why the registrant matters
For generic top-level domains such as .com, ICANN’s Transfer Policy (version updated 21 February 2024) says the Registered Name Holder is the only party with authority to approve or deny a transfer to a new registrar. In plain terms, the name in the registrant record carries real weight. A domain registered in a freelancer’s name is legally and practically harder to recover than one registered to your company.
The same policy also says that a registrar must not refuse to release the authorisation code or remove a transfer lock to the Registered Name Holder solely because of a payment dispute between the registrant and the registrar.
Timing traps to plan around
ICANN’s current Transfer Policy lets registrars deny an inter-registrar transfer within 60 days of a domain’s creation or a previous transfer, and requires a 60-day inter-registrar transfer lock after a Change of Registrant unless the registrant opted out beforehand, where the registrar offers that option. The policy also advises that if your final goal is to move to another registrar, request the inter-registrar transfer before the Change of Registrant to avoid triggering that lock. ICANN has been reviewing these rules, so check the current policy page and your registrar’s terms before you plan dates.
Two practical points follow:
- If you need both a new registrant and a new registrar, ask your registrar which order avoids an unwanted lock.
- Country-code domains such as .in are run under their own registry rules, which can differ from ICANN’s gTLD policy. Ask your registrar how .in transfers and registrant changes work today rather than assuming the .com rules apply.
Domain worksheet
| Field | Current value | Target value | Done |
|---|---|---|---|
| Registrant name / organisation | Your legal business name | ||
| Registrant email | A business-controlled mailbox | ||
| Registrar account owner | Business account | ||
| Expiry date | Auto-renew on, business card | ||
| Transfer lock | On, except while transferring | ||
| 2-step verification on registrar account | On, tied to business-controlled device or app |
For a deeper explanation of registrars, records and domain security, see the site’s domain and DNS management guide.
Step 2: DNS — find where it really lives
DNS is not always hosted at the registrar. Nameservers might point to a hosting provider, a CDN or a separate DNS service. Check the nameservers in the registrar panel, then log in wherever those nameservers point.
Before anyone changes anything:
- Export or copy every record: A, AAAA, CNAME, MX, TXT and any others.
- Note which TXT records are verification tokens (for Google, Microsoft or other services) and which are email authentication records such as SPF, DKIM and DMARC.
- Identify records that only the previous developer understands, and ask what each one is for.
Do not delete unknown TXT records during handover. A record that looks old may still be verifying a service or protecting email delivery. Remove records only after you know what depends on them.
Step 3: Business email — the reset channel
If your business email runs on a hosted workspace service, confirm that someone at the business holds the top administrator role, and that recovery phone numbers and backup emails belong to the business. If the developer set up email forwarding or a contact-form mailbox, document where enquiries land and test that a form submission reaches a business inbox.
Step 4: Hosting, files and backups
Account ownership
The strongest arrangement is a hosting or cloud account opened by your business, billed to your business, with the developer added as a user. If the site runs on the agency’s reseller or shared server, you are relying on that agency’s continued cooperation. That can be acceptable, but get the terms in writing:
- How long they will keep hosting the site.
- What it costs and how renewals are invoiced.
- How quickly they will hand over a full backup on request.
Backups you can actually restore
Ask for, and store outside the server:
- A full file backup (WordPress core, themes, plugins and uploads).
- A database export.
- Any custom code that is not part of the live files, ideally in a repository your organisation owns.
A backup you have never restored is a hope, not a plan. If you can, restore once to a staging copy. The site’s staging site SEO pre-launch checklist explains how to keep a staging copy out of search results while you test.
Hosting worksheet
| Check | Answer |
|---|---|
| Hosting account opened by | |
| Billing card / invoice name | |
| Top-level admin login held by business? | Yes / No |
| Developer access type (panel user, SFTP, SSH) | |
| Latest full backup date and storage location | |
| Restore tested? | Yes / No / Date |
| SSL certificate type and renewal method |
Step 5: WordPress — Administrator, not Editor
WordPress assigns permissions through roles. According to WordPress’s documentation on Roles and Capabilities, an Administrator has access to all administration features within a single site, while an Editor can publish and manage posts, including other users’ posts. On a single-site installation, only Administrators can install, update and delete plugins and themes, and create, edit and delete users. On Multisite networks, several of those powers move to the Super Admin.
That distinction matters during a handover. An Editor login lets you write content, but it does not let you remove the developer, install a security plugin or change site settings. Ask for:
- A named Administrator account for a person at your business, using a business email address.
- The developer’s account either reduced to the role they need or kept as a separate, named Administrator you can remove later.
- No shared “admin” login that several people use.
Also collect:
- Licence keys and account logins for paid themes and plugins. If licences sit on the agency’s account, updates may stop when the agency stops renewing.
- A list of installed plugins, with a note on which ones matter for forms, payments, SEO and caching.
- The location of any custom theme or plugin code.
WordPress user audit worksheet
| Username | Role | Person / company | Keep, change or remove | |
|---|---|---|---|---|
After the handover, check Users for accounts nobody recognises. An unknown Administrator is a security question, not a housekeeping one.
Step 6: Google Search Console — verified owners and leftover tokens
Search Console has several permission levels. Google’s help on managing owners, users and permissions describes them:
- Owner: full control. Owners can add and remove users, change settings, view all data and use all tools. A property must have at least one verified owner.
- Verified owner: verified ownership with a token, such as an HTML file, HTML tag or DNS record.
- Delegated owner: given owner status by a verified owner without a token.
- Full user and Restricted user: view rights with fewer actions.
Two details catch many handovers:
- Removing an owner does not remove their token. Google says that when you remove an owner, their verification tokens are not deleted or revoked. As long as the token remains, the removed person can re-verify. Search Console shows these under Unused ownership tokens, and the matching file, tag or DNS record has to be removed from the site or DNS.
- Be careful which token you delete. Google warns that the same verification token can be used for other services, so removing it can affect them. Remove only the token tied to the person you are removing, and only after your own verification is in place.
Google also says that if all verified owners are removed, the remaining users and delegated owners lose access after a grace period. So the safe order is: verify your business account first, confirm it shows as a verified owner, then remove the departing owner and their tokens.
If you are moving the site to a new domain as part of the change, that is a separate project. The site’s Change of Address guide covers that move.
Search Console worksheet
| Property | Your business account status | Other owners | Unused tokens found | Action |
|---|---|---|---|---|
| Verified owner / delegated / user |
Step 7: Google Analytics, Tag Manager and Business Profile
Google Analytics
Google’s help on adding, editing and deleting Analytics users explains that users can be added at account or property level, and that the level decides their initial access. To add or change users you need the Administrator role at that level. To delete users you need the Administrator role at account level. Google also notes that the last remaining Administrator cannot delete themselves.
For a handover, aim for a business-owned Google account with the Administrator role at the account level. Give agencies only the role and level they need.
Google Tag Manager
If the site loads tracking through Google Tag Manager, check who administers the container. Google’s Search Console help notes that a Tag Manager account can be used to verify Search Console ownership. A departing person with publish or admin rights in the container may still be able to re-verify Search Console unless those rights are removed or the container is replaced.
Google Business Profile
For local businesses, the Business Profile is often worth more than the website analytics. Make sure the primary owner is a business account, with agencies added as managers. If someone else controls the profile and will not hand it over, the site’s duplicate listings and ownership guide explains Google’s ownership-request path. Do not create a new profile to get around the problem.
Step 8: Payments, messaging and other integrations
Indian business websites often connect to services that hold business identity, money or customer data:
- Payment gateways. Confirm which merchant account issued the live keys on your site, and that settlements go to your business bank account. A test account the developer opened and never switched is a serious risk.
- SMS and WhatsApp messaging. If the site sends OTPs, order updates or WhatsApp messages, check whose business entity and account the sender registrations, templates and phone numbers sit under. Moving them later can mean re-registration or migration work, so find out early.
- CRM, booking, maps and email-delivery services. List each API key and the account it belongs to. Where possible, regenerate keys inside business-owned accounts and update the site.
The aim is not to remove every outside account on day one. It is to know which accounts the site depends on and who can act on each.
Step 9: Documents and licences
Collect, in a business-controlled folder:
- Invoices for domain, hosting, SSL, themes and plugins, preferably in the business name.
- The development contract and any clause about who owns the code, design and content. Whether commissioned custom work belongs to you depends on the contract and applicable law. If ownership matters to you, ask a lawyer to review the wording before the final milestone.
- Licence records for fonts, images and third-party components.
- A one-page operating note covering how the site is updated and deployed, where backups are, and who to call if something breaks.
Step 10: The access clean-up
Finish only after your business accounts have been tested.
- Change shared passwords, starting with registrar, email and hosting.
- Turn on 2-step verification on accounts that support it, tied to business-controlled devices or apps.
- Remove or downgrade outside users in WordPress, Search Console, Analytics, Tag Manager and Business Profile.
- Remove the departing person’s Search Console verification tokens after confirming they are not used elsewhere.
- Record the date, the person who made each change and what remains.
Run the handover as a session, not a spreadsheet
A list of passwords sent by email is not a handover. Book a two-hour call with the developer and log in to each system yourself while they are present.
Handover session agenda (hypothetical)
| Time block | Systems | Outcome |
|---|---|---|
| First | Registrar, DNS, email | Business can log in; registrant and renewal confirmed; DNS export saved |
| Second | Hosting, backups, WordPress | Business Administrator works; fresh backup downloaded; plugin and licence list received |
| Third | Search Console, Analytics, Tag Manager, Business Profile | Business owner or Administrator roles confirmed |
| Fourth | Payments, messaging, integrations | Live keys and sender accounts confirmed under business entity |
| Last | Documents, clean-up plan | Folder complete; removal dates agreed |
Then prove control with three small tests:
- Edit test: a business user makes a harmless, reversible content change in WordPress, checks it on the live site, then reverts it.
- Enquiry test: submit the contact form and confirm the message reaches a business inbox.
- Access test: on a non-critical system, confirm a business administrator can add and remove a named user.
Hypothetical scenarios
Scenario A: The freelancer’s personal registrar account
A Kolkata coaching institute finds its .in domain inside a freelancer’s personal registrar account, registered in the freelancer’s name. The site works and the freelancer is friendly. The institute’s best move is to ask the registrar how a registrant change and account move work for .in, schedule the change while relations are good, and confirm renewal billing moves too. Waiting until a dispute arises makes recovery harder.
Scenario B: Editor access only
A clinic’s office manager can publish blog posts but cannot install a backup plugin. She has the Editor role. The clinic asks the developer to create a named Administrator account for the practice owner, then reviews the user list together.
Scenario C: The verified owner who left
A retailer’s Search Console property has one verified owner, a former employee whose HTML tag is still on the homepage. The retailer verifies a business account with a DNS record, confirms it shows as a verified owner, removes the former employee, then removes only that employee’s tag from the theme header.
Scenario D: Agency reseller hosting
A restaurant’s site runs on its agency’s reseller server. Moving hosts is not urgent, so the restaurant gets a written note on hosting term, renewal price and backup delivery time. It also downloads a fresh full backup and database export and stores them in its own cloud folder.
Scenario E: Switching agencies with a redesign planned
A service business is changing agencies and plans a redesign. Handover comes first: domain, DNS, hosting, WordPress and Google accounts move under business control before the new agency touches templates or URLs. Only then does the redesign start, following the site’s website migration SEO checklist.
Build it into the next project
The easiest handover is the one planned before the build starts. When you commission a new site, write the target state into the brief:
- Domain and hosting opened in the business name, on business email, with business billing.
- Business-owned Administrator, Search Console owner, Analytics Administrator and Business Profile primary owner from day one.
- Handover session and the three control tests listed as an acceptance step before the final payment.
The site’s website development process guide covers the wider project stages where these checks fit.
Frequently asked questions
Is it enough if the developer gives me all the passwords?
No. Passwords to the developer’s own accounts still leave the accounts in their control, and reset emails still go to them. Aim for accounts owned by the business, with outside helpers added as removable users.
Should I remove the old developer immediately?
Not before your own access has been tested. Removing access first can break automated tasks, licences or verifications that depend on their accounts. Confirm your access, identify what depends on theirs, then remove or reduce it on a planned date.
Can my developer keep access after handover?
Yes, if it is named, appropriate to the work and removable by you. The concern is ownership, not ongoing help.
What if the developer will not cooperate?
Start with the registrar, using proof of business identity. Use each Google product’s documented ownership or verification path for Search Console, Analytics and Business Profile. For contract or ownership disputes, get legal advice. Avoid creating duplicate accounts or profiles as a shortcut.
Do these domain transfer rules apply to my .in domain?
ICANN’s Transfer Policy governs generic top-level domains such as .com. Country-code domains such as .in follow their registry’s rules. Ask your registrar for the current .in process.
The short version
Control means your business owns the registrar account, registrant record, DNS, email, hosting and backups, holds an Administrator account in WordPress, is a verified owner in Search Console and an Administrator in Analytics, and is primary owner of the Business Profile. Everything else is access you lend to helpers and can take back. Check it in a live session, prove it with small tests, and clean up access only after your own access works.
References
- Transfer Policy — ICANN
- Managing owners, users, and permissions — Search Console Help
- Roles and Capabilities — WordPress Documentation