Changes need a recovery plan
Ask who controls the hosting account, domain, backups and administrator accounts. A freelancer may manage the site while someone else receives renewal notices. Establish ownership first, then review access, update practices and whether a backup can actually restore the site.
Who can publish through an AI tool?
A writing assistant that suggests a draft has different access needs from a plugin that can publish directly. List the tools connected to WordPress, the account each one uses and who can approve a post. Keep editorial review in place for changes to payment instructions, contact forms and client-facing pages.
When a convincing support message arrives
A well-written message can impersonate a hosting provider or an agency. Before granting administrator access, confirm the request through the support channel you already use. Keep a record of who approved the change and when temporary access should end.
How much access does an AI publishing tool need?
Map the tool’s job to the narrowest role that can do it. Drafting an article, publishing a page and installing a plugin are different permissions. Give each integration an identifiable account, record who approved it and test how to revoke access without disrupting the editorial team.
Understand what runs the site
Inventory the site and identify who owns hosting, updates and access.
Plan review and maintenance
Agree a process for updates, backups and verifying that the site still works after changes.
Who owns the update decision?
A site may have separate owners for hosting, plugins and editorial changes. Record who can approve a maintenance window and who can restore the last working version. If the site is already redirecting visitors or showing unexpected pages, begin with hacked WordPress cleanup. For risks beyond the website, read the 2027 guide to cybersecurity threats for small businesses.