Knife sharpening queries split by knife type and service model. A chef searching for "japanese knife sharpening Brooklyn" wants someone trained on single-bevel edges, while a hunter typing "hunting knife sharpener mobile service Boise" wants someone with a van. "Restaurant knife service Chicago" pulls a third audience entirely, with weekly pickup contracts. A single archive page cannot rank for every knife-type-and-service combination.

SleekRank reads a Google Sheet of sharpeners and uses one base WordPress page as the template. Each row becomes a URL like /knife-sharpeners/edge-craft-japanese-brooklyn/ with shop name, knife specialties, service model (drop-off, mail-in, mobile, restaurant), turnaround, and price ranges mapped into the right elements. A second page group filters by service_model and emits /knife-sharpeners/mobile/{city}/ and /knife-sharpeners/restaurant/{city}/ pages.

The service model column drives intent matching. A mobile sharpener parked at a farmers market does not compete with a destination shop charging Japanese-knife specialty rates. Map service_model to a hero badge so the searcher sees the format match before scrolling. Add a row when a new sharpener launches a route; edit turnaround when the shop adjusts its backlog. The directory updates without touching WordPress.

Knife sharpening is three products in one trade. A mobile sharpener working farmers markets does completely different work than a destination shop specializing in Japanese single-bevel edges, and a restaurant pickup contract is a third business model on top of those. Forcing all three onto one archive page sacrifices ranking power for every variant and frustrates searchers who came with a specific format in mind.

Mobile route customers want a schedule, restaurant buyers want a contract structure, and home cooks with a Japanese chef knife want a specialist who knows waterstones. A sheet-driven approach surfaces service model, knife specialty, turnaround, and pricing as data on each URL. Multiple page groups slice the roster into URL shapes that match how searchers actually look.

When a shop adds a Saturday market or shifts a restaurant pickup day, that single sheet edit propagates to every page that surfaces the schedule. The cache refresh rebuilds the affected rows on next request. The directory becomes accurate by default rather than accurate when someone remembers to manually update each per-format page.