Quick answer
Give ChatGPT or Claude the public HTML, CSS, JavaScript, and assets for the pages you want to change. Request a limited revision, review the changed files, preview the website, and publish only the approved output. A normal conversation can prepare changes without having access to your hosting account.
Applies to
Existing static websites hosted by Interactive Online. Confirm that the editable source is ordinary website files or a project that builds static output. A WordPress or Joomla page is normally edited through its CMS, and a server-rendered application needs its own runtime workflow.
Prepare a safe working copy
- Identify the live page and the folder that actually serves it. Keep a recoverable copy of the existing website and a record of the current public result.
- Copy the affected public files into a dedicated working folder. Include shared styles, scripts, navigation, and required images. Exclude private configuration, keys, database dumps, backups, customer submissions, and server logs containing personal data.
- Open the files in a text editor and identify the intended page. If you only have a screenshot or PDF, obtain the editable source first. Rebuilding from a picture can lose working features.
- Provide the relevant files through your AI application's supported attachment or project interface. If its file-generation feature is unavailable, ask for a precise patch and apply it in your editor.
These are public files for an existing HTML website. On services.html, replace only the heading "Our services" with "Garden care for every season" and change the main button label to "Request a quote". Keep its destination, shared navigation, stylesheet, analytics/consent behavior, page URLs, and form backend. Return only the files you changed and a short change list. Do not publish or create an account connection.
Review and preview
- Compare the original and revised files. Confirm that only the requested content changed. Ask the AI to explain any additional file or dependency before accepting it.
- Preview the complete working folder using the existing local preview method. A local web server is more reliable than opening files directly when scripts and relative paths are involved. Follow the publishing guide's preview instructions rather than serving a folder containing private files.
- Check the changed page, shared navigation, images, buttons, and another page using the same CSS. Inspect phone, tablet, and desktop widths.
- Test any affected form using sample data. Confirm the actual receipt or saved result. Browser-only JavaScript cannot safely hold a private email-service or payment API key.
Publish and verify
Use your service's supported File Manager or SFTP workflow to upload the approved public files into the verified destination. For a framework, publish its completed static output, not a source folder or dependency directory. Preserve newer live files and other applications in the account. Open the public HTTPS page privately and verify the changed content, assets, links, and any real form action.
If the result is wrong
- Images or CSS are missing: check relative paths, capitalization, and whether all required assets were included.
- Several pages changed unexpectedly: inspect shared styles or scripts; restore the affected files from your checkpoint and reduce the next request.
- The AI returns React or a server application: request compatible static output or use the appropriate supported runtime. Renaming a source file to .html does not convert it.
- Changes are visible only locally: verify the selected domain, document root, uploaded files, and cache.
When to contact support
Contact Interactive Online if the hosting destination or available account tools are unclear. Include the affected URL, service name, time and time zone, exact error, and a screenshot with private details replaced by sample data. Keep passwords, private keys, API tokens, customer records, and billing information out of the message. Your external AI provider handles its subscription and usage limits.
Related help
- Preview and publish completed static website files
- Identify the website document root
- Check an AI export for runtime requirements
- Review the proposed changes
- Understand connected and unconnected ChatGPT workflows
Official references
Documentation reviewed November 2, 2026. Follow the features and permissions available on your own account. Vendor instructions were reviewed; a completed walkthrough on your account is not implied.
