Clever Linked Terms — User Manual

Clever Linked Terms

Complete User Manual — glossary terms, automatic linking, Term Studio, Term Manager pagination, duplicate detection, customizable glossary index pages, Terms Engine, semantic relationships, term health, SEO fields, compatibility slots, public maps, FluentCommunity support, analytics, import/export, discovery tools, and aOS/AdminOS compatibility.

Version 1.1.1 Manual

1. Getting Started

Clever Linked Terms is a WordPress glossary, automatic linking, and semantic relationship plugin. It helps site owners define important terms, link those terms throughout content, show tooltip previews, build a public glossary index, and optionally enable a deeper Terms Engine for relationships, term health, maps, and semantic organization.

1.1 Requirements

WordPress 6.0 or higher. The v1.1.1 release line is marked Tested up to WordPress 7.0.
PHP 8.1 or higher.
Administrator access to configure settings, add-ons, import/export, and Terms Engine tools.
FluentCommunity is optional and only required when using the FluentCommunity add-on.
A theme or builder that outputs normal frontend content containers. Bricks, block themes, classic themes, and many custom layouts can work as long as selectors are configured correctly.

WordPress 7.0 note: WordPress 7.0 includes admin visual updates and continued movement toward iframed editor behavior. Clever Linked Terms uses its own Term Studio workflow and avoids depending on fragile block-editor assumptions for core term editing.

1.2 Installation

Install from WordPress.org

Go to Plugins → Add New Plugin.
Search for Clever Linked Terms.
Click Install Now, then Activate.

Upload a ZIP package

Go to Plugins → Add New Plugin → Upload Plugin.
Upload clever-linked-terms.zip.
Click Install Now, then Activate Plugin.

FTP/SFTP installation

Unzip the package on your computer.
Upload the clever-linked-terms folder to /wp-content/plugins/.
Activate Clever Linked Terms from the Plugins screen.

1.3 First Setup

Go to Clever Linked Terms → Settings and confirm the main glossary is enabled.
Create your first term from Term Manager or Add / Edit Term. If the title matches an existing term, Clever Linked Terms can warn you and save the duplicate as a draft for review.
Add a title, tooltip summary, and full definition.
Review WordPress Content settings to choose which post types and content selectors should be linked.
Create or place the glossary index shortcode on a public page. If you use the generated page option, set both the glossary index title and slug before creating it.
Enable add-ons only when you need them. For deeper semantic tools, enable Terms Engine first, then enable its individual feature cards from Terms Engine → Overview.

Recommended first test: Create three published terms, visit a normal post/page that contains those phrases, then confirm links and tooltips appear as expected.

2. What Clever Linked Terms Does

2.1 Core Glossary

The core plugin creates a glossary term content type and can automatically link term titles inside selected WordPress content. Each term has its own public page, optional tooltip summary, full definition, sources, exclusions, and display settings.

Terms

Each glossary entry stores the canonical term, definition, tooltip summary, slug, status, and optional metadata.

Automatic Linking

The frontend linker finds matching term titles in configured content areas and turns them into glossary links.

Tooltips

Visitors can hover linked terms to see a quick explanation before opening the full term page.

Glossary Index

A public directory can list terms using modern layouts and optional search/filter controls.

2.2 Terms Engine

Terms Engine is an optional add-on that turns the glossary into a semantic structure system. When enabled, it can add relationships, conflict review, term health, semantic tags, link rules, public maps, and admin relationship tools.

Important: Terms Engine is intentionally gated. When the add-on is disabled, Terms Engine menus, maps, relationship controls, conflict tools, public connection maps, glossary maps, and related UI should not load.

2.3 Add-On Model

Add-ons keep heavier or context-specific features disabled until needed. This helps smaller glossary sites stay simple and gives large sites more control over performance and admin complexity.

Add-On	Default	Purpose
FluentCommunity	Off	SPA-aware linking inside FluentCommunity portal content.
Analytics	Off	Click/impression tracking and reports.
Import / Export	Off	CSV/XML movement of terms and metadata.
Term Discovery	Off	External definition, summary, and synonym lookup helpers.
Terms Engine	Off	Semantic relationships, maps, health, conflict review, and advanced term organization.

3. Settings & Add-Ons

