Adds native Elementor, WPBakery, and Beaver Builder support. All existing integrations continue to work.<\/p>","1.1.1":"
WPLink branding update. Webhook now accepts WPLINK_WEBHOOK_SECRET and X-WPLink-Signature (legacy constants still work).<\/p>","1.1.0":"
Renamed to WPLink and adds native Bricks Builder support. Existing Formerly known as Meshr - AI Internal Linking.<\/strong> This plugin was rebranded to WPLink in 2026. The plugin slug ( 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 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.<\/p>\n\n Why WordPress Users Choose WPLink:<\/strong><\/p>\n\n 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.<\/p>\n\n Supported page builders:<\/strong><\/p>\n\n Features:<\/strong><\/p>\n\n How It Works:<\/strong><\/p>\n\n All endpoints are available under both Health Check<\/strong><\/p>\n\n Returns site info, plugin version, and capability flags (including which builders are detected and supported).<\/p>\n\n Get Post Content (builder-aware)<\/strong><\/p>\n\n Returns extracted plain text and an element-level breakdown. Routes to the appropriate builder handler (Bricks, Elementor, WPBakery, Beaver Builder) or falls back to Insert Link (builder-aware)<\/strong><\/p>\n\n Request body:\n 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 Bulk Link Update (URL migration)<\/strong><\/p>\n\n Unchanged from 1.0.0. Used for URL-replacement migrations in standard Webhook (Optional)<\/strong><\/p>\n\n Requires HMAC signature verification. Configure 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.<\/p>\n\n For support, documentation, and more information, visit:<\/p>\n\n No. This plugin does not store any data locally. It only provides API endpoints for WPLink to communicate with your WordPress site.<\/p><\/dd>\n No admin UI is required. You only need to generate a WordPress Application Password in your user profile and provide it to the WPLink desktop app.<\/p><\/dd>\n Yes. The plugin uses WordPress's built-in authentication system (Application Passwords), proper capability checks ( Yes. Once configured, you can test the health check endpoint:<\/p>\n\n You'll need to authenticate using Basic Auth with your Application Password credentials.<\/p><\/dd>\n Add this constant to your Replace Note: the legacy constant \/meshr\/v1\/<\/code> endpoints continue to work.<\/p>"},"ratings":[],"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":3508946,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-772x250.png":{"filename":"banner-772x250.png","revision":3508946,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.1.0","1.1.1","1.2.0"],"block_files":[],"assets_screenshots":[],"screenshots":[],"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[2353,569,19933,1084,186],"plugin_category":[55],"plugin_contributors":[250138],"plugin_business_model":[],"class_list":["post-238878","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-automation","plugin_tags-internal-linking","plugin_tags-page-builder","plugin_tags-seo","plugin_category-seo-and-marketing","plugin_contributors-linkwithmeshr","plugin_committers-linkwithmeshr"],"banners":{"banner":"https:\/\/ps.w.org\/meshr-ai-internal-linking\/assets\/banner-772x250.png?rev=3508946","banner_2x":false,"banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/meshr-ai-internal-linking\/assets\/icon-256x256.png?rev=3508946","icon_2x":"https:\/\/ps.w.org\/meshr-ai-internal-linking\/assets\/icon-256x256.png?rev=3508946","generated":false},"screenshots":[],"raw_content":"\nmeshr-ai-internal-linking<\/code>) and the original \/meshr\/v1\/<\/code> REST API namespace are preserved for backwards compatibility; a new \/wplink\/v1\/<\/code> namespace has been added alongside.<\/p>\n\npost_content<\/code>.<\/p>\n\n\n
_bricks_page_content_2<\/code> so Bricks pages are fully indexed and linkable<\/li>\n_elementor_data<\/code> JSON tree so Elementor pages work like standard posts<\/li>\n[vc_column_text]<\/code> shortcode blocks in post_content<\/code><\/li>\n_fl_builder_data<\/code> PHP object graph so Beaver Builder modules are fully supported<\/li>\n\n
_bricks_page_content_2<\/code><\/li>\n_elementor_data<\/code><\/li>\npost_content<\/code> as shortcodes ([vc_column_text]<\/code>)<\/li>\n_fl_builder_data<\/code><\/li>\npost_content<\/code><\/li>\n<\/ul>\n\n\n
\n
API Endpoints<\/h3>\n\n
\/wp-json\/wplink\/v1\/<\/code> and \/wp-json\/meshr\/v1\/<\/code> (legacy).<\/p>\n\nGET \/wp-json\/wplink\/v1\/check\n<\/code><\/pre>\n\nGET \/wp-json\/wplink\/v1\/posts\/{post_id}\/content\n<\/code><\/pre>\n\npost_content<\/code> for Gutenberg\/classic posts.<\/p>\n\nPOST \/wp-json\/wplink\/v1\/posts\/{post_id}\/insert-link\n<\/code><\/pre>\n\njson\n{\n \"keyword\": \"digital marketing\",\n \"target_url\": \"https:\/\/example.com\/services\/digital-marketing\/\",\n \"occurrence\": 1\n}<\/code><\/p>\n\n_elementor_data<\/code> widget tree. For WPBakery, replaces inside [vc_column_text]<\/code> blocks. For Beaver Builder, modifies _fl_builder_data<\/code> module settings. Cache regeneration is triggered automatically for each builder.<\/p>\n\nPOST \/wp-json\/wplink\/v1\/bulk-link-update\n<\/code><\/pre>\n\npost_content<\/code>.<\/p>\n\nPOST \/wp-json\/wplink\/v1\/webhook\n<\/code><\/pre>\n\nWPLINK_WEBHOOK_SECRET<\/code> in wp-config.php<\/code>. Requests include an X-WPLink-Signature<\/code> header. The legacy MESHR_WEBHOOK_SECRET<\/code> constant and X-Meshr-Signature<\/code> header are still accepted.<\/p>\n\nPrivacy Policy<\/h3>\n\n
Support<\/h3>\n\n
\n
\n
\/wp-content\/plugins\/meshr-ai-internal-linking<\/code> directory, or install the plugin through the WordPress plugins screen directly.<\/li>\n\n
\n
Does this plugin store any data?<\/h3><\/dt>\n
Do I need to configure anything in WordPress?<\/h3><\/dt>\n
Is my site secure?<\/h3><\/dt>\n
current_user_can<\/code>), and sanitizes all inputs. Webhook endpoints use HMAC signature verification when enabled.<\/p><\/dd>\nCan I test the connection?<\/h3><\/dt>\n
GET https:\/\/your-site.com\/wp-json\/wplink\/v1\/check\n<\/code><\/pre>\n\nHow do I enable webhook support?<\/h3><\/dt>\n
wp-config.php<\/code> file:<\/p>\n\ndefine( 'WPLINK_WEBHOOK_SECRET', 'your-secret-key-here' );\n<\/code><\/pre>\n\nyour-secret-key-here<\/code> with a strong, random string. Webhook requests will include an X-WPLink-Signature<\/code> header for verification.<\/p>\n\nMESHR_WEBHOOK_SECRET<\/code> is still accepted for backwards compatibility.<\/p><\/dd>\n\n<\/dl>\n\n\n1.2.0<\/h4>\n\n
\n
_elementor_data<\/code> JSON tree<\/li>\n[vc_column_text]<\/code> shortcode blocks<\/li>\n_fl_builder_data<\/code> PHP object graph<\/li>\n\/check<\/code> now report supports_wpbakery<\/code>, supports_beaver<\/code>, wpbakery_detected<\/code>, beaver_detected<\/code><\/li>\n1.1.1<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
_bricks_page_content_2<\/code><\/li>\nGET \/posts\/{id}\/content<\/code> returns builder-aware extracted text<\/li>\nPOST \/posts\/{id}\/insert-link<\/code> safely inserts a link into Bricks or standard posts<\/li>\n\/meshr\/v1\/<\/code> (legacy) and \/wplink\/v1\/<\/code> (preferred)<\/li>\n1.0.0<\/h4>\n\n
\n
GET \/meshr\/v1\/check<\/code>)<\/li>\nPOST \/meshr\/v1\/bulk-link-update<\/code>)<\/li>\nPOST \/meshr\/v1\/webhook<\/code>)<\/li>\n<\/ul>","raw_excerpt":"AI-powered internal linking for WordPress with page builder support.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/kin.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/238878","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kin.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/kin.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/kin.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=238878"}],"author":[{"embeddable":true,"href":"https:\/\/kin.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/linkwithmeshr"}],"wp:attachment":[{"href":"https:\/\/kin.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=238878"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/kin.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=238878"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/kin.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=238878"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/kin.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=238878"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/kin.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=238878"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/kin.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=238878"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}