Jonomor

Checklist — Jonomor

AI Visibility Implementation Checklist

A practical implementation reference that translates the AI Visibility Framework into a concrete sequence. Each stage must be stable before the next stage produces reliable results.

Stage 1 — Entity Stability

Before any schema, content, or citation work begins, every entity in the system must be defined with a canonical name, type, @id, and description. These must be locked and governed — not changed without deliberate review.

  • Define canonical name for every entity. No variations permitted across any surface.
  • Assign Schema.org type appropriate to the entity category — Organization, SoftwareApplication, CreativeWork, DefinedTermSet, Person.
  • Assign stable canonical @id with correct fragment — #org, #app, #work, #method, #person.
  • Write canonical description anchored to the specific category — not generic promotional language.
  • Document all entities in a registry before publishing any page.
  • Ensure schema and page copy use identical entity descriptions — no drift between machine-readable and human-readable text.
  • Confirm no name variations exist across existing pages, schema, and cross-domain references.

Stage 2 — Schema Graph

Structured data must declare entity relationships explicitly — not just on the entity's own domain, but as a closed bidirectional graph verifiable from multiple entry points.

  • Deploy Organization schema on the parent organization's homepage with @id, name, description, and url.
  • Add hasPart declarations for every product entity using canonical @ids.
  • Deploy SoftwareApplication, CreativeWork, or DefinedTermSet schema on each product domain with isPartOf referencing the parent @id.
  • Deploy Person schema for the founder with worksFor referencing the parent @id.
  • Ensure all TechArticle and Article schema references canonical @ids in author and publisher fields — no inline object re-declarations.
  • Validate schema on all pages — no duplicate @id values, no inconsistent type declarations.
  • Confirm @id values are fully qualified URLs — https://domain.com/#fragment, not #fragment alone.

Stage 3 — Category Ownership

A definition page and supporting framework article establish the entity's category claim. These are the highest-priority content surfaces for AI Visibility.

  • Publish a definition page for the primary authority category with a precise H1, definition block, and schema.
  • Ensure the definition page states what the category is and what it excludes.
  • Publish a framework or methodology article that demonstrates implementation depth beyond the definitional level.
  • Confirm the definition page URL is treated as a permanent canonical surface — not subject to restructuring.
  • Add internal links from the definition page to related concept and framework surfaces.

Stage 4 — Knowledge Index

A knowledge index organizes the concept architecture into a navigable reference system — making the topic cluster machine-readable as a collection, not just as isolated pages.

  • Publish four or more concept reference pages covering distinct sub-topics within the authority category.
  • Create a knowledge index page listing all concept, framework, and definition surfaces with links.
  • Use CollectionPage schema on the knowledge index with ItemList of all available reference articles.
  • Ensure every concept page links back to the knowledge index and to at least two related concept pages.
  • Link the knowledge index from the homepage, navigation or footer, and the authority definition page.

Stage 5 — Continuous Signal Surfaces

Ongoing articles maintain topic co-occurrence frequency over time. These are not marketing content — they are the repeating signal layer that reinforces entity-topic associations in AI training data.

  • Publish an insights index as a structured CollectionPage with ItemList schema.
  • Publish ongoing articles that apply framework concepts to specific mechanisms, failure modes, or implementation patterns.
  • Ensure all insight articles use TechArticle schema with canonical @id references for author and publisher.
  • Maintain consistent entity name usage in all articles — no variations, no shorthand.
  • Cross-link insight articles to relevant concept pages, framework, and the knowledge index.
  • Add all article URLs to sitemap at consistent priority.

Stage 6 — Reference Surfaces

Reference surfaces — definitions, checklists, audit frameworks — are the dense, structured content that AI systems most reliably retrieve in response to direct-answer queries.

  • Publish a definitions index with DefinedTerm schema for each defined concept.
  • Publish a structured audit or scoring reference with machine-readable schema.
  • Publish a checklist or implementation reference page.
  • Ensure all reference pages link back to the knowledge index, framework, and ecosystem.
  • Add all reference page URLs to sitemap.
  • Review all reference pages for schema-copy consistency — machine-readable descriptions must match visible text.

Related