3.1 Settings Layout

The settings area contains core plugin configuration and optional add-on controls. Modern plugin admin pages use a persistent menu with grouped sections.

Group	Pages	Notes
Core	Dashboard, Term Manager, Add / Edit Term, Settings	Always visible for normal plugin management.
Data	Analytics, Import / Export	Only visible when at least one related add-on is enabled.
Terms Engine	Overview, Relationships, Term Health, Link Rules, Categories, Tags, Tag IQ, Term Map, Bulk Tools	Only visible when Terms Engine and the relevant module are enabled.

3.2 Add-Ons

Use Settings → Add-Ons to enable or disable top-level add-ons. The Terms Engine card only controls the main Terms Engine add-on. Individual Terms Engine modules are managed from Terms Engine → Overview.

Why this split exists: The add-ons screen answers “Do I want this major feature area at all?” The Terms Engine Overview answers “Which Terms Engine tools should this site use?”

3.3 Terms Engine Add-On

When the Terms Engine add-on is disabled, the plugin should behave like a clean glossary/linking plugin. The following should not appear or load:

Terms Engine persistent menu group.
Terms Engine admin pages and direct tool access.
Semantic relationship fields in Term Studio.
Conflict/review queue functionality.
Term maps, public term connections, and glossary knowledge maps.
Relationship phrase auto-linking controls.
Tag IQ, Bulk Tools, and Terms Engine-only panels.

4. Term Manager & Term Studio

4.1 Term Manager

Term Manager is the card-based management area for glossary terms. It supports searching, filtering, quick status views, and actions for editing/viewing terms.

Feature	Description
Status filters	All, Published, Drafts, Scheduled, Review, and Trash.
Search	Find terms by title, slug, definition, or relevant metadata.
Pagination	Choose how many terms to show at a time so large glossaries do not render every term on one admin screen.
Terms per page	Select 20, 50, 100, or 200 terms per page from the Term Manager toolbar.
Conflict badges	When Terms Engine health/conflicts are enabled, badges can link to Term Health filtered for that term.
Actions	Edit/view terms without duplicating confusing actions.
Instant filtering	Search, status filters, terms-per-page changes, and pagination can update smoothly without full page reloads.

Large glossary tip: Use the Terms per page selector when managing hundreds of terms. Smaller pages keep the admin screen faster and easier to scan.

4.2 Term Studio

Term Studio is the modern term editor workflow. It replaces the default post editor experience for managing glossary content in a more structured way.

Title and slug.
Status: Published, Draft, Scheduled, Pending Review, Private, and Trash.
Scheduled date field, shown only when Scheduled is selected.
Tooltip summary.
Full definition editor.
Sources field.
Categories and tags.
WordPress and FluentCommunity exclusions.
Terms Engine panels when the add-on/modules are enabled.
Optional Search / SEO fields when enabled from General settings.
Optional Ad / Compatibility fields when enabled from General settings.
Live duplicate title warning while creating a new term.

4.3 Term Fields

Field	Used For	Notes
Tooltip Summary	Short hover preview	Keep concise. This is not meant to replace the full definition.
Definition	Full term explanation	Appears on single term pages and may provide fallback tooltip text.
Sources	References and URLs	Stored separately from the definition body and can be imported/exported.
Categories	Structured grouping	Useful for navigation and maps.
Tags	Semantic organization	Non-hierarchical taxonomy data; not auto-linking terms by default.
Exclusions	Per-term linking control	Can prevent linking in WordPress or FluentCommunity contexts.
Search / SEO	Optional metadata	Can sync with supported SEO plugins or store local fallback metadata when enabled.
Ad / Compatibility Fields	Optional content slots	Provides before/after definition and before/after metadata areas for ads, shortcodes, or compatible plugin output when enabled.

5. Terms Engine Overview

5.1 Overview Cards

The Terms Engine Overview is the control center for semantic modules. Tool cards and module cards are one and the same: each card explains what the feature does, shows whether it is enabled, provides a toggle, and includes a manage action when active.

Note: Individual Terms Engine features default to disabled and must be enabled before their menus, public widgets, editor panels, and admin tools appear.

5.2 Feature Toggles

