Publirank.io<\/a> community to support the web ecosystem.<\/p>\n\nPrivacy<\/h3>\n\n
This plugin keeps all data on your WordPress site. It does not send your content, settings, or crawl logs to Publirank.io or any other external service as part of its normal operation.<\/p>\n\n
What is stored<\/strong><\/p>\n\n\n- Settings<\/strong> \u2014 Stored in the WordPress options table (
publgeo_settings<\/code>): feature toggles, llms.txt preferences, category filters, and similar configuration.<\/li>\n- AI crawl statistics<\/strong> \u2014 When an identified AI-related bot requests Markdown, the LLM sitemap, or the llms-style list file, the plugin may log a row in a custom database table (
{prefix}publgeo_geo_crawls<\/code>) containing the requested URL (truncated), the HTTP User-Agent (truncated), a derived bot label, the date\/time of the request, and a classification flag. These rows are used only for the in-admin statistics dashboard.<\/li>\n- Short-lived cache<\/strong> \u2014 A transient (
publgeo_geo_llms_txt_cache<\/code>) may cache generated llms.txt output for performance. It is cleared on uninstall and can be cleared from the settings screen.<\/li>\n- Static cache files<\/strong> \u2014 Markdown (
.md<\/code>) and related files under your uploads directory (wp-content\/uploads\/...\/publgeo-cache\/<\/code>). They mirror public content and are regenerated from your posts.<\/li>\n<\/ul>\n\nRetention<\/strong><\/p>\n\n\n- Crawl log rows older than 90 days<\/strong> are deleted automatically by a daily scheduled task.<\/li>\n
- You can uninstall the plugin at any time. By default, settings and the crawl statistics table are kept<\/strong> so you can reinstall without losing configuration or history; generated
.md<\/code> cache files and the internal transient<\/strong> are removed on uninstall. A site administrator remains responsible for any wider data-protection obligations (for example, if URLs in logs are considered personal data in your jurisdiction).<\/li>\n<\/ul>\n\nUpgrading from earlier releases<\/strong><\/p>\n\n\n- Sites that used a previous development build may have data under the legacy option names (
pgr_geo_settings<\/code>) or table ({prefix}pgr_geo_crawls<\/code>). On upgrade, the plugin copies or renames these automatically to the current names. Public URLs (*.md<\/code>, sitemap-llm.xml<\/code>, llms.txt<\/code>, publirank-llms.txt<\/code>) are unchanged.<\/li>\n<\/ul>\n\nOptional checks in the admin<\/strong><\/p>\n\n\n- The \u201cVerify llms.txt\u201d tool uses
wp_remote_get()<\/code> against your own site\u2019s public URL<\/strong> to compare the HTTP response. No third-party analytics service is involved.<\/li>\n<\/ul>\n\n\n\n- Upload the plugin folder to the
\/wp-content\/plugins\/<\/code> directory.<\/li>\n- Activate the plugin through the 'Plugins' menu in WordPress.<\/li>\n
- Go to the 'GEO Ready' menu to see your statistics.<\/li>\n
- Under GEO Ready \u2192 Settings, enable GEO Ready if needed, then in the static cache section click \"Regenerate all
.md<\/code> files\" and \"Rebuild Sitemap & List\" to generate the Markdown files, LLM sitemap, and list file on disk.<\/li>\n<\/ol>\n\n\n\nDoes this create duplicate content on Google?<\/h3><\/dt>\nNo. All .md<\/code> files generated by the plugin send an X-Robots-Tag: noindex<\/code> HTTP header. Googlebot can still fetch these URLs, but it will not index them, so your classic HTML pages keep full SEO priority.<\/p><\/dd>\nWhat is the difference between llms.txt and the sitemap?<\/h3><\/dt>\nllms.txt is a recent standard aimed at AI assistants (such as ChatGPT): it gives a quick, high-level view of your site. The XML sitemap is more exhaustive and supports systematic crawling of all your content. GEO Ready provides both.<\/p><\/dd>\n
Can I block some AI bots but not others?<\/h3><\/dt>\nYes. In the settings, you can turn on protection against \"Training\" bots (scrapers) while still allowing \"Live Search\" bots that reference your links.<\/p><\/dd>\n
Why doesn't Gemini show up in my statistics?<\/h3><\/dt>\nGemini traffic is usually attributed to Google's regular crawler (Googlebot<\/code>), so it cannot be isolated in these statistics. The separate Google-Extended<\/code> user agent is only used to train Google's AI models; if you have enabled blocking of training and scraper bots in the settings, it may be blocked. This is not a bug: Gemini can still read your content through Googlebot\u2014you just cannot see a dedicated \"Gemini\" count in the dashboard.<\/p><\/dd>\n\n<\/dl>\n\n\n1.1.3<\/h4>\n\n\n- Removed automatic deactivation when the full Publirank plugin is detected. The GEO Ready module has been removed from the full plugin, so both can coexist (and you can use this free plugin alongside or instead of the paid version).<\/li>\n<\/ul>\n\n
1.1.2<\/h4>\n\n\n- Security\/standards: removed set_time_limit() in bulk regen (no global PHP limit override).<\/li>\n
- Security\/standards: settings POST array is now sanitized on input via map_deep( wp_unslash(), 'sanitize_textarea_field' ); each field is then re-validated downstream.<\/li>\n
- Security\/standards: JSON-LD output now goes exclusively through wp_print_inline_script_tag() (no unescaped echo fallback).<\/li>\n
- Security\/standards: hard-coded \"Access denied\" string for blocked training bots is now wrapped in esc_html__() (escape + i18n).<\/li>\n
- Security\/standards: Markdown \/ sitemap-llm.xml \/ llms.txt streams are now served via readfile() from the on-disk cache instead of echoing variables (removes WordPress.Security.EscapeOutput.OutputNotEscaped suppressions for these endpoints).<\/li>\n
- Performance: sitemap-llm.xml and llms.txt now warm the on-disk cache on first live render, so subsequent requests are served directly from cache.<\/li>\n<\/ul>\n\n
1.1.1<\/h4>\n\n\n- New setting: optional Article\/BlogPosting JSON-LD in HTML (off by default to avoid duplicate schema with SEO plugins). JSON-LD in .md files is unchanged.<\/li>\n
- Security and coding standards: sanitization on settings registration and form input, safe JSON-LD output in HTML.<\/li>\n
- Internal prefix renamed from
pgr<\/code> to publgeo<\/code> (options, database table, admin hooks) with automatic migration on upgrade. No change to public SEO URLs.<\/li>\n- llms.txt: up to 100 most recent posts, grouped by category (
## Category<\/code>), plain-text excerpts without HTML entities or […]<\/code>.<\/li>\n- Admin: live progress while
.md<\/code> cache regenerates in the background.<\/li>\n<\/ul>","raw_excerpt":"Prepare your WordPress site for AI and LLMs. Generate physical Markdown files, an LLM sitemap and track ChatGPT, Claude and Gemini crawls.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/311423","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=311423"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/iguanemedia"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=311423"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=311423"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=311423"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=311423"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=311423"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=311423"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}