Clever Linked Terms

Description

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.3.0 improves large-glossary performance, moves the public linking dictionary out of inline page HTML, and loads tooltip definitions as needed. It adds checkpointed bulk maintenance, precise conflict-phrase review, and faster resumable CSV imports with refreshed counts and dismissible completed status.

When Block Editor access is enabled, the Block Editor owns the definition body while Term Studio manages the structured glossary fields, relationships, sources, SEO fields, tags, and linking controls.

What you can build with Clever Linked Terms

  • A public glossary or knowledge base for your WordPress site.
  • Automatically linked definitions inside articles, documentation, lessons, tutorials, reviews, and community posts.
  • A semantic term network using synonyms, aliases, abbreviations, and variations.
  • Better content discovery through related terms, tags, categories, sources, and glossary maps.
  • FluentCommunity glossary support for communities that need definitions, shared vocabulary, and learning resources inside the portal.

Core features

  • Create and manage glossary terms in WordPress.
  • Automatically link terms inside selected WordPress content areas.
  • Show hover tooltips with concise definitions.
  • Link terms to full public glossary pages.
  • Control link limits so long articles do not become overloaded.
  • Exclude individual terms, posts, pages, or content areas from automatic linking.
  • Create a public A-Z glossary index page.
  • Customize the glossary index slug and title.
  • Sort index entries while optionally ignoring leading words such as « a », « an », and « the ».
  • Choose from multiple glossary index layouts.
  • Customize tooltip, index, and single-term styling.

New in 1.1.0: redesigned admin workflow

The v1.1.0 release introduces a cleaner management experience built around modern admin screens:

  • Dashboard overview for plugin status and quick access.
  • Term Manager with cards, search, status filters, pagination, and per-page display controls.
  • Term Studio for creating and editing terms without relying on the default post editor workflow.
  • Status support for Published, Draft, Scheduled, Pending Review, Private, and Trash.
  • Cleaner persistent navigation across modern Clever Linked Terms screens.
  • Better Community and User Manual links in admin headers.

New in 1.1.0: Terms Engine

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:

  • Semantic Relationships
  • Relationship Phrase Linking
  • Term Health & Conflicts
  • Admin Term Map
  • Public Term Connections
  • Glossary Knowledge Map
  • Tag IQ
  • Bulk Tools

When Terms Engine is disabled, its menus, maps, conflict tools, relationship panels, and public widgets stay hidden so the base glossary experience remains lightweight.

Semantic relationships

Clever Linked Terms 1.1.0 adds structured relationship fields so alternate phrases can point back to the canonical term:

  • Synonyms
  • Aliases
  • Abbreviations
  • Variations

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.

Term Health and conflict review

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.

Term maps and public connections

Terms Engine can show visual relationship maps for administrators and visitors:

  • Admin Term Map helps you inspect term relationships and refocus the map around selected terms.
  • Public Term Connections can appear on single term pages.
  • Glossary Knowledge Map can be opened from the glossary index without taking up page space by default.

Map features are lazy-loaded and cached to help larger glossaries stay responsive.

Glossary index layouts

The glossary index includes several layout options:

  • Modern Cards
  • Compact Directory
  • Split Index
  • Minimal List
  • Feature Grid
  • Glossy Panels
  • Knowledge Base

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.

Single term page layouts

Choose a public layout for individual term pages:

  • Theme Default
  • Clean Card
  • Hero Card
  • Split Panel
  • Resource Hub
  • Editorial
  • Minimal Modern

Single term pages can show the definition, relationships, categories, tags, sources, glossary return links, and optional public term connections.

FluentCommunity support

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.

Optional add-ons and tools

Clever Linked Terms uses modular add-ons so you can enable only what your site needs:

  • FluentCommunity integration
  • Analytics
  • Import / Export
  • Term Discovery
  • Terms Engine

Analytics

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.

Import / Export

Import and export glossary data for migration, backup, or spreadsheet cleanup. CSV import/export supports glossary fields such as title, definition, tooltip, slug, status, scheduled date, categories, tags, sources, relationships, exclusions, and relationship linking controls.

Term Discovery

Term Discovery can help populate definitions, summaries, sources, and synonyms from optional external lookup providers. Administrators remain responsible for reviewing imported content before publishing.

Performance-minded for larger glossaries

The public linking dictionary is shared and versioned. Complete tooltip definitions load as needed, with cached generated resources and REST fallbacks. The glossary directory loads full term objects for the visible page rather than hydrating every definition. Admin indexes and maps use cached summaries and lazy loading.

Imports and maintenance batches defer repeated rebuilds and use database locks to coordinate concurrent requests. Term edits and linking-setting changes invalidate the relevant cached resources.

Documentation and support

Plugin page: https://wordpress.org/plugins/clever-linked-terms/

Community and documentation links are available from the plugin admin screens.

External Services

This plugin optionally connects to external lookup services when the Term Discovery add-on is enabled and an administrator uses its discovery or API-test tools. When SEOPress generates compatible IndexNow notifications for imported terms, CLT can queue and deliver those notifications through WordPress scheduled events or the administrator’s manual delivery controls. 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.

