Entity plan
Knowledge graph and schema architecture. So that AI systems understand and cite you.
ChatGPT, Perplexity and search engines index you more precisely with it.
What an entity plan is
An entity plan describes your company as a network of entities and relationships. Who you are, what you offer, for whom, where, on which topics. Entities are named and linked through @id references. At the same time in Schema.org markup, llms.txt and cross-links between content. Search engines and AI systems build consistent representations of your brand from this.
Why Yoline offers this service
Yoline first implemented an entity plan for itself. docs/ENTITAETENPLAN.md in its own repository. The service grew out of this in-house use. We build for you what we built for ourselves.
If depth is wanted, an entity plan engagement follows: complete knowledge graph documentation, Schema.org implementation, llms.txt and systematic cross-linking. Effort and investment are set case by case, depending on complexity and what already exists.
Free of charge, a few days.
Entity plan engagement
Case by case, 8 to 12 weeks. Complete documentation, Schema.org implementation, llms.txt, cross-linking as entity relationships.
What the engagement includes
Entity documentation
Root entity, services, USPs, target audiences, geo entities, people, tools, concepts, relationship model.
Schema.org implementation
Organization, LocalBusiness, Person, Service as JSON-LD. @id references for cross-linking. ProfessionalService type for the advisory character.
Master data, main topics, offerings, engagement hierarchy, team profiles, partnerships as a knowledge graph extract for LLM access.
Cross-linking
Content is linked as entity relationships. Service, person, engagement and topic. AI systems recognise connections.
Who it suits
Companies that need to become visible in AI search. Organisations with several locations or business units. Providers competing for topical authority. Prerequisite: an existing web presence with a maintainable content repository (Markdown, headless CMS or your own repository).
What does not work
An entity plan complements the SEO sitemap. It works as a maintained architecture that grows with the company.
How does an entity plan differ from SEO?
SEO optimises pages for search terms. AI systems prefer knowledge graph sources because they show connections.
Do I need technical knowledge?
That is not required. Yoline supplies the documentation, the schema markup and the llms.txt. The prerequisite is a maintainable content repository.