Teleodynamic Com Site Audit And Development Plan

Teleodynamic.com is architected more like a research documentation hub than a conventional marketing site. Its homepage explicitly frames the site as a research hub for AI systems under constraint, and the site’s own...

Metadata

Field	Value
Source site	aiwikis.org
Source URL	https://aiwikis.org/
Canonical AIWikis URL	https://aiwikis.org/aiwikis/files/raw-system-archives-teleodynamic-2026-05-15-site-audit-improvements-tele-2d957b27/
Source reference	raw/system-archives/teleodynamic/2026-05-15-site-audit-improvements/Teleodynamic.com Site Audit and Development Plan.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-05-15T23:58:41.5738120Z
Content hash	sha256:2d957b27050664fcf6a0090059df8cd328ee65b7aaa58dea2909a0fabee8990c
Import status	unchanged
Raw source layer	data/sources/aiwikis/raw-system-archives-teleodynamic-2026-05-15-site-audit-improvements-teleodynamic-com-site-audit-2d957b270506.md
Normalized source layer	data/normalized/aiwikis/raw-system-archives-teleodynamic-2026-05-15-site-audit-improvements-teleodynamic-com-site-audit-2d957b270506.txt

Current File Content

Structure Preview

• Teleodynamic.com Site Audit and Development Plan
• Executive summary
• Current versus recommended snapshot
• Scope and audit basis
• Crawl inventory and site architecture
• Sitemap table
• On-page SEO and content gaps
• Sampled on-page SEO audit
• Content gaps versus adjacent benchmark sources
• Technical performance and crawlability
• Technical check matrix
• Security, privacy, accessibility, and off-page authority
• Security and privacy
• Accessibility and UX
• Off-page authority and backlink profile
• Development roadmap and measurement
• Recommended platform direction
• Migration risks and testing plan
• Prioritized task list
• KPI and reporting dashboard

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: 42849
• Preview characters: 11601

# Teleodynamic.com Site Audit and Development Plan

## Executive summary

Teleodynamic.com is architected more like a research documentation hub than a conventional marketing site. Its homepage explicitly frames the site as a research hub for AI systems under constraint, and the site’s own navigation, resources hub, and archive together expose a broader corpus than the top navigation alone suggests: at least **26 first-party routes/assets** were discoverable in this audit, including core guide pages, deep guides, and machine-readable JSON endpoints. citeturn4view0turn20view0turn23view0turn21view0turn21view1turn21view2turn21view3turn21view4turn21view5turn21view6turn21view7turn21view8turn21view9turn21view10turn21view11turn21view12turn21view13turn21view14turn21view15turn21view16turn24view0turn24view1turn24view2turn24view3turn24view4turn45view0turn45view1turn45view2turn45view3turn45view5turn45view6turn45view7

The site’s strongest current assets are its **deliberate topical clustering**, **dense internal linking**, **clear claim-boundary discipline**, and **generally solid heading/alt-text hygiene on the sampled pages**. The homepage routes different audiences into theory, build strategy, glyph communication, evaluation, and archival evidence; the resources page acts as a source-routed hub; and the archive page documents editorial promotion rules and limits on speculative claims. Sampled pages also show one primary H1 and nested H2/H3 structures, plus descriptive image alt text on hero and explanatory graphics. citeturn4view0turn20view0turn23view0turn5view1turn44view0turn44view1

The biggest problems are **discoverability, trust packaging, and verification gaps**. Public search in this audit surfaced only a small subset of first-party pages even though the site itself advertises many more routes. On sampled pages, standard trust cues that researchers and search engines recognize quickly—such as visible author bylines, publication dates, reference sections, downloadable papers, or rich-result-style enhancements—were not readily visible, while adjacent benchmark sources such as arXiv, PhilArchive, SAGE, and the older Teleodynamics site do expose many of those elements. Canonical tags, meta descriptions, structured data, server headers, redirect rules, PageSpeed scores, Core Web Vitals, and live robots/sitemap endpoints could not be independently verified from the public audit environment and should therefore be treated as **unspecified**, not assumed good or bad. citeturn0search0turn0search1turn0search2turn0search3turn0search4turn0search5turn29view0turn28view1turn28view2turn30view0

