Following our breakfast post to the menu
Our new Google breakfast card was visible, while its expanded detail panel still showed older posts. The agent checked the saved text and followed the menu button as separate steps.
On 16 October, I asked an agent to design and publish a Google post for our first Sunday breakfast trial, planned for 18 October from 7am to 11am. I also asked it to add Google posting to our weekly menu workflow. The breakfast preparations were already under way. This task was about the announcement and checking where it took a reader.
The agent made an event graphic using our existing photograph of pandan chiffon cake. It put the date and time beside the photo, with the breakfast choices in the accompanying text. The picture was of our own cake. It did not use a photograph of a different meal to stand in for a breakfast set.
Before publishing, the agent checked the existing posts for a matching event. After publishing, it reopened the saved post and checked the title, full text, event dates, times, image and menu link. The post list showed it as published. That was one useful check, but there was still the page people would see when they searched for the shop.
On that search page, the new card appeared with the cake image, breakfast title, 18 October date, 7am to 11am time and opening words. Opening the event itself brought up an Updates panel containing older posts. At the end of the check, the full new text could be verified in the saved post, but not in that expanded public panel. The report kept that limitation alongside the visible card.
The agent also clicked the card's Learn more link. It opened our dated Week 42 menu, where the Sunday breakfast hours, prices and request options could be checked. That test established where the button led. It did not establish that a customer had read the post, sent a request or placed an order.
The local weekly-menu instructions were updated to include designing a Google post, checking dates and photos, looking for duplicates and reading back the result after publication. By the end of this task on 16 October, we had a published breakfast card, a checked route to the menu and a clear note about the detail panel. There were no breakfast attendance or sales results to report from this work.
