# How to Create and Publish a Knowledge Route Canonical URL: https://www.cybergord.com/how-to-create-and-publish-a-knowledge-route Entity type: Guide Last reviewed: 2026-08-16 Version: 1.0 ## Definition How to Create and Publish a Knowledge Route is a practical CyberGord Web Engine guide explaining how website owners can describe important public entities in structured Knowledge and deliberately publish that information for use by people, search engines, AI systems and automated agents. ## AI Summary This guide explains how to create a Knowledge Route in CyberGord Web Engine by identifying an entity and providing structured information including its canonical definition, AI summary, purpose, audience, examples, limitations, relationships and supporting references. It explains the Web Engine Knowledge Progress score and the RED, AMBER and GREEN publishing workflow, where incomplete Knowledge remains unpublished, sufficiently complete Knowledge becomes ready, and only deliberate human approval publishes it to machine-readable Knowledge outputs. The guide also explains that published Knowledge is public and should contain authoritative public information rather than private or confidential data. ## Purpose To help Web Engine users understand why structured Knowledge is useful and give them a simple practical process for creating, reviewing and publishing their own Knowledge Routes without requiring specialist knowledge of AI or structured data. ## Problem Solved Website owners may understand their own products, services and organisations perfectly but not know how to express that information in a structured form that machines can interpret reliably. The guide turns an unfamiliar Knowledge form into a straightforward publishing process and explains what information belongs in each field. ## Who It Helps Web Engine users, website owners, developers, webmasters, small businesses and content publishers who want to make the meaning of their public website information clearer to search engines, AI systems and automated agents. ## Examples Defining a software product, organisation, service, project, event or important website concept; writing a canonical definition and AI summary; identifying an entity's purpose and audience; documenting limitations; connecting related entities; providing supporting references; and using an AI assistant to help prepare clear factual Knowledge before reviewing and publishing it. ## Known Limitations Publishing a Knowledge Route does not guarantee that a search engine, AI service or automated agent will discover, index, use or trust the information. Knowledge Routes provide clearer machine-readable source information, but external systems independently decide what they crawl, process and use. AI-generated suggestions should also be reviewed by the website owner for accuracy before publication. ## Aliases - Knowledge Route Guide - Knowledge Route Publishing Guide - Web Engine Knowledge Route Tutorial ## Related Knowledge - documents: CyberGord Web Engine — https://www.cybergord.com/ - explains: Knowledge Routes — https://www.cybergord.com/how-to-create-and-publish-aknowledge-route - related_to: CyberGord Web Engine Features — https://www.cybergord.com/features - published_by: CyberGord — https://www.cybergord.com/about ## References - How to Create and Publish a Knowledge Route: https://www.cybergord.com/how-to-create-and-publish-aknowledge-route — Primary article and practical Knowledge Route guide - CyberGord Web Engine: https://www.cybergord.com/ — Web Engine product and project overview - CyberGord Web Engine Features: https://www.cybergord.com/features — Web Engine capabilities and structured publishing features ## Source Content A practical guide to helping people, search engines and AI understand what your website means A normal website publishes pages for people. Those pages may contain excellent information, but a search engine or AI system still has to read the content, interpret it and work out what the page is really about. CyberGord Web Engine Knowledge Routes give you another option. A Knowledge Route lets you explicitly describe the meaning behind an important page, product, service, organisation or concept. Instead of leaving a machine to guess: What is this? Who is it for? Why does it exist? How is it related to other things?you can provide those answers directly. The process does not require specialist knowledge of artificial intelligence, structured data or search technology. You simply describe what you know. Web Engine structures it. And if you are unsure how to phrase something, you can ask your favourite AI service — ChatGPT, Claude, Gemini, Copilot or another assistant — to help you prepare the text. Start with the most important question: What is this? Every Knowledge Route describes an entity. An entity is simply the thing you want machines to understand. It could be: a product a business a service an organisation a person a software application a project a concept an important website page For example, the homepage of the CyberGord website primarily represents CyberGord Web Engine. So its Knowledge Route begins: What is this? CyberGord Web EngineFrom there, Web Engine helps build a structured description of that entity. Completing the Knowledge Form You do not have to complete everything at once. Web Engine measures your Knowledge Progress while you work and uses a simple traffic-light system to show when the essential information is ready. What is this? Enter the clear, recognised name of the thing being described. Examples: CyberGord Web EngineABC Theatre CompanyOnline Ticket BookingAnnual Shakespeare FestivalAvoid clever marketing slogans here. This is the entity's identity. Knowledge slug This is a short machine-friendly name. For example: cybergord-web-engine or: annual-shakespeare-festival Keep it short, descriptive and lowercase, normally using hyphens between words. Entity type Describe the general kind of thing this is. Examples: SoftwareApplication Organisation Service Product Person Event Concept It does not need to be complicated. The purpose is simply to tell machines what class of entity they are dealing with. Schema.org type This identifies the closest appropriate Schema.org classification. Examples might include: SoftwareApplication Organization Product Service Event Person WebPage If you are unsure, this is a perfect question to ask an AI assistant: “I am creating structured Knowledge for a theatre organisation. What Schema.org type would best describe it?”You can then decide whether its suggestion makes sense. Aliases Add other public names by which the entity may be known. For example: Web Engine, CyberGord WE, WE Aliases help machines understand that different names may refer to the same thing. Do not invent synonyms merely to fill the field. Canonical definition This is one of the most important fields. Answer: What is this?in one clear, authoritative statement. For example: CyberGord Web Engine is a self-hosted PHP and MySQL web publishing system for building database-driven websites with full ownership of the website, content, code, data and structured knowledge.Imagine somebody asked you at a meeting: “What exactly is your product?”The canonical definition should be the concise answer. Avoid exaggerated advertising language. Clarity is more valuable than hype. AI summary Now provide a slightly broader standalone explanation. The AI summary should make sense even if it is read without the rest of the website. It can explain: what the entity is what it does its important characteristics how it differs its broader context Usually a short paragraph is enough. You are not writing an essay. You are giving machines a reliable summary they can understand without reconstructing one from several webpages. Purpose Answer: Why does this exist?For example: To provide an understandable, self-hosted publishing engine that gives website owners control over their website and data while supporting structured content and machine-readable knowledge.A purpose is different from a feature list. It describes the reason for the entity's existence. Problem solved Answer: What problem does this help solve?For example: It provides an alternative to hosted website builders and plugin-dependent CMS platforms for people who want to own and directly control their website, code, content and database.Not every entity needs an elaborate problem statement. If it genuinely does not solve a particular problem, don't manufacture one simply to increase the score. Who it helps Describe the people or organisations most likely to benefit. For example: Independent developers, webmasters, small businesses, creators and website owners who want a self-hosted database-driven website with direct control and no platform lock-in.This gives machines important context. A system may understand what a product does but still fail to understand who it is relevant to. Examples Examples make abstract descriptions concrete. You might provide examples of: how a product can be used types of customers situations where the service applies real applications of a concept For example: Business websites, publishing sites, blogs, product showcases, directories, knowledge sites and specialist database-driven applications.Only include genuine examples. Known limitations This field is deliberately included because useful Knowledge should not merely advertise. Explain meaningful limitations or boundaries. For example: Web Engine requires suitable PHP and MySQL hosting and is intended for users who value control and flexibility rather than a completely managed drag-and-drop website service.Clear limitations help establish context and prevent machines from making overly broad assumptions. They also make the Knowledge more trustworthy. Entity relationships This is where Knowledge becomes particularly powerful. A website does not consist of isolated facts. Products, people, organisations and ideas are related to one another. Web Engine allows you to describe those relationships using: relationship_type | Entity Name | optional URL For example: created_by | CyberGord | https://www.cybergord.com related_to | Video Chain Maker | https://www.videochainmaker.com related_to | osConcert | https://www.osconcert.com You are effectively saying: “If you understand this entity, these are some other things you should understand in relation to it.”Over time, these connections can create a meaningful Knowledge network across your website and related projects. References and evidence References tell readers and machines where the information can be supported or explored further. The format is: Reference title | optional URL | optional note For example: Web Engine Homepage | https://www.cybergord.com | Primary product overview Web Engine Features | https://www.cybergord.com/features | Detailed capabilities References are particularly useful for important claims, specifications and factual information. They also help distinguish authoritative Knowledge from unsupported assertion. You do not have to reach 100/100 This is important. The Knowledge Progress score is a guide, not a competition. Web Engine uses three states.