# What Luria changes Source: https://docs.luriart.com/optimize/variants Plain text: https://docs.luriart.com/optimize/variants.txt The parts of your page Luria is allowed to change on its own, what always waits for your approval, and how every change stays logged and reversible. Luria improves your pages by trying different versions of the things that move buyers and keeping what wins. This page tells you exactly what is on the table, what is not, and where the line between "ships automatically" and "waits for you" sits. ## What Luria changes These are the elements Luria works with. Think of them as the levers on a page that decide whether a visitor keeps reading, trusts you, and acts. | Element | What a change can look like | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------- | | Headlines | A different angle, a clearer promise, a shorter line | | Subheads | Supporting copy that explains the headline or adds a reason to believe | | Offer framing | How the same offer is described (for example "Free shipping on orders over $50" vs "Spend $50, ship free") | | Hero imagery selection | Which of your existing images leads the page. Luria picks from assets you already have; it does not generate product photos | | Social proof placement | Where reviews, ratings, press logos, and customer counts appear and which ones lead | | CTA copy and position | Button wording ("Add to cart" vs "Get yours") and where the button sits | | Section order | Moving a benefits block above a spec table, or proof above the offer | | Trust elements | Guarantees, shipping and returns notes, payment badges, and where they show | | Urgency treatment | Whether and how stock, time, or demand cues appear. Only honest ones; Luria never invents scarcity | Every one of these stays inside the voice, rules, and do-not-say list you set during training. See [How to train Luria](/train/how-to-train) and [Brand Brain](/train/brand-brain). ## What Luria never changes without your approval Some things are yours alone. Luria will propose ideas here, but nothing ships until you say yes. * **Price.** Luria never changes a price. Not a test, not a rounding, not a "let's see." * **Discount depth.** No deeper discounts, no new discounts, no extended promotions. * **Product claims.** Anything about what your product does, contains, or achieves stays exactly as you wrote it. Luria reframes how a claim is presented; it never adds or strengthens one. * **Your do-not-say list.** Words, phrases, and topics you mark off-limits stay off-limits, full stop. If you want to test any of these, [Pricing and offer testing](/optimize/pricing-and-offers) explains what is possible and how approvals work for it. ## The approval ladder Not every change carries the same risk, so not every change needs your time. Luria sorts changes into three rungs. **Ships automatically.** Small copy and layout changes inside your rules: a headline rewrite in your voice, a CTA wording swap, moving a reviews block higher. These are low-risk and easy to reverse, and asking you about each one would slow learning to a crawl. You can still review every one after the fact. **Waits for your yes.** Bigger swings: a whole new hero concept, a new offer framing, a section removed, a new urgency element. These appear in [Approvals](/dashboard/approvals) with a preview. Approve, edit, or decline. Nothing runs until you act. **Never without explicit approval.** Anything touching price, discount depth, or product claims. These are always flagged and always wait, no matter what else you have set. You can move the line. If you would rather approve every change for the first few weeks, turn on review-everything mode in [Approvals](/dashboard/approvals). Many merchants do this for the first couple of weeks, then loosen up once they have seen what Luria produces. **Note:** The more changes that wait in the queue, the slower Luria learns. If you choose to review everything, check the queue every day or two. Pending changes that sit for a week are a week of tests not run. ## What Luria does not touch at all * **Your theme code.** Luria never edits theme files, templates, or your site builder's design. On Shopify it runs through the app embed; everywhere else, through the snippet. Switch it off and your site is exactly as it was. * **Checkout.** Luria does not change your checkout flow or payment pages. * **Your tracking.** Analytics, ad pixels, and attribution tools keep working as they are. ## Every change is logged and reversible Each change Luria makes, automatic or approved, shows up in your dashboard with what changed, when, which traffic saw it, and how it performed. You can roll any change back from the same screen, and pausing Luria stops all changes within about 60 seconds. See [Reading results](/dashboard/reading-results) to find the change log and understand what each entry means. ## Common questions **Will visitors see a broken or half-changed page?** No. A visitor sees one complete version of a page, start to finish. Luria decides which version before the page renders, so nothing flickers or swaps in front of them. If anything fails, the page shows exactly as you built it. **Can I stop Luria from changing a specific page or section?** Yes. Mark pages or sections as off-limits in training. See [How to train Luria](/train/how-to-train). **Does Luria write in my voice?** That is what training is for. The more you give your Brand Brain (voice notes, past copy that worked, words to avoid), the closer the match. See [Brand Brain](/train/brand-brain). ## Next steps * [Approvals](/dashboard/approvals) * [Reading results](/dashboard/reading-results) * [How to train Luria](/train/how-to-train) * [Pricing and offer testing](/optimize/pricing-and-offers)