Reviewing and applying a fix

Previewing a fix

On any fixable issue, click Preview fix. For deterministic fixes the result appears instantly. For AI-written ones the plugin calls Claude right then and returns the actual proposed value — not a description of what it would write.

That distinction is the whole point. What you read on the review screen is the string the writer will receive, read from the same field. There’s no gap between the preview and the write.

What you’re looking at

The review screen shows the change as a before-and-after pair, along with:

• Character counts checked against the real limit for that field
• Which phrases on your page grounded the output, for AI-written content
• Where it will be written — your SEO plugin’s own meta field, not a parallel store
• A countdown. The preview token is valid for fifteen minutes and works once

Editing before you apply

Don’t like the wording? Edit it in place. Your version travels in a separate field and gets re-validated at the writer, so the same length caps and safety rules apply to your text as to the AI’s.

A blank value can’t wipe an existing field. If you clear the box and apply, the fix is skipped rather than writing an empty meta description over a working one.

Applying

Click Apply and the change goes live. Three things happen in order:

1. The request is checked against a single-use token whose hash covers the exact preview you approved. Alter one character in transit and the write is refused.
2. A rollback record is written — before the change runs, so even an interruption mid-write leaves a way back.
3. The value is written to the correct field for your SEO plugin, never duplicated across two.

Bulk apply

You can preview and approve several fixes of the same type together — useful for meta descriptions or alt text across dozens of pages. Each one still gets its own preview and its own rollback record; bulk changes the interface, not the safety model.

Two operations are excluded from bulk apply and labelled as irreversible: anything that submits a URL to a search engine for indexing. That message is already out in the world and can’t be recalled.

Why it won’t invent things

AI content fixes have to ground themselves in text already on your page. Statistics, quotes and cited sources must exist in your own content, and cited URLs get a live HTTP check before they’re proposed.

When nothing on the page supports a claim, the fix returns empty rather than fabricating one. This is enforced by a function in the code, not by an instruction in a prompt — a prompt can be talked around; a gate can’t.

Next: Undoing a fix →