TheFocus.ai

Two-vector IA proposal

TheFocus.ai currently serves two distinct audiences through one undifferentiated architecture. The data supports splitting into a Marketing site (Habitat OS + consulting) and an Academy (reports, courses, recipes, tools).

23 marketing pages

131 academy/content pages

6× content-to-marketing ratio

26 topic-archive noise pages

Current state

The site is organized under one domain with flat URL paths. Marketing pages and academy-level content share the same navigation, same layout patterns, and same URL hierarchy. The Firecrawl crawl discovered:

Marketing side (23 working pages)

Page	URL	Purpose
Home	/	Hero + Habitat OS pitch
Capabilities	/capabilities	L0-L5 maturity framework
Habitat OS	/habitat-os	Product page
About	/about	Company/team
Case Studies	/case-studies + 9 details	Proof + outcomes
Offerings (5)	/offerings/*	Consulting SKUs
Jobs	/jobs + 1 detail	Careers
Vibe Check	/vibe-check	Standalone tool
Use Cases	/use-cases	Use-case index

Academy/Content side (131 pages)

Category	Count	Examples
Report articles	75	Model Showdown, Car Wash Test, Local Providers, MCP Eval
Conference report	~70 subpages	AI Engineering Summit — track recaps, speaker bios, articles
Recipes	35	Add memory to Cursor, Weekend Coding Agent, Superwhisper
Coding agent steps	12	Steps 0-10 + epilog
Use-case detail	5	Flux images, Coding Literacy, Prince
Labs hub pages	4	/reports, /insights, /tools, /tools/browse

Noise pages

26 topic archive pages (/agents/, /models/, /essay/, /process/, etc.) — auto-generated "posts" pages
15 broken 404s (legacy case studies, relative links in conference report)
2 redirects, 1 empty page

What the data reveals

Content-side pages outnumber marketing pages 4× — when you exclude the conference report (which is a single event), it's still 60 content vs 23 marketing. The flat IA hides this.

Topic archives create URL ambiguity — /models/ is a topic archive (generated "posts" page), not a product/models subpage. /process/ is a tag page, not a consulting methodology page. This pollutes the IA and confuses crawlers.

Deep content has no navigational home — Recipes like "Add memory to Cursor" are valuable educational content, but they live at the root level with no obvious parent in the top nav. Users discover them by search or sidebar links only.

15 broken 404 routes — Legacy case-study URLs (/case-study/upper-hand, /rivian-tbm, /samsung-702) return 404. The conference report has a cluster of relative-link navigation 404s.

The content is good — 9 detailed case studies, 75+ report articles with real data, 35 hands-on recipes, and a comprehensive conference coverage archive. The raw material is strong; the IA just doesn't surface it well.

Two-vector proposal

Split the site into two distinct experiences under one domain, using the /academy/ subdirectory. Marketing pages stay at the root.

thefocus.ai → Marketing site

thefocus.ai/academy/ → Academy/content

Vector A: Marketing

thefocus.ai

Habitat OS product page, consulting offerings, case studies, the "where are you on the ladder" interactive assessment, vibe check tool, about, jobs.

~23 pages · Top nav (6 items) · Mega-menu dropdowns

Hero-driven layouts
Single primary CTA per page
Case studies as evaluation-phase proof
"Ladder" as lead-gen interactive content
Vibe Check as standalone utility tool

Vector B: Academy

thefocus.ai/academy/

Reports, Weekend Warrior courses, Recipes, Tools, Use Cases, Conference reports, Speaker bios, Step-by-step tutorials.

~131 pages · Sidebar nav · Hub + detail structure

Sidebar-driven navigation
Hub pages for every category
Educational CTAs ("Start Course", "Read Report")
Individual content pages with reading-time + progress
Structured course paths (e.g. Weekend Warrior)

I/O: what goes where

Stays at root (thefocus.ai)

Page	New path	Why it stays in marketing
Home	/	Front door for all audiences
Habitat OS	/habitat-os	Core product page
Capabilities	/capabilities	Framework + consulting proposition
Case Studies	/case-studies	Social proof for evaluation
Case Study details	/case-study/*	Stay at root (evaluation-phase content)
Offerings	/offerings/*	Consulting SKUs, stays in marketing
About	/about	Company info
Jobs	/jobs	Careers, stays at root
Vibe Check	/vibe-check	Standalone utility tool
Use Cases index	/use-cases	Marketing content

Moves to /academy/

Content	New path	Rationale
Report hub	/academy/reports/	Main academy landing for reports
Report articles	/academy/reports/car-wash-test	Educational deep-dives
Conference report	/academy/reports/ai-engineering-summit/	Event coverage as learning content
Weekend Coding Agent	/academy/courses/coding-agent/	Structured course, not a landing page
Coding Agent steps	/academy/courses/coding-agent/step-0	Course curriculum
Recipes	/academy/recipes/*	How-to guides, belongs in academy
Tools	/academy/tools/*	Labs tooling
Use case details	/academy/use-cases/*	Extended educational content

Topic archives → consolidate or redirect

The 26 topic archive pages (/agents/, /models/, /essay/, /process/, etc.) should either redirect to the relevant academy hub page or be consolidated into a unified /blog/ under marketing. Each one is a thin archive page at a flat root-level URL that adds noise without clear value.

Broken routes → fix

15 404s to resolve. Priority: the legacy case study redirects (/case-study/upper-hand → correct path) and the conference report relative-link issues. The broken speaker/track pages under /reports/aiecode-2025-11/ suggest navigation links use relative paths that don't resolve from subpages.

Navigation & SEO

Top nav (5-6 items)

Habitat OS
Offerings
Case Studies
Academy
About
[Book a Call] — primary CTA button

Academy sidebar nav

Courses
Reports
Recipes
Tools
Use Cases

SEO: subdirectory over subdomain

/academy/ consolidates domain authority
Google treats subdirectories and subdomains equally for indexing
Subdirectories pass link equity directly
One sitemap with two sections (marketing, academy)

Cross-linking strategy

Case study → "Read the full report in Academy"
Academy report → "Need help implementing? Book a consultation"
Homepage → Featured report + "Explore Academy"
Academy hub → Featured case study + "See what's possible"

CTA hierarchy per vector

Phase	Marketing CTA	Academy CTA
Awareness	"Explore Habitat OS" / "Take the Ladder Assessment"	"Browse Reports" / "Start Learning"
Evaluation	"See Results" / "Book a Call"	"Read the Full Report" / "Take the Course"
Conversion	"Talk to Our Team" / "Get Started"	"Apply This with Our Consulting Team"

Subdirectory pattern: A user on a marketing case study clicks "Read the full report in Academy" → lands on /academy/reports/car-wash-test/ with an academy sidebar nav and an educational layout context, not a marketing hero page. The shared domain (thefocus.ai) keeps it feeling like one site; the different layout context signals "you're now in learning mode."

Key findings from the audit

23marketing pages

131academy pages

15broken 404 routes

26topic archives to clean

Strongest assets: The 9 case-study detail pages with measurable results (94.5% accuracy, 78% faster decisions, 27% higher conversion) are the best conversion assets. The 75 report articles and 35 recipes are legitimately valuable educational content that should be easier to find and navigate.

Biggest structural issue: The topic archive pages (/agents/, /models/, /essay/ — 26 total) occupy prime real estate at the root level with thin auto-generated content. They dilute the perceived authority of the marketing pages and add noise to the IA. Consolidating them under /blog/ or merging into the academy structure would clean up the hierarchy significantly.

Broken links hurt credibility: 15 404s, especially the legacy case study paths and the conference report navigation errors. These should be fixed before any major restructuring to avoid compounding the problem.

The Academy has legs: With 131 pages of substantial educational content, the academy isn't hypothetical — it already exists. The question is whether to surface it properly. The Weekend Coding Agent alone has a 12-step structured curriculum, which is practically a course waiting for a course page and progress tracking.

Proposed next steps

Fix the 404s first. Set up redirects for the three legacy case studies and resolve the relative-link problems in the conference report.
Consolidate topic archives. Move the 26 auto-generated "posts" pages under a single /blog/ or absorb them into the academy taxonomy.
Build the academy hub page at /academy/ with clear category cards (Courses, Reports, Recipes, Tools) and sidebar navigation.
Migrate deepest content first. Move recipes under /academy/recipes/, then reports under /academy/reports/, then the course content under /academy/courses/.
Compress the top nav to 5-6 items with the "Academy" item as the entry point to the entire content side.
Design system: unified tokens, two layout modes. Marketing keeps hero + section layouts. Academy gets sidebar + content layouts. Same brand colors and typography.

Source: Full Firecrawl crawl (200 pages, 260 credits), Playwright screenshots (95 pages, desktop + mobile), webreel video walkthroughs (4 recordings).
Full visual inventory microsite published on Pancake.