Security fix in JSON-LD output. Upgrade recommended.<\/p>","1.0.2 = Reactivate the plugin after updating if WordPress lists it as inactive.":"","1.0.1":"
Optional AI features now use the WordPress AI Client.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.5"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[1953,2591,244604,151481,1956],"plugin_category":[34,49],"plugin_contributors":[269283],"plugin_business_model":[],"class_list":["post-369888","plugin","type-plugin","status-publish","hentry","plugin_tags-accessibility","plugin_tags-geo","plugin_tags-llms-txt","plugin_tags-site-health","plugin_tags-wcag","plugin_category-accessibility","plugin_category-maps-and-location","plugin_contributors-sakibbd08","plugin_committers-sakibbd08"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/spg-by-ppros.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
SitePulse Guard by PPros is a companion<\/strong>, not another SEO plugin and not another llms.txt-only generator.<\/p>\n\n It is built for sites that already use Yoast or Rank Math and still have three gaps those plugins do not fully cover:<\/p>\n\n Most directory plugins in this area do one job (usually Nothing is written to the media library until you approve it.<\/p>\n\n 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.<\/p>\n\n Optional AI-assisted alt text is available on WordPress 7.0 or later when the site owner has configured an AI provider under Settings \u2192 Connectors<\/strong>. SitePulse Guard by PPros uses the core WordPress AI Client instead of calling a vendor directly.<\/p>\n\n If the site owner connects one of the official provider plugins, that vendor\u2019s terms apply:<\/p>\n\n If no provider is configured, or you turn the option off in SitePulse Guard by PPros settings, no prompt data leaves the site.<\/p>\n\n\n No. Keep one SEO plugin for titles, schema, and sitemaps. SitePulse Guard by PPros adds AI files, accessibility, and health checks, and it skips JSON-LD when those plugins already handle it.<\/p><\/dd>\n No. SitePulse Guard by PPros is not an llms.txt-only plugin. It combines AI visibility with approve-before-write accessibility and a site-health pass, and it is written as a companion to Yoast\/Rank Math rather than a replacement.<\/p><\/dd>\n No overlay can replace real content fixes. The widget is a helper. Use the scan and approval queue for actual issues.<\/p><\/dd>\n Yes. Builder pages with little stored HTML are noted in the scan so you are not given a false perfect score.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
llms.txt<\/code> \/ llms-full.txt<\/code> from real content, allow answer engines while blocking known training scrapers, and see a plain-English AI Readiness Score.<\/li>\nWhat makes SitePulse Guard by PPros different<\/h4>\n\n
llms.txt<\/code>). SitePulse Guard by PPros is the small toolkit that sits beside<\/strong> your SEO plugin:<\/p>\n\n\n
AI Visibility<\/h4>\n\n
\n
llms.txt<\/code> and llms-full.txt<\/code> from published content<\/li>\nrobots.txt<\/code><\/li>\nAccessibility<\/h4>\n\n
\n
Site Health Guardian<\/h4>\n\n
\n
Designed to stay light<\/h4>\n\n
\n
External services<\/h3>\n\n
WordPress AI Client (optional)<\/h4>\n\n
\n
\n
\n
spg-by-ppros<\/code> folder to \/wp-content\/plugins\/<\/code><\/li>\n\n
Does this replace Yoast or Rank Math?<\/h3><\/dt>\n
Do I need an API key?<\/h3><\/dt>\n
llms.txt<\/code>, crawler rules, scores, and rule-based alt text work without one. SitePulse Guard by PPros never asks you to paste a vendor key. Optional AI alt text uses the WordPress AI Client and a provider configured once for the whole site.<\/p><\/dd>\nHow is this different from other llms.txt plugins?<\/h3><\/dt>\n
Will the visitor widget make my site accessible?<\/h3><\/dt>\n
Can I use this with Elementor or Bricks?<\/h3><\/dt>\n
1.0.5<\/h4>\n\n
\n
wp_json_encode()<\/code> directly inside echo<\/code> instead of via an intermediate variable, satisfying WPCS EscapeOutput<\/code> sniff without suppression comments.<\/li>\n<\/ul>\n\n1.0.4<\/h4>\n\n
\n
JSON_HEX_TAG<\/code> flag to wp_json_encode()<\/code> in the schema output to prevent <\/script><\/code> tag breakout in JSON-LD. Removed phpcs:ignore<\/code> suppression comments that were masking the issue.<\/li>\n<\/ul>\n\n1.0.3<\/h4>\n\n
\n
Tested up to<\/code> from the main plugin PHP header \u2014 it is now declared only in readme.txt per WordPress.org guidelines.<\/li>\n1.0.2<\/h4>\n\n
\n
spg-by-ppros<\/code>.<\/li>\nload_plugin_textdomain()<\/code> was removed.<\/li>\n<\/ul>\n\n1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n