內容簡介
FlowAEO 是一款針對 WordPress 的答案引擎優化 (AEO) 外掛，旨在提升您的頁面和文章在 Google 搜尋及 AI 答案引擎（如 ChatGPT、Gemini、Perplexity 和 Bing Copilot）中的可讀性，透過改善結構化資料、常見問題、頁面結構及內容準備分數來達成。
【主要功能】
• 儀表板：概覽 AEO 準備狀態及快速連結
• 報告：執行網站掃描，查看 AEO 分數
• 頁面：瀏覽並檢視被追蹤的文章和頁面狀態
• 結構化資料：創建和管理 JSON-LD 結構化資料
• 常見問題：建立 FAQ 群組並附加到內容
• AI 助手：生成 AEO 相關草稿和內容建議
外掛標籤
開發者團隊
原文外掛簡介
FlowAEO is an Answer Engine Optimization (AEO) plugin for WordPress. It helps your pages and posts become clearer for Google Search and for AI answer engines such as ChatGPT, Gemini, Perplexity, and Bing Copilot, by improving schema, FAQs, on-page structure, and content readiness scores.
After activation, open FlowAEO in the WordPress admin menu. Every Free feature below maps to a real screen in that menu.
Where each Free feature is used
Dashboard (FlowAEO > Dashboard)
Overview of AEO readiness, recent activity, and quick links into the rest of the plugin.
Reports (FlowAEO > Reports)
Run a full site scan or rescan individual pages. See AEO score, missing schema / FAQ / meta signals, filters (All / Issues / Optimized), and open or edit any page from the results table.
Pages (FlowAEO > Pages)
Browse posts and pages tracked by FlowAEO, review AEO status per item, and jump into optimization workflows.
Schema (FlowAEO > Schema)
Create and manage JSON-LD schema (for example Organization, WebPage, FAQ, HowTo, and related types), assign schema to content, and output structured data on the front end.
FAQ (FlowAEO > FAQ)
Build FAQ groups, attach them to content, and publish FAQ markup/output that search and answer engines can understand.
Blocks (FlowAEO > Blocks, and the block inserter in the editor)
Add Gutenberg blocks for FAQ, How-To, and Key Takeaways directly inside posts and pages.
AI Assistant (FlowAEO > AI Assistant)
Generate AEO-oriented drafts such as schema suggestions, FAQ ideas, meta, and related content helpers. Add your own API key in AI Assistant > Settings: OpenAI, Google Gemini, Anthropic Claude, OpenRouter, DeepSeek, or any OpenAI-compatible custom endpoint. Generations with your own key have no FlowAEO limit; your provider bills you directly.
Settings (FlowAEO > Settings)
Plugin options for schema output, FAQ display, performance, and related configuration.
License (FlowAEO > License)
Connect a FlowAEO account/license key for plan status, upgrades, and hosted service access. Core Schema, FAQ, Reports, and Blocks still work without a paid key.
What goes on your public site
Schema JSON-LD in page output when you assign schema, plus automatic BlogPosting and breadcrumb schema on single blog posts (when Auto-generate Schema is on)
Open Graph, Twitter Card, meta description, and canonical URL on singular content
FAQ markup / display when FAQ groups are published
Gutenberg block HTML on the front end for FAQ, How-To, and Key Takeaways blocks
Pro (separate package)
FlowAEO Hosted AI (no API key needed), Indexing (Google Search Console and IndexNow), Tools, and Logs are not included in this Free WordPress.org build. They ship only in the Pro plugin package from https://flowaeo.myprograming.com/ – with a valid paid license. In Free, the Indexing menu item shows an upgrade notice.
Only one FlowAEO edition (Free or Pro) should be active at a time.
External services
FlowAEO may connect to third-party services when you use related features:
FlowAEO SaaS (https://flowaeo.myprograming.com/) – license activation, account, downloads, upgrade links.
AI providers (only the one whose key you save in AI Assistant > Settings): OpenAI, Anthropic (Claude), Google Gemini, OpenRouter, DeepSeek, or the custom OpenAI-compatible endpoint you enter. Prompt and page content snippets are sent to that provider when you click Generate or Test Connection.
The Free build does not contact the FlowAEO AI Worker or Google Search Console. Those services are used only by the Pro package with an active license.
Data sent depends on the feature (prompt/content snippets for AI, sent only to the provider you configured). You choose when those features run.
Privacy policy: https://flowaeo.myprograming.com/privacy
Terms: https://flowaeo.myprograming.com/terms
MCP integration
MCP lets a local Cursor session read this site and propose SEO changes. It does not publish those changes by itself.
Supported write fields are SEO title, meta description, focus keyword, and related keywords. Each field is saved only after a WordPress administrator approves that exact value in FlowAEO → MCP Integration.
Local setup uses the bundled bridge with FLOWAEO_SITE_URL pointed at this site and FLOWAEO_MCP_TOKEN set to a credential created in MCP Integration. Do not put the token in the plugin files or in this readme. Revoke it from the same screen when it is no longer needed. The plugin stores only a hash of the token.
Any site that is not localhost, 127.0.0.1, .local, or .test must be served over HTTPS. The credential is refused on plain HTTP elsewhere.
Scopes start read-only. Turn on only the scopes that session needs, such as reading content, creating proposals, applying approved metadata, or running a bulk job.
Single apply writes one approved proposal. Bulk apply writes a small batch of proposals that were already approved in WordPress. A chat message is not an approval. Approvals expire, are bound to the same user, site, and post revision, and can be consumed only once.
Activity Logs record apply, failure, and needs-review events. If an apply is interrupted after it starts, the next apply is blocked until the record is reviewed. A consumed approval without a success record stays in needs review. The plugin does not invent a success event.
Proposals are generated on the site with AI off unless the request sets use_ai to true and an AI provider is already enabled under Settings. Enabling AI can send page text to the configured FlowAEO AI service or to a provider whose key you saved.
Approved field values are stored in the flowaeo_mcp_approvals table and a backup option. Audit events are stored in the flowaeo_mcp_audit table. Deleting the plugin removes the approval backup option. The two history tables stay unless an administrator checks “Delete MCP approval and audit history when this plugin is deleted” on MCP Integration → Connection before deleting the plugin.
