# Pulse · August 6, 2026

> Google adds AI food ordering to Ask Maps, Merchant Center tests automatic 'Deal Ends' urgency badges, and WordPress 7.1 changes admin-table markup for screen readers.

Canonical: https://brandonlazovic.dev/pulse/2026-08-06/  
Author: Brandon Lazovic  
Published: 2026-08-06

## Google adds AI-driven food ordering and checkout to Ask Maps

Status: Confirmed  |  Topics: platform-ecommerce, agentic-commerce

Google announced Ask Maps can now place food orders directly: a conversational request finds a matching restaurant along the user's route and adds items to cart through delivery partners Square and Toast, with Uber Eats coming soon, per Google's August 6 blog post. Food ordering and a new hotel/event search with real-time pricing roll out first in the U.S., while a companion live transit-delay widget rolls out everywhere Ask Maps already operates.

In plain terms: Instead of searching for a restaurant and then ordering separately, you can now just ask Google Maps for a specific dish and it finds a place along your route and starts your order for you.

Why it matters: Conversational commerce that finds, carts, and checks out in one request is the agentic-checkout pattern e-commerce brands need their product and location data structured for, not just their ads.

Our take: I've tracked this same mechanic converging across Amazon, Google, and OpenAI: the platform generates the transaction at query time from structured merchant data instead of routing through separate search-then-order steps. Ask Maps applying it to food pickup means restaurant and menu data quality, not just ad spend, decides whether a brand gets found inside that single conversational request.

- [Google: The Keyword - Order food in Ask Maps and more](https://blog.google/products-and-platforms/products/maps/order-food-in-ask-maps/)

## Google Merchant Center rolls out 'Deal Ends' urgency badges generated automatically from feed sale-price data

Status: Confirmed  |  Topics: product-feeds-shopping, ads-paid

Google published a new Merchant Center help document describing 'Deal Ends,' an experimental Product Listing Ads annotation showing countdown badges like '3 days left' beneath prices. Badges generate automatically from existing sale_price and sale_price_effective_date feed attributes when a discount meets seasonal thresholds, 10% off during holidays or 5% otherwise, expiring within 7 days at the lowest price in 15 to 60 days. It runs globally except the EEA+, Switzerland, and the UK, and merchants cannot currently opt out.

In plain terms: Google is now automatically putting 'X days left' urgency labels on qualifying sale prices in Shopping ads, pulled straight from data merchants already submit, and there's no setting to turn it off.

Why it matters: A Shopping-surface feature that reads straight off sale_price and its effective-date field turns feed pricing hygiene into a visibility lever, with no way to decline it once eligible.

Our take: I've called this pattern a convergence tax: Google keeps building new surfaces directly on top of feed attributes merchants already submit, which raises the cost of letting sale_price and sale_price_effective_date drift out of sync. Deal Ends turns that drift into a visible defect instead of a quiet one: get the eligibility math wrong and a badge either fails to appear or shows the wrong countdown, in front of shoppers, not just in an audit report.

- [Google Merchant Center Help - Deal Ends annotation](https://support.google.com/merchants/answer/17371375?hl=en)
- [Search Engine Roundtable - New Google Product Listing Ads Deal Ends Experimental Annotation](https://www.seroundtable.com/google-pla-deal-ends-annotation-41826.html)

## WordPress 7.1 rewrites admin post-list table HTML to fix an 11-year screen-reader bug, risking plugin breakage

Status: Confirmed  |  Topics: crawling-indexing-rendering

WordPress 7.1, releasing August 19, 2026, changes the semantic HTML of admin post-list tables: the row header (th scope='row') moves from the checkbox column to the post-title column, fixing ticket #32892, an 11-year-old bug where screen readers announced 'Select All' instead of the post's title. Make WordPress Core documented the change August 3. Plugins using CSS or JavaScript selectors that assume the old th/td positions may break and should be tested against a 7.1 pre-release build before the stable release ships.

In plain terms: WordPress is changing which table cell in its post-editing screen carries the technical 'label' role, so screen readers correctly announce the post's title instead of a checkbox; any tool that reads that screen by its old cell positions could stop working correctly.

Why it matters: Any SEO or content-ops tooling that bulk-edits titles or metadata through the WP admin post list via CSS/JS selectors should test against a 7.1 pre-release build now, before the August 19 release ships the change live.

Our take: I've argued that machines, agents as much as screen readers, depend on semantic roles rather than positional selectors to parse a page correctly, and that degraded structure measurably hurts task success. WordPress fixing this exact failure mode in its own admin tables is a reminder that the plugins most likely to break are the ones that targeted th and td by position instead of reading the semantic row-header role screen readers actually rely on.

- [Make WordPress Core - Post list tables row headers changed](https://make.wordpress.org/core/2026/08/03/post-list-tables-row-headers-changed/)
- [Search Engine Journal - WordPress 7.1 Accessibility Change May Break Some Plugins](https://www.searchenginejournal.com/wordpress-7-1-accessibility-change-may-break-some-plugins/584820/)