Deep Research Report On Improving Llmwiki Navigation, Seo, And Structure - Source Excerpt 03 - Breadcrumb rules
Back to Deep Research Report On Improving Llmwiki Navigation, Seo, And Structure
Summary
This source excerpt begins near Breadcrumb rules and preserves the surrounding evidence from Wiki.FFTAC.org/agent-file-handoff/Archive/2026-05-11-improvement-concept-layer/Deep Research Report on Improving LLMWiki Navigation, SEO, and Structure.md.
**Source path:** Wiki.FFTAC.org/agent-file-handoff/Archive/2026-05-11-improvement-concept-layer/Deep Research Report on Improving LLMWiki Navigation, SEO, and Structure.md
- **Use one canonical public domain for each role.** If the handbook is on `llmwikis.org`, all handbook equivalents elsewhere should 301 to it. If archived copies remain on `wiki.fftac.org`, they should either be non-indexed replicas or clearly separate evidence pages with their own canonicals. citeturn19search2turn32search16
- **Keep indexable public pages shallow.** A good default is: home plus one section plus one page slug, such as `llmwikis.org/concepts/what-is-an-llm-wiki/`. Public pages should normally stay at **three semantic levels or fewer** below the domain. citeturn20search2turn22search1
- **Use lowercase, hyphenated slugs.** Avoid dates at the front of the slug unless the content is inherently chronological. Put dates at the end when needed. citeturn20search2
- **Separate page purpose from page chronology.** Prefer `archive-transfer-report` over `04-29-cross-site-archive-transfer`. Use the title or metadata for the human-readable date. citeturn20search0turn32search1
- **Reserve filters for query parameters, not crawlable path explosions.** If topic, type, and freshness filters exist, keep non-editorial combinations non-indexable by default, and only curate indexable facet landing pages where search demand and unique content justify them. citeturn19search1
### Breadcrumb rules
Breadcrumbs should reflect **taxonomy, not browsing history**. Google supports breadcrumb structured data, and W3C recommends page structures that improve orientation and predictable navigation. Google also removed visible breadcrumb trails from mobile SERPs in early 2025, which means on-page breadcrumbs remain important for users and for desktop search presentation, but should not be treated as a mobile SERP crutch. citeturn19search0turn27search3turn27search0turn37search0turn37news22
Recommended rules:
- `Home > Section > Subsection > Page`
- Never show more than four breadcrumb nodes on public pages
- Use the same breadcrumb schema sitewide
- If a page belongs to multiple tags, choose one **primary hierarchical parent** for breadcrumbs and use tags only as secondary metadata
- Reports should breadcrumb by content family, then by subject, then by date
### Sample URL hierarchy
| Content family | Canonical URL pattern | Title pattern | Indexability |
|---|---|---|---|
| Concepts | `llmwikis.org/concepts/{topic}/` | `{Topic}` | Index |
| Guides | `llmwikis.org/guides/{task}/` | `How to {Task}` | Index |
| Templates | `llmwikis.org/templates/{type}/` | `{Type} Template` | Index |
| Tools | `llmwikis.org/setup/{tool}/` | `{Tool}` | Index |
| Operations | `llmwikis.org/operations/{workflow}/` | `{Workflow}` | Index |
| Governance | `llmwikis.org/governance/{policy}/` | `{Policy}` | Index |
| Examples | `llmwikis.org/examples/{audience}/{example}/` | `{Audience} Example` | Index |
| Topics | `llmwikis.org/topics/{topic}/` | `{Topic}` | Index |
| Reports | `llmwikis.org/reports/{subject}/{yyyy-mm-dd}/` | `{Subject} Report` | Index if strategic |
| Evidence archive | `wiki.fftac.org/evidence/{type}/{subject}/` | `{Subject} Evidence` | Selectively index |
| Source files | `wiki.fftac.org/evidence/files/{id}/` | `{File role}: {Source}` | Usually noindex unless useful to search |
## Templates, metadata, and wizard redesign
### Page templates and metadata schema
The current public metadata standard is useful for governance but too narrow for modern discoverability and content operations. A stronger page model should unify wiki governance, search appearance, and structured data. That recommendation is justified by the current LLMWikis frontmatter guidance and by Google’s separate requirements for title links, snippets, site names, article markup, organization markup, byline dates, and breadcrumb structure. citeturn14view2turn20search0turn20search1turn32search0turn32search1turn31search0turn31search2turn19search0
A practical schema should include these fields:
| Field | Required | Purpose |
|---|---|---|
| `title` | Yes | Visible page title and default SEO title |
| `seo_title` | Yes | Shorter search-optimized title if needed |
| `meta_description` | Yes | Human-written snippet candidate |
| `canonical_url` | Yes | Canonical target for indexation |
| `slug` | Yes | Stable route identifier |
| `content_type` | Yes | Concept, guide, template, report, tool, example, policy |
| `primary_category` | Yes | Single hierarchical parent for IA and breadcrumbs |
| `tags` | Yes | Secondary taxonomy for search and discovery |
| `summary` | Yes | One-sentence page purpose |
| `owner` | Yes | Accountable content owner |
| `reviewer` | Yes | Editorial or domain reviewer |
| `status` | Yes | Draft, reviewed, current, stale, archived, deprecated |
| `created_at` | Yes | Initial publication date |
| `updated_at` | Yes | Latest meaningful content update |
| `last_reviewed` | Yes | Most recent human review date |
| `review_cycle` | Yes | Monthly, quarterly, annual, release-based |
| `audience` | Yes | Public, builder, maintainer, agent, mixed |
| `sensitivity` | Yes | Public, internal, restricted |
| `agent_use` | Yes | Allowed, cite-only, summarize-only, no-action, blocked |
| `aliases` | Recommended | Alternative names and spellings |
| `redirects_from` | Recommended | Old URLs/slugs that now resolve here |
| `source_urls` | Recommended | Upstream source list |
| `related_pages` | Recommended | Typed related content IDs |
| `schema_type` | Recommended | TechArticle, Article, CollectionPage, WebPage |
| `image` | Recommended | Feature image/Open Graph asset |
| `language` | Recommended | Locale code |
| `noindex` | Conditional | For utility or duplicate pages |
| `entity_id` | Recommended | Stable internal ID for graph/search systems |
A sample public article template could look like this:
' ' ' yaml
---
title: What Is an LLM Wiki?
seo_title: What Is an LLM Wiki?
meta_description: A practical definition of the LLM Wiki pattern, how it differs from RAG and AI Memory, and when to use it.
canonical_url: https://llmwikis.org/concepts/what-is-an-llm-wiki/
slug: what-is-an-llm-wiki
content_type: concept
primary_category: concepts
tags:
- llm-wiki
- knowledge-systems
- ai-agents
summary: Defines the LLM Wiki pattern for humans, search engines, and AI agents.
owner: Editorial Lead
reviewer: Domain Reviewer
status: current
created_at: 2026-05-11
updated_at: 2026-05-11
last_reviewed: 2026-05-11
review_cycle: quarterly
audience: public
sensitivity: public
agent_use: allowed-with-citation
aliases:
- LLM wiki definition
- what is llm wiki
related_pages:
- /concepts/llm-wiki-vs-rag/
- /guides/build-an-llm-wiki/
schema_type: TechArticle
language: en-US
entity_id: concept-llm-wiki-definition
---
' ' '
And the body template should be standardized:
' ' ' markdown
# What Is an LLM Wiki?
## Overview
One-paragraph answer for humans and search snippets.
## When to use it
Clear decision criteria.
## What it is not
Contrast with adjacent concepts.
## Core components
Short, structured list with links.
## Examples
Real examples or implementation patterns.
## Related pages
Typed internal links.
## Sources and review notes
Visible provenance, last reviewed, and owner.
' ' '
For operational or tutorial content, use a different template rather than forcing concepts and how-tos into the same page shape:
' ' ' markdown
# How to Build an LLM Wiki
## Outcome
What the reader will have when finished.
## Prerequisites
Required inputs, access, and assumptions.
## Steps
Task-oriented sequence with checkpoints.
## Validation
How to know it worked.
## Common failure modes
Known problems and fixes.
## Related pages
Adjacent tasks and concepts.
## Review and ownership
Owner, reviewer, last reviewed, review cycle.
' ' '
### Structured data and JSON-LD policy
Use structured data selectively and consistently. Google supports breadcrumb markup, article markup, organization markup, and site-name markup; it also advises validating markup and checking performance in Search Console and URL Inspection. The highest-value stack for this project is:
- **Home page:** `WebSite` site-name markup plus `Organization`
- **Guide and concept pages:** `TechArticle` or `Article` plus `BreadcrumbList`
- **Topic hubs / collections:** `CollectionPage` plus `BreadcrumbList`
- **About / contact pages:** `Organization` and `WebPage`
- **Report pages:** `Article` if editorial; otherwise `WebPage`
- **Do not prioritize Sitelinks Search Box markup**, because Google discontinued that search feature. citeturn32search0turn31search0turn31search2turn19search0turn31search10turn36search1turn31news33
A sample article JSON-LD block: