Skip to content
Get Ranked On TopIllustrative case studySignal plan

A fictional business. The figures are a modelled scenario, not a client result.

URPI PICANTERÍA · GROUP OF 5 PICANTERÍAS · CUSCO

How five Cusco picanterías turned photographed menus into dishes Google can read

+64%

organic reservations a month · 410 → 672

9 months · Latin America · Hospitality & food · Signal plan

M1M2M3M4M5M6M7M8M9
How to read it: each cord is a month. Knots near the top count hundreds, the middle ones tens, and the long knot at the bottom counts units, the way Inca record-keepers did.

THE TANGLE

Five kitchens, and a menu no search engine could read.

Menus were photos, bookings ran through a third-party widget, and Spanish and English pages duplicated each other, so no dish ever surfaced in search.

Urpi’s five picanterías serve what Cusco families eat on a Sunday: rocoto relleno, adobo, chiriuchu in June. Travellers search for exactly those names, in Spanish and in English. But every menu was a photo of a chalkboard or a designed PDF, so to a crawler each one was a single image with a file name.

Bookings ran through a partner’s widget on another domain, which ranked above Urpi for its own name. And every page existed twice, once in Spanish and once in English, with nothing to tell Google they were one page in two languages.

WHAT THE AUDIT FOUND

  1. 11

    image menus, zero words

    Eleven JPG and PDF menus across five sites. No dish, price or allergen existed as text, and the largest file weighed 4.2 MB on mobile.

  2. 212

    pages published twice

    Spanish and English copies with no hreflang and canonicals pointing both ways, so Google showed whichever it picked, often in the wrong language.

  3. 4 of 5

    locations outranked for bookings

    The booking partner’s listing beat Urpi’s own site for “urpi picantería reservas” in four of the five neighbourhoods.

  4. 5.8 s

    mobile LCP

    The menu photo was the largest element on every page. No Restaurant, Menu or MenuItem schema anywhere, and no opening hours a crawler could parse.

THE KNOTS

Four kinds of knot, tied in order.

Built on our Signal plan: technical SEO for sites where what a crawler can parse decides whether you exist at all.

  1. SINGLE KNOTS · NAMES

    HTML menus

    Menus rebuilt as text, one page per picantería

    Eleven JPG and PDF menus became HTML: every dish an element with its name, a short description and a price, in Spanish and English. The photos stayed, as pictures with alt text, compressed from 4.2 MB to under 200 KB, which took mobile LCP from 5.8 s to 2.1 s.

    74 dishes · 148 items

  2. LONG KNOTS · PRICES AND DIETS

    Menu & Restaurant schema

    Restaurant, Menu and MenuItem schema from the kitchen’s own sheet

    The spreadsheet the chefs already kept now generates the JSON-LD: a Restaurant per location with address, hours and servesCuisine, a Menu with its sections, and MenuItems carrying offers in soles and suitableForDiet. Validated on every publish.

    5 Restaurant entities

  3. SUBSIDIARY CORDS · LANGUAGES

    Hreflang

    One Spanish and one English page, paired

    212 pages existed twice with no hreflang and mixed canonicals, so Google picked one at random. Each pair now declares es-PE and en, with x-default on Spanish, and the English menu uses the kitchen’s own translations instead of a browser widget.

    212 → 0 duplicates

  4. PRIMARY CORD · RESERVATIONS

    Reservation markup

    Bookings that start on Urpi’s own pages

    The partner widget lived in an iframe on another domain, so its listing outranked Urpi in four of five locations. Each location now has a first-party reservation page, declared through acceptsReservations and a ReserveAction, with the partner’s booking engine embedded underneath.

    Brand bookings won back

THE MENU QUIPU

Each cord is a dish. Each knot is something Google can read.

Pick a dish, switch between the old photo menu and the rebuilt one, then untie knots one by one to see which part of the search result each of them feeds.

NamePrice ×10Price ×1DietLanguage

24 of 24 fields readable across the menu

Knots on the cords

 

What Google reads

Rocoto relleno: 4 of 4 fields readable.

urpi.example › es › carta

Rocoto relleno · Urpi Picantería

Hot rocoto pepper stuffed with spiced beef and baked under fresh cheese, served with pastel de papa.

PriceS/ 38.00
DietNo dietary claim
LanguageAlso in English: Stuffed rocoto pepper

Markup Google receives

{  "@type": "MenuItem",  "name": "Rocoto relleno",  "offers": { "@type": "Offer", "price": "38.00", "priceCurrency": "PEN" },  "inLanguage": "es-PE",}<link rel="alternate" hreflang="en" href="https://urpi.example/en/menu/#rocoto">

MONTH BY MONTH

Nine months, nine cords.

  1. MONTH 1

    Audit

    Crawl and render tests of five sites, Search Console and booking data: 11 image menus, 212 duplicate pairs, zero structured data.

  2. MONTH 2

    The menu sheet

    One shared spreadsheet of 74 dishes: names in both languages, prices, allergens and diets, signed off by each head chef.

  3. MONTH 3

    First HTML menus

    San Blas and Plaza Regocijo menus go live as text; photos compressed and given alt text.

  4. MONTH 4

    Hreflang

    Spanish–English pairs mapped; hreflang, canonicals and x-default shipped across all five sites.

  5. MONTH 5

    Schema

    Restaurant, Menu and MenuItem JSON-LD generated from the sheet and validated every night.

  6. MONTH 6

    Every menu as text

    Wanchaq, San Sebastián and Urubamba rebuilt; the last duplicate pages resolved.

  7. MONTH 7

    Reservations

    First-party reservation pages with a ReserveAction; the partner widget moves underneath.

  8. MONTH 8

    Festival dishes

    Seasonal dishes, chiriuchu for Corpus Christi among them, added through the sheet in an afternoon.

  9. MONTH 9

    Count and hand over

    Dish searches, reservations and rich-result coverage reviewed; the sheet-to-schema pipeline handed to the team.

THE TALLY

Nine months on, the cords add up.

+64%

Organic reservations a month
410672M0M3M6M9

0 → 148

Menu items readable as text
San Blas36Plaza Regocijo28Wanchaq32San Sebastián24Urubamba28SpanishEnglish

212 → 0

Duplicate ES/EN pages
212M0M3M6M9

120 → 2,940

Clicks from dish searches a month
1202,940M0M3M6M9

Modelled scenario for a fictional business — not a client result. Rankings and traffic are never guaranteed; see our Terms.

DISH SEARCHES, AS TYPED

Google position for six dish and booking searches in Cusco, before the work and in month 9.
SearchLanguageSearches / moMonth 0Month 9
rocoto relleno cuscoSpanish2,400not in top 502
picantería cuscoSpanish1,900141
vegetarian restaurant cuscoEnglish1,300not in top 504
chiriuchu cuscoSpanish880not in top 501
urpi picantería reservasSpanish72061
gluten free food cuscoEnglish590not in top 503

YOUR NEXT CORD

Is your menu still a picture?

If your dishes, prices or bookings live in images, PDFs or someone else’s widget, search engines can’t count them. Start with the Signal plan, or tell us what your kitchen serves.

Back to all case studies