The fix queue brings proposed website changes together with their recorded status. Before approving one, check the page, the wording and the route it will use. Delivery eligibility confirms route support under the current checks; you still need to verify the business facts.
Before you approve
- Open the affected page and compare it with the proposal.
- Check business names, addresses, prices, claims and service areas.
- For schema, verify that the facts are visible on the page and that existing markup will not conflict.
- Check route support, permissions and any manual steps.
Choose the right level of control
Choose Autopilot for eligible automatic delivery, Managed for guided review and batch actions, or Expert for individual fixes and detailed tools. Check your enabled permissions as well as the mode: existing automation can still run during scans. Your plan and website connection determine which actions are available.
Individual and batch actions
Use individual review when wording or business facts need judgement. Batch actions are limited by the supported categories and connection. Read the preflight summary before confirming; opening a preflight is not the same as approving delivery.
Review the proposed change, confirm its facts and check delivery support for your website. After authorising an eligible fix, inspect the delivery record and the separate live-page check. Use your CMS or developer for work the connection cannot deliver.
After an attempt
Inspect the result, including failures or unavailable verification. Check the actual page. Use supported rollback if needed and verify that result separately; deleting a script does not undo a native CMS write.
Where editing is available, correct the proposal before applying it. If a fix cannot be edited or delivered in the app, make the change in the CMS or assign it to the person responsible.
