Export and preview a static website
Generate a static copy, inspect it, and optionally test local serving.

Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- EMCP 3.20 or later, a connected Cloud account with a generation available and a practice site.
- Pretty permalinks on a single WordPress site; multisite is unsupported.
Let’s do this, step by step.
Step 01
Enable Static Site
Enable EMCP Cloud and Static Site in Modules and Save modules. Open Build → Static Site and inspect allowance.
Open EMCP Tools, then Modules. Enable Static Site and the Cloud connection it needs, then save. Open Static Site under Build and check the generation allowance. The module is available in Free, but generating a copy still uses your account’s allowance.
Step 02
Choose output and links
In Settings choose ZIP or Local Directory, then Relative, Offline or Absolute URL mode. Set Absolute base URL when used. Review paths and assets.
In Settings, choose a ZIP or local directory. Choose the link mode for where the copy will be used. If it will live at another address, set that destination carefully. Review included pages and assets.
Step 03
Generate a small selection
Choose Individual Pages for the first test, then Generate. Keep the tab open through discovery, fetch, rewrite and packaging. Inspect failures.
Start with Individual Pages and select a small sample, then Generate. Keep the tab open as pages are collected and links rewritten. Read warnings and failed addresses before calling the export complete. If interrupted, reopen the screen and use its resume controls.
Step 04
Preview the output
Open through an appropriate local/server preview. Check links, assets and layout; dynamic forms, accounts and checkout need live services.
Preview the generated copy and check links, images and layout. A static copy cannot reproduce every live WordPress feature by itself. Decide how forms, accounts and checkout should work before publishing it.
Step 05
Optionally test local serving
Run Check server and satisfy output protection before enabling serving. Test logged-out plain GET pages without query strings. Edits invalidate served files; Purge Served Files falls back to WordPress.
For local serving, use Check server first and follow its protection requirements. Test a logged-out page without extra address parameters. Changes can invalidate saved pages. Use Purge Served Files when you want visitors to fall back to normal WordPress pages.
You’re done when…
The sample export is inspected and dynamic features and failed assets are accounted for.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.
A brief becomes a real page.