Additional Task Layer: External visibility, Wikipedia realism, and AI-search discoverability This project should not treat Google ranking as only a technical sitemap problem. The site also needs a broader visibility strategy so `sol.system42.one`, Sol-37, Möbius Cosmology / Mobius Cosmology, and related public pages become legible across search engines, AI summaries, and knowledge-style discovery systems. Important distinction: Do not optimize only one article. Improve the whole public information architecture so every meaningful page can stand alone as a useful, citable, indexable object. This includes: * Technical crawlability * Stable URLs * Clear metadata * Semantic page structure * Internal linking * External discoverability * AI-search readability * Future citation readiness Wikipedia / knowledge-graph strategy: Do not attempt to create a Wikipedia article for Sol-37, `sol.system42.one`, or Möbius Cosmology unless the subject clearly satisfies Wikipedia’s notability standards. A standalone Wikipedia article generally requires multiple independent, reliable, published sources that provide significant coverage of the subject. Press releases, self-published pages, personal blogs, social media posts, directory listings, and promotional mentions do not establish notability. Also note: * Wikipedia external links are generally `nofollow`, so they should not be treated as a direct SEO link-equity tactic. * Wikipedia is still highly influential for visibility, AI summaries, search engine knowledge panels, and entity recognition. * The goal should be long-term legitimacy and discoverability, not short-term link placement. * Avoid conflict-of-interest behavior. The site owner should not directly write a promotional article about their own project. * Any future Wikipedia presence should be neutral, encyclopedic, and supported by independent coverage. Practical Wikipedia-adjacent strategy: 1. Prepare the site to be citable. Pages should be written and structured so that a neutral third party could cite them if appropriate. This means: * Clear definitions * Dates of publication or revision * Author/project identity * Distinction between factual explanation, speculative model, fiction, visual essay, archive, and personal mythology * Stable URLs * No misleading scientific overclaiming * No vague archive-only pages where the useful content is buried 2. Do not spam Wikipedia. Do not add Sol-37 links to Wikipedia articles unless they genuinely improve the article and meet Wikipedia’s external link / citation standards. Especially avoid promotional insertions into pages such as: * Möbius strip * Non-orientable manifold * Cosmology * Topology * Speculative fiction * Worldbuilding If any future citation is appropriate, it should be made by an experienced neutral editor and should support an encyclopedic claim, not advertise the site. 3. Create pages that could support future independent coverage. Add or improve pages such as: * `/about/` * `/about/sol-37/` * `/glossary/` * `/press/` or `/media/` * `/citations/` or `/references/` * `/timeline/` * `/projects/` * `/mobius-cosmology/` * `/parker-county-packet/` These pages should make the project understandable to journalists, researchers, bloggers, podcast hosts, AI crawlers, and curious humans who arrive without context. External platform strategy: Because niche conceptual projects often rank faster on high-authority platforms than on new independent domains, create an optional off-site visibility plan. Do not implement spam. Recommend a legitimate distribution strategy. Potential platforms: 1. Reddit Identify relevant communities for thoughtful, non-spam discussion, such as worldbuilding, speculative fiction, topology, cosmology-adjacent discussion, creative coding, AI art discourse, or digital archives. Suggested deliverable: * A list of suitable subreddits * A short description of what kind of post would be appropriate for each * Warnings against link-dumping * Suggested post titles that invite discussion rather than advertise 2. Fandom / Wikia or independent wiki Consider whether Sol-37 should have a lore/project wiki. This may be useful for: * Glossary terms * Project mythology * Timeline * Recurring concepts * Characters/personas * Packets/documents * Visual essays * Worldbuilding structure If appropriate, create an implementation plan for either: * A Fandom wiki, or * A first-party wiki section on `sol.system42.one`, such as `/wiki/` The first-party option may be preferable if the goal is to strengthen the main domain. 3. Medium / Substack Prepare republishable summaries or companion essays that introduce major Sol-37 pages in clearer language and link back to the canonical pages. These should not replace the site. They should act as high-authority satellites. Suggested article types: * “What is Möbius Cosmology?” * “Building a Public Archive for a Speculative Cosmology Project” * “Sol-37: A Retro Archive Shell for Visual Essays, Mythic Packets, and Conceptual Topology” * “Why Every Concept in a Digital Archive Needs Its Own URL” 4. GitHub / Git-based archive presence If the project already uses GitHub or a public repo, improve the public README and documentation structure. Include: * Project overview * Site map * Glossary * Canonical links * Public archive description * License / reuse policy if applicable AI-search optimization: Search engines and AI answer systems favor clear, structured, declarative information. Create pages that answer obvious questions directly. Add or improve a glossary / FAQ section. Recommended page: `/glossary/` Recommended entries: * What is Sol-37? * What is the Sol-37 Archive? * What is the Parker County Packet? * What is Möbius Cosmology? * What is Mobius Cosmology? * What is “The Universe Is Tracing Out a Topology”? * What is a visual essay in the Sol-37 archive? * Is Möbius Cosmology a scientific theory? * Is Sol-37 fiction, philosophy, archive, or art? * Who created Sol-37? * What is `sol.system42.one`? Use direct answer structures. Example: “Möbius Cosmology, also searchable as Mobius Cosmology, is a speculative conceptual model and visual essay framework within Sol-37. It describes the universe as a self-referential topology of world-lines, inversion boundaries, recurrence, and non-orientable symbolic structure. It is not presented as an established scientific theory.” Example: “Sol-37 is a public archive and creative research shell hosted at `sol.system42.one`. It collects essays, packets, visual experiments, speculative cosmology notes, narrative logs, and conceptual documents.” Example: “The Parker County Packet is a public information packet within Sol-37 that organizes local, archival, speculative, and conceptual materials into a browsable retro archive format.” Schema / structured data: Add JSON-LD structured data where practical. Use appropriate Schema.org types without overclaiming. Recommended schema types: * `WebSite` * `WebPage` * `CollectionPage` * `Article` * `CreativeWork` * `VisualArtwork` where appropriate * `ImageObject` * `BreadcrumbList` * `FAQPage` for the glossary/FAQ page * `Person` or `Organization` only if accurate and intentionally public * `AboutPage` * `SearchAction` if the site has search Each major page should expose: * Name/title * Description * Canonical URL * Date published, if known * Date modified, if known * Author or creator, if appropriate * Parent collection, if appropriate * Image, if appropriate * Breadcrumb trail Avoid using schema to imply that speculative cosmology is accepted physics. Prefer terms such as: * speculative model * conceptual cosmology * visual essay * creative archive * philosophical topology * worldbuilding document * experimental narrative archive Suggested JSON-LD targets: 1. Homepage: `WebSite` 2. Archive index: `CollectionPage` 3. Individual essays: `Article` or `CreativeWork` 4. Visual essays: `CreativeWork` plus `ImageObject` 5. Glossary / FAQ: `FAQPage` 6. Concept pages: `WebPage` or `CreativeWork` 7. Breadcrumbs: `BreadcrumbList` Implementation task: Create a reusable metadata/schema helper if the framework supports it. The helper should allow each page to define: * title * description * canonical path * page type * image * date published * date modified * author/creator * tags * parent collection * breadcrumbs * noindex flag, if needed Then ensure every meaningful page uses it. Search result testing: Use the currently open Chrome browser window, if available, to observe current Google behavior. Record search behavior manually in the final report, but do not scrape Google aggressively. Useful test searches: * `site:sol.system42.one` * `site:sol.system42.one mobius cosmology` * `"Möbius Cosmology" "Sol-37"` * `"Mobius Cosmology" "Sol-37"` * `"The Universe Is Tracing Out a Topology"` * `"Parker County Packet" "Sol-37"` * `"sol.system42.one" "Sol-37"` * `"Sol-37" "Parker County Packet"` Also test whether major pages appear when searching their exact titles. Add a visibility report: Create a project note or report file, for example: `SEO_VISIBILITY_REPORT.md` Include: * Current indexed pages observed * Pages not yet separately indexable * New standalone pages created * Metadata/schema improvements made * Sitemap coverage * Robots.txt status * Recommended off-site visibility strategy * Wikipedia realism notes * AI-search optimization notes * Remaining tasks Do not claim success based only on `site:` search. That proves indexing, not ranking. Success criteria: The work is successful if: * Every meaningful content object has its own URL. * Every public URL has unique metadata. * Every public URL is linked from at least one crawlable index or parent page. * The sitemap lists all public indexable pages. * The glossary/FAQ provides direct machine-readable definitions. * Schema markup exists where practical. * The Möbius / Mobius terminology is handled consistently. * Wikipedia is treated as a long-term credibility/visibility ecosystem, not a shortcut. * The site becomes easier for Google, AI search, and human readers to understand without flattening the Sol-37 aesthetic into generic SEO paste.