Generating metadata
A run has four steps, and it stops between each of them. Nothing is written to your site until you have read it.
1. Choose what to write
Post type, which fields, and how many. Two choices are worth understanding:
- Only the ones with nothing there is the default and does what it says. All of them, replacing what is already written is the other option, it is never preselected, and it asks you to confirm — with a count of how many written fields you would be replacing.
- How many is a bound on items, not posts. One item is one field on one post, so both fields on 100 posts is 200 items.
2. See what it costs, before it starts
The screen prices the run before it exists. Finding out that "everything, both fields" was 8,400 items after the run has started spending is finding out too late.
Quota is consumed when text is generated, not when it is applied. Discarding a suggestion does not refund it, and regenerating costs again. That is why the review step exists before the write and not after.
3. Read every suggestion
The review queue shows each suggestion beside what the field holds now. You approve or discard each one, and you can edit any of them before approving.
There is no "approve all", on any plan. That is deliberate and it is not coming: a button that writes 200 published pages without anybody reading them is the one action this product must not have.
4. Apply
Only approved items are written, in batches, into your SEO plugin's own fields. Before each write, Metaly re-reads what the field holds now. If it changed since you chose it — because you edited it by hand in the meantime — your edit wins and the item is skipped with the reason recorded. You can override that one item if you want ours instead; the screen shows you both first.
A large run is applied in batches on a schedule rather than in one request, so a shared host that cuts long requests short does not lose it. If it is interrupted it resumes where it left off.
Undoing a run
Every write is recorded before it happens — the previous value, the new one, which plugin it went through — so Undo this run puts every field back to exactly what it held.
The record is kept for 90 days by default and pruned after that. An undo older than that is not available, and the screen says so rather than failing quietly.