Everything Vindex does, and how to use it

Vindex rebuilds the website you already have, then lets you change it by typing what you want in plain English. No agency, no developer, no waiting.

• Clone: point Vindex at a site and it reconstructs the design and hands you an editable copy.
• Edit by chat: describe a change ("replace the headline with X") and the editor makes it and shows you a preview.
• Publish: your change goes live. Edits are live right away by default; switch on Draft mode to stage changes privately first.

Try it first (no sign-up)

Visit /try to edit a sample site with no account. Type a change and watch it happen. This is the fastest way to see how it feels.

Get your own site cloned

1. 1Sign in (top-right My Projects).
2. 2Paste the URL of a site you own or are allowed to use.
3. 3Vindex rebuilds it and adds it to your Projects.
4. 4Open the project to start editing.

A one-time clone fee applies to take a site live (waived on the Enterprise plan). See Plans below.

Your Projects

My Projects is your dashboard of cloned sites. Open any project to launch its editor. Access is tied to your account, and to any teammates you invite (see Team seats).

Opening a project launches the editor. It has:

• A chat panel where you request changes.
• A live preview of your site.
• A status pill (Idle / Building / Live) so you always know what the editor is doing.
• Three tabs: Edit (default), Improve, and Chatbot.
• An Actions menu holding Draft session, Version history, and Backups.

Sessions

Each request runs in a session. Start a new session for each unrelated change so context stays clean and your history is easy to review.

Making a good request

Short version (the full walkthrough is in Writing good edit requests below):

• One change per message.
• Say what and where ("in the services section", "at the top of the page").
• Paste the exact current text to replace, and the exact new text.
• Give real content (phone numbers, hours, quotes); don't make the editor guess.
• Check the preview before you rely on it.
• If something is off, just say "that didn’t work" and point at what is wrong.

Click-to-edit

Instead of describing where, you can click an element in the preview to target it, then type the change. Handy for a specific button, heading, or image.

Undo

Made a change you don't want? Undo reverts the most recent edit in one click. It creates a new forward step (it never destroys history), so you can always move forward again.

Draft mode lets you make changes privately and publish them only when you are happy.

1. 1Click Draft session (in Actions).
2. 2Make as many edits as you want. They apply to a private draft, not your live site.
3. 3Preview the draft in the editor.
4. 4Finish with Publish (your draft changes go live in one clean step) or Discard (throw the draft away and keep your live site as-is).

• Your live site keeps serving normally the whole time a draft is open.
• If you leave and come back with an unpublished draft, Vindex offers to Resume, Publish, or Discard it.
• Improve and Chatbot are paused while you are in a draft session.

Every edit is saved as a checkpoint. Open Version history (in Actions) to see the timeline, including "Original (as cloned)" at the bottom.

• Click Restore on any checkpoint to bring your site back to exactly that state.
• Restore is safe: it moves you forward to that version rather than deleting anything, so nothing is ever lost.

Vindex takes an automatic daily restore point of your site.

• Open Backups (in Actions) to see recent days.
• Restore any day in one click.
• Backups are kept for 30 days.

Think of backups as a coarse daily safety net; Version history (Enterprise) is the fine-grained, per-edit timeline.

The Improve tab reviews your live site against a quality rubric and gives you a prioritized list of plain-English suggestions, tagged Important, Worth doing, or Nice to have.

For each suggestion you can:

• Fix this: hands the change straight to the editor to apply.
• Save: adds it to a backlog to do later.
• Ignore: dismiss it.

Improve only suggests; the actual change is always made (and previewed) by the editor, so you stay in control.

Add an AI chatbot to your site, trained on your content, so visitors get instant answers.

• On the Chatbot tab, click Add a chatbot.
• Configure how it behaves and add FAQ (question/answer) pairs, or upload a file of FAQs to seed it quickly.
• The bot answers visitors using the info you give it.

A cloned site looks right immediately, but interactive forms need to be connected to a real provider. The Finish setup step lets you wire these up by bringing your own account:

• Contact form and Booking form (contact-style).
• Newsletter signup.
• Payments (Donate, Cart, Checkout) via Stripe.

Vindex never collects or stores your provider secrets; it connects your own account so submissions and payments go where they should.

Invite teammates so more than one person can edit, without sharing a login.

• Add collaborators by email (owner-only, in the editor).
• Total seats = owner + collaborators, by plan: Personal 1 (owner only), Standard 3, Enterprise unlimited.

Feature access and monthly edit allowances by plan:

* Enterprise is unlimited with a fair-use ceiling for abuse monitoring only.

• Edit top-ups: if you run out of monthly edits, you can buy more in blocks of 10.
• Reaching your monthly edit cap shows a friendly notice; core actions like Undo are never blocked.

• Instant by default: outside of Draft mode, an approved edit goes live on your site within a minute or two.
• Draft mode (Standard+): stage privately, then Publish when ready.
• The status pill (Building to Live) tells you when a change has finished deploying.

The editor is a chat-based assistant: describe the change in plain English, no code needed. Every change shows a preview first, and nothing goes live until you approve it. Here is how to phrase requests so you get the right result on the first try.

Quick reference

The short version. Details and examples for each row are below.

Step 1: Start a new session for each request

• Open a new session every time you're asking for a different change, even on the same page.
• One long session for unrelated edits makes it easy for the editor to mix up context, and harder for you to review the history later.

Step 2: Be specific about what and where

• Vague requests force the editor to guess. Specific requests get you exactly what you want.

Step 3: One change at a time

• Ask for one thing per message so it's easier to review what happened.

Step 4: Give it the actual content

• Type out specific text, phone numbers, addresses, or quotes exactly, or attach a document.
• Don't make the editor invent details it can't know, like your real hours or a client's exact wording.

Step 5: Paste the exact text to replace

• Copy the exact current text into your message, then say what it should become.

Step 6: Say where on the page

• Pages can have multiple sections. "Add a photo" could mean the header, gallery, or footer.
• Name the section, for example "in the services section" or "at the top of the page", to save a round trip.

Step 7: Check the preview before approving

• Nothing goes live until you approve it. Take the extra 15 seconds to look it over.
• Pay extra attention to prices, phone numbers, or legal wording.

Step 8: Check every page the change should appear on

• Some things repeat: a phone number in the header, footer, and contact page, or a business name that appears site-wide.
• If the editor updates one spot but not another, don't assume it's done.
• You don’t need to list every page yourself: just say "check every page this should apply to".

• "I don’t see my change." Say exactly that in the chat. Don’t rephrase your whole request; just point at what is still wrong.
• A change should appear in several places (phone number in header, footer, contact page): say "check every page this should apply to" rather than assuming one fix covered them all.
• The preview looks stuck: give it a moment to finish building; the status pill shows progress. Use Refresh if needed.
• Still not right after a couple of tries? Stop retrying and contact support rather than burning edits.

• The request-writing walkthrough above (Writing good edit requests) covers most first-try issues.
• For anything the editor can't resolve in a couple of tries, reach out to your Vindex support contact.