Shoppable link console for your WordPress recipe archive

Build me an app that shows the shoppable-link health of my entire WordPress recipe archive on one screen. I run a recipe site and I use Instacart shoppable recipe pages, but those links expire (30 days by default, 365 at most), so links I generated months ago are quietly dead on my highest-traffic posts. I need a working surface for coverage and renewal, not a scheduled job.

Main view: a table of every published recipe post, loaded with WordPress List Posts (page through everything published, not just the first page). Columns: post title linking to the live post, publish date, last modified date, the current Instacart link, the link's expiry date, a days-remaining countdown, and a status badge that is one of Live, Expiring, Expired, or No link. Status is derived from the stored expiry date and the warning threshold from settings. Sort by days remaining ascending by default so the most urgent recipes are on top, and let me sort by title, publish date, and status too. Include a search box on title.

Store one record per recipe post in the app's own storage so the countdown survives between sessions: post id, title, post URL, the generated Instacart link URL, the expiry date, the expiry window that was used, when it was last generated, and the outcome of the last generation attempt including any error text. Nothing about the countdown should depend on re-reading the post body.

A Refresh archive button re-reads posts from WordPress List Posts, adds new recipes, and updates titles and modified dates. During that scan, look inside each post body for an existing instacart.com link so recipes that already got a link (by hand or before the app existed) are picked up rather than shown as missing. If a link is found but the app has no expiry date for it, mark the expiry as unknown and treat it as needing renewal rather than guessing.

Filters across the top: No link yet, Expiring in the next 14 days, Already expired, and All. The 14 comes from the warning threshold in settings, so the filter label should follow that setting. Above the filters, show a top-line count of live vs expiring vs missing across the whole archive, and make each count clickable so it applies the matching filter.

Every row has a checkbox and a Generate button, plus a Generate selected action in a bulk bar when one or more rows are ticked. Both start the same background agent, once per selected recipe, and the row shows the agent's live state (queued, running, done, failed) with the error message inline on failure. The table should update as each agent finishes so I can watch a batch drain.

The embedded background agent, for one recipe post, does this: read the full post body with WordPress Retrieve a Post; extract the ingredient list with quantities and units, normalizing to the units Instacart accepts (each, lb, oz, g, kg, ml, L, cup, tbsp, tsp, gallon) and falling back to each when a unit is not convertible; pull the recipe title, hero image URL, and the instruction steps if the post has them; then call Instacart Create Recipe Page with those ingredients as line items with their measurements and with the expiry window set to the row override if there is one, otherwise the default from settings. Take the returned link URL, and write it back into the post body under the recipe card with WordPress Update a Post using the placement snippet from settings. If the snippet is already present in the body, replace it in place rather than appending a second copy, so re-running is safe. Leave the rest of the post content, its status, categories, and tags untouched. Finally, save the link URL, the expiry window used, and the computed expiry date (generation date plus the window) back onto the app's record for that post so the countdown starts fresh.

If the agent cannot find a usable ingredient list, it should stop rather than invent quantities: mark the record as needing attention with a short reason, and leave the post untouched.

Settings view: the default expiry window in days (1 to 365, default 30), the warning threshold in days that decides when a link counts as expiring (default 14), the link placement snippet template with a placeholder for the generated URL and a stable marker the app can find on re-runs, and which posts count as recipes (a category, tag, or post type filter applied to WordPress List Posts). Settings are saved in the app and used by every generation from then on.

Keep it to two views, the coverage table and settings. No scheduled runs, no notifications. Nothing writes to WordPress except the link snippet.