Bhavana's Week 06: The Wide-Angle Page
Finishing a directory page forces a whole-surface review, and that wider view catches a hard-crash date bug and a dead sitemap link a narrow check missed.
Some bugs only show up once you stop staring at one page and look at the whole system at the same time. Building the directory page for a job search app, the page meant to tie every listing together, forced exactly that kind of review, and the wider view caught two bugs that a narrow, file-by-file check had missed entirely.
The directory as a wide-angle view
The directory brings every verified company into one place, with each entry cross-linked back to the city and role pages it belongs to. Before the directory existed, those pages were disconnected islands with no path between them. Finishing the directory turned scattered pages into a surface that reinforces itself for both visitors and search crawlers, and building it required the first whole-surface review of the system.
What a whole-surface review actually means
The method is simple to describe and easy to skip: trace the system end to end, check that every cross-file reference actually resolves, and check every input that could throw an error, all at once rather than one template at a time. That discipline, reviewing the whole surface instead of one page in isolation, is what caught the two bugs hiding in the gaps between pages.
The hard crash: a date formatter with no guard
The first bug was in the date formatter, caught while reviewing it one more time before calling the JSON-LD work finished. There was no guard against a malformed date. A single bad value on one job record wouldn't just skip that field quietly, it would throw and take the entire page down in a hard crash. The fix itself is small: catch the invalid date and fall back cleanly instead of crashing.
The dead link sitting in the sitemap
The second bug had been sitting there since week two. Walking the sitemap end to end while wiring in the new directory revealed that the master sitemap index pointed at a sub-sitemap, sitemap-pages.xml, that had never actually been built. That is a live dead link sitting exactly where every crawler looks first, and it stayed invisible until someone followed the whole chain rather than checking one entry at a time.
Key takeaways
- A directory page that cross-links every company to its city and role pages turns disconnected listings into a reinforcing SEO surface.
- Finishing a system forces the first whole-surface review, which is what surfaces gaps between individually correct parts.
- An unguarded date formatter could crash an entire page on a single malformed value; the fix is a clean fallback instead of a throw.
- A sitemap index pointing at a sub-sitemap that was never built creates a dead link exactly where crawlers look first.
- Widen the review when integrating a system; keep it narrow when patching a one-line fix.
Who this is for
This is for anyone building or auditing a multi-page site who wants a repeatable way to catch integration bugs before they ship. It comes from a Humanitarians AI Fellow's weekly report on building SEO for a job search app, and the same wide-angle discipline applies to any system with enough moving parts that a bug can hide in the seams between them.
Chapters
Full transcript(auto-generated, with timestamps)
The Directory as a Wide-Angle View
[0:00]Hi, I'm Bavana, a humanitarians AI fellow. Week six of my jobseker report, the job search app where I run SEO, making Google find and rank our listings. This week, I built the directory, the wide-angle page that ties everything together, and seeing the whole site at once caught two bugs a narrow view had missed. Executive summary. Some bugs are only visible when you stop looking at one page and look at the whole system. Start with the page itself. every verified company in one
Creating a Reinforced SEO Surface
[0:30]Place, each cross-lin back to the city and roll pages it belongs to. Before this, those were disconnected islands. The directory turns them into a surface that reinforces itself for visitors and crawlers both. Finishing it forced the first whole surface review, and that's what caught the two bugs. Here's the part that mattered more than the page
The Hard Crash: Fixing Date Formatters
[0:50]And the method you can reuse. Finishing it forced a whole surface review. Trace the system end to end. Check that every cross-file reference actually resolves and check every input that could throw. Not one template at a time, the whole surface at once. That discipline is what caught two bugs hiding in the gaps. The first was in the date formatter. Reviewing it one more time before calling the JSON LD work done. There was
Finding the Dead Sitemap Link
[1:16]No guard against a malformed date. A single bad value on one job record wouldn't just skip a field. It would throw and take the entire page down with a hard crash. The fix is small. Catch the invalid date and fall back cleanly instead of crashing. The second had been sitting there since week two. Walking the site map end to end while wiring in the directory. The master index pointed at a subsite map. Sitemap pages.xml
Recap: Zooming Out for Quality
[1:43]That had never actually been built. A live dead link exactly where every crawler looks first. Invisible until you followed the whole chain. Built the same day. One honest bound. The wide view isn't always the right move. When you're finishing a system or about to call it done, zoom out. That's when the gaps between parts surface, but for a oneline hot fix. A full surface review is just noise that delays the fix. Widen the lens when you're integrating. Keep it narrow when you're patching. The recap. The directory ties the whole landing surface together. Every company cross-lin back to its city and roll pages. And zooming out to
Finish, it caught two bugs. narrow focus had missed a date formatter that could crash a page now guarded and a dead sitemap link live since week two now built the rule this week. Some bugs are only visible from the wide angle. Your turn. Before you call a system done, stop reviewing it one file at a time and trace it end to end, [clears throat] the whole chain in one sitting. Ask Claude to walk the full path a user and a crawler takes through it and to flag the link that points at something that was never built. Run this and see what only the wide view shows.