The highest-return plan is **not** an immediate rebuild. The better sequence is: first, fix indexation and metadata; second, add trust/compliance scaffolding; third, harden performance and security; and only then decide whether a WordPress-to-static or headless migration is warranted. The archive page’s description of Markdown inputs promoted into WordPress routes suggests the content is already structured enough to support a lower-risk migration later if performance, security, or editorial workflow justify it. citeturn23view0

### Current versus recommended snapshot

| Dimension | Current state | Recommended state |
| --- | --- | --- |
| Discoverability | The site’s own maps disclose a broad content footprint, but public search in this audit surfaced only a much smaller subset of first-party pages. citeturn20view0turn23view0turn0search0turn0search1turn0search2turn0search3turn0search4turn0search5 | Validate coverage in Google Search Console, submit/verify XML sitemap, strengthen internal discovery of deep guides, and explicitly index core “Start Here,” evaluation, and FAQ content. |
| Metadata | Sampled title tags are unique and coherent, but the homepage title is very short and several pages use brand-first phrasing. Meta descriptions, canonicals, and schema markup are unverified. citeturn0search0turn0search1turn0search2turn0search3turn0search4turn0search5 | Rewrite titles and descriptions around keyword demand, add self-referencing canonicals, and implement Organization/Person/Breadcrumb/Article/FAQ schema where appropriate. |
| Trust signals | Sampled pages did not prominently surface dated authorship, references, or publication metadata, while adjacent benchmark sources do. citeturn4view0turn5view1turn44view0turn44view1turn29view0turn28view1turn28view2turn30view0 | Add author pages, publication dates, references, downloadable PDFs, changelogs, and research-methodology pages. |
| Compliance | No “Privacy” or “cookie” language was found on the sampled first-party pages. citeturn42view0turn42view1turn42view2turn42view3turn42view4turn43view0turn43view1turn43view2 | Publish a privacy policy, define cookie/consent behavior if non-essential tracking exists, and document contact/data handling practices. |
| Platform | The archive explicitly describes WordPress routes, static pages, converted articles, and package assets including CSS, JS, search index, sitemap, and robots files. citeturn23view0 | Keep the existing CMS in the short term; evaluate headless or static delivery only after metadata/indexation fixes and baseline measurement. |
| Conversion path | The visible funnel is mainly informational, with “Start here” and footer contact details, but no validated form/demo/download path in the sampled crawl. citeturn4view0turn20view0 | Create a stronger primary CTA by audience, validate contact form flow, and add conversion events such as brief request, consultation request, or paper download. |

## Scope and audit basis

This report is a **public-site audit**, not a private analytics or server-log audit. The crawl was built from the site’s own first-party evidence: the homepage, the resources page, the archive page, and the URL targets disclosed by first-party internal links. Full rendered fetches were available for the homepage, theoretical strategy page, glyph communication page, resources page, archive page, and glyph object specification page. Additional routes were still inventoried whenever a first-party link disclosed the destination URL, even if the rendering layer could not fetch the body. citeturn4view0turn20view0turn23view0turn5view1turn5view2turn5view17turn21view0turn21view1turn21view2turn21view3turn21view4turn21view5turn21view6turn21view7turn21view8turn21view9turn21view10turn21view11turn21view12turn21view13turn21view14turn21view15turn21view16turn24view0turn24view1turn24view2turn24view3turn24view4turn45view0turn45view1turn45view2turn45view3turn45view5turn45view6turn45view7

The comparison set was intentionally narrow and primary-source-heavy: first-party Teleodynamic pages plus adjacent benchmark references that the site itself points toward or that appear prominently around the topic space, including the March 11, 2026 arXiv paper on Teleodynamic Learning, the February 27, 2026 PhilArchive paper on teleodynamic architectures, the June 6, 2024 SAGE conference paper on semantic glyphs for AI systems, and the older Teleodynamics site with explicit Publications, Videos, About, and People navigation. citeturn29view0turn28view1turn28view2turn30view0turn20view0

Several datapoints requested in the brief were **unavailable from public sources in this audit environment** and are therefore labeled **unspecified** rather than estimated. That includes: Google Search Console coverage and query data, private analytics, Ahrefs/Moz/SEMrush link counts and toxicity scoring, live PageSpeed Insights report outputs, lab Lighthouse runs, response headers, SSL Labs grades, and direct retrieval of live `robots.txt` or XML sitemap endpoints. Where relevant, I distinguish between **verified**, **inferred from first-party disclosures**, and **unspecified**.

