What I Check When I Inherit a WordPress Site I Didn't Build
Sometimes the site was built by another developer. Sometimes by an agency. Parts of it may also have been generated or changed with AI. But the handoff problem itself is older than AI. However it was built, you're the one touching it now. You don't know what's actually configured under the hood. Not yet. 1. Record the current state before you change anything Before you fix, add, or "clean up"…
When inheriting a WordPress site you didn't build, it's essential to understand its current state before making any changes. Begin by documenting what you find, noting which plugins are active and inactive, the site's indexing status, and whether debug mode is enabled. This initial record will help you compare against any issues that arise later.
Next, examine all installed plugins, not just those that are active. For each plugin, inquire whether it's still maintained and check its last update date on WordPress.org. A plugin with no updates in over a year should be reviewed carefully, even if it was initially installed for a specific reason. Determine if the plugin is inactive on purpose or if it was simply forgotten. Consider whether it's safe to continue using plugins that others have relied on.
It's crucial to verify the site's current state rather than relying on assumptions. Don't assume indexing is off or debug mode is disabled without checking. Thoroughly investigate whether these settings are intentional or remnants of the original site, as they could impact the site's SEO and functionality.
As you make changes, ensure you have a clear understanding of the site's baseline before proceeding. After completing your work, reevaluate the site against the same criteria used in step 3. This includes reviewing indexing settings, debug mode, the default admin username, and any temporary pages or references you added during the process.
When handing the site back, conduct another thorough check to ensure all modifications have been properly tested and are functioning as intended. This disciplined approach helps maintain the site's integrity and ensures a smooth transition for the next owner or developer.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
