Campaign batches now carry your approved typography and branding choice into every image. Reopening a saved creative also keeps those settings when you regenerate it or request another take. Chat proposals have a **Create campaign** action. Choose the output sizes and review the total cost using the proposal you already approved, without asking the studio to plan it again. A rejected or interrupted generation no longer marks the proposal as already generated. You can retry it, including after refreshing the page, while the studio recovers any jobs that were already submitted. **Where:** Creative → your brand → Visuals.
Opening an older visual from a brand's Library took you to your most recent creation instead — so anything but the newest was unreachable from the grid. Every card now opens its own work. **Where:** Creative Studio → pick a brand → Library **How to test:** With at least two generations for a brand, click Open on a card that is not the newest. The takes shown should be the ones on the card you clicked, with the same headline and images. **Watch for:** A card whose Open still lands on the newest batch, or an Open button that does nothing on a logo direction.
The Logo tool now plans four genuinely different mark ideas instead of four versions of one, shows your brand name set beside whichever you pick, and lets you open any result full size. **Where:** Creative Studio → Logo **How to test:** 1. Open Creative Studio, pick a brand, go to Logo. 2. Choose what the mark should be — symbol only, a monogram, or your full name drawn as lettering. 3. Write or edit the direction brief and generate four directions. 4. Click any result to open it full size; use the arrow keys to move between them. 5. Click "Use this direction". It saves to your brand and, right there in the card, shows your name typeset beside the mark in three arrangements. 6. Approve the mark to unlock the monochrome and reversed versions, then export the package. **Watch for:** - The four directions should be four different ideas, not one idea four times. If they look like re-rolls, the planning step fell back to a single brief. - The directions should be about your actual business. If they look like generic stock art, the brand has no description for us to work from — add one in Brand Kit. - If you asked for a monogram or full lettering, each result is checked for spelling and flagged when the drawn letters do not match your brand name exactly. It is a warning, not a block: open it full size and decide for yourself. - The name shown beside the mark is always typeset from your exact spelling, so it cannot be misspelt — only the drawn lettering can. The six social and ad starter layouts that used to sit on this page have been removed. They ignored your brand entirely and invented their own headlines; Visuals already does the same job properly, using your real business details.
Applying SEO fixes reported success but saved nothing — the titles, descriptions and keywords never reached your pages. They now persist, and the change shows up in version history so you can undo it. **Where:** Site editor → SEO. Both the "AI Fix Suggestions → Apply" flow and the inline title/description/keyword editing on the Pages tab. **How to test:** Open SEO, go to Pages, click a page's title and type a new one, press Enter. Re-scan the report: the "default/missing SEO title" issue for that page disappears and the issue count drops. Reload the page — your title is still there. Check History for an "Updated SEO for …" entry. **Watch for:** A title that reverts after a reload, a re-scan that reports the exact same issue count as before, or a missing History entry. The same save path backs page duplication, so also check that a duplicated page survives a reload.
If a creative came back with a look you did not want, saying so meant leaving the work, opening the Brand Kit and typing into a settings field — so most people said it again next time instead. There is now a "Never this look" action on the creative itself: write the rule once, and every future creative for that brand carries it. It stays editable in the Brand Kit. **Where:** Creative Studio → Visuals → the actions under any finished creative **How to test:** Generate something, press "Never this look" and write a short rule ("no warm golden-hour light"). Open Brand Kit → it should be listed under what to avoid. Generate again and the rule should be respected. **Watch for:** The same rule appearing twice, a rule that saves but does not show in the Brand Kit, or one that has no effect on the next creative.
The floating assistant was dark on a light dashboard and, on a phone, sat directly on top of the Continue button in the campaign wizard. **Where:** Anywhere the "Ask AI" pill appears — the dashboard, client pages, and Growth. **How to test:** Open the dashboard on a phone (or a narrow browser window) and tap "Ask AI" — the panel should be white and read like the rest of the app. Then start a new campaign under Growth: the pill should sit above the Continue / Create campaign bar, not on it, and the open panel should leave that bar visible and tappable. **Watch for:** The pill or panel drifting too far up when no bottom bar is on screen, sliding under the bar when you rotate the phone, or the panel's text box clipping its placeholder.
A brand used to be one endless conversation, visible only to whoever started it. Work is now named — a launch campaign and a recruitment film are separate conversations you can switch between, send someone a link to, and pick up where a colleague left off. Everything the brand has made sits in a rail beside the work instead of inside a tab you go to instead of working, and clicking one uses it as a reference for the next thing. The rail also tells you what is still being made, and that it keeps running if you move around. Opening the detail controls no longer takes the conversation away, and two screens that asked questions the studio had already answered are gone. **Where:** Creative Studio → any brand. Work appears in the left rail, the library on the right on wide screens. **How to test:** Start a piece of work from the left rail and name it, have a conversation, then start a second one — switching between them should switch the whole conversation. Copy the address and open it in another tab; it should land in the same work. Click a picture in the right-hand rail and it should attach to what you are making. **Watch for:** A conversation from one piece of work appearing under another, a rail click that seems to do nothing, or work that disappears after a refresh.
A generated video only ever knew your brand's name, palette and typeface — never what you actually do. With nothing to be about, it fell back to big type on a plain colour field no matter what the business was. It now gets the same picture of you that your ads and images already get: what you do, your industry, who it's for, your tone, and anything you've said to avoid. It can also reach for real imagery when the subject is something you can picture, and it can now use our icon set, which was previously locked to presentations. **Where:** Creative Studio → Video → build or rebuild a video **How to test:** Fill in the Brand Kit description for a brand with a concrete subject (a sport, a restaurant, a trade). Build a short video. The result should be visibly about that subject — imagery, symbols or shapes that belong to it — rather than the brand name set large on a colour block. Brands whose subject is abstract (a promise, a name reveal) should still get a typographic treatment; that's a choice now, not a default. **Watch for:** Imagery that doesn't match the business, an icon appearing where a real photo was wanted, or a video that still looks generic — if so, check the brand's description is actually filled in, since that's the field doing the work.
Video voiceovers can now be recorded in 50+ languages, and you can teach a brand how its own words should be pronounced once instead of hoping every recording gets them right. **Where:** Creative Studio → Brand Kit → Pronunciation, and Creative Studio → Video → Stage 2 "Script & voice" → Language **How to test:** 1. Open Brand Kit → Pronunciation. Add a word (your brand name) and how to say it, spelled the way it sounds — "mon-DOH-voh", capitals on the stressed part. Press "Hear it" to check it before saving, then save. 2. Open any video project for that brand and scroll to "Script & voice". The words you saved are listed there, and every recording from now on will use them. 3. In the same panel, open the Language list. Pick Korean, Hindi, Japanese, Arabic — anything your client speaks. Press "Draft a script" and the words come back written in that language, then record as usual. **Watch for:** "Hear it" needs both boxes filled before it will play. Picking a language changes what a *drafted* script is written in — lines you typed yourself are always spoken exactly as you wrote them. If you already had a script in English and switch the language, redraft it or translate the lines yourself before recording.
A video whose design called for real imagery could fail with "We could not create the artwork this video needs" — the artwork step was being cut off before it had a chance to finish. It now gets the time it actually needs, and videos that use generated footage have a source for it. **Where:** Creative Studio → Video → Build video **How to test:** Create a video whose plan calls for photography or a moving shot, then Build video. It should reach Preview with the imagery in place rather than showing the red "That video didn't come out" panel. **Watch for:** A build that still fails on artwork, or one that reaches Preview with a visibly empty frame where a picture or clip should be.
Videos about something you can picture — a sport, a place, a craft, a product — now open on a real photograph with the type animated over it, instead of falling back to type on a plain field. Alongside that, three things that made a video hard to watch are now caught before it reaches you: a photo hidden under too much shading, decorative lines drawn through the headline, and text set too small to read on a phone. **Where:** Creative Studio → Video → Build video **How to test:** Build a video for a concrete subject and watch the first few seconds. The picture should be clearly visible behind the words, nothing should cross the letters, and every line — including small labels and footers — should be readable at phone size. **Watch for:** A frame that still looks too dark to make out the photo, any line or rule crossing a headline, or a label so small you have to lean in.
Creatives used to have the business name drawn by the picture model, which meant a brand could come back blue in one take and green in the next, sometimes with a logo that does not exist. If your Brand Kit has a logo, it is now placed on the creative as your actual mark — and your colours are read off that logo, so a brand that has never filled in a palette still gets art-directed in its own colours instead of nobody's. Teasers are unaffected: if you have asked for nothing identifying in the frame, nothing identifying goes in it. **Where:** Creative Studio → Visuals. Set a primary logo in Brand Kit → Logos first. **How to test:** Add a logo to the Brand Kit, then generate two creatives from the same prompt. Both should carry the same mark, placed small, and pick up colours from it. Set the branding control to "No branding" and neither the logo nor the name should appear. **Watch for:** A logo that fills the frame instead of sitting in a corner, a mark that has been redrawn rather than reproduced, or colours that look nothing like the logo they came from.
Every video had to be silent unless you recorded a voiceover. There's now a library of 33 original tracks built into the studio — browse them by genre and mood, hear any of them before you commit, and pick one. If you don't pick, we choose one that suits what the video is doing, so a video you never think about still arrives with sound. When there's narration, the music automatically drops under the voice and lifts again between lines. **Where:** Creative Studio → Video → the Music panel under the player **How to test:** Open any built video and expand Music. Filter by a genre (Rock, Orchestral, Lo-fi, Latin…) or a mood (Motivational, Calm, Urgent…), press play on a track to audition it, then "Use this" — the preview should start playing it under the picture straight away. Export the video and the music should be in the file, faded in and out. Choose "No music" and it should stay off, including after a rebuild. **Watch for:** Music that keeps playing after you leave the panel, a track that doesn't survive an export, or music drowning out a voiceover instead of ducking under it.
The "Set up lead notifications" next step used to drop you on your submissions inbox, which has no place to enter the email addresses it was asking for. It now opens the notification settings directly, and Notifications and Analytics are both reachable from the Settings sidebar. **Where:** Site → Overview → Next steps → "Set up lead notifications" **How to test:** Open a site whose forms have no notification recipients yet. On the Overview, find the "Set up lead notifications" step and click its button. You should land on Settings → Notifications, showing "Global notification emails" — not on the Leads inbox. Check that Notifications and Analytics now appear in the Settings sidebar. **Watch for:** Landing on Settings → General instead of Notifications, the Notifications entry missing from the Settings sidebar, or the step's button still reading "Open leads".
On a site with a light background, a section designed as a dark band could lose that background and render as a blank gap — and if its text was white, the whole section became invisible. **Where:** Any generated or edited site whose theme background is light and which has a dark section (a footer, a statement band, a call-to-action panel). **How to test:** Open a site with a light theme and a dark section. The band should be dark with its text readable, in the editor preview, the published site and the gallery card. **Watch for:** The reverse — a page whose own background you set deliberately. Setting a dark page background on a light theme is still corrected, because that combination hides the page text.
Creating a visual now shows that it is working while your request is being sent, instead of an empty card. **Where:** Creative Studio → Create a visual **How to test:** Start a visual and press Generate — each take shows a "Submitting…" spinner and a placeholder where the picture will appear. **Watch for:** A take that sits on "Submitting…" for more than a minute. *Updated 11 Sep 2026:* this entry originally also described a "Your last batch is ready" bar with a Review results button, added so you could get back to a finished batch. Results now render underneath the conversation that asked for them, so on the chat path there is nothing to go back *to* — the pictures are already on screen. That bar remains only on the detailed-form path. Do not test for it on the chat path; its absence there is correct.
If a publish ever failed, Mission Control kept showing "Publishing failed — your last publish didn't go live" as your most urgent job, forever, even after the cause was fixed and you'd edited the site many times since. It now says when the attempt actually was, and steps out of the way once it's out of date. **Where:** Mission Control → Home → "Action needed", and the notice on the site hero. **How to test:** 1. Open a site whose last publish attempt failed a while ago. The card should read "Your latest changes are not live yet" (or "Your site has never gone live") and name the date of the attempt, rather than "Publishing failed". 2. It should sit below genuinely urgent items, not above them, and show no technical error text. 3. Publish and let it fail now — the card returns to "Publishing failed" with a plain-language reason and the red notice on the hero. **Watch for:** A publish that fails right now must still be loud and red. A failure only softens once it's over a week old, or once you've edited the site since the attempt — at that point the stored reason describes code your site no longer has, so it's hidden rather than quoted at you.
Connected AI assistants could build, refine and publish a whole site but had no way to give it a browser-tab title, a meta description, a social sharing image or a favicon. They can now set all four directly. **Where:** Any assistant connected to Mondovo — ask it to "set my site title to …", "use this image as my favicon", or "what's my meta description?". **How to test:** 1. Ask a connected assistant to read your site settings — it should report the current title, description, social image and favicon. 2. Ask it to set a favicon from an image link. Open SEO → Settings → Browser Icon and confirm the new icon appears there. 3. Publish, then open your site in a new tab and check the icon on the tab. **Watch for:** These settings only reach visitors after you publish — the assistant will say so rather than claiming the change is already live. A favicon given as a link is copied onto Mondovo storage, so the icon keeps working even if the original link stops.
The "Use a brief" box on the home page now takes the document itself, instead of promising a step that came later. There is a paperclip beside the box, and you can drop a PDF straight onto it — the file is enough on its own, so you do not have to describe the project as well if you would rather not. Dragging a file onto a form now works on published sites generally, not just here: any form with a file field accepts a drop, and highlights while you are over it. **Where:** The "Use a brief" tab in the home page start box, and any form with a file upload field on a published site. **How to test:** On the home page, pick "Use a brief", then drag a PDF onto the box — it should highlight as you drag over it and show the file name once dropped. Press "Build it free" without typing anything; it should carry you through to sign-up with the brief attached. Then try the paperclip icon instead of dragging. On a published site with an upload form, drag a file onto the form rather than clicking the field. **Watch for:** A file that appears attached but is not carried through, a drop that opens the file in the browser instead of attaching it, or the form refusing to submit when only a file is attached and no text typed.
Multi-step follow-ups now check that a contact still belongs to the audience before each message, and no contact can receive more than a few automated messages a day. **Where:** Leads → Journeys, on any site with an automated sequence. **How to test:** Build a journey triggered by an audience with a follow-up a few days later. A contact who leaves that audience in the meantime — because they booked, ordered, or whatever the audience was defined by — quietly drops out instead of getting the follow-up. **Watch for:** Order confirmations, booking reminders and shipping notices are never held back, whatever else has been sent. Marketing messages beyond the daily limit are skipped rather than delayed, and the reason is recorded on the message.
You can now describe a follow-up sequence to the assistant — by typing or by voice — and it builds the audience, writes the emails, and lays out the flow for you to review. **Where:** The assistant, anywhere in your site's control panel. The result lands under Leads → Journeys. **How to test:** Say or type something like "save everyone tagged catering as an audience, then email them fifteen minutes after they join, and follow up three days later". The assistant checks which tags your site actually has, saves the audience, and drafts the journey. Open it from the link it gives you to see the flow and edit the copy. **Watch for:** Journeys are always created switched **off** — nothing sends until you turn it on yourself, and the assistant cannot turn it on for you. If you ask for an audience trigger without saying which audience, it will ask rather than guess, because a journey with no audience would email everyone.
Subscriber campaigns now use a separate Resend connection for each site. The campaign screen includes account and domain setup instructions, connection checks, and a test email to your signed-in address. You can still write drafts and manage contacts before connecting. **Website notifications remain included**, within plan limits. Lead alerts and configured system messages keep their existing notification settings. Campaigns never fall back to Mondovo's notification account if a connection stops working. **Existing campaign users:** verifying a domain in Mondovo's white-label settings does not connect your own Resend account. Complete Campaign sender setup before sending. Your drafts and delivery history remain available. Provider delivery charges and limits are separate from your Mondovo plan's campaign sending limit. **For agencies:** connect the appropriate client's account and sending domain on each site. The [email guide](/help/email) explains workspaces, DNS setup, notifications, subscriber campaigns and the separate prospect-outreach flow. **Where:** Site → Leads → Inbox → Campaigns → Campaign sender, or Email notification settings → Set up campaign email **How to test:** On a site without a campaign connection, save a draft and confirm that sending prompts for setup. Connect a customer-owned Resend account with a verified sending domain, send yourself a test, then review the campaign send flow. Confirm notification settings have not changed. Disconnect the campaign sender and confirm subsequent campaign sends are blocked.
Editing a single file or a few content keys through a connected agent (MCP `update_variation_file` / `patch_variation_content`) was refused whenever the design already had an unrelated validation problem — a one-line image swap in the About section could be rejected because the Hero read a content key that had drifted months earlier. Only problems the edit itself introduces now block it; existing ones are reported back as `preexisting_issues` so the agent can see them without being stuck. Content patches are also validated against the full merged content (site content plus the design's own overrides), the same way file edits already were, instead of against the sparse override layer alone. **Where:** Any MCP / API-key connection making direct edits to a site design (Claude, Cursor, custom agents using `update_variation_file` or `patch_variation_content`) **How to test:** Pick a site whose `validate_design` reports a content-keys issue in one section. Ask a connected agent to change an image URL or headline in a different section. Before: 422 "invalid_code" / "invalid_content" listing the unrelated issue. Now: the edit lands, `list_versions` shows a new row, and the response carries `preexisting_issues`. **Watch for:** An edit that genuinely introduces a new issue (deleting a key the code reads, a file that no longer compiles) must still be refused with that issue listed — check the 422 still fires for a broken edit on the same site.
When you attached an image and asked the studio to use the words printed in it, it wrote its own headline instead — it had only been given the file's name, never the picture. It now sees the image you attached, so it can work from what is really in the frame. **Where:** Creative Studio → Visuals → attach an image in the chat and ask for a concept **How to test:** Attach a photo that has text on it, ask for the wording in the picture to be used, and check the headline and CTA it proposes on the concept card. On a phone, scroll to the bottom of the concept review and tap "Generate" and "Back" — both should respond first time. **Watch for:** A proposed headline that ignores the picture entirely; a "Generate" button that does nothing when tapped on a narrow screen; the "Back" link taking you forward instead.
The pages about your line of work now ask for the one thing they need, rather than asking you to sign up first and explain yourself afterwards. The restaurants page takes a sentence about your restaurant. The WordPress page takes your current address. The redesign page takes the address it was already asking you to imagine typing. Whatever you type carries through sign-up and lands you in the right place, with the page you came from remembered. The pricing calculator's configuration comes with you too, instead of being cleared when you click. **Where:** The home page, "Redesign a website", "Migrate from WordPress", the pricing page, and every industry and agency page under "For businesses" and "For agencies". **How to test:** Open any of those pages signed out. Type into the box in the hero and press the button — you should be asked to create an account, then land in the right workflow with what you typed already applied. On the pricing page, set the site count and tick the add-on before pressing the button. **Watch for:** Landing on a dashboard with nothing carried over, a box that accepts text but does nothing, or the wrong kind of prompt for the page you were on (an address box where a description belongs, or the reverse).
Campaigns now draw their own ad images, keep every campaign at its own web address, and build a landing page you can actually open. **Where:** Site editor → Marketing → Campaigns → open a campaign **How to test:** 1. Open Marketing → Campaigns and click a campaign. Notice the address bar now ends in `/campaigns/<id>` — copy that link, open it in a new tab, and the same campaign loads. 2. Press browser Back. It closes the campaign and returns to the list instead of leaving Marketing. 3. On the Social ads tab, each image now has a picture frame, an editable description and a **Generate image** button with its credit cost shown up front. Click it. The image appears in the slot when it is ready — you can leave the tab and come back. 4. Generate a second time. Both images are kept as thumbnails; click one to choose it. Nothing you already paid for is thrown away. 5. Edit a headline in place and watch the character counter. Try going over the limit — it refuses to save rather than letting the ad be rejected later. 6. Press **Rewrite copy**. The wording changes; your generated images stay exactly where they were. 7. At the top, if the campaign has no landing page, click **Build the landing page**. It creates a real page in your site, links it in the editor, and fills in the Final URL. **Watch for:** - An image that stays on "Drawing…" for more than a couple of minutes — refresh the page; a finished image attaches itself even if the tab was closed. - "Not enough creative credits" should offer a link to add more, not a dead end. - If a campaign was made before today, its landing page may show as a copy draft that is not a real page yet. Building it is the fix. - The Meta download is now called "Download as a worksheet" — it is copy and image links for pasting into Ads Manager, not a file Ads Manager can import. It never was.
Adding a Help Center, a job board, an events list, courses, a directory, a template library or a game catalog is now "add a collection" — you pick it in Content and it arrives with a place to put things, instead of switching on a capability that gave you an empty page. **Where:** Your site → Content → Add collection. The Features tab now lists only capabilities that actually do something on their own — cart, booking, wishlist, comparison, payments, quizzes, funnels and forms. **How to test:** 1. Open Content and click "Add collection". Directory listings, Templates and Games are now offered alongside FAQs, Jobs, Events and Courses. 2. Add one. You get the collection, its page, and the table where you fill it — with search, CSV import, bulk publish and "Generate from a brief". 3. Open Features. The eight list-shaped items are no longer offered there as things to activate. 4. If one of them is already switched on for your site, it still appears under Active — you can still manage its items or turn it off. 5. The Forms card now groups only the three lead-capture forms (quote, inquiry, booking) instead of also folding in events, jobs, courses, directory and templates. **Watch for:** Nothing already on your site changes — active features stay active and keep their content. If you previously reached one of these from the Features tab, it's now also reachable in Content alongside your other lists.
Adding contacts in bulk — a spreadsheet import, an API batch, or re-tagging a group — now updates their audiences without firing the automation triggers, so an import can't start a welcome sequence for people who have been customers for years. **Where:** Contact import, the contacts API, and bulk tagging in Leads. **How to test:** Import a batch of contacts that match an audience with a journey attached. They join the audience and appear in campaign targeting as before, but no journey starts for them. **Watch for:** Contacts added one at a time in response to a real event — a form submission, a new signup — still trigger automations normally. If you use the API and were relying on a batch import to start a journey, add `dispatch_audience_events: true` to that call.
Opening the editor on a link that points at a specific page kept snapping the address bar back to the home page, so sharing or bookmarking that link sent everyone to Home instead. **Where:** Site editor — any link that opens a named page, e.g. `?page=about` **How to test:** Open a multi-page site's editor on a link ending in `?page=<page-name>`. Leave it for a minute, then reload. The address bar should keep the page name the whole time, and the reload should reopen that same page — not Home. **Watch for:** The address showing one page while the canvas shows another; a link to the home page should still read `?page=%2F`.
The Creative Studio's create flow now lives inside the site editor under Marketing → Creative, so a site owner can make a finished social post, carousel or ad image for their site — art-directed from its brand kit — without leaving the site. It uses the same Creative Credits as the studio and the campaign image slots, and it works for people who were invited to just this site. **Where:** Site editor → Marketing (left rail) → Creative tab. Also from the command palette ("Create a social post or ad") and the assistant ("make me an Instagram post for this site"). **How to test:** Open a site with editor access → Marketing → Creative. The flow should open on the chat-style ideation step with the site named in the header and a credit balance chip. Describe a post, accept a concept, generate. Switch to Campaigns and back — the flow should still know the site. Refresh on `/mc/marketing/creative` — it should reopen on Creative. **Watch for:** A spinner that never resolves (the site context did not reach the flow); a "not found" toast on the first click for a user invited to only this site; the Creative tab being hidden behind the "Activate Site Growth" screen (it must stay reachable — there is a link on that screen); `?clientId=`/`?siteId=` lingering in the address after leaving Creative.
The screens where you manage a feature's content — help articles, job listings, events, courses, games, templates, downloads — now have the full content toolkit, and the assistant can fill them for you. **Where:** Your site → Features → open any active feature → Manage. Also under Content, where these collections now appear alongside your blog, menu and products. **How to test:** 1. Open a site with the Help Center switched on and go to Features. 2. A feature with nothing in it now reads "Not set up yet" instead of "Active", and shows how many items it has. 3. Click "Draft articles with AI" — the assistant opens with a brief ready. Send it, review the articles it proposes, uncheck any you don't want, and save the rest as drafts. 4. Open Manage on that feature. You now get search, status filters, bulk publish, CSV import, drag-to-reorder and "Generate from a brief" — the same tools the rest of your content already had. 5. Ask the assistant "what help articles do I have?" and "write three more like these" — it can now read your items before writing new ones. 6. You can also just say "turn on the job board" or "switch off the help center" and it will do it. **Watch for:** New items always save as drafts — nothing appears on your live site until you publish it. If a feature's page looked empty in the manager but had content on your published site, that content should now appear in the manager. Published items also feed your site's chat assistant, which is now noted on each collection.
Credits now cover everything that costs money to run — AI images and brand assets, the voice assistant, and keyword, mention and review data — instead of you juggling a separate pool of voice minutes. Monthly credits went up to match, and keyword tracking is available to everyone. **Where:** Dashboard → Organization → Billing for the balance and top-ups. The search data lives in your site editor under Marketing → Data. **How to test:** 1. Open Billing. The card now reads "Credits" and explains what they cover. Free plans get 50 a month, Pro gets 200 (plus 200 for each extra live site). 2. Open a live site → Marketing → Data → Keywords. There's no upgrade wall any more. Press "Full scan" — the button shows what it costs before you press it. 3. Once you have keywords tracked, press "Refresh rankings". That one is free and says so. 4. Check the Reviews and Citations tabs — same shape, each with its price on the button. 5. Start a voice session in the site builder. It draws 1 credit a minute from the same balance. **Watch for:** A scan that comes back empty should cost you nothing — the credits go straight back. Site generation, refinements, chat and publishing still never use credits. If you had bought extra voice minutes as a monthly add-on, that option is gone; credit top-up packs replace it.
Anything you can set in SEO and Settings, a connected assistant or the API can now set too — including one page's SEO, renaming a page, and moving its URL. **Where:** Any assistant connected to Mondovo, or the public API (`/api/v1/sites/:id/settings`, `/api/v1/sites/:id/pages/:slug`, `/api/v1/sites/:id/pages/:slug/seo`). The full reference is at `/api/v1/openapi.json`. **How to test:** 1. Ask a connected assistant to set the SEO title and description for a single page, then check that page in SEO → Pages. 2. Ask it to move a page's URL — for example `/services` to `/what-we-do`. Open the site and confirm the navigation and every in-page link now point at the new URL. 3. Ask it to block an AI crawler, or to set your llms.txt, then check SEO → Settings. **Watch for:** A rename rewrites links across the whole site, so use it rather than editing a page's file name — and it only reaches visitors after you publish. The homepage's URL cannot be changed. A page's own SEO title beats the site-wide default, so if a page looks unchanged after editing the site default, that page has its own title set.
Preview sites built for your prospects now carry each business's own name, phone, email and address — and a build that loses its connection no longer throws away the previews that were already made. **Where:** Growth → Campaigns → New campaign (steps 3 and 4), and Growth → Templates **How to test:** 1. Open Growth → Campaigns → New campaign, select several prospects, pick a template, and build previews. 2. On the review step, press "Review each". Step with ← and →; approve or reject and it moves to the next undecided one. Each site should show its own business name in the header and footer, its own phone number (and a working tap-to-call link), its own email and address, and its own rating and opening hours. 3. Open "Details" on one, change the phone number, and save. The preview rebuilds with the new number, and the prospect record carries it too. 4. Try it on a phone: at every step the business name should be readable on its own line, with the buttons underneath it rather than squeezing it out. 5. To check the recovery: start a build and put the phone to sleep, or switch networks mid-build. When you come back, the wizard re-checks what actually finished instead of marking everything failed — and any preview that did not build gets a "Retry" button that keeps the successful ones. Previews now also carry the business's own Google rating, review count and opening hours instead of the template's placeholder numbers, and "View site" opens them in a viewer you can step through with arrow keys — approving or rejecting as you go, without leaving the page. A Details panel there corrects the business's name, phone, email or address and lets you upload their logo; the correction is saved against the prospect (so the campaign email gets it too) and the preview rebuilds itself. Previews built before this fix have already been corrected — same links, now showing the right business — and every template's images are now hosted by us instead of hotlinked, so they cannot disappear when a stock photo is taken down. **Watch for:** - A preview still showing the template's own business name, phone or email anywhere on the page. - A prospect with no email or phone on file: their preview should show nothing in that spot, never the template's contact details. - A template that refuses to build previews — that is deliberate now. It means the template has no business-name field to swap, so every preview from it would be an identical copy. Re-save that template from a site whose business name appears in its content. - On the review step, a business you expected to be listed showing up under "can't be emailed and will be left out". - A business with no Google listing keeps the template's example rating and hours — that is deliberate, so the preview still looks finished. - A business rated below 4.0, or with very few reviews, gets a note in the viewer: their real rating is on the page, and showing it may not help the pitch. That is a judgement call left to you.
Email setup guides now open in a side panel from campaigns, notification settings, pricing and the agency guide. Close the panel to return to the same screen with your unfinished setup fields intact. The panel also links to the shareable guide. The standalone email guide now uses Mondovo's shared header and footer. Signed-in users get their dashboard navigation; visitors can read it without signing in.
Opening a concept's preview in the Creative Studio pushed the panel wider than a phone screen, so the copy fields ran off the right edge, the explanation text printed on top of them, and the "Talk to the studio" button was half cut off. The panel now stays inside the screen at every width. **Where:** Creative Studio → Visuals → Review your creative → "Preview & edit" on any concept. **How to test:** 1. On a phone (or a narrow browser window), start a visual in the Creative Studio and get to "Review your creative". 2. Tap "Preview & edit" on a concept. 3. Nothing should sit outside the screen — try swiping sideways; the page should not scroll horizontally. 4. The headline, offer, CTA and image-direction fields should all be readable, with the grey "Preview only the concept you are editing" note below the preview rather than across the fields. 5. The "Talk to the studio" button in the bottom corner should be fully visible. **Watch for:** The dark preview card is now drawn at the true shape of the ad you picked, so on a narrow screen it is a small square (or a wide strip for a landscape format) and the fine print inside it can be cut off — the same wording appears under the card. On a laptop the two-column layout is unchanged.
Two buttons in the SEO section did nothing when you pressed them — the per-issue "Fix with AI" hand-off to the assistant, and the "Suggest" button that proposes keywords for a page. Both work now, on phones as well as desktop. **Where:** Site editor → SEO → Pages (expand any page) **How to test:** Press "Suggest" next to Keywords — a row of suggested keywords appears within a few seconds, with "Add all" and "Dismiss". Then press "Fix with AI" on any issue: the AI Assistant opens with the request already written in the box. Close it and press the same button again — it opens again. On a phone, the assistant panel now stays open instead of sliding shut on its own. **Watch for:** "Suggest" spinning and stopping with nothing shown, or an error toast; the assistant panel closing by itself right after it opens; the second press of a "Fix with AI" button doing nothing.
You can now choose the small icon that appears in browser tabs, bookmarks and search results for your published site — by uploading a file, pasting an image URL, or simply asking the assistant. **Where:** SEO → Settings → Browser Icon, or Settings → SEO. In chat, say "set my favicon to <image URL>", "use my logo as the favicon", or "remove my favicon". **How to test:** 1. Open your site → SEO → Settings. Upload a square PNG, SVG or .ico under 500KB (32×32 or 64×64 is ideal), or click the link icon and paste an image URL. 2. Check the light and dark previews next to the field — a dark icon that vanishes on a dark tab bar is the usual surprise. 3. Publish the site, then open it in a new tab and confirm the icon shows on the tab. 4. Ask the assistant "use my logo as the favicon" and confirm the Browser Icon card updates. **Watch for:** The favicon only reaches visitors after you publish. If you uploaded a logo and favicon before your site was first built, that favicon now carries through to the published site automatically — the card labels it "Inherited from your brand kit", and uploading here overrides it. Removing the favicon clears it for good rather than falling back to the brand kit one.
Creative visuals now design the words into the picture properly, let you say how many you want, and let you decide whether the brand appears at all. **What changed** - **Text is designed, not dropped on.** The brief now says how the copy should be *set* — the typeface register, the hierarchy, where it sits and how it catches the light in the scene. Headlines used to come back in flat default type placed in whatever space was free, which read like a caption pasted over a photo. - **Your brand name is now a choice.** It used to be added to every visual automatically, so asking for an unbranded teaser still produced one with the name on it. You can now ask for no branding at all, the name set as type, or your actual logo placed like a logo. - **Logos work as logos.** Attaching a logo previously treated it as the product, so it came back filling the frame. There is now a Logo option in the reference picker, and your brand's logo is offered first. - **Ask for more than one.** Asking the studio for several versions of an idea now produces that many, up to four. It quietly made one before. - **"More like this" can change the type.** Previously every re-roll only moved the camera or the light, so a visual you disliked for its lettering came back with the same lettering. **Where:** Creative → your brand → Visuals **How to test:** Ask the studio for a teaser and add "no branding, no logo, no name" — the finished image should carry none. Then ask for "four versions" of an idea and confirm you get four. Open Edit on a finished take and use More like this a couple of times; at least one should come back with a different typographic treatment. **Watch for:** A visual that still shows the business name when you asked for none; a request for several versions that returns one; type that sits in the frame without relating to the light in the photograph.
The Marketing Hub's "Activate Site Growth" button used to send you to billing with nothing there to buy — Site Growth is now included with every live site on a Pro workspace, at no extra cost. **Where:** Site editor → Marketing (left rail) **How to test:** Open a published site on a Pro workspace and click Marketing. The hub should load directly instead of showing the activation screen. On a Free workspace the activation screen still shows, and its button now lands on your workspace's billing page. **Watch for:** A full marketing scan should return a complete set of directories, communities, ideas and calendar entries. If it errors with a message about not being able to read the scan results, or comes back with far fewer items than expected, flag it — that means the scan is being cut short.
On a site you've already started building, asking the AI assistant for "another design option" used to run a full design generation and report success — but a built site shows only the one design you chose, so the new one never appeared anywhere. The assistant now says so up front and offers to restyle your current design instead. **Where:** Site editor → AI assistant panel (and the dashboard assistant), on any site you have already started building **How to test:** Open a built site, ask the assistant for "a new design variation" or "another design option". It should explain that the site is already built from one chosen design and offer to change that design instead — with no generation started and no "Generated new design variation" message. On a site still in design selection, the same request should still generate a new option as before. **Watch for:** The request being accepted silently and nothing changing on screen; or the request being refused on a site that is still choosing between designs (it should work there).
On a phone, the small dark preview beside your headline and CTA was too narrow to show them — the call-to-action was cut off below the card, so you were approving copy you could not see. It now takes the width of the column, with the explanation moving underneath. **Where:** Creative Studio → Visuals → describe your creative → Review creative **How to test:** Open the review step on a phone (or a browser window narrowed to 360px). The dark "Native text" card should show the headline and the CTA pill in full, with the caption below it rather than squeezed alongside. On a desktop window it looks exactly as before. **Watch for:** The card should never cut a word in half, and the CTA pill should always be visible. On very wide ad shapes (1.91:1 link ads) the desktop card is still short — that is tracked separately.
Pages added from another tab, a connected assistant, or a background job now show up without you having to guess, and large sites list their pages in folders instead of one long scroll. **Where:** Site editor → Pages (the left page list), and the strip at the top of the editor. **How to test:** 1. Open a site with more than a dozen pages in the editor. Page families that share a path — `/for/restaurants`, `/for/law-firms`, and so on — now appear as a single "For" folder with a count beside it. Click it to expand. 2. Type in the page search box. Matching pages appear even when their folder is closed, and searching by URL (`/vs`) works as well as searching by name. 3. Open the same site in a second tab. In one tab, change a page and save. Within a minute the other tab shows "This site was changed somewhere else" with a Reload button. Click Reload and the new pages appear. **Watch for:** The banner should never appear because of your own edits — if you save in a tab and that same tab shows the banner, that's wrong. It should also stay away while a site build is running, since the site is expected to change continuously then. Expanding a folder should not change which page is selected in the preview.
Publishing a large site could show a full progress bar with every step ticked while the dialog still said it was running — so a healthy deploy looked identical to a stuck one. **Where:** Site editor → Publish **How to test:** Publish a site with many pages and watch the dialog through to the end. The bar should climb steadily, pause near the end on "Your site is live — finishing up", and only then switch to the success screen. **Watch for:** A bar that goes backwards, or one that sits at 100% while the dialog still says "still running".
A site now holds one contact per email address, and the address is compared without regard to capitals — so `Ann@Example.com` and `ann@example.com` are recognised as the same person instead of becoming two records. **Where:** Any site's Contacts list, and the contact import at /developers. **How to test:** 1. Add a contact by hand with a capitalised address, e.g. `Ann.Smith@Example.com`. 2. Submit one of the site's forms using the same address in lower case, then check Contacts — it should be the same record with one entry, not two. 3. Import a batch containing that address in a third spelling of capitals; the response should count it as updated, not created. 4. Run the same import twice at the same time from two terminals — both should finish, with no duplicate appearing. **Watch for:** Adding a contact whose address already exists still reports that clearly rather than failing. Deleting a contact and adding them again later should work — the rule only applies to contacts that are currently live. Contacts matched by phone number are deliberately not covered, since people share phone numbers.
If you pasted a long description of your business and also chose a style, the description could quietly win and your chosen style was ignored — the designs came back looking nothing like the style you picked, with no indication anything had been overridden. **Where:** Site editor → new site → paste a description, then choose a style before generating. **How to test:** Write a description that mentions a look ("warm, soft colours, serif headings"), then pick a style that contradicts it (a dark editorial one). Generate. The designs should follow the style you picked, while every fact, service and section from your description still appears. **Watch for:** The reverse failure — a chosen style that flattens the content, or a description whose non-visual details (prices, service names, audience) stop coming through. Those should be untouched; only wording about appearance is set aside.
Tell us what you want before you have an account, and it now follows you through sign-up into the right workflow instead of being dropped at the registration form. Two things changed. A pasted website address is treated as "redesign this" rather than as a description, so it starts the redesign flow — we read the existing site, then design new versions of it. And whatever you had picked or typed — an address, an idea, a design from the gallery, a ready-made business, a trade setup — is now remembered the same way, so it survives creating an account, signing in, and signing in with Google. Some of those were previously only remembered on one of those routes. **Where:** The prompt box on the home page, the "Redesign a website" page, the design gallery, and the ready-made businesses strip. **How to test:** Signed out, paste a website address into the home page prompt box and press Generate — you should be asked to create an account, and land in the redesign flow for that address afterwards. Repeat, but sign in to an existing account instead of registering, and again with "Continue with Google". Then try the same three routes after picking a design in the gallery, and after picking a ready-made business. **Watch for:** Landing on the dashboard with nothing carried over — that is the failure this fixes. Also watch for a redesign that starts against the wrong address, or being asked to re-enter something you already typed.
When you picked a wide format — a link/Facebook-feed ad or a 16:9 landscape one — the copy preview card was too short for the words in it, so the headline was cut off at the bottom and the button disappeared completely. The card now grows to fit your copy whenever the ad's shape would hide it, and keeps the true shape everywhere it fits. **Where:** Brand Studio → Create → after "Review creative", the dark "Native text" card next to your headline, offer and button fields. **How to test:** In Create, choose the link (1.91:1) or landscape (16:9) output format, write a headline and a button label, then go to Review. All three lines — headline, offer, button — should be visible inside the dark card, on a laptop as well as a phone. Switch the format to square, 4:5, 2:3 or 9:16 and the card should keep exactly the same shape it always had. **Watch for:** Copy cut off at the bottom edge of the dark card; a missing button pill; a square format that no longer looks square.
Generating from the Creative Studio chat keeps you in the thread — the pictures render underneath the conversation that asked for them, with the prompt box still on screen, so you can react to what you got without navigating anywhere. Results used to open on a separate screen, which meant a finished creative was always somewhere you were not. Two things existed only to work around that: the Ideate / Refine / Results chips, and a "Your last batch is ready" bar. Both are gone from the chat, because what they were routing you around no longer happens. Also simpler on the way in: the tall "Choose the deliverable" card is now a slim row above the composer on the chat path, keeping every choice it could make — format, how many outputs, and a carousel's slide count — while dropping a screenful of chrome on a phone. The quality picker has been removed; it asked you to choose between options you had no way to judge. Regenerate is unchanged, and re-asking is still free. The detailed form is unchanged: choosing the deliverable is the task there, so it keeps the full card and its own results step. **Where:** Creative Studio → your brand → Visuals **How to test:** Describe a visual in the chat, accept a concept and generate. The finished picture should appear in the thread with the prompt box still reachable. There should be no stage chips and no "last batch is ready" bar on this path. **Watch for:** Results opening on a separate screen; stage chips or a "last batch is ready" bar returning to the chat; a carousel becoming unreachable because the format row is missing.
Form submissions, leads and store purchases now report as conversions in Google Analytics — previously the goals existed but nothing was ever sent to them, so every site's conversion count read zero. **Where:** Site editor → Analytics, and your GA4 property under Reports → Engagement → Conversions **How to test:** Publish a site with analytics enabled, submit one of its forms from the live URL (not the editor preview), then check GA4 Realtime for a `form_submission` event. Contact forms also send `lead`; a completed store checkout sends `purchase` with the order value. **Watch for:** Nothing is sent from the editor preview — that is deliberate, so testing your own form does not inflate your numbers. Events can take a few minutes to leave Realtime and reach the standard reports.
On a phone, Mission Control's home now opens with a short list of what is waiting on you, and the header keeps a labelled Publish button at every screen size instead of a bare icon. **Where:** Any site → Mission Control home and header, on a phone or a browser window narrower than 768px. **How to test:** Open a site on a phone. If there are unread messages, orders to fulfil, unpublished changes or a failed publish, the home starts with up to three tappable rows saying so; tap one and you land where the matching card below would take you. With nothing waiting, no list appears. In the header, Publish reads "Publish" (or "Publishing") at every width; when there are unpublished changes the header shows Preview draft, otherwise View live, and every header button is at least 40px tall. Widen past 768px: the header shows every button with its full label and the attention list disappears. **Watch for:** The attention list showing on a laptop, an attention row and the card below it disagreeing on where they go, Publish missing from the phone header, the header wrapping onto two lines at 375px, or the home cards sitting 24px lower than before on a laptop.
The floating chat button in the phone editor is now a full bar: a big mic to talk, an "Ask" field, your chat history — and, when you point at something, that element's name plus one-tap actions for it. **Where:** Site editor on a phone — `/client/{clientId}/site/new?siteId={siteId}` at a phone width (or a real phone). **How to test:** 1. Open a site in the editor on a phone. The bar sits across the bottom, above the site, with the mic on the left. 2. Tap the "Ask, or press and hold anything" field: the chat opens with the keyboard already up and the cursor in the message box. 3. Close the chat and tap the chat icon on the right instead: the chat opens to your history, with no keyboard. 4. Tap the mic: your voice session starts and the mic turns red with a pulse. Tap it again to stop. 5. Press and hold a heading in the preview. The bar grows a row above it: the element's name with an ×, then Edit text, Move up, Move down and Delete. Tap "Edit text" and type straight onto the page. 6. Press and hold a photo instead: the row offers "Replace photo", which opens the picker. 7. Tap the × on the name chip: the row disappears and the outline in the site clears. 8. Scroll the site: the bar folds down to just the mic so you can read, and comes back a moment after you stop. 9. First time on a phone, a small tip appears above the bar — "Press and hold anything to point at it" — and goes away after a few seconds or when you tap it. It does not come back. **Watch for:** the bar covering the bottom of the site instead of sitting below it; the keyboard covering the message box after tapping the Ask field; action buttons that do nothing, or that act on the wrong element; the bar staying folded after you stop scrolling; the tip reappearing on later visits; anything at all changing on a laptop.
Closing the publish window no longer hides a running publish, reopening it picks up where it left off, and a custom domain is only described as connected once it actually verifies. **Where:** Site editor → Publish, and the site's Home screen **How to test:** 1. Publish a site, then click "Close & Continue Working" while it is still running. The header button should read "Publishing..." with a spinner until it finishes, and you should get a confirmation the moment it goes live. 2. Reopen the publish window mid-publish. It should show the publish already in progress — not a fresh form with another Publish button — and show the success screen when it lands. 3. Watch the progress bar on a larger site. It should only ever move forward, even while the site is being published in batches. 4. On a site whose custom domain has been added but not yet verified, the Home screen should say the domain is pending and point you at the DNS steps, and the "view your site" link should use the hosted address rather than the unverified domain. 5. Try adding one of our own hosting addresses as your custom domain. It should be refused with an explanation instead of accepted and left pending forever. **Watch for:** A progress bar that jumps backwards; a success screen appearing for a publish that failed; the Home screen claiming a domain is connected while DNS is still pending.
Sections that let visitors save or shortlist items could be replaced by a red "couldn't be displayed here" panel in the editor — not because anything was deleted, but because the browser's storage for the app was full and the section's attempt to remember an anonymous visitor went unhandled. Published sites were more exposed still: without the editor's per-section safety net, the same problem could blank a whole page. **Where:** Site editor → any design containing a save/shortlist, cart, customer-portal or funnel section; also published sites. **How to test:** Open a design with a "save"/wishlist section. Fill the browser's storage for the site (DevTools → Application → Local Storage, or write large values until a write is rejected), then reload the editor. Every section should still render, with no red isolation panel and no console errors. **Watch for:** A section showing the red "couldn't be displayed here" panel with nothing wrong in the content; saved items, cart contents or a currency choice failing to persist between reloads on a browser with private mode or blocked storage — those should now degrade quietly for the session instead of interrupting the page.
When publishing was interrupted by a temporary storage problem, we told you a page could not be prepared and asked you to run auto-fix on it — advice for a problem you did not have. Publishing now tells you what actually happened, confirms your live site was left untouched, and it retries harder before giving up at all. **Where:** Site editor → Publish (the banner on Mission Control after a failed publish) **How to test:** Publish a site. On success nothing changes. If a publish does fail on the storage step, the banner reads "Publishing was interrupted by a temporary storage issue, so nothing on your live site changed. Please try publishing again." and offers a retry, instead of naming a page and pointing at auto-fix. **Watch for:** A genuine page-render failure must still say which page failed and still point at auto-fix — that path is unchanged.
Creating a page that relies on your business details — a privacy policy, terms, or contact page — no longer fails with a technical message, and when a required detail genuinely isn't on file the builder asks you for it. **Where:** Site editor → Publish dialog → "Create Privacy Policy page", and Pages → Add page **How to test:** Open a site, start publishing, and use the "Create Privacy Policy page" suggestion. The page generates using your saved business name, location and contact details. If something essential is missing (a postal address, for example), a short question appears — answer it and generation continues with your answer. **Watch for:** A page created this way should state your real business name and contact details, never invented ones; the questions asked should be answerable in one line each, and should not repeat details you have already saved.
Swapping in a new section layout could produce a card — a booking bar, a stats strip — that was meant to overlap the section below it but was sliced across the middle instead. The editor now catches that before you have to spot it, and the layout swap no longer builds it that way. **Where:** Site editor → open a design → pick a section → Swap layout. Also the Issues panel on any design. **How to test:** Open a design whose hero has a bar or card straddling its bottom edge. Confirm the whole card is visible and the next section starts below it. If a design already has the broken version, the Issues panel lists "Overhanging element is cut in half by its section" with a one-click fix. **Watch for:** A decorative glow or blur in a section corner being reported as an issue — those are supposed to be trimmed by the section edge and should not appear in the list.
Opening Content Manager on a page whose content was already connected could re-run a sync that replaced the page's copy with newly written text — this now leaves such pages alone. **Where:** Site editor → open any page → Content Manager **How to test:** Open a page whose text you have already edited or hand-written, then open Content Manager. It should open without a "Syncing CMS content…" step, and the page should look exactly the same afterwards — same headings, same body copy, same sections. Close the modal and refresh; nothing should change. **Watch for:** A page going blank or showing empty sections right after the modal closes; a page coming back with generic marketing copy in place of your own wording; text you deleted earlier reappearing. Pages that genuinely still have text locked in the layout should still offer the sync and still work.
The list screens that used to squash five to seven columns into a phone screen now show a readable card per row, with the actions always tappable instead of hidden behind a hover. **Where:** Site editor left rail → Customers, Engagement, Functions (Logs tab); and the Journeys and WhatsApp Templates pages. **How to test:** Open each screen on a phone (or a browser window narrower than 768px). Every row should read as a card — name and status first, details underneath — with buttons big enough for a thumb. Widen the window past 768px and the original table comes back unchanged, including sorting and row clicks. **Watch for:** A row that opens the wrong record, a delete or pause button that does nothing on touch, text cut off mid-word with no way to see the rest, or the page scrolling sideways.
If the domain you're connecting is already serving a website, its DNS hosts are already taken — and your DNS provider rejects a second record on the same host. The routing step now says so up front and tells you to edit the existing record instead of adding a new one. **Where:** Site editor → Publish → custom domain setup → step 2, "Add DNS Records (Routing)" **How to test:** 1. Connect a custom domain that is currently pointing somewhere else (a live site, a parked page, an old host). 2. Open the DNS setup steps and let the automatic DNS check finish. 3. Above the records table you should see which hosts are already occupied, with the instruction to edit rather than add. 4. The affected row should be highlighted and show what that host currently points at. 5. Connect a domain with no existing records — the warning should not appear at all. **Watch for:** The warning showing up for a host that is already pointing at us correctly, or for a host that simply has no record yet. Neither is a conflict and neither should be flagged.
Asking the AI to change something on an inner page — by voice or by typing — could come back with "that section exists in the code but isn't on the page right now" and change nothing. The request is now applied. **Where:** Site editor → open any page other than the homepage → describe a change in the chat panel (or use voice). **How to test:** Open a page such as About, Contact or Privacy Policy, ask for a wording or layout change, and confirm the change appears in the preview rather than an amber "isn't on the page" message. Repeat with voice mode. **Watch for:** The same message still appearing on a page edit; a change that reports success but leaves the preview untouched; or the message disappearing on a section that genuinely was removed from the page, where it is still the correct answer.
A page that uses a platform feature — a help center, a cart, a booking widget — could lose its entire body and still look fine to the system: header and footer rendered, nothing in between, no error anywhere. **Where:** Site editor → any page built on a platform component (Help Center is the common one), and the published version of it. **How to test:** Open a Help Center page in the editor. The search box, category list and articles should all render, with the site's own help articles listed. Add an article in Collections and it should appear on the page. **Watch for:** A page that renders only its header and footer; a component that appears as an empty box where a list or search box belongs; a collection-backed listing page reporting that its content is missing when the items live in Collections.
You can now bring an existing customer list into a site's CRM from a spreadsheet or another system — names, phone numbers, tags and any extra columns you keep — instead of adding people one at a time. **Where:** Dashboard → Settings → API Keys to create a key, then the CRM section at /developers. From an AI assistant, connect Mondovo and approve the new contacts permission. **How to test:** 1. Create an API key and tick the new contacts permissions (existing keys do not have them — create a new key or the CRM endpoints will return a permission error). 2. Post a batch of contacts with tags and a few made-up extra columns, sending `dry_run: true` first to see what would change. 3. Repeat the same request without the dry run, then open the site's Contacts list: the people are there, tagged, with the extra columns showing as fields you can filter on. 4. Send the same batch again — the counts should show updates, not duplicates. 5. From a connected assistant, ask it to list contacts tagged from the import and add a tag to them. **Watch for:** Re-importing should never duplicate someone who is already there, and should never remove tags you added by hand — tags merge unless you explicitly ask to replace them. An import will not move an existing contact along your pipeline, and the response says how many stage changes it skipped. Nothing here deletes a contact.
Eight small fixes for anyone running their site from a phone: the Assistant button no longer covers the bottom navigation, Search is in the bottom bar's More menu, notifications open as a sheet instead of running off the screen, pinch-to-zoom works again, one tap opens a content item's editor, row actions are always visible on touch, and the dashboard always shows the grid on a phone. **Where:** Any site's Mission Control on a phone, the sites dashboard, the Content view, and the design editor's chat box. **How to test:** On a phone (or a browser narrowed to about 375px): open a site. The blue Assistant button sits above the bottom bar, not on it. Tap More in the bottom bar → Search opens full screen with a Close button. Tap the bell: notifications slide up from the bottom with nothing cut off on the left. Pinch to zoom the page. Go to Content and tap an item's title: the full editor opens; tap the pencil beside it to rename. On the sites dashboard, with "list" view chosen on a laptop, the phone still shows the grid, and switching back to the laptop shows list again. Tap into the editor's chat box or the assistant: the page should not zoom in. **Watch for:** The More menu being clipped by the bottom bar, the Assistant button hidden behind the bar on tablets between 768px and 1024px, the notifications sheet leaving a gap above the home indicator, a laptop user finding their list preference reset, or a desktop user seeing a Search item in the rail's More menu.
Everything that identifies a page is in one place, reachable from the page you are looking at: its name, its URL, and how it appears in search. **Where:** Site editor → the structure panel on the left → the settings icon beside the page name. **How to test:** Open any page in the editor and click the settings icon next to the page name in the structure panel. Change the URL and save — links to the old address are updated across the site. Set a page title and description; the search preview updates as you type. **Watch for:** The URL field being editable on the home page (it should be fixed at the site root), a rename that leaves links pointing at the old address, or the search preview showing a domain that isn't yours.
If your bank asks you to confirm a recurring payment, the alert now appears in your site workspace — not only on the main dashboard — and the publish window says up front which card will be charged and when. **Where:** Site editor (any screen), and Site editor → Publish **How to test:** 1. Publish a second site on a workspace that already has a card. The publish window should say the charge goes to the card on your subscription, prorated now and monthly after, and that a bank confirmation step will appear in the window if one is needed. 2. Publish on a workspace with no card. It should say card details come next, in the same window, and mention the possible bank confirmation. 3. If a renewal is waiting on a bank confirmation, the alert with the "confirm payment" link should now be visible while you are working on your site, not only on the dashboard. **Watch for:** A charge appearing without the publish window having said it was coming; a payment-confirmation alert that only shows on the dashboard.
On a phone you can now press and hold any part of your site to point at it, then just say what you want changed — no fiddly edit mode, no zooming in to hit a tiny target. **Where:** Site editor on a phone — `/client/{clientId}/site/new?siteId={siteId}` at a phone width (or a real phone). **How to test:** 1. Open a site in the editor on a phone (or a phone-sized browser window with touch emulation on). 2. Press and hold a heading in the preview for about half a second. It gets a blue outline and the phone gives a short buzz. 3. The heading now shows as the selected element in the chat, exactly as clicking it does on a laptop — ask for a change and it applies to that element. 4. Tap somewhere else in the preview: the outline and the selection clear. 5. Press and hold a link or a button: it gets pointed at, and the site does **not** navigate away. 6. Start a press and then scroll: nothing gets selected — scrolling still scrolls. **Watch for:** a hold that selects the wrong thing (a big wrapper instead of the text you held); a hold on a link that still navigates; the outline sticking around after you tap elsewhere; anything changing on a laptop — a mouse click should behave exactly as before, with no outline or buzz.
The publish window now reports what is actually happening on the server instead of a frozen progress bar, and finishing a publish shows a single success screen that tells you how to finish connecting your domain. **Where:** Site editor → Publish **How to test:** 1. Open a site in the editor and click Publish. 2. While it runs, watch the progress panel — the step descriptions should change as the site is rendered and uploaded ("Uploaded 12 of 38 pages"), the bar should keep moving, and an elapsed timer should count up under the heading. 3. If your plan asks you to confirm the monthly charge, note that the window says "Starting Your Publish / Checking everything over" before that prompt appears — it no longer shows completed steps for work that hasn't started. 4. When the publish lands, exactly one success screen should appear. 5. On a site with a custom domain that isn't verified yet, that success screen should name the domain and open the DNS setup steps for it. **Watch for:** A progress bar that sits at the same percentage for more than about fifteen seconds; two success dialogs stacked on top of each other; a success screen that only offers a generic "Connect a custom domain" row when a domain is already claimed.
The publish button now re-checks the terms at the moment you click it, a domain is only claimed once the publish is actually accepted, and the "What's Next" links on the success screen go where they say. **Where:** Site editor → Publish, and Mission Control → Home **How to test:** Open Publish on a site whose plan includes a live site and confirm the button reads "included in your plan". In a second tab, publish a different site so the included slot is taken, then click Publish in the first tab — you should be asked to confirm the $20/month charge rather than being charged silently. Separately: enter a custom domain, click Publish, then close the card/price step — the domain should NOT be attached to the site. Publish successfully and click "Add more pages" on the success screen; it should open Pages. **Watch for:** A publish that charges without asking, a domain that stays attached after you back out, a success-screen link that does nothing, or a republish that quotes a monthly price it will not charge.
Pages now read as "For Agencies" rather than "ForAgencies" everywhere you edit them, and a newly created page starts with a proper title, description and social share image instead of placeholders that immediately show up as SEO problems. **Where:** Site editor → structure panel → page settings; and any newly added page. **How to test:** Open page settings on a page whose name runs words together — it should show spaces. Rename it and save; the URL updates and links follow. Then add a new page and open its settings: the title and description should be written for that page, and the social share image should default to your site's. **Watch for:** A page name saved with spaces in it (the stored file name should stay one word), or a new page whose SEO report still flags a missing title or description.
Reloading the site editor on an inner page could send you back to the homepage and rewrite the address bar, losing your place. **Where:** Site editor → open any page other than the homepage → reload the browser **How to test:** Open a page such as /for-agencies or /client-delivery in the editor and reload. The address should still name that page, and the canvas should open on it. Do the same from a link someone shared to a specific page. **Watch for:** The address changing to end in `page=%2F` on reload; the editor opening the homepage instead of the page you asked for; the page shown not matching the address.
The SEO audit was measuring only a tiny fraction of a site's text, so pages packed with content were reported as "Very thin content (10 words)" — and on phones, notifications could appear as blank cards. **Where:** Site editor → SEO → Pages, and SEO → Overview **How to test:** Open a site with plenty of copy and check the SEO audit — the thin-content warning should be gone and the word count should reflect the real page text. On a phone, tap "Fix with AI" on any issue and confirm you get one readable notification instead of an empty card. **Watch for:** A thin-content warning on a site that genuinely has substantial text, or a notification that shows up blank.
The beta notice is gone from the create-account form, and the panel beside it now walks through the real product story — one brief in, three complete designs out, a white-label client review, then publish. **Where:** app.mondovo.com/auth/register (also linked from Sign in → "Create account") **How to test:** Open the register page in a logged-out browser. Confirm the amber beta notice no longer appears above the Google button. Watch the right-hand panel cycle through its three steps, or click the progress bars to jump between them. Narrow the window below 1024px and confirm the same panel appears under the form. **Watch for:** A panel that jumps in height between steps, unreadable text on the dark background, or a step that shows an empty illustration area.
Every site card was storing its preview image squashed to a narrow strip, and nothing refreshed it when you published — so cards looked blurry and could still show an older design. Previews are now stored at full width and are recaptured the moment a site goes live. **Where:** My Sites (dashboard) — the preview image on each site card. **How to test:** Publish a site, wait about a minute, then reload My Sites. The card should show the design you just published, and the image should look crisp rather than soft — especially on a phone. **Watch for:** A card that still shows an older design more than a couple of minutes after publishing, or a preview that goes blank instead of updating.
Clicking **Activate Site Growth** in a site's Marketing tab used to dump you back on your dashboard with no explanation. It now opens your workspace's billing page on the plans section, where you can actually turn Site Growth on. **Where:** Site editor → Marketing (left rail) → "Activate Site Growth" **How to test:** Open a site whose Site Growth is not active, go to Marketing, and click the "Activate Site Growth" button. You should land on Billing & Subscription for that site's workspace, scrolled to the plans. The "Billing" item in the site header's account menu, and the "clients list" link in organization settings, were going nowhere for the same reason and now land correctly too. **Watch for:** Any button or menu item that silently returns you to the dashboard instead of the page it names — that is the same failure and worth reporting.
Opening the app while signed in used to land you on a marketing page you'd already read. It now goes directly to your dashboard, and visitors who aren't signed in are sent to the main website instead. **Where:** The app's home address, and the installed app icon if you added it to your home screen. **How to test:** 1. Signed in, open the app's home address — you should arrive at your dashboard. 2. Sign out and open it again — you should land on the public website. 3. Sign back in and confirm the home address takes you to the dashboard again on the very same browser. 4. Check that the sign-in and sign-up pages still open normally. **Watch for:** A browser that keeps sending you to the public website even after signing in. That would mean the redirect was cached when it should never be — tell us which browser, and whether a private window behaves differently.
Typing a request to the assistant on a phone no longer hides the box you are typing into — the chat panel resizes to the space the keyboard leaves and sits just above it. **Where:** On a phone, open a site in the editor (Home → your site → Edit design) and tap the assistant bubble. Also the Assistant panel in Mission Control (the blue bubble at the bottom right of any site page). **How to test:** 1. On an iPhone (Safari) and an Android phone (Chrome), open the site editor and tap the assistant bubble. 2. Tap into the message box. The keyboard should slide up and the whole chat panel — message box included — should sit directly on top of it, with the last message still readable. 3. Type a couple of lines, send, and dismiss the keyboard. The panel should return to its previous size and the site preview behind it should be visible again. 4. Cycle the panel's size control (small / medium / near full screen) with the keyboard both up and down. 5. Repeat in Mission Control: tap the assistant bubble, then tap into its message box. **Watch for:** a message box still hidden behind the keyboard; a gap of blank space between the panel and the keyboard; the panel jumping or flickering as the keyboard opens; the site preview being trimmed by the wrong amount after the keyboard closes; rotating the phone while the keyboard is open.
Submissions and chat conversations now fit a phone screen: the list becomes cards you can tap, opening one fills the screen with a Back button, and the record you have open survives a refresh. **Where:** Any site → Leads → Inbox (Submissions and Conversations tabs). **How to test:** On a phone (or a browser narrowed to about 375px): open a site and go to Leads → Inbox. Swipe the tab strip sideways — all six tabs are reachable. Each submission is a card showing the name, email, where it came from, when it arrived and its status, with a checkbox and an Open button that need no hovering. Tap Open (or the card): the details fill the screen with "Back to submissions" at the top; tap Back and you return to the list with nothing lost. Refresh while a submission is open — the same one re-opens. Do the same on the Conversations tab: tap a visitor, read the thread, tap "Back to conversations". On a laptop nothing moves: the table, the column picker, bulk actions, search, filters and paging are exactly where they were, with the detail pane beside the list. **Watch for:** A submission's checkbox selecting the row instead of opening it (or the reverse), bulk actions losing their selection when you open a record, the "Back" header appearing on a laptop, an open record not re-opening after a refresh, or the conversation list losing its 320px width on a wide screen.
On pages that render one item per row — an FAQ, a property, a menu item — the "Editing:" chip that chooses which item you are looking at sat underneath the left structure panel, so the chip was clipped and the list it opens was almost entirely hidden. **Where:** Site editor → open a template page (its address contains `[slug]`, e.g. `/faqs/[slug]`) → the chip at the top-left of the canvas. **How to test:** Open a template page with the structure panel expanded. The "Editing: …" chip should sit clear of the panel's right edge, and clicking it should open the full item list with nothing covered. Collapse the panel to the icon strip — the chip should slide left and stay clear. **Watch for:** The chip overlapping the panel when the panel is floating (not docked) rather than sitting beside it, or the chip failing to move when the panel is collapsed or expanded.
The intake form used to end with "Anything to AVOID?" — a checklist of industry clichés, generic stock photos, long paragraphs, corporate jargon and heavy animation. Those are things we already avoid on every site, so the question is gone and the form is one step shorter. **Where:** Site Builder → the questions shown when you start a new site **How to test:** Start a new site with a short description. Work through the intake questions — none of them asks what to avoid. If you had a form open from before, reload it: the question disappears there too. **Watch for:** The form should not get shorter overall — the freed slot is filled by a more useful question (what the site must include, or what visitors should do). If you tell us in chat that you want something left out ("no carousels on mobile"), that still reaches the design as a hard rule.
Switching pages in the editor left the left-hand section list showing the page you just came from until the new one finished loading. **Where:** Site editor → left "Structure" rail → switch to a different page **How to test:** Open a page, then switch to another one. While the canvas is still compiling, the rail should show "Reading page…" rather than the previous page's section names, then fill in with the new page's sections. **Watch for:** Section names in the rail that don't belong to the page named above them; clicking a rail row scrolling to the wrong place.
You can now make a draft of any page, change it as much as you like, compare it side by side with what's there, and swap it in only when you're happy — your real page keeps working the whole time. **Where:** Open any page in the editor — either the Pages view or the design canvas. Above the preview you'll see **Current** and a **Try a new version** button. Drafts you make appear next to Current as named tabs. **How to test:** 1. Open a page and click **Try a new version**. A draft appears and opens. 2. Ask for a change in chat — including a change to the wording. A banner under the tabs confirms you're editing a draft, and the change lands on the copy. 3. Click **Current** and confirm the page still has its original layout *and* its original words. 4. Name the draft something useful with **Rename**, or make a second one to compare two directions. 5. Click **Use this version**. The page becomes the draft. By default the version it replaced is kept as a draft called "Previous version" so you can put it back in one click — untick that if you don't want it. 6. Undo also works from the page's own history — swapping is one ordinary entry there. **Watch for:** - A draft is a snapshot. If you edit the real page after making a draft, the draft won't have those edits. - Some page text is shared across your whole site — your menu, your footer, and anything drawn from your content library. Changing those from a draft changes them everywhere, because they don't belong to one page. - Occasionally we'll say we can't make a draft of a page. That means we couldn't work out how to give the copy its own text safely, and we'd rather refuse than hand you a draft that quietly edits your live page. - In the design editor you may be looking at a design your site hasn't been switched to. Drafts belong to the design they were made in, and when you swap one in we'll tell you which design you just changed and whether visitors will see it. - Drafts aren't available for your home page yet. Its sections are shared with the rest of your site, so a copy couldn't be kept separate from the live one — the editor says so where the button would be. - You can keep four drafts per page.
The publish window now shows the monthly price, what your plan covers, and whether you'll need to add a card — all on the form, before you commit — instead of asking you to confirm and click Publish a second time. **Where:** Site editor → Publish **How to test:** 1. Open Publish on a site that isn't live yet. If a charge applies you should see it stated on the form, and the button should name it — "Publish — $20/month" or "Publish — included in your plan". 2. Click it once. It should publish; you should not be asked to confirm the price again. 3. On a workspace with no card, the form should warn you that card entry is coming, then take the card in the same window and continue publishing automatically once payment goes through. 4. Close the card step midway. You should be told publishing was cancelled and nothing changed, rather than being dropped back on the form with no explanation. 5. On the screen after a successful publish, the "What's Next" items should actually open the right section, and a pending custom domain should appear in your action list on the Home screen until it's verified. **Watch for:** Being asked to confirm billing twice; a publish that changes your project name even though you cancelled; "What's Next" rows that do nothing when clicked.
When the assistant checks its own edit and decides it would not have made the difference you asked for, it now explains that in plain language instead of showing a technical note labelled as an error. **Where:** Site editor → open a design → select a section → ask for a visual change **How to test:** Ask for something the assistant is likely to get wrong on the first try, such as making several pictures in one section the same size. If it holds the change back, the message should speak to you directly, describe what it tried in terms of what you can see on the page, and suggest what to say next — with no class names, pixel values or references to "the user". **Watch for:** A held-back change described as an "Error", wording that names code, or a message that says what went wrong without saying what to try instead.
Clicking the editor canvas could select something you couldn't see — most often a tall narrow rectangle spanning parts of the page that had nothing to do with each other. Clicks now land on the thing under your cursor, and empty space selects the section you clicked in. **Where:** Site editor → Edit mode → click anywhere on the canvas preview **How to test:** Click in blank space beside a heading, in the gap between two columns, or in the area below a card that shows a scrolling website screenshot. You should get the section you're looking at (or the nearest card), never a stray rectangle spanning unrelated content, and the panel on the right should open with that section's text fields. Clicking text, images, buttons and cards should behave exactly as before. **Watch for:** A card or banner that no longer selects on its own; a section selecting when you meant a block inside it; the size badge under the selection box reporting a smaller number than before for images that are cropped by their frame.
Asking the assistant to suggest improvements to a section used to take up to a minute and a half; it now answers in a fraction of that, and applying an idea from the expanded view hands the page straight back to you. **Where:** Site editor → open a design → select a section in the preview → ask the assistant something like "can you suggest a better way to present this section" **How to test:** Select a section, ask for suggestions, and time the reply. You should get three ideas rather than up to five, each still naming exactly what would change. Expand the ideas card to full screen, tick one, and press Apply — the card should close on its own and leave you looking at the updated page. **Watch for:** Advice that arrives with fewer than two ideas, wording that mentions class names or pixel values instead of what you would see on the page, or the expanded card staying open after you apply a change.
When a request could mean more than one thing — like asking for "the three images" on a section that has tabs — the assistant now makes the change, tells you which parts it changed and which it left alone, and offers the other reading as a button you can click. **Where:** Site editor → open a design → select a section with tabs, steps or slides → ask for a change covering several of them at once **How to test:** On a section with two or more tabbed states, ask for something like "make the three images the same size". The change should apply, and the reply should name which states it changed and which it didn't, with buttons such as "Make all 3 the same height" and "Apply it to Review too" that run immediately when clicked. Where a change genuinely cannot work, the reply should still offer next steps rather than stopping dead. **Watch for:** A change that says it covered every state when it did not; buttons that fill the message box instead of running; or a refusal card appearing for a change that did actually alter the page.
Pasting a screenshot into the design chat used to show a broken-image icon until the upload finished; it now shows the picture straight away with an uploading spinner over it. **Where:** Site editor → design chat composer (the box you type changes into) **How to test:** Copy a screenshot to your clipboard, click into the chat box and paste. The thumbnail should appear instantly, dimmed with a spinner and an "Uploading…" note next to the image counter, then brighten once it is ready to send. **Watch for:** A broken-image icon on paste; the thumbnail disappearing after the upload lands; Send staying disabled after the spinner clears.
Asking to tighten a section used to trim its padding and report success even when nothing on the page moved. The editor now measures the section as it actually renders, so it fixes what is really holding the space open — and there is a one-click way to tighten a whole section yourself. **Where:** Site editor → click a section on the canvas → Properties → Spacing **How to test:** 1. Open a site in the editor and click a section that looks too tall. 2. The Spacing panel is now open by default. Use the Density buttons (−− / − / + / ++) to tighten or loosen every vertical gap in that section at once. 3. For a single value, click "Edit Spacing" and pick a breakpoint (Base / sm / md / lg / xl / 2xl) before changing a number — a dot marks the breakpoints that already carry their own value. 4. In chat, ask "there's too much empty space at the bottom of this section". If the height is being held open by a fixed minimum height or an empty row in the layout, you get told that instead of a padding change that would do nothing. **Watch for:** a section where the density buttons say "no spacing to adjust here" — that means its height is set by something other than spacing, and the chat will name what.
Picking a design in Swap layout now shows it immediately, you can try it on the real page before committing, and an idea you don't like can be deleted — plus layouts that would have rendered an empty section are caught and cost you nothing. **Where:** Site editor → select a section on the canvas → **Swap design** (or the Swap layout button in the section panel) **How to test:** 1. Open a design, click a section, and open Swap layout. 2. Scroll down to any tile in the gallery or Layout ideas grid and click it — the panel on the right immediately shows that design with a **Build this layout — 1 credit** button. Nothing depends on scrolling back up. 3. Build it. The result appears in the same panel, at readable size, and scrolls. Switch between desktop and mobile with the icons above it. 4. Click **See it on the page** — the layout renders on your real page among the other sections. Use it, go back to the ideas, or discard it from the bar at the bottom. Nothing is saved until you choose **Use this layout**. 5. Type a change ("tighter spacing") and hit Revise, then ask for another change. Each turn appears under the idea it came from, and later requests build on the earlier ones. 6. Hover any idea in the list and click the bin icon to discard it. It does not come back. **Watch for:** a built layout that shows an empty section (this should now be rejected before you see it, and no refinement should be charged); the "See it on the page" preview differing from what Use this layout actually applies; a discarded idea reappearing after reopening the picker; the page still showing a try-on layout after closing the picker without applying.
Picking a new layout for a section used to leave the page showing the old one — the change could also be overwritten a moment after it saved. **Where:** Site editor → click a section → Swap layout → try a design on → "Use this layout" **How to test:** Open a homepage section that lives inside the page (not the header or footer), swap its layout, and confirm the canvas keeps the new layout after the picker closes. Reload the page and check it is still there, then use Undo in the chat panel to confirm the swap is in version history. **Watch for:** The section reverting to the old layout after a second or two, the swap landing on a different design than the one you were viewing, or Undo restoring an unrelated change.
After a change landed, the assistant card said only "Updated 1 area" — it named a section and never said what happened to it. It now shows the change description alongside the verified list of sections, and tells you when the canvas is still rebuilding. **Where:** Site editor → Assistant panel (right rail), after any applied change. **How to test:** 1. Open a site in the editor and ask for a specific change ("make the headline full width and move the benefits below the preview"). 2. When it lands, the green card should describe the change in a sentence — not just a count. 3. Below it, the changed sections are listed with a "1 area changed" / "2 areas changed" caption. Click a row to jump to it. 4. "Show details" reveals the per-file specifics when the change spanned several files. 5. While the canvas is still rebuilding, the card shows "Updating the preview…" and the line disappears once the new render appears. **Watch for:** a description that claims more sections than the list shows (the list is the one to trust); "Updating the preview…" that never goes away after the canvas has repainted.
Long requests in the design assistant used to show a timer that guessed — "Almost there…" on a request with two minutes left to run — and never mentioned when your message had been answered with suggestions rather than an edit. It now reports each real step as it happens, and the suggestions card is easier to read and act on. **Where:** Site editor → Assistant panel (right rail), any design or client site. **How to test:** 1. Open a site in the editor and select a section on the canvas. 2. Ask an open question about it ("does this hero grab you?", "how could this section be better?"). 3. Watch the spinner: it should say it's looking at the design in detail, then that it's reading the section's code, then that it's writing recommendations — instead of a generic countdown. 4. Ask for a direct edit instead ("make the heading bigger") and confirm the steps read as an edit: working out the change, finding the files, making the change. 5. When the suggestions card arrives, the panel should scroll to the TOP of it — the summary and first recommendation visible without scrolling up. 6. Tick a recommendation. The buttons should read "Try as a new design" and "Apply 1 change"; hover each for a sentence explaining where the change lands. **Watch for:** a spinner that freezes on one step and never advances; the panel jumping back to the bottom of the feed right after landing on the card; "Apply" acting on a design you weren't editing.
Swapping a section's layout is now something you can experiment with: line the ideas up under your page, flick between them with the arrow keys, keep the ones you like, and change your mind afterwards. **Where:** Site editor → click a section → Swap layout **How to test:** 1. Open a section and generate a couple of ideas ("3 fresh ideas" gives you three for one credit — it always did, it just never said so). 2. The tray appears under your page with a chip for every idea plus a "Current" chip. Click one, or press the arrow keys or 1–9. Your page updates and scrolls to the section each time. 3. Hold the space bar to peek back at what you have now, and let go to return. 4. Star two ideas to keep them as maybes — they move to the front and are still there tomorrow. 5. Press "Use this layout". The tray stays open, so you can keep trying the others, and "Put the original back" undoes it in one click. 6. Sections that live inside a page — most homepage sections — can now be swapped at all. That used to spend a credit and then refuse. **Watch for:** an idea marked "Can't be placed on this page" (it will say why, before you spend anything); the page not scrolling to the section after a switch; a swap landing on a different design than the one you were viewing; or the tray freezing with "this section changed somewhere else", which means someone edited it in another tab.
When a design edit took too long, the editor sat silent for five minutes and then showed a message it had guessed at — it had never actually heard back. Long edits now report their own result, so the chat tells you what really happened. **Where:** Site editor → open a design → Design assistant chat **How to test:** Ask for a broad, site-wide change (for example "change the colour theme across the whole site"). If it does not finish in time, the chat now says the change didn't finish and may still be completing in the background, instead of hanging for the full five minutes first. **Watch for:** A long edit that ends with no message at all, or one that blames a lost connection while your connection is fine. Normal fast edits should be completely unchanged.
Connecting, verifying, retrying SSL for, or disconnecting a custom domain failed instantly with an internal error and never showed the DNS records to add — the whole custom-domain feature was unusable. It now works end to end. **Where:** Site editor → Settings → Domain **How to test:** Open a live site's Domain settings, type a domain into "Enter your domain" and click Connect. You should get the TXT and CNAME records to add at your DNS provider, not an error. Adding a malformed domain should say "Invalid domain format", and Disconnect should work on a site that has a domain connected. **Watch for:** Any error message that looks like internal code rather than plain English; DNS instructions failing to appear after Connect; the Verify button not moving the domain out of "pending". The same underlying problem was fixed in five other places it had been hiding: changing a teammate's access scope, leaving or removing someone from an organization, the website chat knowledge base, Meta Ads lead-form page selection, style preferences submitted from a shared preview, and the recipe/style guidance used when generating a site.
You can now move a Shopify catalog across by typing the store's web address — no export file, no app to install, no password to hand over. **Where:** Site editor → Content → a products collection → Import → Shopify **How to test:** Type any Shopify store's address (for example `yourstore.com`) and start the import. Products, variants, images and collections come across, products are filed into their real collections, and the old `/collections/...` links redirect to the new category pages. Product addresses don't change at all — a product that lived at `/products/blue-shirt` still does. **Watch for:** Three things aren't publicly readable on a Shopify store and so don't come across this way — stock counts, SEO titles and descriptions, and any product that isn't published yet. If you need those, use the "Upload a products CSV instead" link on the same screen. Imported products are saved as drafts for you to review before they go live. Very large catalogs stop at 5,000 products; run the import again to continue. A store whose owner has switched off its public product feed will say so and point you at the CSV.
Scrolling the row of designs at the top of the editor used to jump nearly a full screenful per notch and then snap back to the design you were already on, which made reaching something like Design 7 a matter of luck. **Where:** Site editor → the design strip at the top of the toolbar (D1, D2, D3 …), most noticeable with the Assistant panel open. **How to test:** Open a site with seven or more designs and narrow the window (or open the Assistant) until the design row starts scrolling. Scroll it toward the last design and move your pointer across the pills — it should stay where you put it. Use the ‹ › arrows beside the pills to move exactly one design at a time, or press the left/right arrow keys once a design is focused. Picking a design from the gallery should still bring that design into view. **Watch for:** The row drifting back on its own while you scroll or hover; the whole toolbar sliding sideways instead of just the designs; the arrows not appearing when the designs overflow, or still showing when they all fit.
If another site was already using the project name you picked, publishing stopped with an "Unexpected Error" and a technical database message. You now get a clear message naming the project name and asking you to pick a different one, and the site is left untouched. **Where:** Site editor → Publish → enter a project name → Publish **How to test:** Publish a site using a project name another of your sites already uses (a site you deleted can still be holding one). Expect "Project Name Already Taken" with the name shown and a prompt to choose another — not "Unexpected Error" or "Failed during: Compiling Code". Change the name and publish again; it should go through. **Watch for:** The error appearing as a failed publish *step* rather than a name problem; any technical text in the message; the publish progress bar continuing after the error.
The "Publishing Your Site" progress window could keep running forever when publishing was refused or never got going — no error, no message, and the site never went live. **Where:** Site editor → Publish **How to test:** Open a site and publish it. The progress window should finish with either the live URL or a clear error. If you publish while another publish is already running, the window keeps showing progress and then resolves as normal. **Watch for:** A progress window that sits at the same step for more than a minute, or a publish that ends without either a live link or an explanation.