WordPress and Shopify takeovers: what to check first
The checks to run before handing a WordPress site or Shopify store to a new developer, so you keep control of access, data, payments and search traffic.
ReadWebsites and online stores built on WordPress or Shopify are among the most commonly abandoned projects, partly because so many people build them. A theme gets half customised, a migration stalls, or the person who promised a launch date stops replying. Both platforms are widely understood, so plenty of developers specialise in picking up someone else's build.
Shop owners preparing a launch or seasonal sale, service businesses with a half-finished brochure site, and marketing teams moving between themes or platforms. Agencies also post overflow work and client builds they cannot complete themselves.
A staging copy that no longer matches the live site, a page builder such as Elementor layered over a theme that was edited directly, dozens of plugins or apps with overlapping jobs, and checkout or shipping rules never tested with real orders. Admin access is sometimes held by the departed developer instead of the owner.
Secure ownership of hosting, domain and the admin account, take a full backup, then set up a staging copy that mirrors production. After that comes a plugin or app inventory and a search for edits made straight into a parent theme, which updates would wipe out. What to check first in WordPress and Shopify takeovers covers this sequence.
Give the site URL, the theme and page builder, and the hosting company. List missing pages or store features and any launch deadline. Mention integrations such as payment gateways, booking tools or stock feeds, and confirm you can create a staff or user account for whoever takes the job.
Be the first rescue specialist here
Developers and agencies who finish other people's projects can create a free profile and list this as a specialty.
The checks to run before handing a WordPress site or Shopify store to a new developer, so you keep control of access, data, payments and search traffic.
ReadUse team invites and limited roles instead of shared passwords, service by service, and know exactly how to remove access and rotate keys when the work ends.
ReadAgree scope in writing, pay per milestone against clear acceptance criteria, keep code ownership explicit and use payment methods that leave a record. Practical steps for project owners.
ReadAn unfinished WordPress site is usually recoverable. Start by securing access and backups, then map the theme, plugins and WooCommerce setup.
ReadWhen an agency stops work or closes, you need more than the code: accounts, designs, licences and project history. Here is how to collect them and plan the next step.
ReadYou should. Keep the domain registrar, hosting account and platform subscription in your own name and give developers their own logins through user roles or staff accounts. This makes it easy to change who works on the site later.
Yes, if they work on a staging copy first and only push changes to the live site once you have reviewed them. Ask how they plan to stage and back up before they begin.
Usually. The first job is finding out what was changed and where, especially if edits were made directly to a theme that will receive updates. That review shapes the estimate for the remaining work.
Yes. Short jobs such as fixing checkout, finishing a few pages or cleaning up plugins are common here. Describe the fix precisely so developers can reply with a clear price.
No. The platform does not recommend or endorse hosts, themes or developers. A developer you choose can advise on options for your situation.