Facebook Page audit board for multi location brands

Build me an app for auditing the Facebook Pages we manage across dozens of locations. We run one Page per location and their details drift apart over time: wrong phone numbers, missing websites, stale descriptions, the wrong call to action button. I want to open this board once a month and see at a glance which locations are broken, then fix them right there.

The main view is a board listing every Page we manage. Use the Facebook Pages List Pages operation to get the managed Pages, then Get Page for each one to pull in its current profile: name, phone, website, category, about and description, plus its current call to action button from List Page Call To Actions. Each row shows the location, its key profile fields, a completeness score, and a count of problems found. Sort worst first by default so the most broken locations are at the top, and let me filter to just rows with problems, or search by location name.

Our house standard lives in a Google Sheet, one row per location with the approved phone, website, category and call to action type. Read it with the Google Sheets Get Values operation and match each standards row to a Page by name or Page ID. The app diffs each Page against its standard row and flags two kinds of problem: a mismatch, where the Page value differs from the approved value, and an empty field, where the Page has nothing at all. The completeness score is the share of tracked fields that are both filled in and matching. A location that has no row in the standards sheet is still scored for empty fields, it just does not get mismatch flags, and the board should mark it as missing a standard so I can go add one.

Opening a row shows a detail panel with every tracked field in three columns: the current value on the Page, the approved value from the sheet, and what it will become. Mismatches and empty fields are highlighted. I can accept the approved value for a field, type my own value, or skip the field. When I save, apply the profile changes with the Update Page operation. Always show the before and after values and require an explicit confirm before anything saves.

The call to action button is managed from the same panel. Show the Page's current button from List Page Call To Actions. If the Page has no button, let me add one with Create Page Call To Action. If it has one but the type or destination link is wrong compared to the standard, let me change it with Update Page Call To Action. Treat the button type and its link as two more tracked fields in the diff and the completeness score.

I also need bulk apply for cases like rolling a new website domain across every location. Let me select a field and a set of rows, set the new value or a find and replace rule, and preview a table of every Page it will touch with the old and new value for each. Nothing runs until I confirm that list explicitly. The same applies to bulk call to action changes. Show progress as it works through the Pages, and if a Page fails, report it in the results without stopping the rest of the batch.

Append every change to an audit log tab in the same spreadsheet using the Google Sheets Append Values operation, one row per field changed, with timestamp, Page name, Page ID, field, old value, new value and who made the change. Write these rows after the Facebook write succeeds so the log only ever reflects changes that actually landed. Show the recent audit log entries in the app too, both on the row detail panel as a per location history and as a global recent changes view.

Add a post this month's summary button that sends a message to our marketing channel in Slack with the Slack Bot Send a Message operation. The summary covers the count of Pages fixed this month, the count still broken, the overall completeness across all locations, and the names of the worst remaining locations. Let me pick or preset the channel and preview the message text before it sends.

Some important details. Page writes need the Page access token that comes back per Page in the managed Pages list, not the connected user token, so use the right token for each Page's calls. The connected account only ever sees Pages it actually manages, so if a location is absent, surface that clearly rather than showing an empty board. Some profile fields are read only or depend on the Page category, so show which fields the app can actually write for a given Page, skip the ones it cannot, and save the rest instead of failing the whole update. When a field is skipped for that reason, say so plainly in the result. Rate limits apply per Page, so pace bulk operations and back off on limit errors rather than hammering the API.