# Content Architecture / Semantic Clustering Audit — Quire Guide Scope: 139 English guide articles (`_docs/en/*.md`), organized into ~30 nav categories via `_data/navigation/en.yml` (Overview, Task List, Task List Advanced, Custom Fields, Formula, Sublist, Board, Table, Timeline, Task Dependency, Calendar, Time Tracking, Document, Chart, Chat, Insight, Project, Organization, Sidebar, Search, Integration, Import & Export, Permission Control, Keyboard Shortcuts, Profile/Account Settings, Security, Mobile, Troubleshooting, Billing, Templates). Method: mapped every internal `/guide/...` markdown link across all 139 pages to build an inbound/outbound link graph, cross-referenced against the nav taxonomy, and spot-checked representative clusters (Views: Board/Table/Timeline/Calendar; Formula; Import & Export; Mobile; Notifications; Permissions; Search) for pillar/spoke wiring and topic overlap. ## What Works - The 8 "Overview" pages (`overview-01` … `overview-08`) function as de facto pillar pages and do link down into their category's primary pages (e.g. `overview-05-project-views.md` → Board/Table/Timeline/Calendar/Time-Tracking views; `overview-01-user-interface.md` → sidebar, main panel and detail-panel spokes). - The **Formula** cluster (`formula-01` through `formula-06`) is the best-built hub-and-spoke example on the site: the pillar (`quire-formula-explained`) links to Custom Fields, Formula Operators & Functions, and Field References, and the spokes link back to the pillar and to each other. - Frontmatter includes structured `faq:` blocks and visible "Frequently Asked Questions" sections on sampled pages, which gives each page clear topical self-containment (good for entity/semantic signals) independent of link structure. - Distinct-intent pages that could look duplicative on title alone (e.g. `blink-search` or global search vs. `search-tasks` for in-project task search) are actually scoped differently and are not true keyword cannibalization, though they are never cross-linked. ## Key Problems ### 1. No true pillar/cluster architecture below the Overview layer — only a flat nav taxonomy The sidebar nav groups pages into ~30 categories, but only 8 of those categories (the "Overview" section) have an actual landing/pillar page. The other ~22 categories (Import & Export, Mobile, Troubleshooting, Security, Formula sub-items, Sidebar, Billing, Templates, etc.) have no category landing page at all — the nav heading is purely a UI grouping label with no corresponding URL/content. A search engine or AI crawler parsing page content and links (not the client-rendered sidebar) cannot infer that these pages belong together; the topical relationship exists only in `_data/navigation/en.yml`, which is not part of page content. ### 2. Large fraction of pages have zero contextual internal links Of 139 English pages, 48 (~35%) contain **zero** outbound `/guide/...` links in body content, and internal link counts are heavily skewed (a handful of overview/hub pages carry 15-35 links while most spokes carry 0-2). Whole nav categories are essentially link-islands: - **Import & Export** (5 pages: copy-paste, CSV import, JSON import, copy-to-app, export): 4 of 5 pages have 0 outbound links; the 1 exception links to an unrelated page (`move-tasks`), not to its own sibling import/export pages. - **Troubleshooting** (5 pages: contact support, compatible browsers, clear cache, locked-out account, merge accounts): 0 internal cross-links among any of them. - **Mobile** (8 pages under `mobile-*`): only `mobile-01` links to `mobile-02`; the other 6 mobile pages are unlinked from each other and from the mobile overview. - **Security** (SSO, IP allowlists): 0 links between the two. - **Timeline** and **Table** sub-spokes (`timeline-02/03/04`, `table-view-02/03`): none link back to their own pillar (`quire-timeline-view`, `quire-table-view`) or to each other. ### 3. Spokes frequently fail to link back to their own pillar (mandatory link violated) Even where an overview/pillar page correctly links down to a primary spoke, the spoke does not link back up: - `quire-calendar-view`, `quire-timeline-view`, `quire-table-view`, and `quire-board-view` (the four primary View pages) do **not** link back to `project-view` (`overview-05-project-views.md`), their logical pillar, even though `project-view` links to all four. - `account-03-reminders.md` (a spoke of the notifications cluster) has zero outbound links, including no link back to `get-notified` (its pillar), while its sibling `account-04-email-notifications.md` does link back correctly. This is an inconsistency within the same 3-page cluster (`get-notified` → `reminders` + `email-notifications`). - `table-view-01-quire-table-view.md` has 0 outbound links at all, despite being the primary page for an entire View type. ### 4. Orphan pages (no inbound internal links found in any page body) 55 permalinks receive no inbound contextual link from any other guide page's body content, including some pages that are conceptually important enough to be pillars themselves, e.g. `/user-interface/`, `/navigate-quire/`, `/milestones/`, `/activity-log/`, `/quire-mcp/`, `/single-sign-on/`, `/blink-search/`, `/search-tasks/`, all four Templates pages (`agile-scrum`, `okrs`, `gtd`, `customer-relationship-pipeline`), and all Import/Export pages. These pages are reachable only via the sidebar nav (a site-wide UI element), not via any in-content contextual link — a weak signal for search engines and LLMs trying to establish topical relationships, and a real risk of these pages being under-indexed or seen as disconnected one-offs by AI answer engines that weight in-content links more than chrome/navigation links. ### 5. Latent keyword/topic overlap without disambiguating cross-links Several page groups cover adjacent-but-distinct sub-topics that are never cross-linked, creating a moderate cannibalization/confusion risk for both users and search engines trying to determine which page ranks for a given query: - **Notifications**: `get-notified`, `reminders`, `email-notifications` — overlapping scope (all describe "when/how you get notified"), inconsistent backlinking (see #3). - **Search**: `blink-search` (global entity search) vs. `search-tasks` (in-project task search) — different intent, but zero cross-links between them despite an obvious "you may also want" relationship, and both are orphaned (see #4). - **Calendar**: `quire-calendar-view` vs. `calendar-view-modes` vs. `customized-calendar-view` — three pages splitting what could read to a search engine as one topic ("Quire Calendar View"). No page links to all three; two of the three have zero internal links. - **Permissions**: a general `permission-role` pillar exists but is not linked from any of the four feature-specific permission pages (`document-permission`, `sublist-permission`, `chat-permission`, `insight-permission`) — each links only to `external-team`, never to the general permissions pillar, so the permission topic cluster has no single entry point. ### 6. Homepage does not function as a topical hub `index.md` links to only 6 hand-picked "Highlights" cards (Sublist, Custom Fields, Formulas, Peekaboo, Mobile, Timer) rather than to the ~30 category pillars. This means the homepage passes no contextual link equity to most clusters and gives crawlers no page-level map of the site's topical structure beyond the client-side sidebar. ## Cannibalization Check Summary No hard cannibalization found (no two pages target an identical primary keyword/intent with duplicate content). The risk identified is soft/structural: overlapping-scope page groups (Notifications, Search, Calendar) that are not cross-linked or differentiated by an explicit "see also" — this raises the chance that Google or an AI engine picks the "wrong" page for a broad query, or alternates rankings between pages (classic soft-cannibalization symptom), rather than consolidating relevance signals onto one clear pillar. ## Recommendations Summary 1. Create lightweight pillar/landing pages (or convert one existing spoke into the pillar) for every nav category that currently lacks one — starting with the highest-value gaps: Import & Export, Mobile, Notifications (consolidate reminders/email-notifications/get-notified under one clear pillar), Search, Calendar, Permissions. 2. Add mandatory bidirectional links: every spoke must link to its pillar, every pillar must link to every spoke. Fix the four View pages (Board/Table/Timeline/Calendar) to link back to `project-view`; fix `reminders` to link back to `get-notified`. 3. Add "Related articles" link blocks (2-4 links) to the 48 zero-outbound-link pages, prioritizing Import/Export, Troubleshooting, Mobile, and Security clusters. 4. Cross-link `blink-search` ↔ `search-tasks`, and link all permission-specific pages back to `permission-role`. 5. Consider expanding the homepage "Highlights" section or adding a category index to pass contextual links to more of the ~30 clusters, not just 6 hand-picked features.