Sweetgreen has built 300 strong location pages: each has Restaurant structured data with hours, phone, geo and a featured menu, plus calories and protein per item. That is exactly the data an AI assistant or search engine needs to answer "healthy lunch near me" or to order for a guest. Yet none of the 300 is in the sitemap, which instead lists old sweepstakes rules and dated privacy policies, and every title is double-escaped, so search results and tabs read "Order Salads & Bowls in Philadelphia".
First action
Fix the title template and publish a locations sitemap.
How to measure it
Search clicks to /locations/ pages
- Now
- –
- Target
- +25%
- By
- 90 days
Steps
Build the sitemap
All 300 store URLs, canonical form, real lastmod dates.
Web team 1 day
List it
Add to robots.txt and submit in Search Console.
Web team 1 hour
Fix titles
Escape "&" once in the page title template.
Web team 1 hour
Tidy links
Directory links use the trailing-slash URL.
Web team 2 hours
Prune the old sitemap
Drop past sweepstakes, old policies and preview pages.
Web team 1 hour
Baseline
Indexed store pages, impressions and Order clicks.
Sr. Product Manager, Menu, 3P & Agentic Ordering 1 day
Track
Weekly in Search Console and analytics.
Sr. Product Manager, Menu, 3P & Agentic Ordering weekly
Why it works
Generate a locations sitemap from the same data as the /locations/ directory (300 URLs with trailing slashes, lastmod from hours or menu changes) and add it to robots.txt. Fix the title template so "&" is escaped once. Point the directory's links at the canonical trailing-slash URLs. Then submit the sitemap in Search Console and watch indexed pages, impressions for "sweetgreen <neighbourhood>" and clicks to Order pickup.
Location pages are where near-me searches and AI answers land, and the new agentic ordering role needs these pages discovered and trusted before agents can use them. Owned digital is now 38.8% of sales; every guest who finds the store page instead of a marketplace listing is a cheaper order. Speed is not the problem (real visitors already pass Core Web Vitals); discovery is.
Ready to use
ChecklistLocation page SEO check
[ ] /locations/sitemap.xml with 300 canonical URLs [ ] Listed in robots.txt and Search Console [ ] Title shows "Salads & Bowls" (single escape) [ ] Directory links use the trailing-slash URL [ ] New openings added automatically [ ] Old sweepstakes and policy versions removed from sitemap.xml [ ] Weekly report: indexed, impressions, Order pickup clicks
Risks and how to handle them
New stores missing from the sitemap
Generate it from the same source as the directory, so openings appear automatically.
Evidence
- Your websiteThe /locations/ directory links 300 restaurant pages (its ItemList says numberOfItems 300). Each page carries Restaurant and LocalBusiness structured data with address, phone, geo, opening hours and a featured menu with item descriptions and images, shows calories and protein per item, and says whether "This location offers catering". Every sampled page title reads "Order Salads &amp; Bowls in <city>" (double-escaped), so tabs and search results show "&" instead of "&". Each page is about 520 KB of HTML and answers at both /locations/<store> and /locations/<store>/ (the canonical).Source
- Your websiteSitemaps (checked October 22, 2026): sitemap.xml lists 48 URLs and landing/sitemap.xml 7 more. None of the restaurant pages under /locations/<store> is listed. The sitemap does list past sweepstakes rules (naomi-sweeps, surfboard, cabbage day), two dated old privacy policies, a "terms-of-use-agreement-july-preview" page, /styleguide, /brand-refresh (2021) and the Sweetpass+ FAQ.Source
- HiringSr. Product Manager, Menu, 3P & Agentic Ordering (Los Angeles, posted August 20, 2026): owns "third-party delivery marketplaces and new channels such as agentic ordering, where guests order through AI assistants and agents"; will "Define how sweetgreen's menu, customization, pricing, location, and checkout show up when an AI agent orders for a guest" and "Shape the structured data, APIs, and guardrails that make agent-led orders accurate"; and build "menu publishing and syndication, so a single change flows correctly to every channel", including Infinite Kitchen constraints and 86'ing.Source
- Company resultsSecond quarter 2026 (quarter ended June 28, 2026): revenue up 3.8% to $192.7 million with 36 net new restaurants; same-store sales down 6.2% (traffic down 2.0%, product mix down 4.2%, tied to more promotions, a shift toward wraps and removing ripple fries); total digital revenue 66.3% of sales and owned digital 38.8% (from 33.4%); restaurant-level margin 13.1% versus 18.9%.Source
- PageSpeed testGoogle PageSpeed for the sweetgreen.com homepage (October 22, 2026): real Chrome visitors (Chrome UX Report, 75th percentile) see the main content in 1.7 s, taps respond in 104 ms and layout shift is 0, so the site passes all three Core Web Vitals; load time is steady (4% faster than a year earlier).Source