Feature	Default	What It Controls
Semantic Relationships	Off until enabled	Synonyms, aliases, abbreviations, variations, relationship panels, relationship chips, and the Relationships page.
Relationship Phrase Linking	Off until enabled	Whether relationship phrases can be auto-linked back to canonical term pages.
Term Health & Conflicts	Off until enabled	Possible Issues, conflict review, mark clear/reopen, and related health cards.
Admin Term Map	Off until enabled	Admin-only term map page and focused relationship mapping tools.
Public Term Connections	Off until enabled	Visitor-facing term connection map on single term pages.
Glossary Knowledge Map	Off until enabled	Visitor-facing glossary-level map shown behind a smooth launcher on the glossary index.
Tag IQ	Off until enabled	Tag intelligence and coverage tools.
Bulk Tools	Off until enabled	High-impact bulk term and relationship operations.

5.3 Persistent Menu

The persistent menu should stay focused. It shows only enabled areas and uses clear labels:

Link Rules, not “Linking Rules.”
Tag IQ, not “Tags Intelligence.”
Bulk Tools last in the Terms Engine group.
Review Queue does not appear as a separate menu item because it is merged into Term Health.

6. Semantic Relationships

Semantic relationships let alternate words and phrases point to one canonical glossary term. This helps visitors find the right explanation even when they use shorthand, plural forms, abbreviations, or different wording.

6.1 Relationship Types

Type	Use For	Example
Synonyms	Words or phrases with similar meaning.	`community` → group, network
Aliases	Alternate names, nicknames, product names, older names, or common shorthand.	`FluentCommunity` → FCom
Abbreviations	Acronyms, initialisms, or short forms.	`Search Engine Optimization` → SEO
Variations	Plural/singular forms, spelling variants, tense, hyphenation, or punctuation differences.	`plugin` → plugins, plug-in

6.2 Linking Controls

Relationship phrase linking is intentionally separate from relationship storage. A site can store synonyms and aliases for organization without automatically linking those phrases in content.

Control	Description
Global setting	Turns relationship phrase linking on or off overall.
Per-type controls	Allows different handling for synonyms, aliases, abbreviations, and variations.
Per-term override	Each term can inherit global settings, enable relationship linking, or disable it.

Best practice: Enable relationship phrase linking cautiously on large sites. Start with abbreviations and aliases before turning on broad synonym linking.

6.3 Conflicts

Conflicts happen when the same relationship phrase appears on more than one term. Conflicts are not always errors, but they should be reviewed so the correct canonical term owns the phrase.

Use Term Health to review possible conflicts.
Use Mark this conflict clear only when the phrase has been reviewed and is safe to ignore.
Reviewed conflicts stay out of normal action areas until reopened or viewed through the reviewed-clear filter.

7. Term Health

7.1 Possible Issues

Term Health combines review queue behavior, conflict review, and quality checks into one Terms Engine module. Heavier Term Health views are paginated by default and can update with smoother AJAX-style filtering where supported. The interface should use the phrase Possible Issues rather than “Signals.”

Duplicate or conflicting relationship phrases.
Terms missing helpful definitions or summaries.
Relationship phrases that may need review before auto-linking.
Terms that require editorial attention.

Import cleanup: Placeholder values such as none, n/a, na, null, -, and — should be ignored in list-style import fields.

7.2 Conflict Review

Active conflicts should present one clear action. Conflict lists are paginated so large relationship libraries remain easier to review. Reviewed conflicts should not clutter normal term rows or action panels. Reopen is available from the reviewed-clear view.

State	Expected Behavior
Active conflict	Shows a clear action such as Mark this conflict clear.
Reviewed clear	Hidden from normal action areas and available in the reviewed-clear filter.
Reopened	Moves back into active review.

8. Term Maps & Connections

8.1 Admin Term Map

The admin Term Map shows a focused relationship view for a selected term. Connected term lists are paginated by default so large glossaries do not load every connection at once. Term nodes are clickable and can refocus the map dynamically without a full page reload. Direct URLs can use parameters such as focus_term or term_id so bookmarked links can open a specific map focus.

Connections may be based on:

Shared tags.
Shared categories.
Relationship data such as synonyms, aliases, abbreviations, and variations.

8.2 Public Term Connections

