SocraNext
What the plugin provides – Custom Post Type socranext_post for AI-optimized articles (default URL slug artikelen-sn, configurable via the SocraNext platform). – Custom Taxonomy socranext (hierarchical) for categorizing those articles. – Template-based rendering for single/archive article views (plugin templates via template_include). – Admin screens under SocraNext (Overview, Articles, Categories). FAQ management is handled via the SocraNext platform. – Cache flush on (de)activation to correctly register permalinks. Display The plugin renders views via bundled templates for: – Single SocraNext articles and archive list. Article URL prefixes with WPML WPML determines the canonical URL of an existing article. To change an articles prefix for a language, first configure it in WPML for the SocraNext post type, then enter the same prefix for that language in the SocraNext platform. The platform does not automatically configure WPML’s translated post type prefixes. After saving, check the final article and overview URLs, including redirects from old URLs. Saving an unchanged platform value does not start another URL synchronization. Publishing on the existing WordPress blog New articles use the SocraNext post type by default. In the platform’s project settings, choose the existing WordPress blog to publish new articles as ordinary WordPress posts, with the site’s theme and a selected native blog category. Existing articles retain their post type, URL and locally edited native categories. The selected category must have a translation before publishing a translated article. SocraNext continues to manage its own translations. Managed article saves are excluded from WPML’s automatic translation queue; WPML’s initial “Translate Everything” bulk run does not honor this per-post exclusion, so exclude managed articles from that initial batch. Native posts are rendered by the active theme, not the SocraNext article styler. Moving existing articles into the blog Changing the destination does not move existing content automatically. In the platform settings, preview and move one existing article at a time. The same WordPress post ID, publication date, content, comments, image and platform binding are retained. WordPress assigns the final native permalink and resolves slug collisions; no second article is created. The active theme controls the presentation, including which custom fields it displays. Linked Polylang translations move together, each into the translated native category. A group containing an unpublished or unmanaged translation is rejected before any changes. WPML migrations are explicitly blocked pending a supervised migration; new publication into the WordPress blog remains supported. The plugin records each old canonical URL plus known flat and historical-slug routes, and serves permanent redirects to the current native permalink while it is active. Redirects also follow later native slug edits. Existing live content at a reused URL takes precedence. A saved migration can be retried after interruption, and completed receipts remain available to repair platform URL synchronization. Back up the site and preview the affected language versions before applying; test the public URLs and archive after completion. Structured Data – The FAQ display includes FAQPage JSON-LD to help search engines and AI systems better understand the Q&As. – SocraNext articles output their own SEO title, meta description, Open Graph tags and Article JSON-LD (independent of third-party SEO plugins; mirrored into Yoast / AIOSEO / Rank Math when present). REST API (for platform integration) Under the namespace socranext/v1, routes include: – GET /pages and GET /pages/{id} – list site pages (for adding/showing FAQ widgets). – POST /toggle – enable/disable the FAQ widget per page. – POST /store-aio-information and GET /aio-information/{page_id} – store/retrieve per-page FAQ data. – GET /article-publication and POST /article-publication – read or save the per-site destination (socranext or wordpress_blog) and native categoryId (0 means WordPress default); both require the connection token. The receipt includes native categories and the configured posts-page URL when available. – GET /article-migration lists eligible articles and completed receipts; POST /article-migration accepts postId and dryRun (default true). The token-protected preview and apply responses include the selected receipt plus receipts for its entire translation group, with authoritative IDs, bindings and actual permalinks after apply. – POST /blog and POST /store-blog-custom – create articles and store global custom HTML/CSS/JS for article display. – POST /collection-slugs – sync the configurable articles URL slug from the SocraNext platform (rewrite flush + cache purge). – GET /articles-list-custom – retrieve configuration for list views. – POST /llmstxt and GET /llmstxt – publish and read llms.txt / llms-full.txt content from the SocraNext platform; served at /llms.txt and /llms-full.txt on the site. – POST /cache/refresh with {"url":"https://your-site.example/page/"} – request a cache refresh for exactly one canonical URL on the site’s own origin (same scheme, host and port). Credentials, query strings, fragments and wildcards are rejected. Only integrations scoped to one URL are used; recursive integrations such as WP Rocket are reported in cache.unsupported_integrations and never called. This does not save, regenerate or delete content, change settings, or disconnect the plugin. HTTP 501 means no supported integration; HTTP 502 reports failed or incomplete integration coverage. A successful receipt lists affected_urls and purged_urls and confirms dispatch, not verified public-page freshness. – POST /delete-socranext-content-and-disconnect – permanently remove SocraNext-managed content/settings and deactivate the plugin, using the existing connection-token authorization. This is destructive and is never a cache operation. Success includes operation: "delete-socranext-content-and-disconnect". – POST /purge is retired and always returns HTTP 410 without changing content, settings or caches. Integrations must use the explicit operation; there is no compatibility fallback. Note: without an account/connection to app.socranext.ai, the auto-generation routes are typically not used, but the created post types, taxonomy, and pages remain available for display. Privacy & external services – The plugin does not call external APIs on its own; the integration is typically initiated by the SocraNext platform to your website. – Websites: product site https://socranext.ai and platform https://app.socranext.ai. Prefix & naming policy All plugin identifiers use the unique prefix family “SocraNext”: Functions, hooks, options, AJAX actions, REST namespace, script/style handles: socranext_* (lowercase) Constants: SOCRANEXT_* (uppercase) Human-facing labels and PHP namespaces (if used): SocraNext (PascalCase) We avoid reserved prefixes like wp_, _, and __ for custom identifiers. Existing options and routes already comply; no migrations are required.
WordLift – AI powered SEO – Schema
WordLift – AI-Powered SEO – Schema WordLift connects to your existing website, reads your content, finds entities in it (like places and people), and creates a representation of your content search engines will love. WordLift, without requiring any technical skills, creates code (called Structured Data or Schema markup) that reiterates your page’s content in a manner that search engines best understand. WordLift is available to try free for 14 days. Find out more and get your activation key directly on our website. All our clients enjoy an increase in organic traffic. A lot of them start seeing rich snippets in their Google results pages. Some also experience an increase in website authority. All of them can delegate complex SEO tasks to junior staff. This lift is made possible by our Artificial Intelligence engine working behind the scenes understanding, highlighting, and connecting your content. WordLift lets you create, own and publish your own knowledge graph. WordLift publishes your content as Linked Open Data following Tim Berners-Lee‘s Linked Data Principles. Features WordLift is a plug-in for online content creators to: Support your writing process with trustworthy and contextual facts Enrich content with images, links and interactive visualizations Keep readers engaged with relevant content recommendations Produce content compatible with schema.org markup, allowing search engines to best index and display your website. Engage readers with relevant content recommendations Publish metadata to share, sell and distribute content WordLift brings to your publishing workflow The technology to self-organize content using publicly or privately available knowledge graphs An easy way to build datasets and full data ownership Support for creating web content using contextually relevant information Valued and free to use photos and illustrations from the Commons community ranging from maps to astronomical imagery to photographs, artworks and more New means to drive business growth with meaningful content discovery paths Content tagging for better SEO Supported languages WordLift currently supports 32 languages: Chinese, Danish, German, English, French, Italian, Dutch, Russian, Spanish, Portuguese, Swedish, Turkish, Albanian, Belarusian, Bulgarian, Catalan, Croatian, Czech, Estonian, Finnish, Hungarian, Icelandic, Indonesian, Latvian, Lithuanian, Norwegian, Polish, Romanian, Serbian, Slovak, Slovenian, Ukrainian. We also experimentally support hundreds of languages with many different alphabets. You can use WordLift in any language that is being supported natively by WikiData. The Plug-in is built on open source software. More Information WordLift is happily developed by WordLift, an innovative Italian startup founded in 2017 and based in downtown Rome. WordLift helps companies, operating in all market sectors, including e-commerce, of the small, medium, and large sizes to speak Google’s native language by converting unstructured content into structured data that search engines understand. This will allow them to get more organic traffic to the website and offer a more relevant user experience. For more information, contact us at hello@wordlift.io. Why we are doing this Our mission is an utopian one: organize the world general knowledge by providing tools that everyone can use. In open source we trust WordLift is built on open source software. WordLift uses open source tools for natural language and semantic processing. In data ownership we trust We believe content creators should own, retain and exploit the value of the metadata they create. Get involved with the Development If you are a coder and wish to contribute to WordLift plugin you are welcome to get involved via Github. WordLift Plugin Repo: https://github.com/insideout10/wordlift-plugin WordLift Plugin Issue Tracker: https://github.com/insideout10/wordlift-plugin/issues
