Jeff Brigman

Clever Linked Terms helps you turn ordinary WordPress content into a connected glossary and knowledge system.
Create terms once, then let the plugin automatically link them across posts, pages, selected custom post types, and optionally FluentCommunity content. Visitors can hover linked terms for quick tooltip definitions, open full glossary pages, browse an A-Z index, and explore related concepts when Terms Engine features are enabled.
Version 1.1.1 builds on the major v1.1.0 release with smoother admin performance, better duplicate handling, optional SEO fields, compatibility placement slots, stronger import/export support, and additional cleanup for larger glossaries. Version 1.1.0 expanded Clever Linked Terms from a glossary linker into a modular semantic linking platform with a redesigned admin experience, Term Studio, Term Manager, public glossary layouts, relationship controls, optional maps, and performance-minded lazy loading for large glossaries.
<h4>What you can build with Clever Linked Terms</h4>
<ul>
<li>A public glossary or knowledge base for your WordPress site.</li>
<li>Automatically linked definitions inside articles, documentation, lessons, tutorials, reviews, and community posts.</li>
<li>A semantic term network using synonyms, aliases, abbreviations, and variations.</li>
<li>Better content discovery through related terms, tags, categories, sources, and glossary maps.</li>
<li>FluentCommunity glossary support for communities that need definitions, shared vocabulary, and learning resources inside the portal.</li>
</ul>
<h4>Core features</h4>
<ul>
<li>Create and manage glossary terms in WordPress.</li>
<li>Automatically link terms inside selected WordPress content areas.</li>
<li>Show hover tooltips with concise definitions.</li>
<li>Link terms to full public glossary pages.</li>
<li>Control link limits so long articles do not become overloaded.</li>
<li>Exclude individual terms, posts, pages, or content areas from automatic linking.</li>
<li>Create a public A-Z glossary index page.</li>
<li>Customize the glossary index slug and title.</li>
<li>Sort index entries while optionally ignoring leading words such as “a”, “an”, and “the”.</li>
<li>Choose from multiple glossary index layouts.</li>
<li>Customize tooltip, index, and single-term styling.</li>
</ul>
<h4>New in 1.1.0: redesigned admin workflow</h4>
The v1.1.0 release introduces a cleaner management experience built around modern admin screens:
<ul>
<li>Dashboard overview for plugin status and quick access.</li>
<li>Term Manager with cards, search, status filters, pagination, and per-page display controls.</li>
<li>Term Studio for creating and editing terms without relying on the default post editor workflow.</li>
<li>Status support for Published, Draft, Scheduled, Pending Review, Private, and Trash.</li>
<li>Cleaner persistent navigation across modern Clever Linked Terms screens.</li>
<li>Better Community and User Manual links in admin headers.</li>
</ul>
<h4>New in 1.1.0: Terms Engine</h4>
Terms Engine is a modular add-on layer for advanced semantic workflows. It can be enabled only when needed, and its individual tools can be turned on or off from Terms Engine -> Overview.
Terms Engine modules include:
<ul>
<li>Semantic Relationships</li>
<li>Relationship Phrase Linking</li>
<li>Term Health & Conflicts</li>
<li>Admin Term Map</li>
<li>Public Term Connections</li>
<li>Glossary Knowledge Map</li>
<li>Tag IQ</li>
<li>Bulk Tools</li>
</ul>
When Terms Engine is disabled, its menus, maps, conflict tools, relationship panels, and public widgets stay hidden so the base glossary experience remains lightweight.
<h4>Semantic relationships</h4>
Clever Linked Terms 1.1.0 adds structured relationship fields so alternate phrases can point back to the canonical term:
<ul>
<li>Synonyms</li>
<li>Aliases</li>
<li>Abbreviations</li>
<li>Variations</li>
</ul>
Relationship phrase linking can be controlled globally, per relationship type, and per term. This lets you decide whether alternate phrases should automatically link to a canonical glossary page or simply display as related metadata.
<h4>Term Health and conflict review</h4>
Term Health helps you review possible relationship conflicts and glossary quality issues.
Use it to find duplicate relationship phrases, review possible conflicts, mark conflicts clear, reopen reviewed items, and keep relationship data clean as your glossary grows.
<h4>Term maps and public connections</h4>
Terms Engine can show visual relationship maps for administrators and visitors:
<ul>
<li>Admin Term Map helps you inspect term relationships and refocus the map around selected terms.</li>
<li>Public Term Connections can appear on single term pages.</li>
<li>Glossary Knowledge Map can be opened from the glossary index without taking up page space by default.</li>
</ul>
Map features are lazy-loaded and cached to help larger glossaries stay responsive.
<h4>Glossary index layouts</h4>
The glossary index includes several layout options:
<ul>
<li>Modern Cards</li>
<li>Compact Directory</li>
<li>Split Index</li>
<li>Minimal List</li>
<li>Feature Grid</li>
<li>Glossy Panels</li>
<li>Knowledge Base</li>
</ul>
You can also control whether terms inside glossary index card content are auto-linked. Term titles continue to link to the full term page even when index auto-linking is disabled.
<h4>Single term page layouts</h4>
Choose a public layout for individual term pages:
<ul>
<li>Theme Default</li>
<li>Clean Card</li>
<li>Hero Card</li>
<li>Split Panel</li>
<li>Resource Hub</li>
<li>Editorial</li>
<li>Minimal Modern</li>
</ul>
Single term pages can show the definition, relationships, categories, tags, sources, glossary return links, and optional public term connections.
<h4>FluentCommunity support</h4>
Clever Linked Terms includes optional FluentCommunity integration for community portals using SPA-style navigation.
When enabled, the plugin can process feed and space content, reprocess content after client-side navigation, open glossary links in a new tab for community users, and track analytics context separately when Analytics is enabled.
<h4>Optional add-ons and tools</h4>
Clever Linked Terms uses modular add-ons so you can enable only what your site needs:
<ul>
<li>FluentCommunity integration</li>
<li>Analytics</li>
<li>Import / Export</li>
<li>Term Discovery</li>
<li>Terms Engine</li>
</ul>
<h4>Analytics</h4>
The Analytics add-on can track glossary impressions and clicks, matched phrases, relationship type, context, and FluentCommunity metadata when available. It helps you see which terms users are seeing, hovering, and opening.
<h4>Import / Export</h4>
Import and export glossary data for migration, backup, or spreadsheet cleanup. Version 1.1.0 supports glossary fields such as title, definition, tooltip, slug, status, scheduled date, categories, tags, sources, relationships, exclusions, and relationship linking controls.
<h4>Term Discovery</h4>
Term Discovery can help populate definitions, summaries, sources, and synonyms from optional external lookup providers. Administrators remain responsible for reviewing imported content before publishing.
<h4>Performance-minded for larger glossaries</h4>
Version 1.1.0 adds pagination, lazy-loaded maps, cache-friendly public map rendering, module-level feature controls, and safer index detection. Large glossary features are designed to load only when needed instead of rendering every heavy tool upfront.
<h4>Documentation and support</h4>
Plugin page: https://wordpress.org/plugins/clever-linked-terms/
Community and documentation links are available from the plugin admin screens.
<h3>External Services</h3>
This plugin optionally connects to third-party/external services only when the Term Discovery add-on is enabled and an administrator uses the discovery or API-test tools. The plugin works without these services, but automatic definition, synonym, and encyclopedia lookup features will not be available unless the relevant service is enabled.
When a lookup is performed, the searched glossary term is sent to the selected provider. When an API-key-protected service is used or tested, the configured API key is sent to that provider as required for authentication. API responses may be cached temporarily in WordPress transients to avoid repeated requests for the same term.
Wikimedia / Wikipedia REST API 
* Purpose: Retrieve encyclopedia summaries from Wikipedia as an optional fallback source. 
* Endpoint/domain used: https://en.wikipedia.org/api/rest_v1/page/summary/ 
* Data sent: The glossary term being searched is included in the request URL when an administrator asks Term Discovery to fetch encyclopedia content. 
* Privacy Policy: https://foundation.wikimedia.org/wiki/Privacy_policy 
* Terms of Use: https://foundation.wikimedia.org/wiki/Policy:Terms_of_Use 
* API documentation: https://www.mediawiki.org/wiki/API:REST_API
Merriam-Webster Dictionary API 
* Purpose: Retrieve dictionary definitions. 
* Endpoint/domain used: https://www.dictionaryapi.com/api/v3/references/collegiate/json/ 
* Data sent: The searched glossary term and the configured Merriam-Webster Dictionary API key are sent when an administrator requests a definition lookup or tests the API key. 
* Privacy Policy: https://www.merriam-webster.com/privacy-policy 
* Terms of Use: https://www.dictionaryapi.com/info/terms-of-service.htm 
* Requires API key.
Merriam-Webster Thesaurus API 
* Purpose: Retrieve synonyms, antonyms, and related terms. 
* Endpoint/domain used: https://www.dictionaryapi.com/api/v3/references/thesaurus/json/ 
* Data sent: The searched glossary term and the configured Merriam-Webster Thesaurus API key are sent when an administrator requests a synonym lookup or tests the API key. 
* Privacy Policy: https://www.merriam-webster.com/privacy-policy 
* Terms of Use: https://www.dictionaryapi.com/info/terms-of-service.htm 
* Requires API key.
Encyclopaedia Britannica API 
* Purpose: Retrieve encyclopedic articles and summaries. 
* Endpoint/domain used: https://syndication.api.eb.com/production/articles and https://syndication.api.eb.com/production/article/ 
* Data sent: The selected article type/category, the searched glossary term used to match returned article titles, article IDs from Britannica search results, and the configured Britannica API key are sent when an administrator requests encyclopedia content or tests the API key. 
* Privacy Policy: https://corporate.britannica.com/privacy.html 
* Terms of Use: https://corporate.britannica.com/termsofuse.html 
* Requires API key.
Free Dictionary API 
* Purpose: Retrieve dictionary definitions and pronunciation data as an optional fallback source. 
* Endpoint/domain used: https://api.dictionaryapi.dev/api/v2/entries/en/ 
* Data sent: The searched glossary term is included in the request URL when an administrator requests a definition lookup. 
* Privacy Policy: https://dictionaryapi.dev/ 
* Terms of Use: https://dictionaryapi.dev/ 
* No registration required.
API Ninjas Thesaurus API 
* Purpose: Retrieve synonyms and antonyms. 
* Endpoint/domain used: https://api.api-ninjas.com/v1/thesaurus 
* Data sent: The searched glossary term and the configured API Ninjas API key are sent when an administrator requests a synonym lookup or tests the API key. 
* Privacy Policy: https://api-ninjas.com/privacy 
* Terms of Use: https://api-ninjas.com/terms 
* Requires API key.
WordsAPI through RapidAPI 
* Purpose: Retrieve word data such as definitions, synonyms, and pronunciation. 
* Endpoint/domain used: https://wordsapiv1.p.rapidapi.com/words/ 
* Data sent: The searched glossary term and the configured RapidAPI key are sent when an administrator requests WordsAPI data or tests the API key. 
* RapidAPI Privacy Policy: https://rapidapi.com/privacy 
* RapidAPI Terms of Use: https://rapidapi.com/terms 
* Requires RapidAPI key.
Plugin support and documentation site 
* Purpose: The readme and admin help screens link to the plugin documentation/support community. The plugin does not automatically send site or user data to this site. 
* Site: https://wordpress.org/plugins/clever-linked-terms/ and https://jeffbrigman.com/community 
* Privacy Policy: https://jeffbrigman.com/privacy-policy/ 
* Terms of Use: https://jeffbrigman.com/terms/

