AIWikis Org Audit Report

AIWikis.org is strongest as an expert-facing, documentation-first evidence hub and weakest as a first-time user experience. The live public surface clearly communicates that the site is a source-governed AI memory and...

Metadata

Field	Value
Source site	aiwikis.org
Source URL	https://aiwikis.org/
Canonical AIWikis URL	https://aiwikis.org/aiwikis/files/raw-system-archives-aiwikis-agent-file-handoff-retired-source-archive-20-8a116319/
Source reference	raw/system-archives/aiwikis/agent-file-handoff/retired-source-archive-2026-06-13/2026-05-15/Improvement/aiwikis-site-structure-improvement/AIWikis.org Audit Report.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-05-15T21:24:49.2391854Z
Content hash	sha256:8a116319d2c1abf78e4934b38c0bfd03be40af5a13d05baa892af5d205916c16
Import status	unchanged
Raw source layer	data/sources/aiwikis/raw-system-archives-aiwikis-agent-file-handoff-retired-source-archive-2026-06-13-2026-05-15-impr-8a116319d2c1.md
Normalized source layer	data/normalized/aiwikis/raw-system-archives-aiwikis-agent-file-handoff-retired-source-archive-2026-06-13-2026-05-15-impr-8a116319d2c1.txt

Current File Content

Structure Preview

• AIWikis.org Audit Report
• Executive Summary
• Scope and Method
• UI and UX Evaluation
• Key UX Findings
• Information Architecture and Navigation
• IA and Navigation Findings
• SEO and Discoverability
• SEO Findings
• Technical Signals and Analytics
• Technical Findings
• Desktop and Mobile Comparison
• Prioritized Fix Checklist
• Suggested Experiments and Metrics

Raw Version

This public page shows a bounded preview of a large source file. The complete source remains in the raw and normalized source layers named in metadata, with the SHA-256 hash above for verification.

• Source characters: 24784
• Preview characters: 11965

# AIWikis.org Audit Report

## Executive Summary

AIWikis.org is strongest as an expert-facing, documentation-first evidence hub and weakest as a first-time user experience. The live public surface clearly communicates that the site is a source-governed AI memory and LLM Wiki demonstration, and it offers real onboarding assets such as `/start-here/`, `/what-is-an-llm-wiki/`, `/how-to-build-an-llm-wiki/`, `/source-map/`, `/browser/`, `/files/`, several topic indexes, and a public `llms.txt`. The core pages are semantically plain, text-first, and easy to parse structurally, with consistent H1-led page layouts and visible skip links across sampled routes. citeturn1view0turn3view0turn8view0turn24view3turn41view0turn11view0

The biggest problems are not aesthetic polish so much as discoverability and information overload. The site relies heavily on long, dense link lists, a minimal top nav, overlapping index pages, jargon-heavy labels, and a footer that behaves more like a source-network directory than a utility footer. No visible on-site search entry point was found on sampled pages, and search engines currently surface stale hashed URLs under `/files/aiwikis/...` that return 404 when opened. That is the highest-priority issue because it directly harms findability, credibility, and SEO hygiene. citeturn5view0turn6view2turn26view0turn32view0turn10view1turn10view2turn31view0turn29view0turn28view0

AIWikis also shows several signs of a live system that is still converging on its final public contract. Some route normalization is already working well — for example, `/llm-wiki-index/` redirects to `/llm-wiki/`, and `/source-provenance-index/` redirects to `/source-provenance/` — but other public-facing inventory or indexed artifact URLs still drift away from the canonical human-readable pages. This suggests that AIWikis is conceptually strong and operationally promising, but not yet fully normalized as a high-confidence public documentation product. citeturn14view0turn32view0turn31view0turn29view0

| Area | Overall assessment | Priority |
|---|---|---|
| UI and onboarding | Clear intent, but overloaded and insider-oriented | Medium |
| IA and navigation | Rich, transparent, but redundant and hard to browse | High |
| SEO and discoverability | Strong core slugs, weak canonical/index hygiene | High |
| Technical surface | Crawlable and HTTPS, but route/index drift is visible | High |
| Accessibility | Good semantic basics; several AA checks remain unverified | Medium |

## Scope and Method

This audit is based on public, observable evidence only. I reviewed the live home page and major human-facing routes including `/`, `/start-here/`, `/browser/`, `/what-is-an-llm-wiki/`, `/how-to-build-an-llm-wiki/`, `/source-map/`, `/reports/`, `/topics/`, `/llm-wiki/`, `/uai-reference/`, `/ai-memory-systems/`, `/best-practices/`, `/source-provenance/`, `/files/`, `/lessons-learned/`, `/recommendation-adjustments/`, and `llms.txt`, plus search-engine-visible results for AIWikis pages and artifacts. citeturn1view0turn3view0turn5view0turn8view0turn24view3turn41view0turn41view1turn6view2turn26view0turn26view1turn14view2turn14view3turn32view0turn5view1turn24view0turn24view1turn11view0

