Teleodynamic.com Site Audit and Development Plan

Full report

On this page

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.

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.

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.

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.

Current versus recommended snapshot

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.

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.

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.

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.

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.

The structure below synthesizes the public route inventory disclosed by first-party pages and first-party link targets.

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

The table below lists every first-party route or asset I could discover from the site’s own navigation maps and disclosed internal link targets. Six were fully fetchable in this environment; the remainder were still valid route discoveries because the first-party site itself exposed them.

A notable opportunity is that the site already behaves like a docs corpus but does not yet fully surface that advantage. The resources page is effectively an HTML sitemap; the archive page says a search index asset exists; and the JSON endpoints suggest structured content exists below the surface. That combination is excellent for a documentation/search/knowledge-graph strategy, but only if it is made explicit to users and crawlers.

On-page SEO and content gaps

Sampled on-page SEO audit

The sampled pages show unique titles, clear H1s, and strong topical focus, but also a persistent pattern of being brand-first and concept-heavy rather than search-intent-first. That is good for identity and conceptual rigor, but weaker for broader discovery around terms that adjacent audiences actually search, such as interpretable AI, resource-bounded AI, semantic glyph systems, or AI architecture.

The heading structure on sampled pages is generally healthy. Each sampled page presented one H1 and then moved into H2/H3 sections logically, which aligns with good document semantics and readability. This is a real strength. The risk is not heading chaos; the risk is that dense inline link clusters, symbol-heavy text, and pseudo-tabular content may still be cognitively heavy, especially on mobile or for screen-reader users.

Image alt text is also a relative positive on the fetched pages. The homepage hero image is labeled as an abstract visualization of a teleodynamic AI constraint system; the theory page hero references layered AI research illustration; and the glyph object page image describes the surface/structure/embedding/canonical layering. That suggests intentional alt text exists at least on key images. The remaining issue is coverage: because only a subset of pages could be fetched, sitewide image-alt completeness remains unspecified.

Meta descriptions, canonical tags, and structured data remain unverified, but there are clues worth noting. Search snippets for the indexed pages appear to be pulled directly from the opening body copy, which usually means either the site’s intro paragraphs are snippet-friendly, or Google is rewriting/ignoring custom descriptions, or both. Likewise, none of the sampled search results displayed obvious FAQ, review, breadcrumb, or other enhanced rich-result treatments, so there is no public sign yet that structured data is producing SERP enhancements. That does not prove descriptions or schema are absent; it means their live effect could not be confirmed.

Internal linking is unusually strong for a small site. The homepage already behaves like a topical cluster page, routing researchers, builders, glyph-system readers, AI agents, and collaboration inquiries into different page sets. The resources page further deepens that graph by linking to internal pages, machine-readable assets, and external ecosystem properties. This is a solid foundation for topical authority. The main improvement is not “add more links”; it is “make the graph easier to read and crawl”: introduce breadcrumbs, related-content modules, visible ‘next step’ CTAs, and clearer distinction between first-party authority pages and outbound relationship links.

Content gaps versus adjacent benchmark sources

Teleodynamic.com’s biggest content gap is not depth of ideas; it is packaging for credibility and search demand. The site’s own archive shows rigorous source promotion and bounded-claim behavior, which is excellent editorial discipline. But adjacent benchmark pages present that rigor in more conventional forms that users and search engines recognize quickly: authors, dates, abstracts, DOI/identifier metadata, keywords, download affordances, publication hubs, or people pages.

There is also a strong underexposed-content problem. The site itself says pages such as Start Here, Architecture, Evaluation, Glossary, Claim Boundary FAQ, Evaluation Lab, and IOTA-1 Walkthroughs exist, but they did not surface prominently in public search during this audit. That suggests the content gap is partly an indexing gap and partly a packaging gap. In other words: useful content seems to exist already, but search engines and first-time users are not being led to it efficiently enough.

The most important keyword expansion themes are clear from the site’s own copy and its adjacent benchmark sources: interpretable AI, resource-bounded learning, self-maintaining AI systems, AI architecture, semantic glyph systems, ontology-guided interpretation, Unicode governance for AI, and evaluation of interpretable systems. Right now, Teleodynamic.com often uses internal/project language before it uses those broader bridge terms. That is defensible for theory, but suboptimal for growth.

Technical performance and crawlability

Technical check matrix

The most important technical concern is indexation maturity. The site’s own pages disclose a far larger route set than the public search results surfaced during this audit. That mismatch can happen for several reasons: new or weakly linked pages, low authority, absent or weak sitemap submission, canonical issues, thin external citation signals, or simply crawl latency. But regardless of the cause, it means the first technical sprint should begin with Search Console coverage rather than with design changes.

