webforce2026

Webforce Automation connects your WordPress site to the <a href="https://webforce.co.il" rel="nofollow ugc">Webforce</a> content management platform. Publish, manage, and track SEO-optimized articles via a secure REST API.
Features:
<ul>
<li>Secure REST API — Token-based authentication with one-time registration for secure external access.</li>
<li>SEO Integration — Auto-detects Yoast SEO and RankMath. Automatically maps SEO fields between plugins.</li>
<li>Article Marking — Mark articles by URL for tracking and management. Filter marked articles via REST API.</li>
<li>Elementor Integration — Custom Query IDs (<code>wlive</code> and <code>wlive_mix</code>) for Elementor Posts/Loop Grid widgets.</li>
<li>Articles Shortcode — Display marked articles with <code>[wlive_articles]</code> shortcode with responsive grid layout.</li>
<li>Featured Images — Auto-assign featured images from article content for articles missing them.</li>
<li>Admin Dashboard — Statistics, article list, URL marking, and protected advanced settings.</li>
</ul>
How It Works:
<ol>
<li>Install and activate the plugin.</li>
<li>Visit Settings > Webforce Automation to access the admin dashboard.</li>
<li>Use the Register endpoint to connect your external content management system.</li>
<li>Publish articles via the REST API with automatic SEO field mapping.</li>
<li>Track and manage articles from the admin dashboard.</li>
</ol>
REST API Endpoints:
<ul>
<li><code>GET /wlive/v1/register</code> — One-time registration, returns API token.</li>
<li><code>GET /wlive/v1/ping</code> — Connection test (requires token).</li>
<li><code>GET /wlive/v1/articles</code> — List marked articles (requires token).</li>
</ul>
Standard WordPress REST API for creating and updating posts is also supported with the registered SEO meta fields.

Webforce Automation

Manage and publish SEO-optimized articles via REST API with Yoast & RankMath integration.

cfischer83

Does your website utilize categories and tags? Does it use custom taxonomies? If so, this plugin will find similar content 
based on all your taxonomies. There are two ways to show related posts within your page.
<ul>
<li>The first way to show related content on your post is to use the widget provided. This only works when is_single() is true</li>
<li>The second way to show similar content on your site is to use the pk_related_return($post->ID); function which can be 
called programmatically anywhere you wish!</li>
</ul>
The Widget included with this plugin gives you the option to limit the amount of posts; it allows you to determine which 
fields to show: Featured Image, Author, Date, and Excerpt (Title is required); it allows you to determine which 
variant of the featured image to show: thumbnail, medium, large, or full. As of version 2.0, you can now decide whether the 
‘similar posts’ sorting prefers posts that are newer or posts that were created closer to the date of the post you’re 
viewing.
If you find the Widget doesn’t meet your needs or is too limiting, you can call the functionality programmatically using 
this function:
<pre><code>pk_related_return($post->ID, $args);
</code></pre>
Where $post->ID is the ID of the post for which you are wanting to show related articles.
The $args parameter is an array with the following values available to you (more coming soon):
<ul>
<li>posts_per_page (int defaults to 5)</li>
<li>thumbnail_size (string consisting of one of these values: “thumbnail”, “medium”, “large”, “full”. Defaults to thumbnail).</li>
<li>sort_prefer (string consisting of one of these values: “newest”, “closest”. Defaults to newest).</li>
</ul>
An example might be:
<pre><code><?php
$args = array (
 'posts_per_page' => 6,
 'thumbnail_size' => 'medium',
 'sort_prefer' => 'closest'
);
</code></pre>
The return value of pk_related_return is an array of objects that includes most of the fields within WordPress’s posts 
table plus permalink and featured image.
Future Additions:
Allow the user to specify only certain content types (posts, pages, custom) in a request. This would allow you to specify 
only products get returned, or only blog posts. This would only be an issue if content types share taxonomies.

Webforce Automation vs Similar Posts Ontology