Yes. ssa.gov publishes the field office locator with full data for each office, accessible via a public JSON endpoint used by the locator widget. A periodic full pull stored as a local file is the practical pattern, since the data refreshes slowly.

SSA office hours change rarely outside federal closures. A weekly cache refresh is enough for the main fields, with a daily refresh on a closures column that drives a banner. Major schedule changes get rolled into the source feed manually as they are announced.

Most SSA business can be scheduled by phone (1-800-772-1213) or online at ssa.gov. Some services (disability intake, certain identity-document reviews) require an in-person visit. The per-office page should explain that distinction clearly and link to the right scheduling path.

SSA's my Social Security account handles benefit statements, address updates, direct deposit changes, and benefit applications. Each per-office page should reference the online alternative for services that don't require in-person handling, which reduces foot traffic and is genuinely helpful.

GovernmentOffice with PostalAddress, openingHoursSpecification, geo coordinates, serviceType entries, and a parentOrganization pointer to the Social Security Administration. Render the JSON-LD via a tag mapping; the structure is identical across pages, only the field values vary.

Yes. SleekRank handles 1,200 to 1,500 URLs without strain, and Google crawls a corpus that size on a sensible cadence. State-aggregate pages add another 50 to 60 URLs for a total below 1,600, plus service-aggregate pages for disability, card replacement, and benefit verification.

Add an officeType column to the source (field office, card center, resident station, contact station). Resident and contact stations have limited hours and limited services, so the template renders a different services block and a clear notice when the office is a part-time facility.

Yes. Medicare enrollment is handled through SSA, so per-office pages naturally rank for queries like "Medicare enrollment {city}". A dedicated Medicare section on the template (with State Health Insurance Assistance Program contacts pulled from a parallel dataset) extends the page's relevance without adding load to the SSA roster.