Edit your existing website without moving it

Kite edits copy directly on most of the platforms marketing teams use, but what it can change depends on what each platform lets an outside app do. Here's where things stand on each one:

• Webflow. Kite finds the CMS item behind a page or blog post, rewrites its fields, and publishes the site so the change goes live. Your Webflow site can appear in your Kite website list next to any sites Kite built for you.
• Self-hosted WordPress. Kite rewrites the title, body, and excerpt of existing blog posts and publishes new posts with a featured image, categories, tags, and an author. Pages built in WordPress, such as your homepage, are still edited in WordPress.
• WordPress.com. Kite publishes new posts and pages and takes down old posts. It doesn't rewrite a post that's already on your site, so for those it writes the new version for you to paste in.
• Shopify. Kite writes and updates product descriptions, store pages, blog posts, and the custom content fields your theme displays.
• Contentful, Sanity, Storyblok, and self-hosted Payload. Kite rewrites the text stored in your content entries, one field at a time, and the change goes live in your content system as soon as it's written.
• Ghost. Kite publishes new posts to your Ghost site.
• A site built from code in GitHub. Kite edits the code itself, including copy that's written into the code, and your own deployment ships the change.

Kite doesn't edit pages on Wix, Squarespace, or Framer directly today. If your site runs on one of those, Kite still writes the changes and tells you exactly where each one goes, so pasting them in takes a minute instead of an afternoon.

On many websites, the words on a single page come from two places. Headlines, blog posts, FAQ answers, and testimonials usually live in the content system. The navigation, the page layout, and some buttons or taglines are often written directly into the site's code. A change only sticks if it's made in the place the page actually reads from.

Kite checks this before it promises anything. On an imported site, it knows which pages draw their content from your content system and which copy is written into the code. You can ask it directly, too: "Is the headline on our pricing page in Contentful, or is it in the code?" Kite tells you where it lives and whether your team can edit it in the content system without a developer.

That answer decides the route. Copy in Contentful, Sanity, Storyblok, Webflow, or Payload gets changed there. Copy in the code gets changed in your GitHub repository, where Kite merges the change into your main branch for your own deployment to ship. If you protect that branch, Kite opens a pull request instead and waits for someone to merge it.

Kite writes website copy from the research it did on your company when you started. Your team's knowledge base holds your positioning, products, pricing, customers, competitors, and brand voice, so Kite doesn't need a brief for every edit.

That lets Kite handle the copy work that usually sits on a to-do list for months. It can:

• rewrite a homepage headline, subheadline, and call to action so they say what you do and who it's for
• turn generic lines like "the all-in-one platform for modern teams" into specific claims a buyer can check
• write the benefits, how-it-works steps, and problem sections of a page
• update every post that still mentions a product name, price, or feature you've changed
• remove customer logos, badges, or testimonials that the business can't actually back up

Say your homepage headline reads "Smarter scheduling for everyone." Kite knows from your customer research that most of your buyers run physical therapy clinics and care most about filling cancelled appointments. It might propose "Fill cancelled appointments before the day starts," with a subheadline that explains how, and a note on why it's the stronger choice.

Kite shows you each change before it touches your live site. For an edit in your content system, that means the entry, the field, the text that's there now, and the text Kite wants to put there. If a change touches a headline and a subheadline, Kite makes them as two separate edits, one field at a time, and you approve each one.

Kite asks for confirmation on these platforms whenever there's any doubt about the match, because on a content system like Contentful or Sanity, writing the change is the same as publishing it. The one exception is a request where you quote the exact text to replace and give the new wording, and that text appears in only one place: Kite treats your request as the approval and makes the change. There's no separate draft on Kite's side to catch a mistake later. If the text you asked about appears in more than one place, Kite lists each match and asks which one you mean rather than guessing.

On WordPress and WordPress.com, you can also ask Kite to save a new post as a draft, so you can check it in your own editor before it goes live. On a site built from code with a protected main branch, the pull request is the review step.

For edits in Contentful, Sanity, Storyblok, Webflow, or Payload, the person who owns the website in Kite, or an admin on your Kite team, approves them. Anyone else on the team can still ask Kite to research a page and draft new copy for one of them to approve.

Once you approve, Kite writes the change into your platform and reads it back to confirm it landed. Then it tells you what changed, where, and how to see it.

Where the change stands depends on your platform. In Contentful, Sanity, Storyblok, and Payload, the new text is live in your content system right away, and your website shows it the next time it rebuilds or refreshes its cache. In Webflow, Kite publishes the site so the staged edit goes live, and it tells you whether each change is staged or live. On a site built from code, the change ships when your own deployment runs.

That last step is what saves the copying and pasting. The approved text goes from Kite into the exact field it belongs in, without passing through a document, a chat window, or someone's clipboard.

A website stays accurate when small edits happen regularly, not when someone schedules a cleanup once a year. You can ask Kite to keep your site current on a schedule, such as "check the site every Monday and fix anything out of date." Each run starts fresh, looks for what needs changing, and brings the proposed edits to you.

Kite can also check whether an edit helped. Because your site isn't hosted by Kite, it reads results through the analytics and search tools you connect, such as Google Analytics or Google Search Console. It compares how the page performed before and after the change and uses what it learns to decide what to work on next.