When enabled, single term pages can show a visitor-facing Term Connections map. This is separate from the admin map link. Visitors can explore related terms without admin access.

Performance note: Public term connection maps lazy-load when they come into view, instead of rendering all map markup during the initial page load.

8.3 Glossary Knowledge Map

The glossary index can include a visitor-facing Glossary Knowledge Map behind a simple launcher such as View glossary map. The map expands with a smooth transition so it does not take up space by default.

The map is available only when the Terms Engine add-on and Glossary Knowledge Map module are enabled.
Terms in the map link to single term pages.
The larger map is lazy-loaded through AJAX/JSON-style rendering to avoid slowing down initial glossary page load.
Map output uses cached HTML/data where possible and invalidates when relevant term/category/tag data changes.

9. Glossary Index

9.1 Creating the Index Page

The glossary index is a public directory of published glossary terms. Create it from Settings → General → Glossary Pages or place this shortcode manually on any page:

[clevlite_linked_terms_index]

When generating the index page from settings, you can set both the public page title and the URL slug.

Setting	Purpose	Notes
Glossary Index Title	Controls the generated page title and the wording used by “Back to” buttons on single term pages.	You may also edit the page title directly in WordPress after the page is created.
Glossary Index Slug	Controls the generated page URL slug.	You may also edit the page slug directly in WordPress after the page is created.
Create Index Page	Creates the public glossary page with the selected title, slug, and shortcode.	The plugin tracks the generated page by stored page ID and shortcode so title or slug edits do not cause duplicate page creation.

Good to know: If you rename the glossary page directly in WordPress, Clever Linked Terms should still recognize it as the glossary index as long as the page remains available and contains the glossary index shortcode.

9.2 Layouts

Glossary index layouts include:

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

9.3 Index Auto-Linking

The setting Auto-link terms inside glossary index controls whether glossary card content should be processed for tooltip/linking behavior.

Setting	Recommended Default	Description
Auto-link terms inside glossary index	Off	When disabled, the index avoids tooltip auto-linking/popups inside glossary card content. Term titles still link to full single term pages.

9.4 Sorting & Sticky Menu

Glossary index settings include options for cleaner A-Z sorting and sticky navigation behavior.

Setting	Default	Description
Ignore leading words when grouping the glossary index	Off	When enabled, terms such as The Odyssey can still display normally while grouping under O instead of T.
Ignored Leading Words	`a, an, the`	Comma-separated leading words to ignore for glossary grouping and sorting.
Sticky Header Offset	0	Manual fallback offset for themes/builders with sticky headers. The glossary menu also attempts to detect visible sticky/fixed headers automatically.

Sorting note: Leading-word sorting does not change the term title, slug, permalink, tooltip, or automatic linking behavior. It only affects glossary index grouping and sort order.

10. Single Term Pages

10.1 Layouts

Single term pages can use several global layout styles:

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

10.2 Page Elements

Single term pages can show the title, full definition, relationships, categories, tags, sources, glossary index link, and optional public term connections. The definition should appear only once.

Element	Notes
Definition	Shown once as the main term content.
Relationships	Relationship chips should link when relationship display is enabled.
Categories/tags	Linked to taxonomy archives where appropriate.
Sources	Shown separately from the definition body.
Back to glossary link	Uses the configured/generated glossary index title, such as Back to Knowledge Base. The same wording should appear at the top and bottom where supported.

10.3 Admin Map Link

Users who can edit/manage terms may see a clear link such as View Term Map or Explore term connections. This admin link opens the Terms Engine admin map focused on that term. Public visitors should not see the admin link.

11. WordPress Content Linking

11.1 Post Types

The WordPress Content settings decide where automatic linking is allowed in normal WordPress frontend content.

Setting	Default	Description
Enable WordPress Content	On	Enables linking in normal WordPress content.
Select Post Types	Posts, Pages	Choose which public post types should be processed. Glossary terms and attachments are excluded.

11.2 Selectors

The content selector tells the frontend linker where to look for terms.

.entry-content, .post-content, .article-content

Advanced setting: A bad selector can make the plugin appear broken. Change selectors only when your theme/builder uses unusual markup.

11.3 Exclusions

Use exclusions to keep certain pages/posts or individual terms from being automatically linked. This is useful for sales pages, legal pages, landing pages, or content where automatic links would be distracting.

