內容簡介
SitePulse Guard by PPros 是一款輔助性外掛，旨在補足 Yoast 和 Rank Math 等 SEO 外掛未能完全涵蓋的三個重要領域，包括 AI 搜尋可見性、實際無障礙性和網站健康狀況，幫助網站提升整體效能。
【主要功能】
• 自動生成 llms.txt 和 llms-full.txt
• 掃描圖像的替代文字和標題
• 審核後再寫入無障礙性建議
• 監控網站健康狀況
• 提供 AI 可見性評分
外掛標籤
開發者團隊
原文外掛簡介
SitePulse Guard by PPros is a companion, not another SEO plugin and not another llms.txt-only generator.
It is built for sites that already use Yoast or Rank Math and still have three gaps those plugins do not fully cover:
AI search visibility (GEO) — publish llms.txt / llms-full.txt from real content, allow answer engines while blocking known training scrapers, and see a plain-English AI Readiness Score.
Real accessibility (EAA / WCAG) — scan for missing alt text, weak headings, unlabeled fields, and vague links. Suggested alt text is never written until you approve it. A visitor widget is a helper, not a substitute for fixes.
Site health — unused or heavy plugins, common SEO/cache/security overlap, local Core Web Vitals impact, and a simple security surface.
What makes SitePulse Guard by PPros different
Most directory plugins in this area do one job (usually llms.txt). SitePulse Guard by PPros is the small toolkit that sits beside your SEO plugin:
Schema is deferred when Yoast or Rank Math is already outputting JSON-LD, so you do not get duplicate markup.
Accessibility changes are approve-before-write. Nothing is silently patched in the media library.
Core features run locally. No AI provider is required to generate files, scores, crawler rules, or rule-based alt text.
Optional AI-assisted alt text uses the WordPress AI Client (WordPress 7.0+) and the provider the site owner already configured under Settings → Connectors. SitePulse Guard by PPros does not store vendor API keys and does not call a provider HTTP API directly.
AI Visibility
Auto-generate and preview llms.txt and llms-full.txt from published content
Choose post types and regenerate in one click
Allow answer engines and block known training scrapers via robots.txt
JSON-LD structured data (WebSite, Organization, Article/WebPage, FAQ) only when Yoast/Rank Math are not active
AI Readiness Score (0–100) with clear next steps
Accessibility
Image alt scan (missing and filename-like text)
Rule-based suggestions; optional AI via the WordPress AI Client when a site-wide provider is configured
Per-page and site-wide scores
Heading, form label, iframe, and vague-link warnings
Visitor widget (text size, contrast, links, spacing, reduce motion)
Accessibility statement page generator
Nothing is written to the media library until you approve it.
Site Health Guardian
Unused / inactive plugin list with folder size
Common SEO, cache, security, and optimizer overlap
Local Core Web Vitals impact (plugin count, autoload size, cache, HTTPS)
Outdated and possibly abandoned plugin reminders
Overall health score on the dashboard
Designed to stay light
No page-builder lock-in (Gutenberg, Elementor, Bricks, and others)
Front end loads a tiny widget only when you enable it
Admin assets load only on SitePulse Guard by PPros screens
Native WordPress APIs — no Composer stack in the free plugin
External services
Core features (llms.txt generation, robots.txt rules, scores, rule-based alt text, site health) run on your WordPress site. They do not send content to a third-party API.
WordPress AI Client (optional)
Optional AI-assisted alt text is available on WordPress 7.0 or later when the site owner has configured an AI provider under Settings → Connectors. SitePulse Guard by PPros uses the core WordPress AI Client instead of calling a vendor directly.
What it is used for: improving suggested image alt text when an administrator clicks generate.
What data is sent, and when: the generation prompt, a short image context (title/filename), and — when the model supports it — the public image URL. Data is sent only after an administrator action, never on ordinary front-end page views.
Where it goes: whichever provider the site owner already connected (for example the official OpenAI, Anthropic, or Google provider plugins). SitePulse Guard by PPros does not collect or store those API keys.
If the site owner connects one of the official provider plugins, that vendor’s terms apply:
OpenAI — Terms of use and Privacy policy
Anthropic — Consumer terms and Privacy policy
Google Gemini — API terms and Privacy policy
If no provider is configured, or you turn the option off in SitePulse Guard by PPros settings, no prompt data leaves the site.
