NV oOS Content Graph transforms your WordPress content into a visual knowledge graph \u2014 organized, searchable, and interactive. Every post, page, category, tag, and author becomes a node; every relationship becomes an edge.<\/p>\n\n
No API keys. No AI required.<\/strong> The core graph engine runs entirely on your WordPress server using your existing content. Optional remote sources (like Wikidata) are opt-in \u2014 see External services below.<\/p>\n\n Click \"Build Graph\" and ~10-30 seconds later, your entire site becomes a visual graph. Supports incremental rebuilds and scheduled cron updates.<\/p>\n\n Explore your content visually using Cytoscape.js. Search for nodes by label, click for details, zoom and pan. Color-coded by content type (posts, pages, terms, users).<\/p>\n\n Discover orphan content (no internal links), thin topic clusters, and missing link opportunities. Generate actionable content strategy recommendations.<\/p>\n\n Download your graph as JSON (NetworkX), GraphML (Gephi\/yEd), CSV, Neo4j Cypher, Obsidian vault, or standalone HTML page.<\/p>\n\n Automatic structured data injection for SEO \u2014 taxonomy terms as Appends graph-neighbor posts to your content based on knowledge graph proximity.<\/p>\n\n Full programmatic access with 14 endpoints. Read endpoints require the 14 built-in tools for graph operations: query, search, traverse, analyze, export. Addon plugins can register their own tools.<\/p>\n\n This plugin does not collect, store, or transmit any personal data by default. The core graph engine runs entirely on your WordPress server using your existing content.<\/p>\n\n Remote Sources (opt-in only):<\/strong> When you explicitly configure a remote source driver (e.g. Wikidata, REST API, RSS feed), the plugin sends HTTP requests to the URLs you provide. No data is sent off-site without your explicit setup. Remote source credentials (API keys, tokens, passwords) are stored in the database encrypted with AES-256-GCM via the OpenSSL PHP extension, falling back to base64 encoding with an admin warning when OpenSSL is unavailable.<\/p>\n\n Optional AI Addons:<\/strong> The companion plugin This plugin does not require any external service for its core functionality. All graph data is computed and stored on your own WordPress server.<\/p>\n\n Wikidata (wikidata.org)<\/strong><\/p>\n\n The optional \"Resolve External Entity\" tool and the Wikidata remote-source driver query the Wikidata API ( User-configured remote sources (opt-in only)<\/strong><\/p>\n\n When you configure a remote source driver (REST API, RSS\/Sitemap feed, SPARQL endpoint, webhook receiver, etc.) in Settings, the plugin sends HTTP requests to the URLs you provide. What is sent depends entirely on the endpoint you configure. These requests happen only when you manually trigger a sync, schedule one, or receive a webhook. Remote source credentials (API keys, tokens, passwords) are stored in the database encrypted with AES-256-GCM via the OpenSSL PHP extension.<\/p>\n\n This plugin bundles the following open-source libraries:<\/p>\n\n Both libraries are served locally from That's it. Your content is now a knowledge graph.<\/p>\n\n\n No. The core graph engine works with zero external dependencies. AI features require their respective addon plugins and API keys.<\/p><\/dd>\n ~10-30 seconds for a typical WordPress site (100-500 posts). Large sites (10,000+ posts) may take 1-2 minutes.<\/p><\/dd>\n Yes. Enable \"Incremental Builds\" in settings to only process content changed since the last build.<\/p><\/dd>\n Yes. The graph explorer, shortcode, related content widget, and schema.org injection work with any theme. The shortcode Yes. Any public post type (including JetEngine CPTs) is automatically detected. You can configure which post types to index in Settings.<\/p><\/dd>\n The core graph engine runs entirely on your server. The optional \"Resolve External Entity\" tool queries Wikidata (wikidata.org) when you explicitly ask it to look up a QID. Remote source drivers connect to user-configured endpoints (REST APIs, RSS feeds, SPARQL, etc.) only when you set them up in Settings. See the External services section below for full details.<\/p><\/dd>\n Yes. The plugin supports WordPress multisite with per-site configuration.<\/p><\/dd>\n Cron schedules are cleared. Your data stays intact \u2014 reactivate at any time.<\/p><\/dd>\n All custom tables and options are removed (see What You Get<\/h3>\n\n
One-Click Graph Builder<\/h4>\n\n
Interactive Graph Explorer<\/h4>\n\n
Content Gap Analysis<\/h4>\n\n
Six Export Formats<\/h4>\n\n
Schema.org JSON-LD<\/h4>\n\n
about<\/code> and internal links as relatedLink<\/code>.<\/p>\n\nRelated Content Widget<\/h4>\n\n
REST API<\/h4>\n\n
read<\/code> capability (all logged-in users) or a valid guest token (guest tokens are provided by the NV oOS base plugin when installed); write endpoints require manage_options<\/code>.<\/p>\n\nExtensible Tool System<\/h4>\n\n
Addon Ecosystem (all optional)<\/h3>\n\n
\n
Privacy Notice<\/h3>\n\n
nvoos-content-graph-ai<\/code> (not included in this plugin) sends content to third-party AI providers (OpenAI, Google Gemini, etc.) when configured. Refer to that addon's documentation for its privacy policies.<\/p>\n\nExternal services<\/h3>\n\n
https:\/\/www.wikidata.org\/w\/api.php<\/code>) \u2014 only when you explicitly request an entity lookup by QID (e.g. Q42) or configure a Wikidata source.<\/p>\n\n\n
Third-Party Libraries<\/h3>\n\n
\n
assets\/vendor\/<\/code> and never loaded from third-party CDNs.<\/p>\n\n\n\n
nvoos-content-graph<\/code> folder to \/wp-content\/plugins\/<\/code><\/li>\n\n
Do I need an API key?<\/h3><\/dt>\n
How long does a build take?<\/h3><\/dt>\n
Can I build incrementally?<\/h3><\/dt>\n
Is this compatible with my theme?<\/h3><\/dt>\n
[nvoos_graph]<\/code> embeds wherever you place it.<\/p><\/dd>\nDoes it work with custom post types?<\/h3><\/dt>\n
Does the plugin connect to external services?<\/h3><\/dt>\n
Does it work on multisite?<\/h3><\/dt>\n
What happens if I deactivate?<\/h3><\/dt>\n
What happens if I uninstall?<\/h3><\/dt>\n
uninstall.php<\/code>). Export your graph first if you want to keep it.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.3 \u2014 2026-08-20<\/h4>\n\n
\n
[nvoos_graph]<\/code> shortcode and block embed (invalid inline script)<\/li>\n1.0.2 \u2014 2026-08-18<\/h4>\n\n
\n
nvoos-content-graph<\/code>)<\/li>\n\/resolve<\/code> auto-ingest to administrators<\/li>\n1.0.0 \u2014 2026-06-05<\/h4>\n\n
\n
NvoosContentGraph\\<\/code> namespace<\/li>\nNvoosContentGraph\\Contracts\\Tool<\/code><\/li>\n\/wp-json\/nvoos-content-graph\/v1\/<\/code><\/li>\n[nvoos_graph]<\/code> shortcode + Gutenberg block<\/li>\n