Specialty grocery searches are recipe-driven. "Where to buy gochujang Atlanta," "Italian deli Boston," "specialty cheese shop Charleston," or "Mediterranean market Phoenix" pair cuisine, ingredient, and city in queries a generic supermarket archive cannot rank for.

SleekRank reads a Google Sheet with one row per store and columns for cuisine focus (Italian, Asian, Mediterranean, Latin), signature ingredients carried, hours, prepared foods availability, and city. Each row renders through one WordPress base page that matches the site theme. Update the sheet when an import line changes, and the directory mirrors the change.

Signature ingredients are what shoppers actually search for. Map a curated list of hard-to-find items (gochujang, lardo, true Parmigiano, Aleppo pepper) to a visible block on the page. A recipe-driven shopper searching for an ingredient picks the store that surfaces the ingredient on its page over the one whose page lists only the cuisine label.

Specialty grocery search is the most recipe-driven retail tail there is. A home cook making a Korean stew searches "where to buy gochujang Atlanta," not "specialty grocer near me." The rankable surface is cuisine x ingredient x city, which multiplies across any meaningful directory of specialty stores. Per-store pages capture the brand-plus-city tail; per-cuisine hubs collect stores by culinary tradition; per-ingredient hubs capture the recipe-driven discovery layer that converts the highest-intent searches.

Maintaining all three by hand fails when imports shift weekly. SleekRank ties the SEO surface to the operations sheet so the same person tracking import deliveries updates the page that ranks for those imports. Cultural authenticity comes from data: signature ingredients carried by a Levantine market in Phoenix versus a Persian market in Phoenix are different even when both rank for Middle Eastern grocery, and the data layer surfaces that distinction across hundreds of stores.