Same leasing site. Completely different nervous system. Here's what shipped — and why it's built for search engines that don't even use a search results page anymore.
Short version: Pine Ridge went from a single 336-line file doing everything to a real content platform — and it's now built to be found, understood, and cited by AI assistants, not just Google.
By 2026, a real slice of apartment search happens inside an AI assistant — "find me a pet-friendly 2-bed in Chubbuck under $X" — not a row of blue links. A site optimized only for classic crawlers is invisible to that traffic. So this rebuild treats AI discoverability as a first-class requirement, not something bolted on after launch.
llms.txt, an agent-facing discoverability file, and ApartmentComplex + FAQPage + BlogPosting schema that all regenerate automatically every time staff hit publish.llms.txt both rebuild from the same posts table, so the classic-SEO surface and the AI-search surface never drift apart.Pulling auth into shared middleware and applying it uniformly across every staff route surfaced a gap: two endpoints had been missing the same check every neighboring route already enforced. Refactoring properly caught it as a side effect — not a follow-up patch.
Four weeks in, GA4 shows 7 users arriving via an AI Assistant referral — a small number next to organic search, but traffic that would have been literally invisible to a site without structured data and an llms.txt for an assistant to draw from in the first place. Full numbers, the before/after code, and the technical deep-dive are in the case study.