Eye surgery is irreversible in ways that shape patient behavior. A LASIK candidate reads about every laser platform within driving range. A cataract patient compares premium intraocular lens options. A diabetic retinopathy patient wants a retina specialist, not a general ophthalmologist. Search queries reflect that: "refractive cataract surgeon Tampa," "vitreoretinal surgeon Aetna Atlanta," "glaucoma SLT laser Denver" all need a surgeon-and-procedure match.

SleekRank reads a roster sheet with slug, surgeon name, fellowship subspecialty (cornea/refractive, vitreoretinal, glaucoma, oculoplastics, pediatric ophthalmology), procedures performed, laser and IOL technology used, board certification, hospital and ASC affiliations, accepted insurance, and city. Each row renders through one base WordPress page, so /eye-surgeons/dr-naomi-rivera-cornea-tampa/ surfaces the fellowship, procedures, technology, and accepted carriers.

Selector mappings push fellowship into the page H1 and the schema description. List mappings render procedures, technology, and insurance carriers. Define a /eye-surgeons/{procedure}/{city}/ page group and the same roster builds per-procedure hubs (LASIK, premium cataract, vitrectomy). Cache the source for a day, flush rewrites, and the directory rebuilds itself when a row changes.

Ophthalmology is the specialty where the fellowship after residency determines almost everything a patient cares about. A cornea/refractive fellow performs LASIK and premium cataract; a vitreoretinal fellow does vitrectomies and treats macular degeneration; a glaucoma specialist runs MIGS and trabeculectomies; an oculoplastic surgeon does blepharoplasties and tear-duct repair. Lumping all five into one general ophthalmologist directory wastes the patient's time and the search engine's signal.

The patient who needs a retina surgeon for a detachment cannot afford to call the wrong subspecialty. A sheet-driven directory promotes fellowship, procedures performed, laser and IOL technology, ASC affiliation, and accepted insurance to first-class data, then slices them with URL patterns so a patient searching for a vitreoretinal surgeon in Atlanta lands on a page that surfaces the right two or three names. The directory operator updates one cell when a surgeon adds a new IOL platform or signs a new insurance contract, and that change propagates across the surgeon page, the procedure hub, and the city hub once the cache flushes.

The data layer becomes the SEO surface, and the SEO surface stays accurate because it shares one source with the practice's credentialing roster.