Some requested checks could not be directly verified in this environment: exact font stack, rendered color values and contrast ratios, focus styling, canonical tags, structured data in the `<head>`, live `robots.txt` and `sitemap.xml` contents, analytics scripts, and official PageSpeed/Core Web Vitals numbers. Where that happened, I have treated the item as **unverified**, not as an automatic pass or fail. The report therefore separates **confirmed live findings**, **reasonable structure-based inferences**, and **open verification items**.

| Confidence level | Meaning | Examples in this report |
|---|---|---|
| Confirmed | Directly observed on live public pages or live search results | skip links, redirect behavior, stale indexed URLs returning 404, hidden utility routes, redundant indexes |
| Inferred | Strongly suggested by public structure, but not directly device-rendered here | mobile scroll burden, weak visual hierarchy from long flat lists |
| Unverified | Needs source/head/CSS/network access or proprietary tooling | contrast ratios, canonical tags, schema.org, robots/sitemap content, analytics, PageSpeed scores |

## UI and UX Evaluation

AIWikis presents itself as a deliberate low-chrome documentation interface. Across sampled pages, the structure is very simple: a skip link, a minimal top bar, a single H1, then text and long lists. That simplicity is a real strength for expert readers because it avoids modal clutter, ads, aggressive CTAs, or decorative distraction. It also means the semantic reading order is probably cleaner than many typical WordPress documentation sites. citeturn1view0turn3view0turn5view0turn8view0turn24view3

The weakness is that the interface puts almost all of its burden on terminology. The home page opens with source-boundary explanations and a long ecosystem list before it clarifies user goals, and `Start Here` gives newcomers a 25-step human path plus a 19-step AI-agent path. That is impressive as internal operating documentation, but heavy for a first session. Put simply: AIWikis has onboarding, but not lightweight onboarding. citeturn1view0turn3view0turn4view0

Microcopy and polish are also inconsistent. The top navigation label alternates between `Browser` and `Browse`, and the brand is surfaced as `aiWikis.org` on some pages and `AiWikis.org` on others. On their own those are small issues, but on a site whose value proposition depends on trust, precision, and citation discipline, such inconsistencies make the UI feel less governed than the content claims it is. citeturn1view0turn24view3turn24view0turn24view1

Accessibility looks better at the semantic level than at the interaction level. Positives include skip links on all sampled pages, clear H1 use, mostly linear content, and low widget complexity. Risks include repeated generic link labels such as `Open site`, `Source guide`, and `Coverage`, which weaken link-purpose clarity outside local context, plus extremely long unfiltered lists that will be tedious for keyboard and screen-reader users. No visible public forms appeared on the sampled primary pages, so form validation and form error states could not be directly audited. Exact contrast and focus-state compliance remain open checks. citeturn1view0turn3view0turn5view0turn10view1turn10view2

### Key UX Findings

| Finding | Severity | Recommendation | Effort | Expected impact | Validation |
|---|---|---:|---:|---:|---|
| First-time onboarding is too dense | High | Add a newcomer layer on `/` and `/start-here/` with 3–5 task cards: “What it is,” “How to use it,” “Browse sources,” “For maintainers” | Medium | High | A/B test current intro vs task-card intro; measure CTR to core pages, scroll depth, bounce rate |
| Microcopy is insider-heavy | Medium | Rewrite top-level labels in user language; keep specialist terminology deeper in the hierarchy | Medium | High | Track exits from `/` and `/start-here/`; run 5-task usability test |
| Label and brand inconsistency reduces polish | Medium | Standardize `AIWikis.org` casing and choose one nav label, preferably `Browse` or `Explore` | Low | Medium | QA snapshot of top nav and footer across key templates |
| Link affordances are weak in large lists | High | Add contextual snippets, tags, and primary/secondary CTA hierarchy on index pages | Medium | High | Measure click distribution and time to first successful content click |
| WCAG 2.1 AA is only partially provable from public evidence | Medium | Run direct contrast, keyboard, focus, landmark, and screen-reader audits on live templates | Medium | High | Manual WCAG pass + automated axe/Lighthouse accessibility test |

## Information Architecture and Navigation

