Baike.dev
Log in
AI coding/GEO
G

GEO

Generative Engine Optimization: make content readable, citable, and consistently restated by AI answer engines. Handbooks, reading list, rewrite prompts, and GEOFlow.

Papers, handbooks, and two books

The livestream handbooks, research note, three papers, plus Thinking in Systems and Engineering: A Beginner’s Guide.

Rewriting one article

From the handbook to the rewrite prompt and the annotation demo: one article the model can grasp as facts, structure, and sources.

Systems, skills, and the meta skill

GEO Skills, GEOFlow, and the meta skill cover content actions, production and distribution, and how a skill itself is built.

GEO Content Engineering Handbook and Evaluation Standard

GEO Content Engineering Handbook and Evaluation Standard

Operating steps, the six-layer model, a 12-step workflow, and a 100-point scorecard drawn from 53 papers.

  1. 1Scope and main findingsScope and main findings
  2. 2A map of the 53 papersA map of the 53 papers
  3. 3First principles from the papersFirst principles from the papers
  4. 4Definition and the six-layer architectureDefinition and the six-layer architecture
  5. 5Twelve operating steps, with examplesTwelve operating steps, with examples
  6. 6Quality standard and the 100-point scorecardQuality standard and the 100-point scorecard
  7. 7Quality assessment and attributionQuality assessment and attribution
  8. 8Three complete case templatesThree complete case templates
  9. 9Roles, templates, and cadenceRoles, templates, and cadence
  10. 10Risk boundaries and white-hat GEORisk boundaries and white-hat GEO
  11. 11The 53 papers and how each one is usedThe 53 papers and how each one is used
  12. 12Checklists and prompt templatesChecklists and prompt templates
  13. 13ReferencesReferences

GEO Content Engineering Systems Research Report

GEO Content Engineering Systems Research Report

Engineering definition, how generative engines work, modules, attribution, and a 30-60-90 day path.

  1. 1Executive summaryExecutive summary
  2. 2Why content and feedback can be engineeringWhy content and feedback can be engineering
  3. 3Definition, boundary, and a working pictureDefinition, boundary, and a working picture
  4. 4From search engines to generative enginesFrom search engines to generative engines
  5. 5Cross-disciplinary mapCross-disciplinary map
  6. 6Core modules and the workflowCore modules and the workflow
  7. 7Operations, attribution, and implementationOperations, attribution, and implementation
  8. 8Cases and what other industries suggestCases and what other industries suggest
  9. 9A 30-60-90 day rolloutA 30-60-90 day rollout
  10. 10Structure for a weekend talkStructure for a weekend talk
  11. 11Risk, ethics, and boundariesRisk, ethics, and boundaries
  12. 12References and evidence gradesReferences and evidence grades
  13. 13ChecklistChecklist
  14. 14Workshop templateWorkshop template

GEO Content Engineering Method and Single-Article Tutorial

GEO Content Engineering Method and Single-Article Tutorial

A global content system and a single-page method, with a scorecard, checklists, and a running example.

  1. 1Two layers of the methodTwo layers of the method
  2. 2The global system, from assets to citationsThe global system, from assets to citations
  3. 3Global steps and the running exampleGlobal steps and the running example
  4. 4One page as a citable assetOne page as a citable asset
  5. 5Managing the features of a single pageManaging the features of a single page
  6. 6Running case: an AI support SaaSRunning case: an AI support SaaS
  7. 7Scorecard, workflow, and collaborationScorecard, workflow, and collaboration
  8. 8Templates and checklistsTemplates and checklists

Thinking in Systems

Thinking in Systems, chapter by chapter

Read it here chapter by chapter. How content, sources, and citations pull on each other.

  1. 1Stocks, flows, and feedbackSeparate stocks, flows, and feedback before deciding whether a rewrite can move anything.
  2. 2A few common structuresBalancing loops, reinforcing loops, and delays show up between publishing, measurement, and citation.
  3. 3Why a system holds togetherResilience, self-organization, and hierarchy decide whether the system can keep going.
  4. 4Why a system surprises youA wrong boundary, a model treated as the world, and nonlinear effects split "optimized" from real citation.
  5. 5TrapsA metric replaces the goal, several people edit one fact, or rules pile up without new information.
  6. 6Where leverage sitsWord frequency is weak leverage. Information, feedback, and goals make citation stable.
  7. 7Living with the systemKeep watching, put responsibility on the structure, and judge citations over a longer span.

Engineering: A Beginner's Guide

Engineering: A Beginner's Guide, chapter by chapter

Read it here chapter by chapter. Content production as engineering, with requirements, design, and failure.

  1. 1What engineering is forEngineering makes a requirement work under constraints. Content engineering does the same.
  2. 2Which layer each kind of engineering maps toStructure, information, materials, and interface each map to a layer. Do not collapse them into one line of copy.
  3. 3From requirements to a design you can testWrite the acceptance tests before the prose. Failure has to be pointable.
  4. 4What content shapes, and what constrains itA page changes how others answer a question, and it is constrained by platforms, sources, and responsibility.
  5. 5How doing the work creates knowledgeAnnotation, rejection, and sampling create knowledge the handbook does not have. Write it back into the standard.
  6. 6Old pages, capacity, and riskPublished pages age. Capacity, the cost of upkeep, and a failure plan belong in the same account.