Entity Factory
When to Use Entity Factory
Use Entity Factory when you need: - Persistent entity profiles you can edit over time - Schema blocks with custom structured data - Topic clusters and keyword groupings - AI search intent maps - Bulk metadata injection into existing Google Drive files Start with Entity Stack for a quick setup, then use Entity Factory to refine.
Creating an Entity Profile
Open Tools → Entity Factory. You can: - Auto-fill from a URL - paste your website and click Scan Website - Auto-fill from GBP - enter a Google Business Profile URL and click Lookup - Enter details manually
Schema Blocks & Topic Clusters
After saving, expand Schema Blocks to add structured data (Organisation, LocalBusiness, Product, or custom types). Add Topic Clusters to group related keywords - these inform AI content generation.
The canonical page on your own site
Open the entity's hub and press Publish in the Canonical page card. We write one page on the entity's own site that states what it is - in plain sentences, and in schema.org JSON-LD (an AboutPage whose main entity is your organisation, dated), because that is the machine-readable form every AI engine reads. It goes to your connected WordPress site, or to the Shopify, Ghost, Wix or webhook connection for that domain. With none connected, the card says so, and the Google Doc and Sheet remain the hub. The page keeps one address and is rewritten whenever the entity changes; the card shows when it was last written and says if it has fallen behind. Two things stop a rewrite going out by itself. Once we have written the page on or after 7 October 2026, if it is changed on your site after we last wrote it, it is left as it is and the card says what changed - press Write it again if you want our version back. (A page we last wrote before that day has no copy of ours to compare with, so its next rewrite goes ahead and keeps one.) And once an AI engine cites the page, it is never rewritten until you approve the change: the new version waits on the project page under "A page update waits for you", and the card says it is waiting. A version waiting there stops waiting if the page is then changed on your site, because publishing it would replace that change. If you discard it, it is not offered again until the entity's facts change, and the next one waits there without a notification. The new version carries the date its text last changed. If your site does not take a version you approved, nothing on the page changes, and it waits for you again the next time the hub is written. The entity's Google Doc is held the same way while an engine cites it. Below 150 readable words the page is refused rather than published - a thin canonical page is the fault it exists to fix. The card also offers the same facts as an llms.txt to place at your site root; no major AI engine had committed to reading that file when we checked (20 Sep 2026), so it is offered because it costs nothing, not because it changes anything today. Every fact you keep on the entity under a name of your own - your prices, what a plan includes, what you connect to - is stated in the page's key facts, in the Doc and in the llms.txt, in the order you stored them, with the name made readable ("free_trial" shows as "Free trial"). A fact you have not stored is never stated.
Metadata Injection
Switch to the "Metadata Injector" tab. Browse your Google Drive, select Docs and Sheets, and inject your entity metadata. This adds hidden structured data to existing files, reinforcing your entity across the Google ecosystem.
Entity Factory and Entity Stack work together. Run Entity Stack first to create the foundation assets, then use Entity Factory to add schema blocks, topic clusters, and inject metadata into your growing library.