A drug-resistant epilepsy patient searching "epileptologist Pittsburgh" wants the closest NAEC level 4 center and the named physicians who staff its EMU, not a national AES member list. Neither NAEC nor AES ships city landing pages, so the result belongs to whoever does build them and ranks at metro level for that intent.

The data layer holds 250 US cities anchoring an NAEC level 4 center, with epileptologist counts, EMU bed counts, annual resective surgery volume, and laser ablation availability. Each row maps to one URL via the slug column. ep_count drives the hero stat, emu_beds a stat block, and a JSON column of named physicians feeds a card grid.

The base page stays a normal WordPress page in your existing theme. Gutenberg, Bricks, or classic markup all work because SleekRank operates on rendered HTML. The XML sitemap auto-includes every /epileptologists/{slug}/, and stale rows 404 cleanly when a center drops accreditation.

Epilepsy surgery and EMU evaluation are regional. Drug-resistant patients and their referring neurologists pick a level 4 center based on distance to the EMU, surgical volume, and named epileptologists, not a national NAEC PDF. That is why "epileptologist near me" and "epileptologist [city]" together pull more monthly searches than national specialty queries.

A PDF and a search form cannot win those queries against a competitor who shipped a real URL for each metro. Google ranks pages, not query parameters. The cities that rank carry specifics: epileptologist counts, EMU bed counts, annual surgical volumes, laser ablation flags, named lead physicians.

Maintaining that uniqueness across 250 NAEC metros by hand is unrealistic. Maintaining it across 250 rows in a sheet your operations team is already updating yearly is a single afternoon of mapping work. SleekRank turns the joined NAEC and AES sheet into the SEO surface that owns drug-resistant epilepsy intent.