Loading
Because content and engineering keep separate lists that cannot be compared. What gets done is what was asked for most persistently, which is a poor proxy for value.
The opportunity backlog is a single ordered list of every identified improvement — content gaps, technical issues, cannibalisation, metadata.
Every item carries the page it affects, that page's current performance and value, and an effort estimate. Ordering comes from value against effort rather than from the meeting.
A metadata fix on a page producing enquiries sits above a new page on a cluster nobody searches, and both teams can see why.
It will not settle a disagreement about strategy. It makes the trade-off explicit and records what was chosen; the argument is still available, just better informed.
Page records, clusters, the audit, gap analysis, and the tasks it creates in Loop for whoever does the work.
Yes, keeping the link to the page record.
Roughly by fix type, and it improves as you complete items.
Yes, and the override is recorded.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.