What Terra can do

Terra builds and edits a real website for your brand. Everything below is something you can ask for in plain language in a chat. This page is organised by what you want to accomplish, and it is explicit about the limits, because knowing what Terra will refuse is as useful as knowing what it will do.

Change what is already on a page

The most common request, and the fastest. Terra reads the exact current text, changes it, and saves.

• Rewrite a headline, a paragraph, a button label, an image's alt text.
• Add or remove one item from a list: a feature, a testimonial, a pricing row, an FAQ entry.
• Add a whole new section to a page, or reorder what is there.
• Swap an image.

Edits are transactional. A batch of changes either all lands or none of it does, so a page is never left half-edited. If a person changed that content in between, Terra's edit is rejected, and it re-reads and tells you rather than overwriting your version.

Edit directly on the page

You do not have to describe what you mean. Turn on editing from the preview toolbar (the pencil icon) and click any element on the page.

For text, the toolbar offers four one-click actions that hand the exact element to Terra: Rewrite, Shorten, Expand, and Brand voice. For an image, it offers Generate. Selecting an element and then typing a request in the chat works too: the selection rides along, and Terra edits that element rather than guessing.

Section headers carry one more action: Try 3 takes. Terra reads the section and proposes three different angles on the copy, for example benefit-led, proof-led, and urgency-led. You flip through them in the preview and press Keep on the one you want. Nothing is written until you do. Takes vary copy only, never images or layout.

Build a new page

Ask for a page and Terra plans before it builds: it pulls your theme tokens, your existing pages and sections, and your brand guidelines, decides what to reuse versus build fresh, then composes the page section by section, saves it, screenshots it, and reviews its own result before calling it done.

Expect several minutes for a multi-section page. Terra sends a short heads-up before starting rather than going quiet.

You can also point it at a page opportunity from your account with /build-page-opportunity, which picks up the keyword and brief that opportunity carries, or hand it a freeform brief.

Every page it builds carries your site's real navigation and footer. A page without that chrome is treated as incomplete work.

Recreate an existing page

Give Terra a live URL and it produces a close replica: it opens the page in a real browser, captures it, and compiles it into your project. No redesign, no rewritten copy.

• The replica lands at the same route as the source page. A home page replaces the home page.
• If that route already exists, Terra stops and asks whether to overwrite it or put it somewhere else.
• After the first replica, later pages from the same site reuse the navigation and footer it already captured.
• Some things cannot be captured: paused animations, or stylesheets a browser will not let it read across origins. Terra reports those instead of inventing a substitute.

This is the mechanism for any "clone this", "rebuild this from my old site", or "make it look like this page" request against a live URL.

Look at the real web

Terra does not guess at facts or at design values.

• Your live site: it reads the page text for facts, copy, and structure.
• Computed design facts: from any live URL it extracts the actual colours with usage counts, the loaded fonts, heading and button treatments, shadows, asset URLs, and the navigation and footer link by link. This is where your brand tokens come from. It does not read colours off a screenshot, and it does not infer them from class names.
• Page structure: it can pull the real markup skeleton and layout classes from a live page, which is how a hand-built page ends up matching an existing site's geometry.
• The web at large: it searches public sources, but only after checking your own brand knowledge and your own site first, and it opens the source page before relying on anything it found in a search result.

Use what it knows about your brand

• Brand knowledge: your crawled site and any documents you have uploaded. Terra searches this before it searches the web, and it keeps the source of each fact it uses so claims can be traced back.
• Brand documents: Terra writes and curates a set of documents about your brand (pricing, positioning, audience, decisions). It checks what exists before writing so it updates rather than duplicates, and it prunes stale ones. You can read and edit these in your dashboard, and they open as tabs beside the preview when Terra touches them.
• Memory and brand guidelines: a running activity log of what changed and why, plus the design decisions it has made. Both are written in plain language for you to read, not internal notes.
• /remember: saves a durable preference or fact as a general rule, and confirms what it saved.

Images

Three routes to an image, in order of preference:

1. Your asset library. Terra searches your real assets first and uses the real file.
2. Import from a URL. It pulls a real image (a logo, a product photo) into your asset library. The file lives on a CDN.
3. Generate one. Terra can generate brand-appropriate imagery and save it to your library.

Translations

• One page: Terra creates the locale sibling of that page, for example /es/pricing.
• The whole site: a background job that translates every page.

Both have the same safety rule: an existing translation is never overwritten. Re-running a whole-site translation only fills in pages that are missing one. If you want an existing translated page changed, ask Terra to edit it.

Whole-site translation runs one job per brand at a time, and progress lives in the Languages panel in the preview toolbar, where you can also cancel or resume a running job.

Search metadata

Terra drafts SEO titles and descriptions grounded in the page's own content, your other pages, and your brand voice. These arrive as suggestions. If a person already wrote that metadata, Terra confirms before replacing it. The page settings panel in the preview toolbar shows how the result looks in search results and as a social card.

/seo-check audits the page in view: title and description, heading hierarchy, search intent, internal links, image alt text. It ranks findings by impact and only applies the fixes you ask for.

Understand how the site is doing

Ask /whats-happening for a visitor-centred digest, or ask about a specific page.

• Visitor signals are keyed to the same sections Terra edits: how many visitors reached each section, click-through on it, how long they stayed with it, clicks that did nothing, repeated frustrated clicks, where visitors abandon a form, and which paths hit a 404. This closes the loop: measure, edit that exact section, measure again.
• AI visibility reports your mention rate, share of voice, competitors, and citation gaps across AI platforms, when visibility tracking is on for your brand.

When it spots something worth counting that is not yet a defined conversion, it proposes one. A proposal is not counted until an owner approves it in the dashboard, and Terra will describe it as proposed, not as tracking.

Publish

Publishing is per page, from the button at the right of the preview toolbar. The button reads your page's actual state: Publish for a page that is not live, Publish changes when the live version is behind, Republish when it is already live.

The panel behind it shows:

• Whether this page is live, and its live URL.
• Changes since last publish: the commits that have not gone out yet.
• Preview link: a private copy of your latest work you can share without touching your live site. Search engines never see it.

Put the site on your own domain

/go-live walks the domain setup. Terra checks the current state, explains the options that apply to your situation and their tradeoffs, lets you choose, then executes and verifies.

Along the way it registers the domain and hands you the exact DNS record to add, re-checks ownership, attaches the domain to the serving layer, reports certificate and validation state, sets the canonical host used in canonicals, sitemap, and hreflang, and can keep watching in the background until every declared path is live.

Every step that changes live serving state requires your explicit approval first. Terra asks, waits, and only then acts. It never claims a step ran while approval is still pending.

Undo

/undo shows you what would be reverted, confirms the exact change with you, and then reverts it. Terra never rewrites history to make a change disappear.

Independently of that, the preview toolbar carries Version history for the page in view.

Playbooks

A playbook is a saved, runnable workflow for your brand. /playbook lists yours and runs the one you pick. Small scoped playbooks run inline in the current chat. Longer ones start their own dedicated chat, and Terra tells you the title of the chat it started. Playbooks open as editable tabs beside the preview, with a Run button in the header.

Where the limits are

These limits are firm.

• Page-by-page editing. Multi-page work is sequential, so it takes longer than it looks.
• No invented facts. Copy comes from your live site or your brand knowledge. Terra will ask rather than fabricate a statistic, a testimonial, a customer name, or a capability.
• No generated product UI. See above.
• No acting on statistically thin signals.
• No overwriting an existing translation.
• No overwriting a person's edit. Terra re-reads content before changing it and reports a conflict instead.
• No running code you hand it. The workspace is Terra's workshop, not a shell you drive. It will decline requests to execute arbitrary commands or scripts and offer the product-level alternative.
• No rewriting site history, and no leaving broken code committed. Every save runs a verification gate before it lands.
• No unrequested work. If Terra notices a problem outside what you asked for, it flags it in one sentence and leaves it alone.

Where to go next

Writing good requests: how to phrase an ask so you get the result you wanted the first time.