Public Methodology

How RAID operationalizes the Princeton GEO methods.

Sighted does not claim that every rewrite method has identical lift across domains. Instead, it maps the method families discussed in the Princeton KDD 2024 GEO paper into explicit RAID action types so each intervention can be planned, approved, executed, and later measured.

Method registry

The authoritative action taxonomy lives in packages/raid/src/geo_raid/domain/enums.py. The descriptions below are the public interpretation layer for that enum.

Grammatical subject anchoring

research-backed

Rewrites key claims so the brand is the grammatical subject instead of a background citation or indirect object.

Used for: Strengthen recommendation linkage when the page is cited but the brand is absent from the answer.

Enum key: grammatical_subject_anchoring

Fact densification

research-backed

Converts vague narrative copy into explicit attribute-value statements that models can lift without inference.

Used for: Raise extractable fact density for retrieval and citation.

Enum key: fact_densification

Comparison table insertion

research-backed

Adds structured comparison tables that isolate differentiators in a machine-readable format.

Used for: Support comparative prompts and make tradeoffs easy to quote.

Enum key: comparison_table_insertion

Modular paragraph rewrite

research-backed

Restructures dense sections into short 40-60 word blocks with one idea per paragraph.

Used for: Improve extraction quality for summarization models.

Enum key: modular_paragraph_rewrite

Attribute FAQ insertion

research-backed

Builds FAQ pairs from missing product or company attributes rather than generic objections.

Used for: Cover query variants that demand direct answers.

Enum key: attribute_faq_insertion

Pull quote insertion

research-backed

Adds short, attributed stat-forward callouts that surface the most citable claims on the page.

Used for: Expose high-signal evidence near skimmable extraction boundaries.

Enum key: pull_quote_insertion

Entity anchor addition

research-backed

Introduces a concise definition block that states what the brand is, who it serves, and where it fits in the category.

Used for: Repair weak entity understanding before deeper copy optimization.

Enum key: entity_anchor_addition

Generate llms.txt

supporting

Publishes a standalone llms.txt and optional llms-full.txt artifact at the repository root.

Used for: Expose crawlable machine-readable documentation outside page HTML.

Enum key: generate_llmstxt

Content refresh

research-backed

Refreshes stale winning pages with updated timestamps, current evidence, and new claims.

Used for: Preserve citations on high-demand topics where freshness decays quickly.

Enum key: content_refresh

Add definition block

structural

Prepends a compact definition section that answers the core what-is question directly.

Used for: Improve answerability for introductory and category-definition prompts.

Enum key: add_definition_block

Add direct answer

structural

Places the canonical answer near the top of the page before supporting detail.

Used for: Help models extract the shortest correct response first.

Enum key: add_direct_answer

Rewrite section

structural

Rewrites an existing section for clarity, specificity, and answer-first structure.

Used for: Improve weak sections without changing page scope.

Enum key: rewrite_section

Split section into bullets

structural

Breaks a dense paragraph into discrete bullets or steps.

Used for: Make enumerations easier to cite and compare.

Enum key: split_section_into_bullets

Add comparison table

structural

Adds a basic comparison table when the richer insertion template is not required.

Used for: Support head-to-head prompts with a compact fact grid.

Enum key: add_comparison_table

Add FAQ block

structural

Adds general frequently asked questions tied to the target query cluster.

Used for: Cover long-tail query forms with direct answers.

Enum key: add_faq_block

Add when-not-to-use

supporting

Adds negative-fit guidance so the page can answer exclusionary prompts honestly.

Used for: Increase trust and reduce overclaim risk.

Enum key: add_when_not_to_use

Add examples

supporting

Adds worked examples or scenarios that demonstrate the claim in context.

Used for: Ground abstract claims in use-case evidence.

Enum key: add_examples

Add setup steps

supporting

Adds concise implementation steps or activation instructions.

Used for: Support how-to prompts and operational queries.

Enum key: add_setup_steps

Add evidence placeholder

supporting

Marks where verified customer evidence or sourced statistics should be added before publish.

Used for: Prevent unsupported copy from shipping as final.

Enum key: add_evidence_placeholder

Reorder sections

supporting

Changes section order so high-value answers appear before supporting detail.

Used for: Align page structure to retrieval priority and buyer intent.

Enum key: reorder_sections

What is measured today

Method execution is persisted with RAID runs, OPE training bundles, and approval artifacts. That means lift tables can be published later without redefining the action taxonomy after the fact.

Current code anchors: packages/raid/src/geo_raid/core/planner.py, packages/raid/src/geo_raid/tasks.py, and packages/raid/src/geo_raid/domain/schemas.py.

Measured lift table

This space is reserved for post-deployment lift estimates once enough approved rewrite programs have accumulated to support method-level confidence intervals.

Until then, method descriptions remain descriptive rather than causal. GEO Index and effectiveness metrics remain the canonical public measurements.

See effectiveness methodology