AIWikis has a lot of information architecture — arguably too much of the same kind. The positive side is that the home page clearly exposes multiple navigation modes: conceptual pages, operational pages, source maps, file indexes, reports, and a workspace browser. The negative side is that several index pages overlap heavily while offering only slight scope differences. `Topic Index`, `LLM Wiki Index`, and `Source Provenance Index` are all large link inventories with very similar content footprints, while `UAI Reference Index`, `AI Memory Systems Index`, and `Best Practices Index` narrow scope only modestly. That creates retrieval optionality for power users, but weakens information scent for everyone else. citeturn1view0turn6view2turn26view0turn26view1turn14view2turn14view3turn32view0

Navigation is underpowered relative to this depth. In the sampled pages, the persistent global header is usually just the site title plus `Browser/Browse`. No breadcrumb trail was surfaced in the sampled body output. The footer is not a conventional documentation footer with About, Contact, Privacy, Terms, Search, Help, and metadata; instead it is mostly a repeated list of external domains plus `Browser` and `llms.txt`. Meanwhile, `Contact` exists in the Global File Index but was not surfaced in the sampled primary global navigation, and the `Reports` hub lists report filenames as code-style text rather than obvious, clickable report entries. `Source Map` itself explicitly says source manifest records are “not available yet.” citeturn10view4turn9view0turn9view1turn9view2turn21view0turn41view1turn41view0

That combination means AIWikis is navigable if the visitor already understands the site’s internal ontology. It is much less navigable if the visitor arrives with a normal documentation question such as “What is this site?”, “How do I find the relevant guide?”, or “Where is the current authoritative page?” The architecture privileges transparency and provenance over task completion. That is a valid product choice, but it should be made explicit rather than left to the user to infer. citeturn1view0turn3view0turn5view0turn6view2

A simplified version of the visible navigation model looks like this:

```mermaid
flowchart TD
    Home["/"] --> Start["/start-here/"]
    Home --> Browser["/browser/"]
    Home --> Files["/files/"]
    Home --> SourceMap["/source-map/"]
    Home --> Topics["/topics/"]
    Start --> WhatIs["/what-is-an-llm-wiki/"]
    Start --> HowTo["/how-to-build-an-llm-wiki/"]
    Topics --> LLMWiki["/llm-wiki/"]
    Topics --> UAIRef["/uai-reference/"]
    Topics --> AIMemory["/ai-memory-systems/"]
    Topics --> BestPractices["/best-practices/"]
    Topics --> Provenance["/source-provenance/"]
    Browser --> External["Workspace source sites"]
```

That flow is present in the content, but it is not strongly expressed as a task-driven UI. citeturn1view0turn3view0turn5view0turn6view2

### IA and Navigation Findings

| Finding | Severity | Recommendation | Effort | Expected impact | Validation |
|---|---|---:|---:|---:|---|
| Overlapping index pages create taxonomy noise | High | Merge or clearly differentiate indexes by role: Topics, Sources, Files, Operations, Learn | Medium | High | Compare click depth and exits before/after taxonomy consolidation |
| No visible global site search on sampled pages | High | Add a persistent search box or search CTA in header and empty-state prompts | Medium | High | Measure search usage, zero-result rate, and time to first relevant click |
| Footer is source-network oriented, not user-task oriented | Medium | Replace repeated domain cloud with utility footer: About, Contact, Search, Privacy, llms, Reports | Low | Medium | Track footer CTR and visits to utility routes |
| Reports hub is not actionable enough | Medium | Turn filenames into linked cards with descriptions, modified dates, and formats | Low | Medium | Measure report-page clicks and report downloads/views |

Why This File Exists

This is a memory-system evidence file from aiwikis.org. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.

Role

This file is memory-system evidence. It records source history, archive transfer, intake disposition, or another piece of provenance that should be retrievable without becoming an unsupported public claim.

Structure

The file is structured around these visible headings: AIWikis.org Audit Report; Executive Summary; Scope and Method; UI and UX Evaluation; Key UX Findings; Information Architecture and Navigation; IA and Navigation Findings; SEO and Discoverability. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

Prompt-Size And Retrieval Benefit

Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.

How To Use It

• Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
• LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
• Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
• Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.

Update Requirements

When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.

Related Pages

• Source overview
• Site file index
• Site report index
• UAI system index
• Source provenance
• Site directory
• Organization reports

Provenance And History

• Current observation: 2026-06-22T01:56:21.9510185Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-652 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "AIWikis Org Audit Report",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/aiwikis/files/raw-system-archives-aiwikis-agent-file-handoff-retired-source-archive-20-8a116319/",
    "source_reference":  "raw/system-archives/aiwikis/agent-file-handoff/retired-source-archive-2026-06-13/2026-05-15/Improvement/aiwikis-site-structure-improvement/AIWikis.org Audit Report.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:8a116319d2c1abf78e4934b38c0bfd03be40af5a13d05baa892af5d205916c16",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-15T21:24:49.2391854Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-652",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-06-22T01:56:21.9510185Z"
}