imperal.io
  • How it works
  • Use cases
  • Technology
  • Pricing
Login
Webbee AIWebbee Codeimperal-mcpDevelopers & SDKSecurity & Vault
Add an app 路 Marketplace
imperal.ioICNLI Cloud OS

One OS for everything you run. Webbee is your agent inside it, she does the work, you stay in control.

Product
  • Webbee
  • Webbee Code
  • Imperal MCP
  • Marketplace
  • Use cases
  • Pricing
  • Open panel
Resources
  • Security
  • Technology
  • Success stories
  • Blog
Developers
  • Developers
  • Docs
  • Quick start
  • SDK reference
  • Developer portal
Company
  • About
  • Contact
  • Legal
Open protocol
  • ICNLI
  • SDK on GitHub
漏 2026 Imperal, Inc. 路 ICNLI published at icnli.org under CC BY-SA 4.0
TermsPrivacy
  1. Home
  2. /
  3. Marketplace
  4. /
  5. Internal Linking Engine

Internal Linking Engine Extension

馃摪 Publishing路by bluebeeweb路v0.1.0
Pay per use2-20 tok/action
Open in panel
0 capabilities230 actions1 installs

About this extension

Automatic organic internal linking + one conversion CTA block per article, for every connected site. Builds a lightweight content index, proposes language-isolated relevant link targets, drafts anchor placements and a CTA with a strict preview -> apply -> rollback diff -- never a silent content rewrite.

What you get

Every capability exposed by Internal Linking Engine, metered per action and guarded by the two-step safety protocol.

  • enable_sitewrite

    Turn on Internal Linking Engine for one site already known to Sites Registry. Creates the site's settings row in review_first mode by default -- no content is touched until a plan is previewed and explicitly applied.

  • update_site_settingswrite

    Update an existing site's Internal Linking Engine settings (mode, limits, CTA targets, exclusions, languages). Only given fields change.

  • list_sitesread

    List every site with Internal Linking Engine settings (enabled or not), across every connected site.

  • get_site_settingsread

    Read one site's Internal Linking Engine settings in full.

  • index_postswrite

    Cache metadata for a batch of posts already fetched via wordpress-hub, so the Relevance Engine can score them without re-fetching. Call this once per post before get_relevant_targets/preview_internal_links can use it as a candidate or source.

  • get_site_index_statusread

    One-glance index health for a site: how many posts indexed, by language, and when last indexed.

  • get_relevant_targetsread

    Find the top-N internal-link targets for one already-indexed source post, using deterministic metadata + term-overlap scoring (categories/tags/product_type/title). Language isolation is a hard filter -- a candidate whose lang differs from the source post's lang is never returned, even if it scores highest (the climtec.md RU/RO lesson). Excluded URLs from the site's settings are also dropped before scoring.

  • preview_internal_linkswrite

    Build a preview linking+CTA plan for a site -- NEVER writes anything. Takes raw content Webbee already fetched via wordpress-hub.get_post_content, and (optionally) anchor/CTA insertions Webbee already drafted via an LLM pass, and validates every proposed insertion's find_exact_substring occurs EXACTLY ONCE in that post's current raw content -- any insertion that doesn't is dropped, never guessed. Returns a plan_id; nothing is applied until apply_internal_links is called after Webbee has actually written each surviving diff via wordpress-hub.replace_post_content_text.

  • get_linking_planread

    Read one linking plan in full -- every post's proposed diff, for review before applying.

  • list_linking_plansread

    List linking plans, optionally filtered by site and/or status.

  • apply_internal_linkswrite

    Record that a pending_review plan's diffs were actually written to the site -- call this ONLY AFTER Webbee has already called wordpress-hub.replace_post_content_text for each surviving insertion in the plan (using expected_state_token per post for safety). This function does not write to any site itself; it only transitions the plan's own status and increments the site's confirmed_applies_count toward its full_auto threshold.

  • reject_linking_planwrite

    Reject a pending_review plan without applying it. Nothing was ever written, so this is purely a status change.

  • rollback_linking_runwrite

    Roll back an already-applied plan: returns the original find/replace pairs (the inserted anchor/CTA text as 'find', the pre-insertion original snippet as 'replace') for Webbee to write back via wordpress-hub.replace_post_content_text, restoring each post's content. This function does not write to any site itself -- it only returns the rollback instructions and transitions the plan's own status once Webbee confirms.

  • list_linking_runsread

    List the linking runs dashboard -- one row per plan lifecycle event, newest first.

Related extensions

More extensions in Publishing ready to enable in one click.

  • NotesPersonal notes with folders, tags, full-text search, and trash management for your workspace.
  • Mail ClientMulti-provider email client - Google, Microsoft, Yahoo, IMAP. Inbox, send, reply, forward, search, archive, manage emails, contacts, custom folders/labels. Gmail batchModify for instant bulk operat...
  • Web ToolsWebsite monitoring, DNS lookup, SSL checker, and web diagnostics
  • Vikunja Tasks ConnectorKanban task manager connecting to your own Vikunja instance - create, assign, filter tasks and manage projects and labels.

Ready to use Internal Linking Engine?

Enable Internal Linking Engine in your Imperal workspace in one click - 10,000 free starter credits included.

Open in panel