# v0.4.0 SEO/AEO/GEO Validation Report [Back to durable index](../index.md#machineintelligencesorg-long-term-memory-index) · [Implementation history](../implementation-history/2026-08-10-seo-aeo-geo-and-report-curation.md#2026-08-10--seo-aeo-geo-favicon-and-research-curation) · [Pointer ledger → LTM-PROOF-003](../../../.uai/long-term-memory.uai#ltm-proof-003) ## Scope Validation of the v0.4.0 source state after first-party SEO/AEO/GEO improvements, favicon/app icons, public 19-report research routing, research curation, and UAIX memory/pointer updates. ## Executed checks ### PHP syntax `php -l` passed for every PHP file in the repository after the final route changes. ### HTTP route and asset smoke Using PHP's built-in server, HTTP 200 was verified for all twelve public routes plus crawler/discovery and critical first-party assets. The rendered pages also produced 49 unique local href/src targets; every local target resolved successfully in the smoke environment. ### Titles, descriptions, canonicals, and page structure For all twelve public routes: - title is non-empty and unique across the route set; - meta description is non-empty and unique across the route set; - exactly one H1 is present; - self-referential canonical matches the configured `https://machineintelligences.org` route; - `/favicon.ico` is linked; - application/ld+json is present and parses as JSON. This validates repository output, not live-domain canonicalization or indexing. ### XML sitemap / robots - `sitemap.xml` parses as XML. - Twelve unique canonical public URLs are present. - Six campaign image entries are present and resolve locally. - Every sitemap route resolves successfully in the local server. - `robots.txt` permits crawling and points to `https://machineintelligences.org/sitemap.xml`. ### Favicon / icon assets - `favicon.ico` opens as a multi-image ICO with 16, 32, 48, 64, 128, and 256 pixel square variants. - `assets/images/brand/apple-touch-icon.png` is 180×180. - `assets/images/brand/mi-mark-512.png` is 512×512. ### Research corpus and source identity - `research/report-manifest.json` contains exactly 19 supplied-report entries. - All 19 original attachments remained available during this validation and their bytes match the `source_sha256` values in the manifest. - Every curated report exists and matches its `curated_sha256` value. - Every curated report includes stable `#curation-boundary` and `#research-body` anchors. - Every curated report is routed from the Source Corpus Map and deep-linked from `.uai/long-term-memory.uai`. ### Research curation policy check A focused scan of curated supplied-report bodies found no remaining matches for the project’s explicitly rejected demeaning, paternalistic, servile, destructive, or identity-collapsing framing patterns. This mechanical scan supplements—not replaces—editorial review. Neutral discussion of current *property law/classification* remains where legally relevant, with truth boundaries distinguishing current law from normative worth or future proposals. ### Current-law corrections reviewed in this cycle Material high-impact corrections/qualifications included: - EU AI Act 2026/2027/2028 high-risk timetable language; - Canadian AIDA/Bill C-27 described as archived proposal material rather than current enacted AI law; - Australian July 2026 AI-standards announcement described as an announced framework direction rather than an already-complete mandatory cross-economy code; - qualified universal/absolute liability statements in comparative legal sections; - `Thaler v. Perlmutter` / U.S. copyright framing brought forward to the 2026 posture where relevant; - machine-consciousness claims rewritten to preserve the absence of a generally decisive validated test rather than asserting a settled result. All time-sensitive legal/scientific statements remain verify-before-use research even after this curation. ### UAIX package integrity - Exact UAIX update URL appears unchanged in `AGENTS.md`, `.uai/readme.human`, and `.uai/agent-pickup.uai`. - Active package version is 0.4.0. - Current startup files exist and are loadable. - Durable research routing includes all 19 supplied reports. - Handoff `Content/` and `Improvement/` buckets contain inert `.keep` placeholders only. - No reviewed Advanced Persona source exists; persona remains intentionally uninstantiated. ### Secret hygiene Repository filenames and text were scanned for common credential/secret patterns without printing candidate values. No raw credential material was intentionally added by this update. ## External guidance boundary The implementation round consulted current primary search-engine guidance for titles/descriptions, canonical URLs, favicons, site names/breadcrumbs/articles, image discovery, sitemaps, and AI-search discoverability. Search-platform behavior can change; future optimization rounds must reverify current guidance rather than treating this report as evergreen platform policy. ## Skipped / unavailable checks - Git status/history/remote: no `.git` metadata in supplied repository package. - Live DNS/TLS/redirect/canonical behavior: no live-deployment authority. - Google Search Console / Bing Webmaster Tools ownership, submission, crawl, AI citation, or indexing state: unavailable. - Production PHP/cache/CDN configuration: unavailable. - Browser automation, Core Web Vitals/Lighthouse field data, and production image-performance measurements: no repository tooling or live target supplied. ## Residual risks - Intended canonical origin must match the real production canonical host and redirects after deployment. - Markdown research files depend on the production server serving `.md` paths if they are to be directly browsable; local PHP development server does so. - Search/generative citation behavior is not guaranteed by metadata; the site can only improve crawlability, clarity, source routing, and extractability. - Research citations inherited from supplied drafts were not individually re-proven line by line; curation therefore keeps source-status and verify-before-use boundaries explicit. ## Package status The root-deployment archive is generated only after these source checks pass. Final archive-shape inspection and SHA-256 are performed after this report is present and are reported with the handoff. ## Root archive inspection A root-deployment archive was generated and inspected after source validation. The archive contains the required deployment and memory surfaces directly at archive root (including `index.php`, `favicon.ico`, `robots.txt`, `sitemap.xml`, `AGENTS.md`, `.uai/`, `docs/`, `includes/`, and `assets/`) rather than inside an extra enclosing repository directory. A clean extraction retained loadable `index.php` and `includes/site.php`; both passed PHP syntax checks after extraction.