# Campus guides

[All work](https://sulayman-bowles.dev/work)

I run ten college-town guides that show students what a lease really costs and how to get around campus, all built on one shared engine.

ProblemEngineDataSearchJudgment

## Signing a lease shouldn’t take a dozen tabs

A first-year student signing a lease pieces together rent, required fees, the walk to class and the bus route from a dozen tabs, most of them written by someone selling the apartment. The guides put those answers on one site per college town: housing with the full monthly cost, classes and grade history, clubs, maps and the money a student will spend.

It started in June 2026 as one apartment-comparison site. Three more guides joined on November 5 and six on November 16. AI coding agents write most of the code, copy and design under rules I set. I set the direction and make the calls that change it: what to build, what to cut and what needs my approval. The ten guides, one per campus, are linked at the end of this section.

**The network on November 18, 2026**

| Measure | Count |
| --- | --- |
| Live guides | 10 |
| URLs in their sitemaps | 12,144 |
| Properties the rent collector tracks | 208 |
| Asking-rent and offer history | 37,803 observations |
| Rows in the shared campus-data API | 44,759 |

The property count is from November 17.

- [UT Austin · utaustin.guide](https://utaustin.guide/)
- [Texas A&M · collegestation.guide](https://collegestation.guide/)
- [Texas Tech · lubbock.guide](https://lubbock.guide/)
- [Texas State · sanmarcos.guide](https://sanmarcos.guide/)
- [UNT and TWU (Denton) · denton.guide](https://denton.guide/)
- [UCLA · westwood.guide](https://westwood.guide/)
- [Purdue · westlafayette.guide](https://westlafayette.guide/)
- [Illinois (UIUC) · urbanachampaign.guide](https://urbanachampaign.guide/)
- [UCF · orlandocampus.guide](https://orlandocampus.guide/)
- [UConn · storrs.guide](https://storrs.guide/)

## One engine, ten settings files

The first guides were three separate codebases. A November 12 audit found 126 same-named files that had drifted apart and 25 to 39 post-build passes in each build, so every new campus now goes through one shared engine. A campus is a settings file and a data folder. One command scaffolds a new one, and a check stops one campus’s text from leaking into another’s pages.

The engine’s last build step holds every page to one standard: one type scale, one main heading, a breadcrumb that matches the structured data search engines read, and a Markdown copy of the page for AI agents. Before it, the guides carried 100 to 222 font sizes each and up to 20 shapes of structured data.

Each guide has one release slot on Cloudflare. A release reads the live deployment first, deploys, reads the changed pages back, then pings search engines through IndexNow with only the pages that changed.

## Rent is checked every hour, and an unknown fee stays unknown

A listing shows a headline rent. The amount a student pays depends on required fees, the payment schedule and who qualifies for the price. A Cloudflare Worker checks published property pages every hour, up to eight properties a run, and each rent appears with its basis, required fees and the date it was checked. It launched on November 3 with 94 properties; the registry held 208 by November 17.

When a fee isn’t published, the page says so instead of estimating it. Self-hosted vector maps are live on all ten campuses and never ask for the device’s location. The oldest guide also times walks between buildings on real paths.

## One guide went from 303 to 6,370 daily impressions in four days

Every page is built to be quoted: the answer in its first lines, structured data, a Markdown copy and an llms.txt entry. From November 11 to 17 the ten guides drew 34,102 Google impressions and 180 clicks. The fastest grower went from 303 impressions a day on November 13 to 6,370 on November 17.

That same week, three of the older guides lost 86% to 97% of their daily impressions from their peaks, during Google’s November core update. The cause isn’t settled yet.

**Daily Google impressions to November 17: each falling guide from its peak, the growing guide from November 13**

| Guide | From | November 17 | Change |
| --- | --- | --- | --- |
| Largest guide | 2,504 on November 12 | 74 | −97% |
| Second guide | 2,291 on November 13 | 121 | −95% |
| Third guide | 1,473 on November 14 | 208 | −86% |
| Fastest-growing guide | 303 on November 13 | 6,370 | 21× |

Google Search Console web search figures.

## I cut 6,042 pages nobody had seen

On the largest guide, 6,042 single-course pages had no impressions from November 1 to 18. I set them to noindex and took them out of the sitemap, which now holds about 4,000 URLs, and I’ll check the result around December 1. A page earns a sitemap slot when it answers something a student searches for. A row in the course catalog isn’t enough.

Running agents taught me the expensive part isn’t writing code. It’s re-reading. From November 5 to 12, 98% of the 13.1 billion tokens my Claude agents used across my projects went to re-reading context. The rules now say one task per session, smaller models for hands-on work and cross-guide work built once in the shared engine.

Method & limits: search figures are Google Search Console data through November 17. No guide has reached my goal of 1,000 visitors a month yet; the best drew 49 clicks in its latest week.

[All work](https://sulayman-bowles.dev/work)[Continue with Chegg](https://sulayman-bowles.dev/work/chegg)

---
Source: https://sulayman-bowles.dev/work/campus-guides · Sulayman Bowles
