GEO Generate — Optional Discovery Artifacts
Generate reviewable candidate artifacts. These files do not guarantee crawling, indexing, search features, visibility, or citation.
Workflow
-
Identify an authorized static build directory.
-
Preview without writing:
npx geoptimize generate <directory> --dry-run -
Review every output:
llms.txtandllms-full.txtare experiments based on a proposal.- Candidate
ArticleorBreadcrumbListJSON-LD must match visible content. - Crawler rules have service-specific meanings; an allow rule is not an outcome guarantee.
-
Write only after the user approves the exact directory:
npx geoptimize generate <directory>
Boundaries
- Never overwrite an existing artifact without confirmation and a recoverable copy.
- Never infer
FAQPagefrom question headings. - Never add
<link rel="llms-txt">as if it were a standardized discovery mechanism. - Never auto-apply
robots.txtsuggestions. - Validate structured data against current primary documentation before deployment.