El Pilón Criollo
A family-run Puerto Rican steam-table kitchen on La Avenida with 4.5 stars across more than a thousand Google reviews — and nowhere online that they control. Built on spec: four bilingual pages, a full schema layer, and a domain plan the owner actually holds.
This one wasn't commissioned. I found the restaurant, researched it, and built the site on spec before asking for the work — so what follows describes a build and a set of findings, not a result. Nothing on this page is a performance claim. There is no traffic data, because it isn't live on their own domain yet.
No website. And their name pointing at a casino.
El Pilón Criollo has fed North Clinton Avenue for years. What they didn't have was anywhere online they owned — and the obvious domain, once theirs, had lapsed and now serves an offshore gambling site under the restaurant's own name. The rest compounds it: their own Instagram captions list a phone number that isn't theirs any more, the hours on their listings disagree with each other, and a whole line of business — catering and party trays — is invisible everywhere. Meanwhile the strongest asset they have, a hand-painted mural on the building, appears nowhere online at all. Across roughly eight Puerto Rican restaurants in Rochester, exactly one has a website of any kind, and none has a menu a search engine can read.
Four pages, two languages, one owner who holds the keys.
- Four bilingual pages, matched line for lineHome, menu, about and contact — each with its own title, description and canonical, and 132 matched EN/ES string pairs so every line of copy exists properly in both languages rather than as a machine-translated afterthought.
- A menu a search engine can readTwenty-three menu items in structured data across five sections — in a market where no competitor has any. The menu is laid out as a line of steam-table pans, because that is how you actually order there.
- Every business fact verified, not assumedHours, phone, address and geo-coordinates were checked against the restaurant's own managed ordering page and confirmed with the owner — because the three places those facts live currently disagree with each other, and a site that repeats the wrong number just multiplies the problem.
- A deliberate omission
aggregateRatingwas left out of the schema on purpose. The reviews are real and excellent, but marking them up on the business's own site is the kind of thing that gets a listing flagged rather than rewarded. - A domain plan that ends the exposureRegister in the owner's name, on her card, with her email — and specifically don't buy the hijacked domain back, which only rewards the squatter. The Google Business Profile stays in her account, and the site is static and in version control, so nothing here is rented.
Built, verified, and waiting on three things.
This is a build and a set of findings, not an outcome. Being measured, once it's live on a domain the owner holds: search visibility for the catering line that's currently invisible, and whether a readable menu earns the map-pack position no competitor is contesting. I'll add real figures here when there's enough data to stand behind — and not before.