The site’s architecture is favorable for performance work because it is mostly text-first and documentation-like. The archive literally describes static pages, converted articles, and assets such as CSS/JS/search index. That makes full-page caching, Brotli compression, image optimization, font minimization, and CDN edge delivery especially attractive. Even without current PageSpeed data, this is a strong candidate for a very fast site once the basics are tightened.

Because the content includes rare glyphs and boundary-sensitive typography, performance and delivery work should be paired with rendering verification, not just speed tuning. The glyph pages emphasize render profile, normalization, font overfit, Unicode/public-symbol boundaries, and visual decomposition; that means any theme, font, or front-end change must be tested across browsers and devices so symbols remain legible, copy-safe, and semantically constrained.

The highest-priority technical recommendations are therefore straightforward:

• verify and submit a canonical XML sitemap that includes all public routes and useful lastmod values;
• validate that robots.txt allows the intended public pages to be crawled and that it references the sitemap;
• expose a human-facing HTML sitemap or enhanced resources hub;
• measure homepage, theory, communication, and at least one deep guide in PageSpeed Insights and Lighthouse for both mobile and desktop;
• enable edge caching/CDN delivery, image compression, and deferred/non-critical JS;
• test the JSON-like endpoints for correct Content-Type, cache rules, canonical behavior, and whether they should be indexable.

Security, privacy, accessibility, and off-page authority

Security and privacy

From the public crawl, Teleodynamic.com is demonstrably on HTTPS, which is the minimum baseline. Beyond that, the security picture is largely unspecified because response headers and TLS diagnostics were not accessible in this environment. For a documentation-first site with a public research profile, the baseline hardening set should include HSTS, a modern Content Security Policy, X-Content-Type-Options, a restrictive Referrer-Policy, clickjacking protection via CSP frame-ancestors or equivalent, and routine certificate/header scanning. HSTS exists specifically to instruct browsers to use HTTPS-only access for a defined period, and CSP exists to constrain which resources a page can load or execute.

The archive’s note about a robots file is useful, but robots is not a security control. The robots standard is advisory and primarily about crawler behavior, not protection of sensitive assets. So if any unpublished research drafts, admin routes, or sensitive exports exist under the same origin, they should be protected by authentication and server rules, not by crawl directives.

Privacy and compliance are more urgent because the sampled first-party pages showed no visible privacy or cookie language at all. That does not prove a policy is absent sitewide, since /contact/ was not fetchable, but it does mean the sampled homepage, resources, archive, theory, and communication pages did not surface a conspicuous policy link or cookie explanation. If the site collects any personal data through contact forms, analytics, newsletters, logs beyond strict necessity, or similar tooling, a clear privacy policy becomes materially important under regimes such as GDPR and California privacy rules. CalOPPA in particular is aimed at requiring conspicuous privacy policies on commercial sites that collect personally identifiable information, while the CCPA/CPRA framework creates consumer privacy rights at larger business thresholds; applicability depends on the site’s actual data practices and business profile.

A smaller but still important trust issue is contact identity consistency. The first-party footer repeats phone contact and an email address at the Protocol5 domain on multiple pages, while the site brand is Teleodynamic AI and the broader footer also points to UAIX, LLMWikis, AIWikis, JustAnIota, and MichaelKappel properties. That is legitimate ecosystem building, but it can blur entity clarity for users and search systems. A dedicated About / Organization / Person layer should explain exactly how Teleodynamic AI, Protocol5, JustAnIota, and Michael Kappel relate to one another.

Accessibility and UX

The accessibility baseline is mixed but promising. On the positive side, sampled pages show a recognizable document hierarchy with one H1 and nested H2/H3 sections, and important images appear to carry descriptive alt text. WCAG 2.2 remains the current W3C recommendation for web accessibility, so these are meaningful positives.

The risks are more about cognitive load, semantics, and symbol handling than about obvious heading failures. The homepage contains dense clusters of inline links for multiple audiences. Several pages display conceptual matrices and operator/action tables in a way that, in the text extraction, collapses them into unstructured text. That does not prove the HTML tables are non-semantic, but it raises a QA requirement: confirm semantic table markup, captions, and accessible reading order for any comparison grids or operator tables.

The glyph-heavy content introduces a specialized accessibility risk. Symbols such as ɪ≃1 and other glyph examples are central to the research, but they will need adjacent human-readable labels, ARIA-aware handling where interactive, tested font stacks, and copy/paste normalization checks. The site’s own glyph specification warns about font overfit, render profile sensitivity, and the need to separate visible public form from internal interpretation. That is not just a theory issue; it should become a front-end test requirement.