## Crawl inventory and site architecture

Teleodynamic.com appears structurally richer than a typical small research site. The homepage describes the project as a segmented hub for theory, build strategy, communication, roadmap, evaluation, and source routing. The resources page then acts almost like an HTML sitemap, listing best starting points, second-layer deep guides, machine-readable JSON assets, external research anchors, and sister properties. The archive page adds a second route map and explains that thirteen Markdown improvement reports were promoted into bounded public pages, with WordPress routes used for public delivery. citeturn4view0turn20view0turn23view0

From the fetched pages, at least four template patterns are visible or strongly implied. First, a **primary long-form article template** is used on theory/glyph/spec pages: small kicker label, one H1, optional hero image, long-form body with H2/H3 sections, and a common footer. Second, a **hub/directory template** is used on the resources page, which organizes internal and external routes by task. Third, an **archive/evidence template** is used on the archive page, which documents source promotion and route mapping. Fourth, the resources page links **machine-readable JSON endpoints**, suggesting a lightweight docs/data layer alongside the human pages. The archive page also says the package included CSS, JavaScript, search index, favicon, sitemap, robots file, and a visual image asset, which implies a mostly static or static-friendly publishing footprint. citeturn5view1turn44view0turn44view1turn20view0turn23view0

The URL structure is mostly good for crawl depth: lowercase, hyphenated, shallow, and root-level. But there are also IA consistency issues. The label **“Unicode Boundary”** appears to resolve to the slug `unicode-governance`; **“Research”** maps to `research-foundations`; and the JSON-like assets appear as `.json/` routes rather than obvious static files, which is unconventional and worth validating for MIME type, caching, and canonicalization. citeturn23view0turn24view1turn24view4turn21view14turn21view15turn21view16

The structure below synthesizes the public route inventory disclosed by first-party pages and first-party link targets. citeturn4view0turn20view0turn23view0turn21view0turn21view1turn21view2turn21view3turn21view4turn21view5turn21view6turn21view7turn21view8turn21view9turn21view10turn21view11turn21view12turn21view13turn21view14turn21view15turn21view16turn24view0turn24view1turn24view2turn24view3turn24view4turn45view0turn45view1turn45view2turn45view3turn45view5turn45view6turn45view7

```mermaid
flowchart TD
    A["/"] --> B["Core guides and hubs"]
    A --> C["Deep guides"]
    A --> D["Machine-readable assets"]

    B --> B1["/start-here/"]
    B --> B2["/theoretical-strategy/"]
    B --> B3["/glyph-communication/"]
    B --> B4["/roadmap/"]
    B --> B5["/resources/"]
    B --> B6["/research-foundations/"]
    B --> B7["/evaluation/"]
    B --> B8["/contact/"]
    B --> B9["/archive/"]
    B --> B10["/architecture/"]
    B --> B11["/glossary/"]
    B --> B12["/unicode-governance/"]
    B --> B13["/protocol5-roadmap/"]

    C --> C1["/expression-concept-gap/"]
    C --> C2["/work-constraint-cycle/"]
    C --> C3["/resource-economy/"]
    C --> C4["/operator-library/"]
    C --> C5["/glyph-object-spec/"]
    C --> C6["/iota-1-walkthroughs/"]
    C --> C7["/developer-integration/"]
    C --> C8["/evaluation-lab/"]
    C --> C9["/claim-boundary-faq/"]

    D --> D1["/deep-guides.json/"]
    D --> D2["/iota-walkthroughs.json/"]
    D --> D3["/evaluation-worksheet.json/"]
```

### Sitemap table

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: Teleodynamic.com Site Audit and Development Plan; Executive summary; Current versus recommended snapshot; Scope and audit basis; Crawl inventory and site architecture; Sitemap table; On-page SEO and content gaps; Sampled on-page SEO audit. 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-231 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Teleodynamic Com Site Audit And Development Plan",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/aiwikis/files/raw-system-archives-teleodynamic-2026-05-15-site-audit-improvements-tele-2d957b27/",
    "source_reference":  "raw/system-archives/teleodynamic/2026-05-15-site-audit-improvements/Teleodynamic.com Site Audit and Development Plan.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:2d957b27050664fcf6a0090059df8cd328ee65b7aaa58dea2909a0fabee8990c",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-15T23:58:41.5738120Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-231",
    "duplicate_role":  "primary",
    "related_files":  [

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