GoodocDocument

GoodocInfrastructure

GoogleApi.ContentWarehouse.V1.Model.GoodocDocument

3
out of 10
Low
SEO Impact
Top-level representation of OCRed document

SEO Analysis

AI Generated

Backend infrastructure with indirect SEO impact. This model (Goodoc Document) contains 6 attributes that define its data structure. Key functionality includes: Debug info, recording the history of any editing done through the interface in goodoc-editing.h. The strings look like "MoveParagraph(page_index = 0, ...

Actionable Insights for SEOs

  • Understanding this model helps SEOs grasp Google's internal data architecture
  • Consider how this system might interact with other ranking signals

Attributes

6
Sort:|Filter:
EditingHistorystring
Default: nilFull type: list(String.t

Debug info, recording the history of any editing done through the interface in goodoc-editing.h. The strings look like "MoveParagraph(page_index = 0, source_block_index = 3, ...);

LogicalEntitystring
Default: nilFull type: list(String.t

Logical entities are stored as blobs. Depending on the kind of thing this is a goodoc of, a separate .proto file is expected to define the logical entity structure. Hence we can still parse this as a goodoc for people who dont care about this, and people who care about this can parse it specifically. ocr/goodoc/logical-entity-utils.h has methods to read and write these. See Goodoc++ doc

LogicalEntityMessageNamestring
Default: nilFull type: list(String.t

The names of the proto messages serialized in LogicalEntity, one for each LogicalEntity. The repetitions should number 0 to leave this unspecified, or they should equal the number of LogicalEntity strings.

SubDocumentsGoodocDocument →
Default: nilFull type: list(GoogleApi.ContentWarehouse.V1.Model.GoodocDocument.t

For multi-goodoc documents

headerGoodocDocumentHeader →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.GoodocDocumentHeader.t
pageGoodocDocumentPage →
Default: nilFull type: list(GoogleApi.ContentWarehouse.V1.Model.GoodocDocumentPage.t