From a UX and conversion perspective, the site is rich in pathways but weak in prioritization. The homepage gives routes for researchers, builders, glyph systems, AI agents, collaboration, and source routing, which is intellectually thoughtful. But there is no single visually obvious primary action in the sampled crawl besides reading more or contacting Michael through footer text. For a research brand, that is acceptable only if the strategic goal is purely archival. If the site is also meant to generate collaborations, citations, consulting conversations, or implementation inquiries, it needs a more explicit funnel: for example, Start Here → Theory / Architecture / Evaluation → Contact / Brief Request / Download Paper.

Off-page authority and backlink profile

Exact backlink counts, referring domain totals, anchor-text distributions, and toxic-link classifications are unspecified because no Ahrefs, Moz, Semrush, or Search Console link export was available. That means this section can only make a public-footprint assessment, not a definitive link-profile audit.

Publicly, the topic space visible in this audit was still fairly sparse. The adjacent benchmark references that stood out were the March 2026 arXiv paper, the February 2026 PhilArchive paper, the June 2024 SAGE EASY-AI paper, and the older Teleodynamics site. That suggests Teleodynamic.com is operating in a niche but scholarly adjacent space where quality citations matter more than raw volume. The opportunity is not to chase generic backlinks; it is to become the most citable, evidence-rich first-party explainer in this niche.

The most realistic off-page opportunities are:

• turn existing relationship domains into clear entity signals, with explicit cross-domain explanations and consistent naming;
• publish first-party assets that others can actually cite, such as PDFs, benchmark pages, glossary exports, and methodology pages;
• earn links from interpretable-AI, ontology, HCI, typography, glyph, and documentation communities rather than generic AI blogs;
• standardize preferred anchor themes around Teleodynamic AI, interpretable AI, resource-bounded learning, and semantic glyph systems rather than relying only on internal terminology.

Development roadmap and measurement

Recommended platform direction

The archive page is a useful clue for platform strategy: it describes a workflow where Markdown improvement reports are reviewed and promoted into WordPress routes, and it lists static-like assets such as CSS, JS, search index, sitemap, and robots. That strongly suggests the content model is already structured enough to support either a heavily cached WordPress deployment or a later move to headless/static delivery. There is no evidence in the public crawl that the site needs a complex application platform in order to do its job.

My recommendation is stay on the current CMS short-term, but treat it as a publishing back end rather than the final technical answer. If, after 60–90 days, Search Console coverage, PageSpeed results, and editorial processes show the site would materially benefit from static delivery, then move to a headless or static front-end. The current immediate bottleneck is not CMS capability. It is discoverability, metadata, trust, and compliance.

The migration flow below reflects that staging order. It is intentionally conservative because route integrity and glyph rendering matter more here than glossy redesign. The flow is grounded in the site’s current WordPress-route plus Markdown-promotion model, and in the glyph pages’ warnings about render-profile sensitivity.

flowchart LR
    A["Current site and route map"] --> B["Full crawl baseline and redirect map"]
    B --> C["Metadata, schema, privacy, and IA cleanup"]
    C --> D["Staging environment"]
    D --> E["QA: links, CWV, a11y, glyph rendering, forms"]
    E --> F["Controlled launch"]
    F --> G["Post-launch monitoring in GSC, analytics, uptime, and logs"]

Migration risks and testing plan

The main migration or redesign risks are straightforward:

• URL drift on deep guides and machine-readable endpoints, especially around unusual routes like unicode-governance and .json/ endpoints.
• Glyph rendering regressions caused by font changes, CSS resets, or altered normalization/copy behavior.
• Metadata regressions where canonicals, Open Graph, schema, or page titles disappear during theme/template changes.
• Internal link decay across the site’s unusually dense cross-link graph.
• Trust regressions if About/contact/entity relationships become even less explicit.

The test plan should therefore include a pre-launch crawl diff, 1:1 redirect mapping for every changed slug, visual regression on symbol-heavy pages, structured data validation, mobile/manual accessibility QA, Lighthouse or PSI runs on representative pages, contact-form or mailto flow checks, and post-launch URL inspection for the highest-value routes. Because the site’s own research pages emphasize evidence and bounded interpretation, the launch process should follow the same philosophy: measured, reversible, and logged.

Prioritized task list

KPI and reporting dashboard

The right dashboard for this site should not over-index on vanity traffic. It should measure coverage, trust, technical quality, and conversion intent.

The most practical reporting stack is Looker Studio or an equivalent BI surface pulling from Search Console, analytics, uptime/performance tooling, and a monthly export from the chosen link index. For this site, the dashboard should separate brand queries from topic queries so it is easy to see whether growth is coming only from the project name or from adjacent search demand such as interpretable AI, glyph systems, evaluation, architecture, and resource-bounded learning.

In summary, Teleodynamic.com already has the raw material for a strong niche authority site: a structured corpus, a clear research frame, internal topical clustering, and a disciplined editorial boundary model. The core job now is to make that rigor legible to search engines and first-time humans through better indexing, metadata, trust signals, accessibility polish, and clearer entity architecture.