Skip to main content
Cookbook Migration

Inspect a Site Before Migrating It with AI

Get a complete read-only inventory of a site's content, theme, plugins, users, and URLs before you move it.

Difficulty Beginner
Time ~10 min
Tools site_info, rest_api, run_wp_cli

Prerequisites

A connected site. The audit is read-only and changes nothing, so no backup is needed to run it.

The prompt
Audit my connected site [site URL] to help me plan a migration. This is read-only, do not change anything. Report back: total posts, pages, and any custom post types with their counts; the active theme, its version, and which template files it ships; every active plugin with its version; all user accounts and their roles; the categories, tags, and any custom taxonomies in use; and the permalink structure with a few example URLs. Then flag anything that will need special handling when I move the site, such as page-builder content, custom fields, or plugins that keep data in their own database tables. Give me the whole thing as one inventory I can save.

Already connected to WPVibe?

Skip the copy-paste. Just ask your AI for the “Inspect a Site Before Migrating It with AI” recipe, or describe the task, and WPVibe runs these steps on your own site.

Migrations go wrong before they even start, because nobody writes down what is actually on the site. The custom post type a developer added two years ago, the plugin that quietly stores data in its own tables, the theme that does more than it looks, the old URLs that still pull traffic. That inventory usually lives in someone’s head or a spreadsheet that never got finished, so the gaps only show up after the move, when something is already broken.

Your AI assistant can take that inventory for you in one read-only pass. It reads the content counts by type, the active theme and the template files it ships, every active plugin and its version, the user accounts and their roles, the categories and tags and any custom taxonomies, and the permalink structure. It changes nothing on the site, so you can run it on a live production install without risk, and it flags the parts that need special handling, like page-builder content or custom fields.

Paste the prompt below, name your site, and read the report before you touch the migration itself. Because the audit only reads, it is safe to run any time. The one thing it does not replace is a real backup: take one with your backup plugin or your host before you start moving anything, not before the audit.

Outcome

A single read-only inventory of content, theme, plugins, users, taxonomies, and URLs, with migration-risk items flagged.