An AI website builder will not import your existing WordPress content on its own. Most builders have no direct connection to a live WordPress site, so the reliable path is to export your content first, as clean Markdown or structured data, and then bring it into the new build. That export step is not a formality: it is where you also capture the metadata, internal links, and URLs you need to preserve rankings. WPBuildAI handles both halves, the export and the import, rebuilding your content in Lovable with metadata and redirects intact, so the move loses nothing.
Import quality matters more than it did, because content that survives the move is what gets quoted: Seer Interactive found pages cited in an AI Overview earning roughly 2.1 percent click-through against 0.9 percent for uncited pages, so a half-finished import quietly costs visibility as well as words.
Pointing a builder at your URL is not an import
Some tools can take a rendered snapshot of a page for layout inspiration, and people mistake that for importing their content. It is not. A snapshot captures how a page looks, not your structured content, your metadata, or your URL list. The 2024 Web Almanac shows how much of a rendered page is layout markup rather than content, so a scrape mostly captures the shell, the menus, the wrappers, the visible text tangled in presentation. For a real move you need an export of the actual content, which gives the new site clean text, headings, and images you control, plus the data a snapshot can never provide: the metadata and the URL structure. “Point it at my site” feels like importing, but it copies the surface and drops the substance.
What “export” actually means here
Export is a specific, well-supported step, not a vague idea. WordPress can produce a content export of your posts, pages, and media, and its content is also reachable in structured form through its data layers, so the words, headings, and relationships come out as data rather than as a picture of a page. The goal is clean, structured content: each page as text and headings, its title and description recorded, its images listed, and its URL noted. That is what an AI builder can rebuild from faithfully. The format matters less than the completeness, Markdown, structured JSON, or a content export all work, as long as they carry the content and the metadata together. This is the same clean-content step behind uploading a blog into an AI.
What a careless import loses
The visible words usually survive a sloppy import. The invisible parts are what vanish: titles, meta descriptions, canonical tags, internal links, image alt text, and the URL structure. Those are precisely the parts that hold rankings, which is why a site can “look like it imported fine” and still lose traffic. Ahrefs found in its search traffic study that a small set of pages carries most organic traffic, so losing the metadata or URLs on those specific pages is a direct, measurable hit. A proper export captures all of it up front, so the import rebuilds a complete page, not just its text. The danger is that the loss is silent: nothing looks broken, because the part you can see is intact.
A worked example: the words survived, the rankings did not
Consider a blog that moved to an AI builder by copying each post’s text into the new editor by hand. Every article’s body made it across, so the team called the import a success. Three weeks later, rankings had slid. The reason: copying the visible text left behind every title tag and meta description, flattened the heading structure, dropped the internal links between posts, and, because the new builder used different URLs, 404’d every old address with no redirect. The content was all there to a reader; to Google the pages were thinner, disconnected, and at new addresses with no history. A structured export would have carried the metadata and the URL list, and a redirect map would have preserved the addresses. The manual copy saved the words and lost everything around them that earned the rankings.
How to import without losing rankings
- Export the content with its metadata and a full URL list, as structured data or clean Markdown.
- Rebuild in the AI builder using that clean content, preserving titles, descriptions, and heading structure.
- Recreate internal links between the rebuilt pages so the structure carries over.
- Map every old URL to a 301 before launch, per Google’s site move guidance and redirects guidance.
- Verify on staging, then cut over and resubmit the sitemap.
This is the same process as migrating a WordPress site to Lovable and moving blog posts without losing rankings. The redirect step is what connects the old rankings to the new pages.
Handling images and media
Images are the part of an import people forget until links break. If the new site references images by their old WordPress URLs, you have not really imported them; you have hotlinked back to a site you are about to retire, and when it goes the images vanish. A proper import re-hosts every image on the new platform and carries its alt text, which matters both for accessibility and for image search. List the media in the export, move the files, and update the references so nothing points at the old domain. This is easy to overlook because the images display fine right after the move, while the old site is still up, and only break later when it is decommissioned, which is exactly when it is hardest to fix.
What transfers cleanly and what needs rework
Setting expectations avoids nasty surprises. Text content, headings, images, and basic metadata transfer cleanly through a structured export and import. What needs deliberate rework is anything WordPress generated dynamically: layouts built in a page builder, shortcode-driven elements, forms, and plugin-powered features have no automatic equivalent and must be rebuilt in the new tool’s own components. Internal links need to be re-pointed to the new structure. And the URL map has to be built regardless. So an import is “content moves as data, functionality gets rebuilt,” and budgeting for the rebuild half, rather than assuming everything imports, is what keeps the project realistic. The content is the portable part; the WordPress-specific machinery around it is not.
When a direct connection does exist
To be fair to the nuance: some tools and plugins do offer a more direct path, pulling content through WordPress’s data layers or via a migration plugin, so “no AI builder imports from WordPress” is too absolute. Where such a connection exists, it can save the manual export. But the same caveats apply: a connection that pulls the body text but not the metadata, internal links, and URLs still leaves you exposed, and you still need the redirect map regardless of how the content arrived. So even with a direct import, check what it actually carries, and treat the metadata-and-redirects step as non-negotiable. The connection is a convenience for the content half; it does not replace the migration half that protects rankings. Whether a given builder keeps content as real, editable data is part of converting your WordPress site to an AI website.
Common mistakes importing into an AI builder
The recurring errors all stem from treating the import as “get the words across.” Copying visible text by hand drops metadata, internal links, and structure. Pointing the builder at a live URL imports a snapshot, not the content. Leaving images referenced on the old domain breaks them when it is retired. Rebuilding at new URLs with no 301s strands every ranking page. And assuming everything imports, then discovering forms and plugin features did not, derails the timeline. Each is avoided by exporting structured content with its metadata and URL list, rebuilding functionality deliberately, re-hosting media, and mapping redirects, the difference between a complete move and a lossy one.
Key points to remember
Most AI website builders will not import from a live WordPress site, and pointing one at your URL captures a snapshot, not your content, metadata, or URLs. Export your content as structured data first so the move carries the words and the invisible parts that hold rankings, titles, descriptions, internal links, alt text, and the URL list, then rebuild, re-host media, and map every old URL to a 301 before launch. Expect text and media to transfer while page-builder layouts, forms, and plugin features need rebuilding. Even a direct-import tool still needs the metadata-and-redirects step. WPBuildAI runs the export, the rebuild in Lovable, and the redirect map together, so your content moves complete and keeps its traffic; send your site URL for a fixed quote.
Not affiliated with WordPress or Lovable.