Skip to content
TakeoverWork
Guide for owners

WordPress and Shopify takeovers: what to check first

6 min read

On this page
  1. Checks that apply to both platforms
  2. WordPress: what to check first
  3. Shopify: what to check first
  4. SEO redirects on both platforms
  5. First-day checklist

WordPress sites and Shopify stores often pass through several hands: a freelancer builds the theme, an agency adds features, someone else installs apps along the way. When you bring in a new developer to finish or fix things, the first job is not writing code. It is finding out what you actually have, who controls it, and how to undo a change if it goes wrong. These checks take a few hours and protect your access, your customers' data and your search traffic.

Checks that apply to both platforms

Who owns the domain and DNS?

Your domain is the one thing you cannot easily replace. Log in to the registrar where the domain is registered and confirm the account is in your name or your company's name, with your email address and a working payment method. DNS may be managed somewhere else, such as your host or Cloudflare. Find out where, and export or screenshot the current records before anyone changes them. Pay special attention to the MX records, which route your email; a careless DNS change can stop email without anyone noticing for days.

Is there a backup you can actually restore?

A backup only counts if you know where it is and how to restore it. Make a fresh one before any work begins and store a copy somewhere other than the server or store itself.

Access through separate accounts, not shared logins

Give the developer their own account on every system, with only the permissions they need. Never share your own password, and never paste keys or passwords into chat. Our guide on giving a developer access without sharing passwords covers the details. The Handover Checklist Generator can build a list of every account, role and credential to rotate for your project.

WordPress: what to check first

User roles

In WordPress, go to Users and review every account. Remove people who no longer work on the site, and check which accounts have the Administrator role. Add the new developer as a new user. Administrator access is often needed for theme and plugin work, but give a lower role, such as Editor, if their task is only content. Remove or downgrade their account when the work ends.

You will usually also need to give access to hosting, SFTP or SSH, and the database. Most hosts let you add a separate user or collaborator in the control panel rather than sharing the main account.

Backups and staging

Make a full backup of both the files and the database. Many hosts provide backups and one-click staging; if yours does not, a backup plugin can create both. All development should happen on a staging copy first, never directly on the live site. Make sure the staging copy is password-protected or set to discourage search engines, so it does not appear in search results next to your real site.

Plugin and theme inventory

List every plugin and theme, active or not, with its version and where it came from: the WordPress.org directory, a premium vendor, or custom code. Then look for:

  • Plugins with updates waiting, or not updated by their authors for a long time
  • Plugins that have been closed or removed from the WordPress.org directory
  • Inactive plugins and themes that are still installed; remove what you do not need
  • Several plugins doing the same job, such as two caching or two SEO plugins
  • Premium themes or plugins from unofficial sources ("nulled" copies), which can contain malicious code
  • Edits made directly to a parent theme instead of a child theme, which are lost when the theme updates
  • Custom code in functions.php or a site-specific plugin that nobody has documented

Licences

Premium plugins and themes often need a licence key for updates and support. Find out whose account each licence is in. If it is in a previous developer's or agency's account, it may stop updating when they stop paying. Move licences into your own account where the vendor allows it.

PHP version and hosting

Go to Tools, then Site Health, then Info, and check the PHP and database versions under Server. Old PHP versions no longer receive security fixes, and upgrading can break older plugins, so test an upgrade on staging first. Also confirm who pays for hosting, whose name the account is in, and when it renews.

wp-config.php holds your database password and security keys. Never send it in chat. If you suspect secrets have been shared or committed to a repository, paste the text into the Secret Leak Scanner, which runs locally in your browser, then change the database password and regenerate the security keys.

WooCommerce stores

If the site runs WooCommerce, check payment gateway settings, whether any gateway is still in test or sandbox mode, the webhook URLs registered with your payment provider, and that order emails reach customers.

Shopify: what to check first

Ownership, staff and collaborator accounts

Confirm that you are the store owner, not a staff member on a store someone else owns. Then review Users and permissions in Settings. Remove staff and collaborators who no longer need access. A developer with a Shopify Partner account should send a collaborator request, which you approve with only the permissions they need. You can require a collaborator request code so nobody can request access without it.

Apps

Review every installed app: what it does, what data it can access, and what it costs. Uninstall apps you no longer use. Some older apps add code directly to the theme and leave it behind when uninstalled, which can slow pages or cause errors, so ask the developer to check the theme for leftover snippets.

Theme versions

Before any theme work, duplicate the live theme and download a copy. Find out which theme it is based on and which version. A theme heavily edited in code can be hard to update, and an older vintage theme may not support Online Store 2.0 features such as sections on every page and app blocks. The developer should work on an unpublished copy and publish only when you have approved it.

Checkout customisations

Shopify has replaced the old checkout.liquid approach with checkout extensibility, which uses checkout UI extensions and Shopify Functions. If your store relied on older checkout customisations, some may have stopped working or need rebuilding. Many deeper checkout changes are only available on Shopify Plus, so check what your plan supports before you plan the work.

Payment gateway settings

Review Settings, then Payments. Confirm which providers are active, whether test mode is off on the live store, and that the payout bank account belongs to you. A developer rarely needs permission to change payment settings, so leave it out of their collaborator permissions unless the task requires it.

Data exports

Export products, customers and orders as CSV files, and keep the theme download. This is your fallback if something goes wrong.

SEO redirects on both platforms

Changing a product handle, page slug or permalink structure breaks every link that points to the old URL. Before launch changes, export a list of current URLs and set up permanent (301) redirects from old to new. Shopify has a built-in URL redirects feature and can create a redirect when you change a product handle. On WordPress, use a redirect plugin or server rules, and check existing redirects are kept. Make sure you, not only the developer, have access to Google Search Console.

First-day checklist

  • Domain registrar account is in my name; DNS records exported
  • Fresh backup made and stored off the server or store
  • Developer has their own account with limited permissions
  • Old staff, users and collaborators removed
  • Staging site or unpublished theme copy ready
  • Plugin, theme and app inventory written down
  • Premium licences moved into my own account
  • PHP version checked (WordPress)
  • Payment settings reviewed and test modes off on the live site
  • Redirect plan agreed for any URL changes

For a broader pre-launch list, use the Production Readiness Checklist for WordPress or Shopify. If your site was left half-done, our page on an unfinished WordPress site explains how to describe it, and if the previous developer stopped replying and still holds key access, start with developer disappeared with the code.

Frequently asked questions

Should I give the new developer my WordPress admin login?

No. Create a separate user account for them with the role they need, and remove it or lower its role when the work ends. That way every change is linked to their account and you never share your own password.

How does a developer get access to my Shopify store?

Developers with a Shopify Partner account can send a collaborator request, which you approve and limit to the permissions they need. You can also require a collaborator request code. Staff accounts are another option, but they count towards your plan's staff limit.

Does Shopify back up my store automatically?

Shopify keeps the platform running, but it does not offer a simple one-click restore of your whole store to an earlier point. Export your products, customers and orders, download a copy of your theme, and consider a backup app if your store changes often.

Why does the PHP version matter on a WordPress site?

Old PHP versions stop receiving security fixes, and newer plugins may not run on them. Upgrading can also break old plugins or custom code, so it should be tested on a staging copy first.

What happens to my search rankings if the developer changes URLs?

If old URLs stop working without a redirect, visitors and search engines hit error pages and you can lose traffic. Any URL change should come with a permanent redirect from the old address to the new one.

Stuck with a half-built app?

Post your project free. Developers who finish and rescue projects can send you an interest note, and you decide who to talk to. You agree scope and payment directly with them.

Free tools that help

Related guides

Related problems