Optimizations

Template Optimizations

Optimize → Template Optimizations (also reachable as Content Rules). Each rule matches a path pattern — /products/*, /blog/**, /pricing — and tells the AI how to treat every page under it. A rule carries:

• A template. Pick from the gallery (product page, collection, article, documentation, landing page, pricing, FAQ, or custom). Each ships a best-practice prompt: for example the product template opens with one sentence stating what the product is and who it is for; the docs template preserves every code block and command; the FAQ template structures the page strictly as question-and-answer pairs with the direct answer first.
• Custom prompt additions. Your own instructions appended to the template prompt (“always mention the 30-day returns policy”).
• A cache TTL. How long the optimized copy is served before it is regenerated; 1 hour by default.
• Pre-render scripts and settings (per domain): device, viewport, wait strategy and timeout for the headless browser, plus optional JavaScript to run before capture — used by the pre-render action, not the AI rewrite.

Template Optimizations are the right tool when a whole class of pages should read the same way to an AI. They apply on the next crawl of each matching URL and refresh as the cache expires.

Page Optimizations

Optimize → Page Optimizations works one URL at a time. Analyze a page and Wrenda proposes specific, reversible improvements grounded in the page's own content, its Search Console data and the fan-out queries AI engines ask about the topic. Nothing changes until you enable a suggestion.

1. Suggest

   Click Analyze on a URL. Each suggestion has a title, a rationale, evidence, a confidence score, an estimated impact and a priority. Transformation suggestions enrich the content served to AI crawlers; pre-render suggestions adjust the HTML served to search bots.

2. Enable

   Enable a suggestion (or select several and use the bulk bar). It applies on the page's next crawl; existing cached copies refresh within the Template Optimization's TTL. The status becomes Enabled · measuring and the enable date starts the measurement window.

3. Verify

   Once enough data has accumulated — usually about 14 days — the URL's Search Console impressions and clicks before and after are compared and the suggestion gets a verdict: Won or Flat. This needs a Search Console connection for the property; see Integrations.

Auto-apply

Per domain you can turn on Auto-apply high-confidence, low-risk suggestions. Wrenda then enables new suggestions automatically when their confidence meets your minimum (default 0.8; adjustable between 0.5 and 1.0). A separate re-analyze switch controls whether pages are re-analyzed weekly for new suggestions. Auto-applied changes go through the same measure-and-verify cycle and can be disabled at any time.

Reversibility

Every optimization — template or page — lives in Wrenda, never in your origin. Disabling a suggestion, deleting a rule, switching the domain to Shadow or Paused, or pointing DNS away all return crawlers to your original HTML on the next request (or on cache expiry, if you don't purge). Your site's source is never edited.

Brand Voice

Settings → Brand Voice is a free-text style guide the AI follows for every rewrite: tone, writing style, terminology to prefer and avoid, key messages, how formal to be. Template Optimizations, Page Optimizations and generated FAQs all read in that voice. Leave it blank and the AI uses a neutral, informative voice. It is a setup-checklist step because a page rewritten in the wrong register can read as off-brand even when every fact is right.

What the AI does — and what it must not do

The optimization pipeline works on a copy of the page and is allowed to:

• Restructure for answer-first reading: a one-sentence summary up top, clear headings, self-contained sections.
• Add semantic context: short definitions of the entities on the page, “what is X” framing, use cases, related items.
• Generate FAQs from the page's own content and the questions AI engines ask about it.
• Add structured data (JSON-LD) built from facts already on the page — a Product with the price and availability the page states, an Article with its author and date, an FAQPage from the FAQs.
• Tidy markup so extractors get clean text.

The same prompt runs in production and in Bot Testing, so the preview is byte-for-byte what a crawler receives. If a rewrite ever contradicts the page, disable the rule and report it with the X-Correlation-ID — that is a bug, not a setting.

Next