WooCommerce metadata repair — small-batch checklist WP Shelf / SnippetGrove — 13 November 2026 Guide: https://wp-shelf.com/snippetgrove/guides/woocommerce-metadata-repair Make a copy for each batch. Keep this log locally; it may contain private URLs. Batch/date: Reviewer: SEO host and version: Site backup / recovery location: Selected product URLs: For each product [ ] Record the current stored description and actual rendered description tag. [ ] Distinguish an empty stored field from a template fallback or repeated output. [ ] Verify source facts: material, size, capacity, compatibility and other claims. [ ] Draft wording that identifies this product; omit unsupported promises. [ ] Choose one path: - Free manual missing-field Save (writes directly); or - Existing SEO host editor for a populated field; or - Explicit hosted generation with a checked selection and item count. [ ] For generated wording: review/edit each suggestion, Approve individually, and check the entire run's approved total before Apply. [ ] Confirm the save/apply result; resolve partial failures before continuing. [ ] Inspect tags in a fresh frontend request and account for page/CDN caching. [ ] Record the after-value and recovery method. Before expanding [ ] Test one recovery and inspect the page again. [ ] For applied generation writes, read Activity and restored/skipped undo counts. Later changes are protected; the journal is kept 90 days by default. [ ] Manual missing-field Save and direct SEO-host edits are outside that journal. Restore those in the host editor using the previous values you retained. [ ] Keep generation cost separate: successful generation consumes items before Apply; discarding or undoing does not refund those items. [ ] Decide the next small batch only after the first result is verified. Per-product log (repeat as needed) URL / product ID: Stored description before: Rendered description before: Verified facts / source: Write path and run or Activity reference, if applicable: Saved wording after: Rendered wording after: Recovery check and skipped entries: Next action: A corrected HTML tag is not proof that Google will use the same snippet or that rankings, click-through or sales will improve. Compare performance over time.