Strikingly HTML: edit an exported HTML site with an AI agent

Edit an exported HTML site with an AI agent

1. 01

   Identify the site and route

   Connect your agent using FNJ's MCP setup and authorize the access the task needs. Have it call list_sites and get_site, then confirm the site ID and route against the preview. Similar project names are not enough to select a site safely.

2. 02

   Inspect before changing content

   Use get_page_text for editable text and get_page_outline for section keys. Ask the agent to quote the target copy and describe the section it found. Those keys are tied to the actual captured page; inventing selectors from a screenshot can edit the wrong element.

3. 03

   Make a bounded draft change

   Use edit_text for copy, set_style for supported style changes and add_section for new content. To create a new page, clone a suitable existing route with create_page so shared styling carries over. Specify the exact replacement text, destination links and routes you want.

4. 04

   Review and publish deliberately

   Preview the result at desktop and phone widths. Confirm shared footer or header changes appear on each intended page. Ask for a summary of pending changes before publish. That tool uses the site's saved deployment provider, so first confirm the connected hosting account in FNJ.

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: Strikingly. Output: static HTML, not the original builder workspace.

Inspect my FNJ site [site name or ID] at [route] using get_site, get_page_text and get_page_outline. Change [exact copy, section or links]. Preserve its existing fonts, colors, header and footer. Use supported FNJ tools and inspect their current input schemas. Show me the draft and list what changed. Do not publish until I approve the preview; confirm the saved deployment provider first.

Platform checks: For Strikingly, inspect the captured section and anchor target before changing page copy. Additional public pages and one-page sections need different navigation edits. Membership or store widgets can remain externally hosted; updating surrounding HTML does not alter their access rules or order data.

Verify the result before launch

• ✓The agent selected the correct saved site and route.
• ✓Requested copy and links changed without removing adjacent content.
• ✓The reviewed draft, chosen export and live deployment match.

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

Will MCP changes update my original builder project?

No. FNJ changes its saved site draft. A downloaded or GitHub-exported version also needs to receive the reviewed changes. There is no automatic synchronization back to the original website builder.

Can I cancel Strikingly hosting right after exporting?

First verify the content, assets, routes and business actions on the replacement host. Follow mobile section navigation and test store or membership actions through their actual service endpoints. 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.