WordPress SEO automation: Fix the live page. Touch nothing else.

A fixed set: the title and meta description (the SEO title where your SEO plugin has one), the canonical and social preview text, headings, link words, image alt text, a broken link pointed somewhere live or removed, page schema, a snippet-shaped answer block, a Key Takeaways block, a source citation attached to one claim, an internal link, the disclaimer your compliance pack requires, one paragraph reworded so it no longer makes a claim your rules flag, and a year rollover on the references you tick. Anything larger is a content refresh you do in the editor and publish as a whole page.

No. A model drafts the short new text (a title, a 40 to 50 word answer, three to five bullets, or one reworded paragraph that is checked against the rule it broke before you see it) or picks a phrase already present in your page to use as a link anchor. The write itself is code: it locates that one claim, phrase or year in the current page and inserts at that offset. The apply step never sends your page to a model.

Nothing is written. The weave matches the claim, anchor or year against the page as it is right now, ignoring whitespace and markup, and refuses any match that would sit inside an existing link, a heading, the intro or a takeaways block. If it can't find a clean spot you are told the page may have changed, rather than getting an edit somewhere approximate.

Very little now, and each says so in the product. On a git site built from Markdown, social preview tags come from your layout, so Verand tells you to add them there once, and schema for the whole site arrives as a pull request because it touches every page. On WordPress, fixes are proven on the block editor, the classic editor and Elementor; Divi, Beaver Builder and WPBakery pages are declined by name rather than edited, and on any other builder Verand re-reads the live page after most fixes and tells you if the change didn't show. Everything else applies on WordPress and on git sites alike, Markdown included.

No. Every apply is approved by a person who has seen the change: a button on a preview in the dashboard, or a yes in an AI chat after the assistant shows exactly what changes, if an account owner has turned that on. Scheduled routines find the work and draft the fix; none of them writes to your site. An article a compliance check has blocked can't be published to WordPress or committed to your repo either, because both publish paths check the same flag.

It applies to static sites whose pages are baked HTML, where a new page is rebuilt from a recent article in your repo. Before the commit: exactly one H1, the canonical and og:url pointing at the new article rather than the one it was derived from, no scripts or stylesheets lost from the head, balanced structural tags, the surrounding layout still there, the previous article's heading and opening paragraph gone, this article's hero in the header, and the site's own navigation unchanged. Any failure returns the list instead of a pull request.