Two Identities Of Anonymous Website Audit And Improvement Plan - Source Excerpt 01 - Two Identities Of Anonymous Website Audit and Improvement Plan
Back to Two Identities Of Anonymous Website Audit And Improvement Plan
Summary
This source excerpt begins near Two Identities Of Anonymous Website Audit and Improvement Plan and preserves the surrounding evidence from 2IA.org/agent-file-handoff/Archive/2026-05-18-publication-readiness-pass/Two Identities Of Anonymous Website Audit and Improvement Plan.md.
**Source path:** 2IA.org/agent-file-handoff/Archive/2026-05-18-publication-readiness-pass/Two Identities Of Anonymous Website Audit and Improvement Plan.md
# Two Identities Of Anonymous Website Audit and Improvement Plan
## Executive Summary
2IA already has a distinctive editorial voice and a few solid fundamentals. The published pages consistently expose a skip link, most rendered pages have clear page titles and visible H1s, the site uses HTTPS, and the privacy policy explicitly says the theme avoids analytics, tracking pixels, external fonts, CDN assets, and unnecessary cookies by default. Those are meaningful strengths for a site about surveillance, identity, and civil liberties. citeturn29view0turn30view0turn12view0
The larger problem is not concept; it is launch readiness. The current public experience still looks partly like a seeded or pre-launch WordPress build: the archive shows the default “Hello world!” post, the homepage still advertises draft topics, six footer-linked topic archives are empty, and several high-value routes exposed in navigation, footer, or homepage teasers could not be fetched in the audit environment, including Start Here, Methodology, Support, Newsletter, Volunteer, Public Records and FOIA, Corrections and Right of Reply, and multiple planned briefing URLs. That combination weakens trust, wastes crawl value, and interrupts user journeys at exactly the points where first-time readers or supporters need clarity. citeturn30view1turn28view7turn5view6turn5view7turn5view8turn5view9turn5view10turn5view11turn2view0turn2view2turn2view3turn5view0turn5view1turn5view2turn5view3turn42view0turn42view1turn42view2turn42view3turn42view4turn42view5turn42view6turn42view7turn42view8
The most important immediate move is to stop exposing unfinished structure. Every linked public route should either be fully publishable or intentionally hidden/noindexed. Google’s guidance is explicit that good title links are descriptive and distinct, snippets are built from page content and sometimes meta descriptions, structured data should describe visible page content, and `noindex` is the correct page-level way to keep low-value pages out of Google Search. For 2IA, that means removing or noindexing placeholder posts, empty taxonomies, and incomplete routes before investing in finer SEO polish. citeturn24view1turn24view2turn24view6turn41view0
The second priority is to turn the site into a coherent funnel. Right now, the homepage nav emphasizes Start Here, Methodology, Support, and About, while interior pages switch to a different nav model built around Home, What They Look For, Two Identities, Research Archive, and About. That inconsistency makes the site harder to understand and harder to navigate, especially on mobile or for first-time visitors. A single navigation model centered on cornerstone pages, topic hubs, and evidence-backed briefings will produce a much stronger user experience and a cleaner crawl path. citeturn28view0turn30view0turn38view2
The third priority is to make the published content look and behave like research, not just rhetoric. The best existing pages are thoughtful, high-level concept essays, but most of them still need dates, bylines, source notes, cross-links, clearer evidence framing, and related-briefing pathways. Google’s article, organization, and breadcrumb documentation makes it straightforward to support this with structured data, while manual accessibility testing should focus on text alternatives, descriptive link purpose, visible focus, labels, and reflow at 320 CSS pixels. citeturn37view1turn37view3turn35view0turn19view0turn19view5turn19view6turn19view7turn19view8turn19view9turn19view3
If those three things are done well—publishable routes only, one coherent information architecture, and real research-page craftsmanship—the site can quickly move from “intriguing concept with unfinished scaffolding” to “credible independent research publication.” citeturn29view0turn30view1turn21view0
## Audit Scope and Method
This audit was based on rendered-page review, public route discovery from navigation/footer/internal links, and comparison against official guidance from W3C WCAG 2.1 and Google’s Lighthouse, Search Central, Search Console, and web.dev documentation. Several same-domain URLs were discoverable from public navigation or homepage cards but could not be rendered in the browsing environment because they returned fetch failures; those were treated as public-facing risks and included in the page inventory below rather than omitted. Lighthouse itself is designed for exactly this kind of work: it audits performance, accessibility, SEO, and related quality dimensions, and can be run in Chrome DevTools, from the command line, or in CI via Lighthouse CI. citeturn29view0turn30view1turn2view0turn2view2turn2view3turn5view0turn5view1turn5view2turn5view3turn42view0turn42view1turn42view2turn42view3turn42view4turn42view5turn42view6turn42view7turn42view8turn21view0turn21view2
Because direct PageSpeed Insights or Lighthouse reports were not available within this audit capture, the performance observations below are qualitative, structure-based estimates rather than lab scores. They should be validated during implementation with mobile and desktop Lighthouse runs, PageSpeed Insights, and real-user monitoring. Google’s Web Vitals guidance remains the right benchmark: p75 LCP should be at or below 2.5 seconds, INP at or below 200 milliseconds, and CLS at or below 0.1. Google also recommends first-party real-user monitoring for these metrics rather than relying only on aggregated tools. citeturn17view0turn21view2
The effort estimates below use this scale: **Low** means copy, config, routing, or template cleanup; **Medium** means template/component/CMS changes or substantial rewrites; **High** means a new content model, significant engineering work, or a multi-sprint editorial rollout.
The chart below shows a **qualitative performance-risk estimate by page template**, based on page structure rather than machine-scored lab tests.
' ' ' mermaid
xychart-beta
title "Qualitative performance-risk by template"
x-axis ["Home","Archive","Topic essays","Legal/contact","Empty taxonomies"]
y-axis "Risk score" 0 --> 5
bar [5,4,3,2,1]
' ' '
## Sitewide Findings
The most serious sitewide issue is that the public IA currently exposes more ambition than execution. The homepage advertises Start Here and Methodology as primary onboarding routes, but those routes could not be fetched. The footer advertises Public Records, Corrections, Newsletter, and Contact-related pathways, but some of those routes were likewise unavailable. Meanwhile, the footer’s “Research areas” links route users into empty taxonomy archives rather than the better-developed conceptual pages that do exist. Google emphasizes that links are crucial both for users and for discovery, and weak internal-link destinations directly undercut that. citeturn28view0turn28view8turn2view0turn2view2turn5view0turn5view2turn5view3turn5view6turn5view7turn5view8turn5view9turn5view10turn5view11turn38view2
Branding is also inconsistent enough to create trust and SEO drag. The homepage H1 uses “2IA - Two Identities of Anonymous,” the footer uses “2IA — Two Identities of Anonymous” or “Two Identities Anonymous,” inner-page eyebrow text varies, and the visible site name line includes “International Intelligence Apparatus” even while the page repeatedly states that the project is “not affiliated with any government agency.” Google recommends distinct, concise titles and a clear main title relationship between page content and title text; 2IA should settle on one canonical brand string and use it everywhere. citeturn28view0turn28view8turn30view0turn24view1turn38view3
Content maturity is the next major issue. The site’s strongest pages are conceptual essays on identity, surveillance, OSINT, influence operations, ethics, privacy, and contact boundaries. That gives the project a coherent worldview. But the site still lacks the visible signals of a mature research publication: real briefings in the archive, stable topic hubs, bylines, publication/updated dates on most key pages, source notes, correction history, and outward-facing transparency about who writes and how claims are checked. Google’s SEO Starter Guide emphasizes useful, people-first content and corroborating resources, while Article structured data is specifically designed to help search engines understand titles, dates, authors, and images on article pages. citeturn30view1turn14view0turn14view1turn12view4turn12view5turn12view6turn12view3turn38view0turn38view2turn37view1