MainWP stores its managed-site list in a custom table called mainwp_wp, with one row per child site and columns for the connection URL, last sync time, and update counts. Reports and groupings live in mainwp_wp_group and mainwp_wp_settings. The dashboard surface is a normal WordPress admin page, and the public-facing report pages (for clients who get read-only access) are standard pages with embedded MainWP shortcodes.

The links agencies share most often are these report URLs. Pasted into Slack for a teammate, forwarded to a client over email, or dropped into a runbook. The default preview is the agency site's homepage card, which carries no information about the report itself. A reader has to click through to know whether it covers 5 sites or 50, and whether anything is broken.

SleekPixel queries the mainwp_wp table for the sites in the report group, totals the pending updates, and renders a card with site count, update backlog, last-sync timestamp, and report period. The card refreshes when the daily sync runs, so a Monday report URL forwarded on Friday still previews with current numbers.

Agencies running MainWP live in their dashboard. Every conversation about a client portfolio starts with a URL. Without per-report previews, those URLs all look the same in chat, which means context lives entirely in the message text around the link.

Anyone joining a thread has to read up. With SleekPixel, the preview itself carries the report period, site count, update backlog, and freshness state. A scan of the channel surfaces the routine reports from the urgent ones without anyone opening a page.

The MainWP data is already there. The mainwp_wp table is the source of truth for child sites. The sync cron updates counts on a schedule.

Pending update totals are queryable. SleekPixel just composes that into an image and writes it to the meta tag, so the same numbers that power the dashboard view also drive the share card. The agency keeps its brand on the surround, the report keeps its identity on the inside.