12. FluentCommunity

12.1 Enabling

Install and activate FluentCommunity.
Go to Clever Linked Terms → Settings → Add-Ons.
Enable the FluentCommunity add-on.
Configure the FluentCommunity content areas.

12.2 SPA Behavior

FluentCommunity uses client-side navigation. Clever Linked Terms includes SPA-aware processing so terms can continue working after portal route changes and feed updates.

Portal assets load through FluentCommunity-aware hooks.
Term processing can re-run after navigation without relying only on full page refreshes.
Analytics context can identify FluentCommunity events separately from normal WordPress content.

12.3 New Tab Links

In FluentCommunity, glossary links open in a new tab to preserve the community portal state. Normal WordPress content links can use standard same-tab behavior.

13. Styling

13.1 Tooltip Styling

Tooltip styling controls include background color, text color, border color, border width/style, font size, and font weight for light/dark contexts.

13.2 Glossary Styling

Glossary styling controls affect the generated index, including accent color, navigation backgrounds, term card backgrounds, borders, and active/inactive letter colors.

13.3 Term Page Styling

Single term pages include layout and typography controls so users are not locked into overly narrow widths or tiny type. Styled layouts should remain useful for themes and builders such as Bricks.

Builder note: If your theme already provides strong layout styles, use Theme Default or choose width/font controls that complement the builder rather than fighting it.

14. Analytics

14.1 Tracking

The Analytics add-on tracks glossary impressions and clicks so you can understand which terms are being seen, clicked, and engaged with.

Data	Example	Description
Event Type	impression, click	Whether a term was seen/hovered or clicked.
Term ID	123	The canonical term attached to the event.
Matched Text	FCom	The exact phrase matched.
Relationship	alias	Primary term, synonym, alias, abbreviation, or variation.
Context	wordpress, fluentcommunity	Where the event occurred.

14.2 Reports

Top Performing Terms.
Recent Events.
Activity Over Time.
Activity by Relationship Type.
Top Matched Words & Phrases.
Activity by Context.
Top FluentCommunity Spaces when available.

15. Import & Export

15.1 Supported Fields

CSV/XML import and export workflows support v1.1.1 fields:

Title, definition, tooltip, slug, status, and scheduled date.
Categories and tags.
Sources.
Synonyms, variations, abbreviations, and aliases.
WordPress and FluentCommunity exclusions.
Per-term relationship linking mode.
Per-type relationship linking toggles.
SEO title, meta description, Open Graph title, Open Graph description, and social image URL.
Before/after definition compatibility content and before/after metadata compatibility content.

15.2 Placeholder Values

Importer cleanup should ignore placeholder values in list-style fields:

none
n/a
na
null
-
—

This prevents imported placeholder text from becoming real relationship phrases, tags, or source entries.

Duplicate handling: Imports check for existing term titles before creating new terms. If duplicates are found, the import can stop for review. If you explicitly allow duplicate imports, imported duplicates are saved as drafts.

16. Term Discovery

Term Discovery adds helper tools for fetching definitions, synonyms, antonyms, and encyclopedia summaries. It is an optional add-on and external calls happen only when an administrator initiates a lookup or API test.

16.1 Sources

Source	Requires Key?	Used For
Wikimedia / Wikipedia REST API	No	Encyclopedia summaries.
Merriam-Webster Dictionary API	Yes	Dictionary definitions.
Merriam-Webster Thesaurus API	Yes	Synonyms, antonyms, and related terms.
Encyclopaedia Britannica API	Yes	Encyclopedic articles and summaries.
Free Dictionary API	No	Fallback definitions and pronunciation data.
API Ninjas Thesaurus API	Yes	Synonyms and antonyms.
WordsAPI through RapidAPI	Yes	Definitions, synonyms, pronunciation, and related data.

16.2 Fetch Tools

Action	Expected Result
Fetch Definition	Populates definition/tooltip where appropriate and adds source data to Sources.
Fetch Synonyms & Antonyms	Populates Synonyms with synonym data only. Antonyms should not be added as synonyms.
Fetch Encyclopedia Summary	Routes summary/definition to content and source URLs to Sources.
Fetch All	Routes definitions/summaries to the editor, synonyms to relationship fields, and sources to Sources without removing manual values.

