When working on a multi-page project in Website Studio, two questions come up often: does an edit affect only the page I'm working on, or can it touch other pages? And why does the AI agent sometimes rewrite content instead of making the small change I asked for? This article explains how page-level editing scope works, what causes content to change unexpectedly, and how to get the most precise results from Website Studio.
Website Studio is designed so that edits — whether you upload HTML or send a prompt — are scoped to the active page you have open in the editor. In a 21-page project, for example, only the page currently selected should be affected by your instruction.
In practice, the following rules apply:
Uploading HTML: The uploaded file replaces or updates only the page it is mapped to. Other pages in the project remain unchanged.
Prompting the agent: Instructions sent while a specific page is open are interpreted in the context of that page. The agent should not propagate changes to other pages unless you explicitly ask it to.
Global elements (headers, footers, shared components): If your project uses shared components that appear across multiple pages, editing a shared component will affect every page that includes it. This is expected behaviour, not a bug.
If you notice changes appearing on pages you did not intend to edit, it is likely because a shared component was modified, or because the instruction was phrased in a way the agent interpreted as site-wide. See the tips below for how to avoid this.
The Website Studio AI agent is generative by nature. When it processes an instruction, it regenerates the affected section rather than performing a surgical find-and-replace. This can cause more text to change than you expected, even when your prompt was specific.
Common reasons this happens:
Ambiguous phrasing: Instructions like "improve this section" or "fix the copy" give the agent creative latitude. It interprets these broadly and rewrites accordingly.
Context bleed: In some cases, the agent may lose track of exactly which element you are targeting, especially in pages with complex or deeply nested HTML. This can cause it to rewrite a larger block than intended.
Regeneration vs. patching: The agent builds output token by token. Even a small change instruction may cause it to regenerate a full paragraph or section to maintain stylistic consistency in its output.
Use these best practices to keep changes contained and match your exact intent:
Be specific about the target element. Instead of "update the intro," try "change only the first sentence of the hero heading to read: [your exact text]." The more specific you are, the less room the agent has to interpret broadly.
Use exact text anchors. Quote the exact text you want changed. For example: "Replace the text 'Book a demo today' with 'Start your free trial'." This removes ambiguity.
Avoid open-ended improvement prompts. Phrases like "make this better" or "rewrite this page" will almost always result in significant content changes. Reserve these for when you genuinely want a full rewrite.
Upload HTML for precise replacements. If you have a finalised version of a section, uploading the HTML directly gives you full control over the output and bypasses the agent's generative behaviour entirely.
Check shared components before editing. If your project uses a global header, footer, or navigation component, be aware that changes to those elements will appear on all pages that include them.
Review changes before publishing. Always preview the page after an agent edit to confirm only the intended elements changed before making the page live.
To access Website Studio, go to the left sidebar and select Website Studio. Your projects and pages are listed in the panel. Click the specific page you want to edit before sending any prompt or uploading HTML to ensure the correct page scope is active.
The Search Atlas team is actively working to improve editing precision in Website Studio. Improvements to scoped editing — so that "change only this" instructions are honoured more reliably — are already in progress. If you experience consistent context bleed or unintended rewrites, documenting the exact prompt and the page structure can help the team investigate.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.