Workspace Metadata
What It Is
Workspace Metadata is a JSON payload describing your entity (name, domain, categories, NAP, schema, citations, topics, FAQs). Ranking Factory carries this payload into supported assets, ensuring consistent entity signals across all content. A WordPress post sent through the API with it gets the payload as custom fields (rf_entity_id and the rest), which WordPress keeps only where your site registers those keys for its REST API (register_post_meta with show_in_rest); on your own site the page itself shows one line linking to your About page - nothing hidden in the post.
Where It Comes From
Use Entity Factory to build your entity profile and copy the JSON payload, or provide your own. The payload must include entity_id, entity_type, canonical_name, primary_domain, and categories.
How to Apply It
1. Open Entity Factory and switch to the Metadata Injector tab. It is the one place with a box for the payload. 2. Pick your entity and press Generate Payload, or paste your own Workspace Metadata JSON into the payload box. 3. Choose the Google Docs, Sheets and Drive files, then press Inject Metadata: a Doc gets a metadata block, a Sheet a metadata sheet, and a Drive file a description and custom properties.
Supported Tools
Doc Stack, Sheets Stack, Slides Stack, Deep Embedding, Cloud Stack.
WordPress takes it too, but only through the API, as entityMetadata: no screen sends it (What It Is, above).
Not on LinkedIn
A LinkedIn post carries the text you wrote and nothing else. LinkedIn shows a post's text exactly as it was written, with no hidden part, so metadata added to a post would be read by everyone who sees it. The LinkedIn Publisher has no metadata field, and nothing is added to the posts it publishes or schedules.
Keep one canonical payload per brand and reuse it across all tools and campaigns to reinforce entity consistency.