Add a certificationExpiry column to the roster sheet and run a quarterly audit comparing expiry dates against today. Flag expired rows for re-verification, update the kitchen status to under-review while waiting, and let the cache flush propagate the status change to every URL referencing the venue.

Yes. The kitchenStatus column carries values like dedicated, shared-with-protocols, or unverified. Each value drives a clear badge on the venue page and a filter for per-status hub pages. Diners can find dedicated-only directories in a single click without ambiguity.

No. SleekRank renders whatever the source sheet says. Verification is an editorial process the maintainer performs by visiting venues, contacting chefs, and checking certification body listings. SleekRank just keeps the published directory in sync with the verified data.

Update the certification column to expired or move it to a verified-expired status. The badge disappears or changes on the next cache flush. Most directories then schedule a follow-up visit and update the column again once the venue renews or formally drops certification.

Yes. Add a crossContactPolicy column with structured text covering fryer separation, surface handling, and utensil protocols. Map it to a selector so each venue page renders the policy in a consistent format. Trust scales with detail per URL.

Yes if you add columns. An allergensServed column listing nut-free, dairy-free, and soy-free options drives additional badges and filter pages. The architecture is the same as gluten-free: one column per allergen, one filter per column, one hub page per filter value.

City-level hub pages roll up venues by city via a list mapping filtered on the city column. Add country and region columns to build broader hubs for celiac travel guides. A traveler researching Naples can land on a per-city hub listing every verified pizza shop and bakery.

Yes, because each page carries unique kitchen-handling content that matches specific long-tail queries. Pages ranking for "dedicated gluten-free bakery Toronto" need that exact phrase and surrounding context in the URL. A generic filtered archive cannot offer that specificity, which is why per-row pages win the niche.