Review required: External lookup data may be incomplete or contextually wrong. Treat fetched content as a starting point, not a final editorial answer.

17. SEO & Compatibility Fields

Clever Linked Terms v1.1.1 adds optional SEO and compatibility fields for glossary term pages. These tools are disabled by default so sites that do not need them keep a lighter Term Studio experience.

17.1 SEO Fields

The optional Enable SEO Fields in Term Studio setting shows a Search / SEO card on term edit screens.

Field	Purpose	Notes
SEO Title	Search result title	Includes a live length counter and search preview.
Meta Description	Search result summary	Includes a live length counter and search preview.
Open Graph Title	Social sharing title	Used by supported SEO integrations or local fallback metadata.
Open Graph Description	Social sharing summary	Used by supported SEO integrations or local fallback metadata.
Social Image URL	Social preview image	Can use the WordPress Media Library picker when the SEO fields setting is enabled.

Supported SEO plugin detection includes Yoast SEO, Rank Math, SEOPress, and All in One SEO. Yoast, Rank Math, and SEOPress can sync compatible post meta fields. AIOSEO is detected, but Clever Linked Terms stores local fallback SEO data because AIOSEO manages advanced data differently.

Asset note: SEO-specific media picker behavior loads only when SEO fields are enabled and the admin is editing a term.

17.2 Ad / Content Compatibility

The optional Enable Ad / Content Injection Fields in Term Studio setting adds an Ad / Compatibility Fields card. This provides controlled placement slots around the definition and metadata areas on single term pages.

Slot	Where It Renders	Common Use
Before Definition Content	Directly before the definition area.	Shortcodes, ad placements, notices, or custom content.
After Definition Content	Directly after the definition area.	Related calls to action, shortcodes, or ad placements.
Before Metadata Content	Directly before the metadata area.	Sidebar/meta-column snippets or ad placements.
After Metadata Content	Directly after the metadata area.	Supplemental snippets, banners, or shortcodes.

These slots are separate from the definition body. Empty slots do not render wrappers, and stored slot content is preserved even when the compatibility setting is disabled.

17.3 Advanced Ads & Field Plugins

Clever Linked Terms includes lightweight detection for Advanced Ads / Advanced Ads Pro, Advanced Custom Fields, Meta Box, and Pods. Detection does not force those plugins to load or change their settings. It simply helps site owners understand when compatibility-oriented fields may be useful.

Advanced Ads note: If ads do not appear on glossary term pages, confirm that Advanced Ads placements or display conditions target the clevlite_term post type or use the compatibility slot fields to place a shortcode or ad output manually.

18. Privacy & External Services

Clever Linked Terms can run without external lookup services. External services are only contacted when Term Discovery is enabled and an administrator performs a lookup or API test.

Feature	Data Involved	Admin Action Required?
Normal term linking	Local glossary terms and page content.	No external service call.
Analytics	Local impressions/clicks, context, matched text, optional user ID.	Analytics add-on must be enabled.
Term Discovery	The searched term and any configured API key.	Admin must initiate lookup or API test.
Documentation/support links	No automatic site/user data sent by the plugin.	User/admin clicks link manually.

Privacy note: If analytics is enabled, review whether your privacy policy should mention glossary engagement tracking. If Term Discovery APIs are used, your privacy policy may also need to mention the chosen dictionary/encyclopedia providers.

19. Performance

Performance matters most on sites with large glossaries, many relationship phrases, or heavy public maps. Clever Linked Terms v1.1.1 includes module controls, pagination, AJAX-style admin filtering, and lazy-loading patterns so heavier features can be enabled only when needed.

Area	Risk on Large Sites	Mitigation
Relationship phrase linking	More phrases to scan can increase frontend processing work.	Use per-type controls, per-term overrides, and conservative max-link settings.
Term Manager and Terms Engine admin screens	Large datasets can make admin pages heavy if everything renders at once.	Use 20-per-page defaults, pagination, and AJAX-style filtering/search where available.
Term Health/conflict scanning	Large relationship datasets can produce expensive review calculations.	Keep it modular, run review workflows intentionally, and avoid loading conflict UI when disabled.
Admin Term Map	Rendering too many nodes at once can get noisy and slow.	Use focused maps centered on one term with direct connections.
Public term connections	Single term pages could get heavier if connection data renders immediately.	Lazy-load maps when visible and cache generated output/data.
Glossary Knowledge Map	A full glossary map can be large on big sites.	Use a collapsed launcher, AJAX/lazy loading, cached HTML/data, and cache invalidation on term/category/tag updates.

