What you will have afterward
An asset inventory with working paths and a clear record of external dependencies. Locally captured files can be served from your new host; an embedded video or remote script may still rely on its original provider.
Before you start with Wix
Evaluate one public Wix page first. Script-built sections can be absent or incomplete in a markup capture; a successful request is not proof that the exported site is usable.
Treat a Wix HTML capture as a preview to evaluate, not an automatic complete migration. Wix relies heavily on platform scripts, and some content or interactions may not become an independent static page. Read the migration guide.
What matters for Wix
Wix media can load through platform endpoints and responsive transformations. Inspect the actual captured files and requested variants before renaming URLs. A remote script may also create the content referencing an image; absent markup and a failed asset request require different repair plans.
Fix images, fonts and assets after an HTML export
- 01
Inspect requests on the deployed preview
Open the browser Network panel and reload the affected route with caching disabled. Filter failed image, font, CSS and JavaScript requests. Record the requested URL and response status; a missing file, incorrect relative path and denied cross-origin request need different fixes.
- 02
Keep file references and folders together
Extract the full bundle and preserve referenced asset folders. Test nested routes as well as index.html: a relative path can work at the root and fail under an article. Update CSS url() references, srcset candidates and preload links alongside image src attributes when moving a file.
- 03
Review fonts and remote dependencies
Compare computed font families and weights with the source. Confirm fonts load from the intended URLs and that you are authorized to host them. Catalog remaining external scripts, videos and widgets. Do not delete an external dependency just to make an asset report shorter; test or replace the behavior it provides.
- 04
Recheck appearance and loading
Compare image crops, lazy-loaded media, logo sizes and text wrapping at multiple widths. Use dimensions that reserve layout space and descriptive alt text where meaningful. Remove obsolete references only after the replacement works. Review the hosted preview again so local file paths are not mistaken for deployment URLs.
Give your agent a clear starting point
Copy this prompt for your connected agent and fill in the project details. Tasks that inspect browser requests, edit downloaded files or configure another service may need your agent's own browser or code tools. FNJ MCP alone does not configure those external services. Keep credentials in the relevant account's setup screen, never in the prompt.
Source: Wix. Output: static HTML, not the original builder workspace. Audit assets for my exported Wix HTML site [site ID or folder]. Inspect failed image/font/CSS/script requests on [preview URL] including nested routes. Identify missing files versus broken paths or external-service dependencies. Preserve authorized assets and font weights; update src, srcset, CSS url() and preload references consistently. Do not remove scripts without checking their behavior. Show changes and a repeatable hosted verification plan before deployment. Platform checks: Wix media can load through platform endpoints and responsive transformations. Inspect the actual captured files and requested variants before renaming URLs. A remote script may also create the content referencing an image; absent markup and a failed asset request require different repair plans.
Use with your own agent. Replace bracketed values.
Verify the result before launch
- Representative root and nested routes have no required asset failures.
- Font weights, image crops and responsive sources are reviewed.
- Remaining remote services are documented and intentional.
Use the final hosted preview as well as the saved FNJ draft. Keep a backup of the reviewed files, record what remains external and test the important customer action on the final domain. A draft edit, downloaded ZIP and live site can represent different versions until you export and deploy the intended one.
Common questions
- Does an export make every embedded service local?
- No. Reachable assets can be captured, but a video player, hosted widget or builder script may remain external. Inspect actual requests and decide which dependencies to keep or replace before cancelling the source hosting.
- Can I cancel Wix hosting right after exporting?
- First verify the content, assets, routes and business actions on the replacement host. Compare the preview with Wix at two screen widths and verify galleries, booking links and important page content before switching traffic. Keep or replace external dependencies before relying on the new site.
- Where do these HTML changes get deployed?
- Use a compatible static host in your own account. FNJ supports deploying the saved site to your own Cloudflare Pages account, and exporting code to your own GitHub repository. A GitHub push stores code; configure hosting separately and confirm the reviewed version is what visitors receive.