IndexNow through SEOPress
* Purpose: Batch compatible SEOPress term-publication notifications so CSV imports do not wait for a separate indexing request per term.
* Endpoint/domain used: https://api.indexnow.org/indexnow/
* Data sent: The website host, SEOPress-configured IndexNow key and key-location URL, and the published term URLs supplied by SEOPress. CLT does not generate indexing credentials.
* When used: During background queue delivery or when an administrator chooses Run Pending URLs. Failed deliveries remain queued for retry. Controls are displayed only when SEOPress is detected.
* Service documentation and protocol: https://www.indexnow.org/documentation
* SEOPress documentation: https://www.seopress.org/features/instant-indexing/

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/

Screenshots

Installation

  1. Upload the plugin files to the /wp-content/plugins/clever-linked-terms directory, or install the plugin through the WordPress plugins screen directly.
  2. Activate the plugin through the ‘Plugins’ screen in WordPress.
  3. Navigate to Linked Terms -> Settings to configure the plugin.
  4. Create your first glossary term from Linked Terms -> Add New Term.
  5. Optional: create a glossary index from Settings -> General -> Glossary Pages.

FAQ

Does Clever Linked Terms work with normal WordPress posts and pages?

Yes. You can enable term linking for posts, pages, and selected public custom post types.

Does this work with FluentCommunity?

Yes. Enable the FluentCommunity add-on in Settings -> Add-Ons, then configure the FluentCommunity tab. The integration is designed for SPA-style portal navigation.

Can I control which post types have term linking?

Yes. In the WordPress Content settings you can choose which public post types should be processed.

Can I stop a term from linking automatically?

Yes. Terms can be excluded from WordPress content, FluentCommunity content, or both. Individual posts/pages can also be excluded.

What is Terms Engine?

Terms Engine is an optional modular layer for semantic relationships, conflict review, term maps, public term connections, Tag IQ, and bulk tools. It can be enabled only when you need advanced relationship features.

Are synonyms and aliases automatically linked?

Only if Relationship Phrase Linking is enabled and the relevant global, per-type, and per-term rules allow it.

Can I create a public glossary index?

Yes. Go to Settings -> General -> Glossary Pages to create or manage the index page. You can customize the slug and title.

Can I change the glossary index title directly in WordPress?

Yes. Version 1.1.0 tracks the generated index page by stored page ID, shortcode, and plugin marker data so changing the title directly should not cause duplicate index pages.

Does Clever Linked Terms call external APIs automatically?

Term Discovery lookups require an administrator to run a lookup or API test. Separately, compatible SEOPress IndexNow notifications may be delivered from the persistent queue by scheduled events or manual delivery. CLT does not submit import notifications inline for each term.

How do bulk deletion and Clear All work?

Select terms in Term Manager, Term Health, or Bulk Tools, choose the operation, and preview the selection. Permanent deletion requires DELETE confirmation. Clear all glossary data requires administrator access and CLEAR ALL confirmation. Export a backup first. Clear All removes glossary terms in every status and associated CLT term data; plugin settings and unrelated WordPress content are retained.

Can I resume or cancel an import?

CSV imports save progress between batches. Reloading the import page resumes the active job. Cancel Import stops subsequent work while retaining terms already created. A failed batch can be retried. Completed or cancelled import status can be dismissed without deleting terms or queued notifications.

Why can imported terms be complete while IndexNow URLs are pending?

Glossary creation and indexing delivery are separate operations. When SEOPress is detected, the delivery panel shows pending URLs and provides Refresh Queue, Run Pending URLs, and Stop Sending. WordPress scheduled events also retry pending delivery; SEOPress Instant Indexing logs show the HTTP responses.

Reviews

18 Maggu 2026
Love the plugin so much…especially its use cases. This glossary plugin can be used in multiple cases and is highly useful for your site. Much appreciate the plugin author's act of creativity, intelligence and logic.
Read all 1 review

Contributors & Developers

“Clever Linked Terms” is open source software. The following people have contributed to this plugin.

Contributors

Translate “Clever Linked Terms” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.3.0

  • Improved performance and responsiveness for large glossaries.
  • Added shared linking resources and on-demand tooltip definitions.
  • Added bulk selection, permanent deletion, and complete glossary cleanup.
  • Added bulk health maintenance and precise conflict-phrase review.
  • Improved resumable CSV imports, cancellation, progress, and term-count refresh.
  • Added background and manual IndexNow delivery for compatible SEOPress notifications.
  • Added dismissal of completed import status and conditional SEOPress controls.
  • Improved query handling, input validation, translations, and cache invalidation.
  • Preserved literal backslashes in coding terms, definitions, and structured fields when importing or saving.

1.2.2

  • Improved frontend performance for large glossaries by keeping tooltip payloads compact and honoring the Tooltip Characters setting.
  • Improved WordPress Content and FluentCommunity tooltip payloads so they prefer term excerpts before falling back to definition content.
  • Reduced frontend DOM size by avoiding repeated tooltip data on every linked term occurrence.
  • Improved Block Editor-authored glossary definition rendering for embeds and dynamic block elements.
  • Improved embedded Block Editor scrolling inside Term Studio.
  • Improved Relationship Phrase Linking setting persistence.
  • Thank you to Fabien Fons.

Development build history is retained in changelog.txt.