
內容簡介
Visualithic Phyllix 是一款專為提升網站搜尋能見度而設計的外掛,透過分析網站內容,幫助使用者找出關鍵字、填補內容空白,並自動生成草稿文章,讓網站更具競爭力。
【主要功能】
• 分析已發佈頁面,建立商業概況
• 發現內容缺口,並建立關鍵字地圖
• 自動撰寫草稿文章,並進行 SEO 審核
• 提供頁面改進建議,並保留原始版本
• 追蹤已發佈文章在 Google 的表現
• 檢查技術健康狀況,如破損連結等
外掛標籤
開發者團隊
原文外掛簡介
Phyllix reads your website, works out what your business actually does, and then works on your search visibility the way a marketing manager would – by finding what you could realistically rank for, what your existing pages half-cover, and what is missing entirely.
By default, it never publishes anything. Every article it writes is filed as a draft for you to read, edit and approve, and if you want that to stay true forever, it will. Every change it proposes to a page you already have is shown to you in full first, and the original is kept so it can be undone. An explicit Automation section in Settings lets an owner who wants more turn on exactly as much as they choose — anywhere from just sending findings to your Ideas queue automatically, up to approving, writing and publishing articles with no click at all. Every level is off by default, and turning any of it on is a deliberate choice you make.
What it does
Reads your published pages and builds a profile of your business from them
Maps your existing content and finds the gaps in it
Builds a keyword map, cross-checked against Google Search Console where you connect it
Researches a topic, then writes a full article and files it as a draft
Reviews its own drafts for SEO, readability and accuracy before you see them
Improves pages you already have, one at a time, always as a reviewable proposal (or, if you turn automation on, applied automatically with the same safety checks a manual click passes through)
Tracks how published articles actually perform in Google over time
Checks technical health: image dimensions, heading structure, broken links, redirect chains, mixed content, accidental noindex
Adds a call to action to pages that attract visitors but never ask for the business
Optional automation: approve, write and publish articles unattended, spread across the week at a pace you set, with a full audit trail of what it did and when
How it treats your content
This is the part we care most about. A page you already have is a page that already works for someone, so:
Nothing is published automatically unless you explicitly turn that on in Settings — off by default, and every level of automation is its own separate, individually-labelled toggle, not an all-or-nothing switch
Every idea, draft and published article keeps a full record of when it was proposed, when and by whom it was approved, when and by whom it was written, and when and by whom it was published — so you can always see what automation did versus what you did yourself
A published article is an ordinary WordPress post — you can edit it, unpublish it, or delete it at any time through Phyllix’s own editor or WordPress’s own post editor, exactly as you would with anything you wrote yourself
Pages linked in your site’s navigation menu are never touched by any automated action, at any setting — quick fixes, calls to action, page rewrites, none of it. Those always wait for your own explicit review
What gets read is an allow-list you control – only Pages and Posts by default, nothing else unless you add it in Settings
Private and password-protected content is skipped outright, and any email address found in a page’s text is stripped before that text ever reaches an AI request
Page structure is preserved, whatever built the page. Only the text inside your existing layout is edited — the block editor, the classic editor, Elementor, Divi, WPBakery, Avada, Beaver Builder and Bricks alike — and the layout itself is never sent to the AI in the first place. Sections, columns, images, forms and embeds stay exactly where they were
Pages built with Oxygen, Breakdance, Brizy, Thrive or SiteOrigin are not rewritten at all
Every edit to a live page keeps the original, so it can be reversed
A newly published article is left alone for four weeks before Phyllix offers to improve it, because Google needs that long before its position means anything
Free plan
The free plan includes 3 AI-written articles, once — a one-time allowance, not a monthly one. Reading your site, the business profile, the content map, the keyword map, the gap analysis, manually-tracked competitors, Google Search Console tracking, and fixing technical SEO problems are always included, for free, forever, with no limit. Once the 3 free articles are used, buy AI credits ($1.25 each, pay only for what you use, no subscription) or move up to a paid plan for an ongoing monthly allowance. Free also reads up to 25 pages of your own site, once, ever.
External services
Phyllix cannot work without connecting to an external service. It does not run AI models on your server, and it does not ask you for API keys. Instead it sends work to the Phyllix service, which runs the AI on your behalf. You should understand exactly what that means before you use it.
The Phyllix service (Visualithic Solutions)
Phyllix connects to https://visualithicsolutions.com, operated by Visualithic Solutions, to license the plugin and to run every AI request.
When it connects:
When you first connect the plugin, to create your free licence
Every time you ask it to do something that needs AI
A licence check roughly every 6 hours while you are using it — more often (down to every few minutes) only while your plan is showing as fully used up, so a credit purchase or upgrade is noticed quickly rather than waiting out the normal cache
When the service calls your site: with a licence connected, the service calls your site every few minutes at /wp-json/phyllix/v1/wake to remind it to run Phyllix’s queue, so work starts on time even when nobody visits (WP-Cron only runs on visits). Only a call signed with your own licence key is accepted; it runs the work Phyllix would run on its own 5-minute schedule, and no content is sent in either direction. Switch it off in Settings → Automation → Advanced (“Keep my schedule on time”).
What is sent:
A randomly generated install identifier, created by the plugin for your site
Your site address (home_url())
Your licence key, once you have one
The text of the pages and drafts Phyllix is working on, including titles and meta descriptions
The business profile Phyllix has built from your pages
Your Google Search Console figures, if you have connected Search Console
Your WordPress administrator email address – only when you activate a paid licence, not when a free licence is created
With each licence check, a short health report about Phyllix itself: its version, whether it is paused, how many of its tasks are waiting or have failed, how many drafts are waiting for approval, and when it last ran and last published. Counts and dates only, no content. It is used to email the licence owner if a site stops writing or gets stuck
What is not sent: your database, your users, your customers’ data, your orders, or the content of any page Phyllix has not been asked to work on. Pages you have marked Private or password-protected are skipped outright, whatever content type they are, and any email address found in a page’s text is stripped before that text reaches an AI request.
Terms: https://visualithicsolutions.com/terms
Privacy: https://visualithicsolutions.com/privacy
AI providers used by that service
The Phyllix service passes your request to one of two AI providers, depending on the task. Your content is sent to them by the Phyllix service, not directly by this plugin.
Anthropic – used for writing the final text of an article or page rewrite.
Terms: https://www.anthropic.com/legal/consumer-terms
Privacy: https://www.anthropic.com/legal/privacy
Google (Gemini) – used for research, analysis, review and classification. When researching, it uses Google Search grounding, which means your topic is searched on the web.
Terms: https://policies.google.com/terms
Privacy: https://policies.google.com/privacy
Google Search Console (optional)
If you choose to connect Google Search Console, Phyllix calls
https://oauth2.googleapis.com to exchange the credentials you supply for an
access token, and https://searchconsole.googleapis.com to read which searches
your site appears for. This is entirely optional and nothing is sent to Google
beyond the API request itself.
Terms: https://policies.google.com/terms
Privacy: https://policies.google.com/privacy
Google PageSpeed Insights (optional)
If you run a site health check, Phyllix calls https://www.googleapis.com/pagespeedonline with the public address of the page being checked, to retrieve its performance scores.
Terms: https://policies.google.com/terms
Privacy: https://policies.google.com/privacy
Google grounding redirect (AI Visibility and competitor discovery only)
When checking AI Visibility questions or discovering competitors, Phyllix’s
research sometimes comes back with a citation on vertexaisearch.cloud.google.com
— a Google redirect link, not a real page. For those two features only, Phyllix
makes a HEAD request directly to that link to follow the redirect to the real
address, so it can show or record the actual source rather than a redirect
link. No data about you or your site is sent – the request only asks where
the link redirects to.
Google privacy: https://policies.google.com/privacy
Links on your own pages
When you run a site health check, Phyllix makes a HEAD request to the addresses
your pages link to, in order to find broken links and redirect chains. These are
the sites you have already linked to. No data about you or your site is sent –
the request only asks whether the address still responds.
Connectivity diagnostics
The Diagnostics page in Settings makes one request to https://api.wordpress.org/
as a control check – a destination every WordPress site already trusts. This
confirms your server can reach the internet at all, so a failure to reach the
Phyllix service reads correctly as a problem with that one destination, not
your server’s outbound access in general. No data about you or your site is
sent – the request carries nothing beyond the request itself.
Public DNS resolvers (fallback only)
If your server’s normal DNS lookup for the Phyllix service ever fails, Phyllix
asks Cloudflare (1.1.1.1) and, if that also fails, Google (8.8.8.8) – both
public DNS-over-HTTPS resolvers – to look up the address instead, the same way
a browser’s own DNS-over-HTTPS setting would. This only happens after your
site’s normal outbound connection has already been proven to work. Only the
hostname being looked up is sent, and nothing about your site or its content
is included.
Cloudflare privacy: https://www.cloudflare.com/application-privacy-policy/
Google privacy: https://policies.google.com/privacy
