When a platform has no export button, you capture the site from its published pages instead, because anything that is publicly visible can be read and saved. This is the reframe that turns a dead end into a method. The text, images, metadata, and URLs that visitors and search engines already see are, by definition, available, so a crawler can read the live site page by page and return those as files: the content as text or markdown, the images as files, the titles and descriptions as metadata, and a complete list of URLs. This works on closed builders and locked platforms that offer no clean export, because you are not relying on an export feature; you are capturing what the site already serves. The limits are honest ones: you can capture what is public, not private pages, databases, or anything behind a login the crawler cannot reach. But for most sites the public content is the content that matters, the pages that rank and that you want to move. WPBuildAI scans your live site and returns the content, images, and full URL list as files, so you can rebuild elsewhere even when the platform gives you no way out.
Crawling your own site is the reliable fallback, and it is worth doing before you need to: Patchstack found 46 percent of the WordPress vulnerabilities disclosed in 2025 had no patch available at the moment of disclosure, which is a reminder that the time to obtain a clean copy is while the site is still healthy.
The key idea: published means capturable
The whole method rests on one fact. If a page is published, it is being served to anyone who visits, including search engines, which means its content is already leaving the platform every time someone loads it. So you do not need the platform’s permission to get your content out; you need to read what it is already handing to every visitor. A missing export button blocks one path, the convenient file download, but it does not hide the content, because the content is public by definition. This is why a locked platform feels more trapping than it is: the data you want is on display, and reading what is on display is exactly what a crawler does.
What you can capture from the live site
A capture from the published pages returns the pieces you need to rebuild. The visible text becomes content you can save as plain text or markdown. The images, which the pages load, can be downloaded as files. The titles and meta descriptions, which sit in each page’s markup, come across as metadata. And by following the site’s links, a crawler builds a complete list of URLs, which you need both to capture every page and to plan redirects later. Web Almanac 2024 (HTTP Archive) is a reminder of how much a site holds, especially in images, so a systematic capture usually recovers more than you would gather by hand. These four pieces, content, images, metadata, and URLs, are the substance of the site.
Why this is usually enough
It is reasonable to ask whether captured public content is as good as a proper export, and for what matters, it generally is. The pages that rank, that people visit, and that you want to carry to a new platform are public pages, so capturing them gives you the content that carries your value. Rankings attach to content and the URLs it lives on, not to a database format, as the Backlinko analysis shows, so a faithful capture of the public content preserves what search cares about. Traffic concentrates on a minority of pages, as the Ahrefs study shows, so confirming those high value pages were captured completely is the main quality check. For most migrations off a closed platform, the public capture is the migration.
How to capture systematically
Doing this well means being systematic rather than saving pages one at a time. Start by building the list of URLs, so you know every page that exists and can capture each, the approach behind downloading all pages of a website. Then read each page and extract its content, images, and metadata into files organized so you can rebuild from them. Keep the URL list itself, because it becomes your redirect map when the new platform changes addresses, the same need as any site move with URL changes. Capturing the structure, not just individual pages, is what makes the result a rebuildable site rather than a pile of saved files, which is the difference a good structure capture tool provides.
The honest limits of capturing
It is essential to be clear about what this method cannot reach, so you plan around it. A capture reads what is public, so it does not retrieve private pages, member only content, drafts, or anything behind a login that the crawler is not given access to. It does not pull the underlying database, user accounts, or platform settings, because those are not part of the served public page. And it captures the rendered content, so anything that only appears after a visitor interacts may need extra care. None of this undermines the method for public content; it just defines its edge. If you need private or account data, that has to come from the platform directly where possible, while the public site is what the capture covers.
Steps to capture a site with no export
- Build a complete URL list by following the site’s links.
- Read each page and extract its visible content as text or markdown.
- Download the images each page loads, as files.
- Capture titles and descriptions as metadata per page.
- Keep the URL list as the basis for redirects on the new platform.
- Verify high value pages were captured completely before rebuilding.
Worked example: leaving a closed builder
Imagine a business on a closed website builder that offers no usable export, wanting to move to a platform they control. There is no export button, so they capture from the published site. A crawler follows the links to build a list of every URL, then reads each page, saving the text as markdown, downloading the images, and recording each page’s title and description. The team checks that their most visited pages, the service pages and top blog posts, came across complete. They now have the content, images, metadata, and a URL list as files, everything needed to rebuild on the new platform and to 301 the old URLs to the new ones. The closed builder never gave them a way out, but the public site did, the same principle used to recover old content from the Wayback Machine when a site is gone entirely.
Limitation: capture is for public content, not a full backup
To be honest about scope, capturing from published pages is a method for moving and preserving public content, not a substitute for a full platform backup. It gives you the pages, images, metadata, and URLs that make up your visible site, which is what you need to rebuild and to keep ranking, but it does not give you a database, private records, or platform specific configuration. So use it for what it is excellent at, getting your public content off a platform that will not export it, and handle any private or account data separately through the platform itself. Going forward, owning a platform you can export from avoids the situation, which is part of why people leave closed builders in the first place, as covered in migrate off Wix without losing SEO.
Common mistakes
- Assuming a missing export button means the content is unreachable.
- Saving pages one at a time instead of capturing systematically from a URL list.
- Capturing text but forgetting images, which break when the old site closes.
- Skipping metadata, so titles and descriptions are lost in the rebuild.
- Expecting a public capture to include private or database content it cannot reach.
Key points
A website with no export button is not a dead end; you capture it from its published pages, because anything publicly visible can be read and saved. A crawler reads the live site and returns the content as text or markdown, the images as files, the titles and descriptions as metadata, and a complete list of URLs, which is everything you need to rebuild elsewhere and to plan redirects. This works on closed builders precisely because the content is already served to every visitor. Be honest about the edge: it captures public content, not private pages, databases, or login protected data. Capture systematically from a full URL list, verify your high value pages, and keep the URL list for redirects, the same foundation as downloading all pages of a website. WPBuildAI scans your live site and returns the content, images, and full URL list as files, so you can rebuild elsewhere even when the platform gives you no way out. Send your web address for a free analysis.
Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.