Free one-pager · RADAR
Aggregator visibility checklist for multi-unit QSR.
Your menu card is a product surface at ~120px. Discovery orders die in the feed before they die in the kitchen. Run this weekly. Obsess daily only when something moves.
US: DoorDash · Uber Eats
Canada: Skip · Uber Eats · DoorDash
India: Swiggy · Zomato
- • Creative + offer + menu accuracy checks
- • Outlet × platform × query monitoring rules
- • Weekly ritual (and what not to obsess daily)
Prefer the printable now? Open checklist. Want the systems playbook? QSR systems · How chains lose rank.
A · Creative
- Hero photo readable as a thumbnail (dish clear at phone size)
- Name + cuisine scent obvious without opening the store
- Rating presentation honest — no “4.9” theater on thin reviews
- Promo hygiene: expired banners and spammy stacked discounts cleaned up
B · Listing ops
- ETA / fees don’t surprise after the click
- Bestsellers still listed tonight (delist = silent rank death)
- Stock / 86’d items not showing as available
- Menu accuracy matches what the store can actually fire
C · Rank monitoring
- Track outlet × platform × query — not “how’s DoorDash feeling?”
- Missing listing = unknown, not fake rank #99
- Alert on meaningful moves (e.g. ≥3 positions) with cooldown
- Keep a receipt (screenshot / observation time) when something slips
D · Weekly owner ritual
| Do weekly | Don’t obsess daily |
|---|---|
| Spot-check top 3 queries per priority outlet | Refreshing apps at dinner rush for vibes |
| Fix listing breaks the same day | Debating footfall with no rank evidence |
| Note competitor jumps with date + screenshot | Blaming the platform without a time series |
This checklist fixes creative and ops hygiene. Ongoing silent slips need instrumentation — poll → normalize → threshold → plain-language alert. That product pattern is Rank Radar.