內容簡介
SocraNext 外掛專為 AI 優化文章設計，提供自訂文章類型及分類法，並支援 FAQ 管理及結構化數據，提升網站的 SEO 效能與使用者體驗。
【主要功能】
• 自訂文章類型 socranext_post
• 自訂分類法 socranext
• 模板化顯示單篇及文章列表
• FAQ 管理介面整合於 SocraNext 平台
• 支援 REST API 進行平台整合
外掛標籤
開發者團隊
📦 歷史版本下載
原文外掛簡介
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.
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.
– 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.
