Saffron Restaurant & Lounge

Saffron's first September on the new site, by Google's own count. These are the restaurant's Business Profile numbers, September 2026 against September 2025.

Google reports the change; the 2025 figures are worked back from it, so treat them as approximate. What these numbers do and do not show is under The found, below.

The challenge

Saffron Restaurant & Lounge serves modern Persian food on North Palm Canyon Drive, in the Uptown Design District of Palm Springs. It has an OpenTable award for visitor experience and a dining room people drive out from the whole valley for. What it did not have was a website that let anyone find it.

The old site was built on Wix, and since 2025 its menu and about pages had carried <meta name="robots" content="noindex">. That tag is an instruction to search engines to leave the page out of the index, and Google obeyed it: the homepage was the only page of the site in the index, so the page people want most from a restaurant, the menu, could not be found from Google at all. Searching for the restaurant by name returned Yelp, OpenTable, Tripadvisor and the visitors bureau, all ranking with the restaurant's own information, on pages the restaurant does not control. The sitemap the robots file advertised returned a 404. Two pages still carried the Wix template's name in the title, so they read "About | Lawrence" and "Contact | Lawrence". The structured data listed hours that contradicted the hours on the site, and the hours on every listing. Not one of the five pages had a meta description. We scored it at 33 out of 100.

Underneath the search problem was a legal one. We ran a WCAG 2.1 AA review, because a restaurant with a dining room is squarely covered by the ADA, and in California any ADA violation is automatically an Unruh Act violation with statutory damages attached. We confirmed 17 issues by hand: 5 critical, 7 high, 4 medium, 1 low. The worst of them was the navigation. The "More" menu opened on hover only, so a visitor using a keyboard or a screen reader could not reach the Contact page or the Menus page from the navigation at all.

The road

We told them what was real first. Automated scanners reported 255 contrast errors across the five pages. We re-measured every one in a live browser, and 122 of them, all on the menu page, were false alarms caused by the menu app styling itself late during the scan. The real menu text measures about 18:1. We reported the 17 we could stand behind, because a client who pays to fix problems that do not exist has been sold a report, not a repair.

Then we rebuilt the site instead of patching it. Ten pages of hand-written HTML with no build step, deployed on Vercel: home, menu, happy hour, events, about, press, reservations, an accessibility statement, a privacy page and a real error page. Fonts self-hosted, so the site loads no third-party font service and the content security policy does not have to allow one. Every photograph ships in AVIF and WebP alongside the JPEG, and stylesheets and scripts are fingerprinted so a browser can cache them for a year and still get the new one the moment it changes.

Accessibility went into the build rather than on top of it. Real headings in order, one H1 per page, images described rather than named after the camera file, everything reachable and operable from a keyboard, and a menu that is text on a page rather than a picture of a menu. The consent banner gives Decline the same size and weight as Accept, and analytics does not load at all until somebody agrees.

The foundations Google and the assistants read. A schema graph tying the restaurant to its menus, its opening hours, its awards and its Google Maps listing, with a WebPage node and a real modified date on every indexed page. A sitemap, a robots file and an llms.txt. The events page is regenerated from the restaurant's Google Calendar by a scheduled job, and the job is written to fail loudly rather than let the page keep advertising a night that has already passed.

And the listing that sits next to it. Most people meet a restaurant in Google Maps before they meet its website, so the Business Profile got the same attention. Its website button is tagged so those clicks show up in Search Console, and it sent 88 of them in its first week. The menu link moved off an insecure http:// address that had been shown 760 times in a single week. The description and categories were rewritten around what the place actually is, a Persian restaurant that is also a bar, a lounge and a Mediterranean kitchen, and the photo count went from 164 to 183. Google's own card now shows the real price range, $30 to $70, instead of a lone "$". And seven recent reviews got warm, personal replies instead of silence.

The found

The cutover happened on 2 September 2026. By the next day all nine indexable pages were in Google, the menu and about pages included, and every page we inspected came back as "Submitted and indexed". We rescored the site at 94 out of 100. Lighthouse put the homepage at 98 on a phone and the reservations page at 100 on desktop, with a search score of 100 on the home, menu and reservations pages. Those are lab scores. The site does not have enough traffic yet for Chrome to report real-visitor speed, so we are not claiming it.

One thing to say before the rest of the numbers. Search Console and Google Analytics went in on launch day, so there is no Wix-era traffic to compare against, and the restaurant had been closed for August anyway. What follows is the restaurant's first month on the new site, 2 September to 3 October, not a before and after.

Search. Google showed the site 7,575 times and sent 707 clicks. The busiest week, 16 to 22 September, drew 82% more impressions than the first. Saffron sits at position 1 for "persian restaurant palm springs" and "persian food palm springs". Most clicks still come from people searching for Saffron by name, about 474 of the 707, which is what you would expect from a site that used to be invisible. The cuisine searches are where it is only starting to show: 1,386 impressions and 44 clicks so far, and that is the next stretch of road.

Visits and bookings. 869 visits from 567 people, 65% of them engaged, and half of them arriving from Google search. From 12 September, when we started counting, visitors pressed the Reserve button 67 times and the call button 13 times. That is about 11.5 reserve clicks for every 100 visits, and 14 in the best week. These are clicks through to OpenTable, not completed reservations, and they are a floor, because visitors who decline cookies are not counted.

AI assistants. By 27 September, ChatGPT named Saffron its top pick for "best Persian restaurant in Palm Springs", and it was reading the restaurant's own about page to answer. For "Mediterranean food with good cocktails in Palm Springs" it moved from second of five to first of six in eight days. AI assistants sent only 13 visits all month, but those visits produced 6 reserve clicks and a call, the best booking rate of any source.

The Google listing. In the map results Saffron held first place for "persian restaurant palm springs" and third for "mediterranean restaurant palm springs" through most of September, ahead of competitors with far more reviews: by review count it was 15th of 19. Google's own Performance report for the profile is the table at the top of this page.

September 2026 was the shorter month for the restaurant, which reopened on the 2nd and is dark Mondays and Tuesdays, and it still beat a full September 2025. The new site and the listing work landed in the same month, so this is what happened after the relaunch, not proof of which change did it. The detail we like best is in the search terms: the profile appeared 2,210 times for "restaurants" and 410 times for "saffron". Most people found Saffron while looking for somewhere to eat, not while looking for Saffron.

Saffron served its last night at 1107 North Palm Canyon on 3 October and reopens at a new address in December. The site went into a temporarily closed state that weekend: the Reserve button became links to follow the restaurant on Instagram and Facebook, the opening hours came out of the schema so Google stops promising a table, and the printed flyer QR code still works. The listing was marked temporarily closed, not permanently, so all 175 reviews stay with it. When the new room opens, everything this month built moves with it.