Large glossary recommendation: Keep the base glossary fast, enable Terms Engine modules one at a time, and test with object cache/page cache/CDN cache cleared after major updates.

20. aOS / AdminOS Compatibility

Clever Linked Terms includes a lightweight compatibility integration for aOS/AdminOS. This integration does not require aOS to be installed and only runs when the AdminOS registration function is available.

aOS Route	Destination	Purpose
Dashboard	`edit.php?post_type=clevlite_term&page=clevlite-dashboard`	Main Clever Linked Terms dashboard.
Terms	`edit.php?post_type=clevlite_term&page=clevlite-term-manager`	Term Manager.
New Term	`post-new.php?post_type=clevlite_term`	Create a new linked term.
Settings	`edit.php?post_type=clevlite_term&page=clevlite`	Main plugin settings.

Compatibility note: If aOS/AdminOS is not active, Clever Linked Terms continues to work normally in the standard WordPress admin.

21. Troubleshooting

Terms Are Not Linking

Confirm the main glossary is enabled.
Confirm the target post type is enabled.
Confirm the term is published.
Check whether the term is excluded from WordPress or FluentCommunity.
Review the advanced content selector.
Clear page cache, object cache, CDN cache, and browser cache after plugin updates.

Terms Engine Pages Are Missing

Enable the main Terms Engine add-on from Settings → Add-Ons.
Go to Terms Engine → Overview.
Enable the individual feature card for the tool you want to use.
Save changes and reload the admin page.

Semantic Relationship Fields Are Missing

Confirm Terms Engine is enabled.
Confirm Semantic Relationships is enabled from Terms Engine Overview.
If disabled, the entire Semantic Relationships card is intentionally hidden in Term Studio.

Maps Do Not Appear

Confirm Terms Engine is enabled.
Confirm the relevant map module is enabled: Admin Term Map, Public Term Connections, or Glossary Knowledge Map.
Check browser console/network requests for blocked AJAX calls.
Clear cache after enabling map modules.

FluentCommunity Links Work on Refresh but Not After Navigation

Confirm the FluentCommunity add-on is enabled.
Test inside the actual portal, not only a normal WordPress page.
Clear cached assets after plugin updates.
Check whether portal scripts are present after SPA navigation.

Glossary Page Title or Slug Was Changed

You can change the glossary index title and slug from Settings → General → Glossary Pages.
You can also edit the generated page title/slug directly in WordPress.
If the plugin cannot detect the glossary page, confirm the page still contains [clevlite_linked_terms_index].

Term Manager Feels Slow With Many Terms

Use the Terms per page selector to show fewer terms at a time.
Use search and status filters instead of loading every term on one screen.
For very large glossaries, keep heavier Terms Engine modules disabled unless needed.

Plugin Update Does Not Seem to Replace Files

Confirm the dashboard version matches the version you uploaded.
If the version does not change, deactivate the old plugin package, upload the new package, then reactivate.
Clear browser, page, object, and CDN cache after updating.

Duplicate Term Warning Appears

An exact title match already exists in the glossary.
The new duplicate can be saved as a draft for review instead of being published immediately.
For imports, review duplicate warnings before choosing whether to import duplicate titles anyway.

SEO Fields Are Missing

Go to Settings → General and enable SEO Fields in Term Studio.
Reload Term Studio after enabling the setting.
If using Yoast, Rank Math, SEOPress, or AIOSEO, confirm the SEO plugin is active.

Ad / Compatibility Fields Are Missing

Go to Settings → General and enable Ad / Content Injection Fields in Term Studio.
Reload Term Studio after enabling the setting.
Use the definition or metadata slots depending on where the content should appear on the single term page.

Term URLs 404 After Changing Slug

Go to Settings → Permalinks and click Save Changes. No permalink format change is required; saving flushes rewrite rules.