# Review & Approval — MetaPilot **Automated updates, with a human in the loop.** Auto-pilot proposes fresh metadata; you see it as a diff against what your page serves today and decide. All the speed of automation, and you still read every change that carries your name. --- ## The Problem Regenerating metadata automatically is powerful, and risky if it publishes blindly. One bad generation across hundreds of pages can quietly cost you rich results for weeks before anyone notices. But reviewing every change by hand does not scale either, and a workflow nobody keeps up with is the same as no workflow. What you actually want is a **metadata review workflow** that shows you the diff, takes seconds per page, and gets out of the way when you decide you trust it. --- ## How It Works 1. **A change is proposed** — When a page changes, MetaPilot generates fresh metadata and queues it as a proposal instead of publishing it. Nothing on your live site moves yet. 2. **Read the diff on the card** — A line-by-line diff against what your page serves right now: red for what goes, green for what arrives, unchanged lines folded away. Title, meta description, JSON-LD, Open Graph and the Markdown for agents, all on one card. 3. **Approve, edit or reject** — Approve publishes it as it stands, in one click. Edit opens the wording first. Reject keeps what you have. Seconds per page. --- ## What You Get ### A structured data diff you can actually read A git-style diff, not a wall of minified JSON buried in a deploy. Runs of unchanged lines collapse behind a disclosure, so a sixty-line JSON-LD block where six lines moved reads as about fifteen. ### Approve is one click, and the diff is right above it No modal, no confirmation step, no scrolling past an editor to say yes to something obviously correct. The diff sitting directly under the button is the informed-consent step. When you do want to change something first, Edit is its own action and opens every field. ### A queue you can work through Above one proposal the cards collapse, and each collapsed header still carries the summary chips and all three buttons: *Page title rewritten · Schema.org JSON-LD +34 −6 · Open Graph unchanged*. One button reads **Approve all**, or **Approve 3 selected** once you tick rows. ### Approve without logging in The digest email names the pages waiting and links to a signed review page. Same diff, same Approve and Reject, no password. The signature is the authorization and it only ever reaches proposals you could already see in the app. ### Human-in-the-loop SEO, per person Requiring approval is a preference on your profile, on by default. Leave it on where you want oversight; turn it off and generations publish straight away. The same preference drives auto-pilot runs and manual ones, so behaviour never depends on how a change was started. ### Proposals do not pile up forever Each one expires after a week, so an ignored queue quietly ages out instead of publishing something written against a page that has since changed again. ### An honest "before" side The left of the diff is whatever your page serves today: our published value where we already publish that field, your own baseline where we do not. Where MetaPilot cannot prove either, it says so instead of showing an empty panel that reads as "you had no metadata." --- ## Plan Availability Available on **every plan**, Free included. Approval is a preference rather than a paywalled feature: control over your own metadata should not be an upsell. Your first 5 pages are free. Approve every change or run on autopilot. --- ## Frequently Asked **What exactly am I approving?** The generated page title, meta description, schema.org JSON-LD, Open Graph tags and Markdown for agents, shown as a diff against what your page is serving right now. **Can I skip review and auto-publish?** Yes. Turn the "require approval" preference off on your profile and generated changes go live as soon as they are produced. It is on by default, so you opt out of the safety net rather than into it. **Does review work with auto-pilot?** Yes, that is the point of it. Auto-pilot proposes into the queue rather than publishing directly, so you can turn automation up without handing your rankings to a black box. **Can I change what was generated before approving it?** Yes, with the **Edit** action, which opens the proposed title, description, JSON-LD, Open Graph and Markdown in a form. Whatever you submit is written both to the page and back to the proposal record, so the audit trail reflects what actually shipped. Approve on its own does not open a form: it publishes the proposal as it stands. **Can I approve a batch?** Yes. Above one proposal a single bulk button appears, reading **Approve all** until you tick rows and then **Approve 3 selected**. It confirms first, and the count only ever includes proposals still actionable, so a page approved in another tab cannot inflate it. **What happens to a proposal I never look at?** It expires after seven days and stops being actionable. Your live metadata is untouched, and the next time the page changes a fresh proposal is queued. **Who gets the review email?** Members of your organization who have the approval preference switched on. Each gets their own signed link, good for seven days, and it names the pages waiting rather than only counting them. --- ## Keep Reading - How to review and approve changes - Auto-pilot: metadata that keeps itself fresh - Structured data generated for every page - Verify your schema is actually live