Clever Linked Terms

Build a smarter WordPress glossary with automatic linking, tooltips, semantic relationships, maps, and FluentCommunity support.

linkwithmeshr

Formerly known as Meshr – AI Internal Linking. This plugin was rebranded to WPLink in 2026. The plugin slug (<code>meshr-ai-internal-linking</code>) and the original <code>/meshr/v1/</code> REST API namespace are preserved for backwards compatibility; a new <code>/wplink/v1/</code> namespace has been added alongside.
WPLink – AI Internal Linking is the companion WordPress plugin for the WPLink desktop app. It exposes REST API endpoints that let WPLink discover your site, extract content from supported page builders (Bricks, Elementor, WPBakery, and Beaver Builder), and safely insert internal links – including into pages that store content in page-builder metadata rather than <code>post_content</code>.
Unlike keyword-based linkers, WPLink uses semantic AI analysis to understand content meaning and context. Most websites miss 60%+ of their internal linking potential; WPLink finds them automatically and this plugin is what lets the AI reach content stored inside page builders.
Why WordPress Users Choose WPLink:
<ul>
<li>Native Bricks Builder support – Reads and writes <code>_bricks_page_content_2</code> so Bricks pages are fully indexed and linkable</li>
<li>Native Elementor support – Reads and writes the <code>_elementor_data</code> JSON tree so Elementor pages work like standard posts</li>
<li>Native WPBakery support – Reads and links directly inside <code>[vc_column_text]</code> shortcode blocks in <code>post_content</code></li>
<li>Native Beaver Builder support – Reads and writes the <code>_fl_builder_data</code> PHP object graph so Beaver Builder modules are fully supported</li>
<li>Yoast SEO & RankMath compatible – Works alongside your existing SEO plugins</li>
<li>Custom post type support – Analyzes and links all your content types</li>
<li>2-minute setup – Connect your site via Application Passwords, no coding required</li>
<li>AI-powered analysis – Semantic topic clustering and context-aware link scoring (done in the WPLink desktop app)</li>
<li>Automatic updates – Link changes are applied directly to your WordPress posts and pages via secure REST API</li>
</ul>
This lightweight plugin provides REST API endpoints that allow WPLink to discover your site, read content from standard posts and page-builder-built pages, and apply internal links safely using builder-native write paths.
Supported page builders:
<ul>
<li>Bricks Builder – content in <code>_bricks_page_content_2</code></li>
<li>Elementor – content in <code>_elementor_data</code></li>
<li>WPBakery Page Builder – content in <code>post_content</code> as shortcodes (<code>[vc_column_text]</code>)</li>
<li>Beaver Builder – content in <code>_fl_builder_data</code></li>
<li>Gutenberg / Classic Editor – standard <code>post_content</code></li>
</ul>
Features:
<ul>
<li>Multi-builder support – Bricks, Elementor, WPBakery, Beaver Builder, Gutenberg, and Classic Editor</li>
<li>Works with Yoast SEO & RankMath – Compatible with major WordPress SEO plugins</li>
<li>AI-powered semantic linking – Understands content meaning, not just keywords (analysis runs in the WPLink desktop app)</li>
<li>Custom post type support – Analyzes and links all your WordPress content types</li>
<li>Bulk link management – Review and approve AI suggestions from the WPLink app</li>
<li>Orphan page detection – Find and fix pages with zero internal links</li>
<li>2-minute setup – Configure entirely via WordPress Application Passwords</li>
<li>REST API integration – Secure, automatic link updates without manual work</li>
<li>Minimal footprint – Doesn’t store data locally</li>
<li>Security-first design – Proper capability checks and sanitization</li>
</ul>
How It Works:
<ol>
<li>Generate a WordPress Application Password in your user profile</li>
<li>Configure the credentials in the WPLink desktop app</li>
<li>WPLink discovers your site and reads from and writes to Bricks, Elementor, WPBakery, Beaver Builder, Gutenberg, and classic posts</li>
<li>All communication happens securely via WordPress REST API with Basic Authentication</li>
</ol>
<h3>API Endpoints</h3>
All endpoints are available under both <code>/wp-json/wplink/v1/</code> and <code>/wp-json/meshr/v1/</code> (legacy).
Health Check
<pre><code>GET /wp-json/wplink/v1/check
</code></pre>
Returns site info, plugin version, and capability flags (including which builders are detected and supported).
Get Post Content (builder-aware)
<pre><code>GET /wp-json/wplink/v1/posts/{post_id}/content
</code></pre>
Returns extracted plain text and an element-level breakdown. Routes to the appropriate builder handler (Bricks, Elementor, WPBakery, Beaver Builder) or falls back to <code>post_content</code> for Gutenberg/classic posts.
Insert Link (builder-aware)
<pre><code>POST /wp-json/wplink/v1/posts/{post_id}/insert-link
</code></pre>
Request body: 
 <code>json 
{ 
 "keyword": "digital marketing", 
 "target_url": "https://example.com/services/digital-marketing/", 
 "occurrence": 1 
}</code>
For Bricks pages, finds the keyword in a text-bearing element and wraps it with an anchor inside the Bricks JSON. For Elementor, mutates the <code>_elementor_data</code> widget tree. For WPBakery, replaces inside <code>[vc_column_text]</code> blocks. For Beaver Builder, modifies <code>_fl_builder_data</code> module settings. Cache regeneration is triggered automatically for each builder.
Bulk Link Update (URL migration)
<pre><code>POST /wp-json/wplink/v1/bulk-link-update
</code></pre>
Unchanged from 1.0.0. Used for URL-replacement migrations in standard <code>post_content</code>.
Webhook (Optional)
<pre><code>POST /wp-json/wplink/v1/webhook
</code></pre>
Requires HMAC signature verification. Configure <code>WPLINK_WEBHOOK_SECRET</code> in <code>wp-config.php</code>. Requests include an <code>X-WPLink-Signature</code> header. The legacy <code>MESHR_WEBHOOK_SECRET</code> constant and <code>X-Meshr-Signature</code> header are still accepted.
<h3>Privacy Policy</h3>
This plugin does not collect, store, or transmit any personal data. All communication occurs between your WordPress site and the WPLink desktop app via REST API endpoints. No external services are contacted by the plugin itself.
<h3>Support</h3>
For support, documentation, and more information, visit:
<ul>
<li><a href="https://wplink.ai/wordpress/docs" rel="nofollow ugc">WPLink Documentation</a></li>
<li><a href="https://wplink.ai/support" rel="nofollow ugc">WPLink Support</a></li>
</ul>

WPLink – AI Internal Linking

AI-powered internal linking for WordPress with page builder support.

Clever Linked Terms vs WPLink – AI Internal Linking