Skip to main content

Check your live website and approve improvements

The Live site tab in the site canvas reads your published pages the way a search engine's crawler receives them, compares them with what you published and what is saved, and proposes changes made only from words already on the page. You approve each change; nothing goes live until you publish.

Steps

  1. Open the site canvas and choose the Live site tab, then press Check the live site.
  2. Read the findings. Each says where its evidence came from: the live page, the live page against the published version, or the saved site, and how it is fixed: by publishing, by a change proposed below, or by going to the page.
  3. Under Proposed changes, compare Now with Proposed and read where the words were taken from. Tick only the changes you approve and press Apply. They are saved as a new version, shown in History.
  4. Publish, then check the live site again: After publishing says, for each change, whether the public page now shows it.

Questions

Is this an SEO or AI visibility score?
No, and there is no score at all. It reads the public HTML of your pages and nothing else. Whether a page appears in search results or is cited in an AI answer is measured in Search Console and the search measurement screen, never inferred from markup.
Can a proposal overwrite something I changed later?
No. Every proposal remembers the value it was made from. If that field changed after the check, the change is reported as a conflict and left as it is. And while the canvas holds unsaved edits, nothing can be applied.
Why are some findings without a proposal?
Because fixing them needs facts the page does not hold: alt text for a picture, a heading, new copy. Those are yours to write, and the finding takes you to the page. Business details for search engines and the canonical address are added by publishing again.
Can my AI assistant do this?
It can read the diagnosis and apply proposed changes to the saved draft, through design_site on mcp.brandmyinbox.com or site_diagnosis and site_apply_improvements on the EmailPro MCP server. It is asked to show you each change first, and every change it applies is a new version in History marked as the assistant's. It cannot publish: nothing goes live until you publish.

Updated 2026-10-25 · llms-full.txt