Blog / WordPress /

A WordPress SEO review after a site ownership change

Picture a new owner who inherits a WordPress site. Nobody is sure what changed last month. Search visibility looks different, a plugin update is pending and the old administrator’s notes stop halfway through. The urge to start fixing things is strong. Don’t. An SEO review starts by restoring a clear picture of the site.

An ownership change touches accounts, hosting, analytics, editorial processes and technical settings. The safest review separates what’s known from what’s inferred, handles access responsibly and checks the fundamentals before any redesign or cleanup. Continuity first, then a prioritised plan.

Establish access and ownership

When I pick up a site, I first confirm who controls the domain registrar, DNS, hosting, WordPress administration, backups, Search Console, analytics, tag management and any CDN or security service. I never assume that the person with a WordPress login owns the related accounts. Use the organisation’s approved access process, create named accounts where appropriate, and remove former access only after responsibilities and continuity have been confirmed.

Check that recovery routes work and that a current backup exists before any high-impact maintenance. Confirm what the backup includes and whether anyone has tested a restore. A backup nobody can restore is not a recovery plan. Avoid sharing passwords in email or asking for credentials in a document.

Write down the current hosting and DNS arrangement, SSL certificate status, renewal responsibilities, and who receives operational alerts. A domain transfer or nameserver change can interrupt email or the website if dependencies are missed. If the setup is unclear, have the responsible technical administrator map it before making changes.

Preserve a baseline

Capture the current state before editing. Note the important URLs, templates, indexability directives, canonical patterns, robots rules, XML sitemaps, redirects, internal navigation, and any known indexing issues. Use a crawl appropriate to the site and preserve its date, settings, and exclusions so later comparisons are meaningful.

Review Search Console ownership and property scope. Check whether the verified property covers the site’s current protocol and host variants, and whether relevant historical data remains accessible. In analytics, verify that the correct property and streams are in use and that key events have definitions the team understands. Do not silently replace tracking during a handover; first document what is present and what cannot be verified.

Look for recent changes in release notes, backups, plugin histories, CMS revisions, deployment records, and Search Console annotations if available. These records may be incomplete. Treat them as clues, not proof of cause. If a decline started around a particular period, compare multiple sources and inspect the affected page groups before assigning blame.

Review WordPress without creating avoidable risk

Inventory the active theme, child theme, plugins, PHP and WordPress versions, and any custom code that affects templates, metadata, redirects, schema, caching, or consent. Check update and support status through legitimate sources. I don’t update every component on production as a first step just to make the dashboard look clean.

Separate SEO functionality that is duplicated across plugins or custom code. Multiple systems may output conflicting canonicals, titles, schema, or redirects. Confirm the rendered HTML and response behavior rather than relying only on settings screens. Where practical, reproduce changes in a staging environment, maintain a rollback path, and schedule work with the person responsible for the site.

Review content types, taxonomies, author pages, archives, and search results. Understand which are intentionally indexable and which create thin or duplicate pages. A new owner may be tempted to apply a blanket noindex or redirect rule to simplify the site. Inspect URL examples and their role first; broad rules can remove useful pages or break navigation.

Identify the work that matters first

Group findings by risk and affected scope. An issue that prevents important pages from being crawled deserves attention before a cosmetic metadata inconsistency. A broken form or certificate problem may be urgent even though it is not a ranking task. Include dependencies, responsible owners, and a verification step for every high-priority action.

Use a small sample to validate each finding before expanding it. Check representative page types and compare the rendered result with the source or CMS setting. A crawl flag can be a useful lead, but context determines whether it is an actual defect. Avoid presenting a tool-generated list as a complete diagnosis.

Finally, create a short handover note: what is confirmed, what remains unknown, what was changed, where the evidence is stored, and who owns the next step. This gives the incoming team a dependable starting point without overstating certainty.

Check the environments too. Staging sites sometimes leak into search, and production settings get mistaken for staging rules. Confirm with the technical owner which environment search engines can reach, and how emergency changes are approved and reversed.

Review user roles as well. Who can install plugins, edit theme files, publish posts or change site-wide SEO settings? Remove access that’s no longer appropriate through the documented process, but keep a named operational contact and a recovery route.

An ownership change is a good moment to improve the documentation, and a bad moment for rushed edits that hide the original state. Which account, setting or dependency would you verify first on a site you’ve just inherited?