[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fitpTbHAQxzsx4gcKuVOkPK8xSE1udo6iaEe7S27iuMg":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":18,"download_link":25,"security_score":13,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":36,"analysis":134,"fingerprints":334},"onebutton-log","OneButton – Log","1.10.0","Ekin Yalıncak","https:\u002F\u002Fprofiles.wordpress.org\u002Fonebutton\u002F","\u003Cp>OneButton – Log is the ultimate WordPress plugin for monitoring and analyzing search engine bot and AI bot activity on your website. Perfect for SEO professionals, webmasters, and site administrators who want to optimize their site’s crawlability, indexing performance, and AI training data usage.\u003C\u002Fp>\n\u003Cp>This powerful tool provides detailed insights into how search engines and AI systems interact with your content, helping you identify and fix crawl issues, improve site performance, enhance your overall SEO strategy, and understand how your content is being used for AI training.\u003C\u002Fp>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Real-Time Bot Monitoring\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Instant detection of search engine bot visits\u003C\u002Fli>\n\u003Cli>Live tracking of crawl patterns\u003C\u002Fli>\n\u003Cli>Immediate notification of crawl issues\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Dashboard Widget\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Quick bot visit statistics\u003C\u002Fli>\n\u003Cli>Recent activity overview\u003C\u002Fli>\n\u003Cli>Most visited pages\u003C\u002Fli>\n\u003Cli>24-hour visit summary\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Overview Dashboard\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Comprehensive statistics and analytics\u003C\u002Fli>\n\u003Cli>Interactive charts and graphs\u003C\u002Fli>\n\u003Cli>Improvement suggestions and recommendations\u003C\u002Fli>\n\u003Cli>Recent activity monitoring\u003C\u002Fli>\n\u003Cli>Most visited pages analysis\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Smart Bot Activity Calendar\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Interactive calendar view\u003C\u002Fli>\n\u003Cli>Color-coded visit indicators\u003C\u002Fli>\n\u003Cli>Daily crawl statistics\u003C\u002Fli>\n\u003Cli>Historical data analysis\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Automatic Log Cleanup\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Configurable cleanup intervals (1 day, 1 week, 1 month, never)\u003C\u002Fli>\n\u003Cli>Automatic removal of old log entries\u003C\u002Fli>\n\u003Cli>Database cleanup for optimal performance\u003C\u002Fli>\n\u003Cli>Scheduled cleanup via WordPress cron\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Export & Reporting\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Data analysis and reporting\u003C\u002Fli>\n\u003Cli>Historical data tracking\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>SEO Enhancement Tools\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Crawl error identification\u003C\u002Fli>\n\u003Cli>Indexing status monitoring\u003C\u002Fli>\n\u003Cli>Site structure analysis\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Supported Bots\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Search Engine Bots\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Googlebot (Google)\u003C\u002Fli>\n\u003Cli>Bingbot (Bing)\u003C\u002Fli>\n\u003Cli>YandexBot (Yandex)\u003C\u002Fli>\n\u003Cli>Baiduspider (Baidu)\u003C\u002Fli>\n\u003Cli>DuckDuckBot (DuckDuckGo)\u003C\u002Fli>\n\u003Cli>Slurp (Yahoo)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>AI Training Bots\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>GPTBot (OpenAI\u002FChatGPT)\u003C\u002Fli>\n\u003Cli>ChatGPT-User (OpenAI)\u003C\u002Fli>\n\u003Cli>DeepSeek (DeepSeek AI)\u003C\u002Fli>\n\u003Cli>DeepSeek-Web (DeepSeek AI)\u003C\u002Fli>\n\u003Cli>Gemini (Google AI)\u003C\u002Fli>\n\u003Cli>Google-Extended (Google AI)\u003C\u002Fli>\n\u003Cli>ClaudeBot (Anthropic)\u003C\u002Fli>\n\u003Cli>Claude-Web (Anthropic)\u003C\u002Fli>\n\u003Cli>Anthropic-ai (Anthropic)\u003C\u002Fli>\n\u003Cli>CCBot (Common Crawl)\u003C\u002Fli>\n\u003Cli>CCBot-Web (Common Crawl)\u003C\u002Fli>\n\u003Cli>PerplexityBot (Perplexity AI)\u003C\u002Fli>\n\u003Cli>YouBot (You.com)\u003C\u002Fli>\n\u003Cli>Omgilibot (Omgili)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>OneButton – Log collects and stores information about search engine bot visits to your website. This data is stored locally on your server and is not shared with any third parties. The plugin does not collect any personal information about your website visitors.\u003C\u002Fp>\n\u003Ch3>Additional Information\u003C\u002Fh3>\n\u003Cp>For support, feature requests, or bug reports, please visit our \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fonebutton\u002Fonebutton-log\" rel=\"nofollow ugc\">GitHub repository\u003C\u002Fa> or contact us through our website.\u003C\u002Fp>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>FullCalendar for calendar functionality\u003C\u002Fli>\n\u003Cli>WordPress core team for the excellent platform\u003C\u002Fli>\n\u003C\u002Ful>\n","Monitor and analyze search engine bot and AI bot visits to your WordPress site and optimize your SEO performance.",40,901,100,2,"2025-07-21T18:22:00.000Z","6.8.5","5.0","",[20,21,22,23,24],"analytics","bot","googlebot","log","seo","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fonebutton-log.1.10.0.zip",0,null,"2026-03-15T15:16:48.613Z",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":14,"total_installs":32,"avg_security_score":13,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"onebutton",50,30,94,"2026-04-04T15:54:58.677Z",[37,59,81,99,116],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":48,"last_updated":49,"tested_up_to":16,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":18,"download_link":56,"security_score":13,"vuln_count":57,"unpatched_count":26,"last_vuln_date":58,"fetched_at":28},"simple-googlebot-visit","Simple Googlebot Visit","1.2.6","codents","https:\u002F\u002Fprofiles.wordpress.org\u002Fcodents\u002F","\u003Cp>Simple Googlebot Visit is a plugin that lets you know at all times the last time that the googlebot visited any of your content. This is important because it is in charge of indexing all your pages and showing them in the search results of Google.\u003C\u002Fp>\n\u003Cp>Thanks to Simple Googlebot Visit you have this valuable information integrated into your WordPress administration panel, without having to integrate tools such as Search Console.\u003C\u002Fp>\n","Plugin to view the last visit of googlebot to your pages, entries and woocommerce products.",2000,16794,96,16,"2025-06-28T15:21:00.000Z","3.0.1","5.5",[53,22,54,55,24],"google","indexation","pages","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsimple-googlebot-visit.zip",1,"2023-07-24 00:00:00",{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":13,"num_ratings":69,"last_updated":70,"tested_up_to":16,"requires_at_least":71,"requires_php":72,"tags":73,"homepage":77,"download_link":78,"security_score":79,"vuln_count":57,"unpatched_count":26,"last_vuln_date":80,"fetched_at":28},"traffic-monitor","Traffic Monitor","3.2.7","Dmitri Martin","https:\u002F\u002Fprofiles.wordpress.org\u002Fdmitriamartin\u002F","\u003Cp>Traffic Monitor gives you full visibility into how people and bots are hitting your site.\u003C\u002Fp>\n\u003Cp>Unlike bloated analytics and security plugins, Traffic Monitor focuses on logging raw request data that you control. You’ll know which pages are cached, which bots are visiting, where users are coming from, and how many requests are tied to each IP\u002Fbrowser combination.\u003C\u002Fp>\n\u003Cp>Perfect for developers, marketers, and site owners who want fast insights—without handing over their traffic data.\u003C\u002Fp>\n\u003Ch3>What Makes It Different\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>✅ Logs requests for both \u003Cstrong>cached and non-cached pages\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>✅ Lets you \u003Cstrong>export raw traffic logs\u003C\u002Fstrong> as raw CSV for your own analysis\u003C\u002Fli>\n\u003Cli>✅ Identifies \u003Cstrong>repeat ad clicks\u003C\u002Fstrong> for spotting potential click fraud\u003C\u002Fli>\n\u003Cli>✅ Reveals \u003Cstrong>which bots are hitting your site\u003C\u002Fstrong>, so you can block them elsewhere (example: Cloudflare)\u003C\u002Fli>\n\u003Cli>✅ Tracks \u003Cstrong>IP address, fingerprint, device type, cache status, response code\u003C\u002Fstrong>, and more\u003C\u002Fli>\n\u003Cli>✅ Displays \u003Cstrong>referrer URLs and query strings\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>✅ Records the \u003Cstrong>original source\u003C\u002Fstrong> of requests by the same visitor as they surf your website\u003C\u002Fli>\n\u003Cli>✅ Doesn’t auto-block or inject junk—\u003Cstrong>just clean, useful data\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>✅ Works great with \u003Cstrong>Cloudflare, caching plugins, and reverse proxies\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Key Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Logs every page request\u003C\u002Fstrong>, including IP address, referrer, user-agent, browser, device, method, and more.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Detects cached traffic\u003C\u002Fstrong> even if served by Cloudflare, your web host, or a plugin.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Identifies bot traffic\u003C\u002Fstrong> by bot name and category.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>View click IDs\u003C\u002Fstrong> like gclid and fbclid from ad platforms like Google and Meta.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Records repeat ad clicks\u003C\u002Fstrong> to detect potential click fraud.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Bulk delete or export logs\u003C\u002Fstrong> with one click.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Search, sort, and drill into data\u003C\u002Fstrong> from your dashboard.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Built-in help tabs\u003C\u002Fstrong> with definitions, setup help, and troubleshooting.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Use Cases\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Debug integrations instantly\u003C\u002Fstrong>: Know exactly what URLs are being hit, by which devices, and with what parameters. No guesswork.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Spot caching gaps\u003C\u002Fstrong>: See which pages are served from cache and which aren’t, even with Cloudflare or plugin-level caching.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Understand real-world traffic\u003C\u002Fstrong>: Track entry pages, referrers, devices, and browsers—whether human or bot.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Catch click fraud signals\u003C\u002Fstrong>: Identify repeat ad clicks tied to the same IP\u002Fuser agent fingerprint or session, even if served from cache.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Audit referrers\u003C\u002Fstrong>: View exactly which websites or campaigns are driving traffic (including query strings).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Filter out noise\u003C\u002Fstrong>: Use bot labels and device types to focus only on human traffic when analyzing patterns.\u003C\u002Fli>\n\u003C\u002Ful>\n","Lightweight traffic logger for WordPress analytics. View, filter, and export page request data; monitor caching; detect bots; and spot click fraud.",1000,5056,3,"2025-10-21T17:44:00.000Z","6.2","7.4",[20,21,74,75,76],"fraud","logging","traffic","https:\u002F\u002Fgithub.com\u002Fdmitrimartin817\u002Ftraffic-monitor","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftraffic-monitor.3.2.7.zip",99,"2025-06-12 14:33:50",{"slug":82,"name":83,"version":84,"author":85,"author_profile":86,"description":87,"short_description":88,"active_installs":89,"downloaded":90,"rating":26,"num_ratings":26,"last_updated":91,"tested_up_to":92,"requires_at_least":50,"requires_php":18,"tags":93,"homepage":96,"download_link":97,"security_score":98,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"unblock-cs-jss-for-googlebot","Unblock CSS & JS for Googlebot","1.0","Miina Sikk","https:\u002F\u002Fprofiles.wordpress.org\u002Fmiinasikk\u002F","\u003Cp>Unblock CSS & JS for Googlebot plugin allows Googlebot to access the JavaScript and CSS files.\u003C\u002Fp>\n\u003Cp>Google periodically sends to webmasters warnings that their JavaScript .js files and their CSS stylesheets are blocked – even when the webmasters have never explicitly done so. In fact, it is estimated that 85% of all users of Google webmaster tools have received such a warning.\u003C\u002Fp>\n\u003Cp>Unblock CSS & JS for Googlebot solves this problem for you — and no configuration is needed. Just install and activate the plugin.\u003C\u002Fp>\n\u003Cp>How does it work? It just adds in three lines to your robots.txt file to ensure the Google spider can get through.\u003C\u002Fp>\n\u003Cp>You don’t want it anymore? Just uninstall and the added lines will be removed.\u003C\u002Fp>\n\u003Cp>For more information and support, check out: http:\u002F\u002Fwww.wpsos.io\u002Fwordpress-plugin-unblock-css-js-for-googlebot\u002F\u003C\u002Fp>\n","Modifies robots.txt to allow Googlebot access JS and CSS files.",60,3103,"2016-02-05T23:17:00.000Z","4.4.34",[22,94,95,24],"robots","robots-txt","http:\u002F\u002Fwww.wpsos.io\u002Fwordpress-plugin-unblock-css-js-for-googlebot\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Funblock-cs-jss-for-googlebot.zip",85,{"slug":100,"name":101,"version":102,"author":103,"author_profile":104,"description":105,"short_description":106,"active_installs":32,"downloaded":107,"rating":13,"num_ratings":57,"last_updated":108,"tested_up_to":109,"requires_at_least":110,"requires_php":72,"tags":111,"homepage":114,"download_link":115,"security_score":13,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"crawler-record","Crawler Record","0.9.1","dizzysoft","https:\u002F\u002Fprofiles.wordpress.org\u002Fdizzysoft\u002F","\u003Cp>\u003Cstrong>Crawler Record\u003C\u002Fstrong> logs the last time specific user agents (for search and AI chat\u002FLLMs) accessed your content including:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Google\u003C\u002Fli>\n\u003Cli>Bing\u003C\u002Fli>\n\u003Cli>ChatGPT (OpenAI)\u003C\u002Fli>\n\u003Cli>Claude (Anthropic)\u003C\u002Fli>\n\u003Cli>Perplexity\u003C\u002Fli>\n\u003Cli>DuckDuckGo\u003C\u002Fli>\n\u003Cli>Meta\u003C\u002Fli>\n\u003Cli>Apple\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>You can view this information:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Admin page\u003C\u002Fstrong>: a grouped list of all crawlers, with last seen time, last page, and robots status for the crawler.  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Admin Bar (front-end)\u003C\u002Fstrong>: quick-glance status for the current singular or URL context (no dropdowns in wp-admin).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Per Page\u002FPost\u003C\u002Fstrong>: From the edit screen on any page or post, you can see that last time each crawler visited that page.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Robots-aware:\u003C\u002Fstrong> The plugin checks  your \u003Cstrong>robots.txt\u003C\u002Fstrong> and evaluates \u003Cstrong>Allow\u002FDisallow\u003C\u002Fstrong> rules for a given path. If \u003Cstrong>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Reading \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> “Discourage search engines”\u003C\u002Fstrong> is enabled, all agents are shown as blocked with a prominent warning.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Performance-friendly by design:\u003C\u002Fstrong> Write-throttling (default 10 minutes) and an auxiliary “last post ID per agent” record avoids heavy admin queries on large sites.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Privacy-friendly:\u003C\u002Fstrong> Saves only bot visit timestamps and last URLs crawled — no personal data.\u003C\u002Fp>\n\u003Cp>Learn \u003Ca href=\"https:\u002F\u002Fwww.dizzysoft.com\u002Fcrawler-record-plugin-for-wordpress\u002F\" rel=\"nofollow ugc\">\u003Cstrong>how to use this plugin\u003C\u002Fstrong>\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Highlights\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Supports common user-agent variants for Google, Bing, OpenAI (ChatGPT), Anthropic (Claude), Perplexity, Meta, Apple, and DuckDuckGo.\u003C\u002Fli>\n\u003Cli>Robots status computed from local robots.txt (physical or virtual) without outbound requests.\u003C\u002Fli>\n\u003Cli>Clear UI with grouped sections, microsecond timestamps, and a small diagnostics toggle showing the matched robots group and rule.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Known limitations\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>robots.txt \u003Cstrong>wildcards\u003C\u002Fstrong> (\u003Ccode>*\u003C\u002Fcode>) and end-of-line marker (\u003Ccode>$\u003C\u002Fcode>) are \u003Cstrong>not\u003C\u002Fstrong> interpreted; matching is prefix-based only. Future versions may add full spec support.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>This plugin stores:\u003Cbr \u002F>\n– \u003Cstrong>Timestamps\u003C\u002Fstrong> of crawler visits (float, with microseconds)\u003Cbr \u002F>\n– \u003Cstrong>Last URL\u003C\u002Fstrong> seen per crawler (per-URL records)\u003Cbr \u002F>\n– \u003Cstrong>Last post ID\u003C\u002Fstrong> per crawler (for admin performance)\u003C\u002Fp>\n\u003Cp>It does \u003Cstrong>not\u003C\u002Fstrong> collect or store personal data about site visitors. No data is transmitted to third parties.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>GPLv2 or later. See LICENSE file.\u003C\u002Fp>\n","Crawler Record tells you the last time each of the most common search\u002Fchat bots visited (Google, ChatGPT, etc)- and the pages at which they looked.",553,"2026-01-07T16:00:00.000Z","6.9.4","6.0",[112,22,113,94,24],"bingbot","gptbot","https:\u002F\u002Fwww.dizzysoft.com\u002Fcrawler-record-plugin-for-wordpress\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcrawler-record.0.9.1.zip",{"slug":117,"name":118,"version":119,"author":120,"author_profile":121,"description":122,"short_description":123,"active_installs":11,"downloaded":124,"rating":26,"num_ratings":26,"last_updated":125,"tested_up_to":126,"requires_at_least":127,"requires_php":128,"tags":129,"homepage":18,"download_link":132,"security_score":133,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"get-user-agents","Get User-Agents","1.0.4.1","Santos R. Guerra Faro","https:\u002F\u002Fprofiles.wordpress.org\u002Fdragondeluz\u002F","\u003Cp>WordPress plugin to keep track of User Agents that come to our website. This information is usually extracted from the server log, but in many cases it is a cumbersome process and a lot of valuable time is lost, so I decided to make a simple plugin that allows you to get the information without consuming resources and easily export it for further analysis.\u003C\u002Fp>\n\u003Cp>A User Agent is a text string that identifies the software and hardware used by a client when accessing a website or online service. It typically includes information about:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Web browser (type and version)\u003C\u002Fli>\n\u003Cli>Operating system\u003C\u002Fli>\n\u003Cli>Device (in the case of cell phones or tablets)\u003C\u002Fli>\n\u003Cli>Rendering engine\u003C\u002Fli>\n\u003Cli>Other client characteristics\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example User Agent:\u003Cbr \u002F>\n”’Mozilla\u002F5.0 (Windows NT 10.0; Win64; x64) AppleWebKit\u002F537.36 (KHTML, like Gecko) Chrome\u002F91.0.4472.124 Safari\u002F537.36””\u003C\u002Fp>\n\u003Cp>User Agents’ collection and analysis provides valuable insights for developers, analysts and security professionals, allowing to improve user experience and website effectiveness.\u003C\u002Fp>\n\u003Cp>The information collected by this plugin can be used for:\u003Cbr \u002F>\n* Search bots identification: Allows to identify search engine bots (such as Googlebot, Bingbot, etc.) that are crawling your site.\u003Cbr \u002F>\n* Detection of technical problems.* Resource optimization.* Identification of malicious traffic.\u003Cbr \u002F>\n* Verification of SEO tools.\u003Cbr \u002F>\n* Traffic analysis.\u003C\u002Fp>\n","WordPress plugin tracks User Agents, avoiding server log analysis. Records and exports data easily for further analysis.",898,"2024-11-27T17:57:00.000Z","6.6.5","3.0","5.6",[22,24,130,131],"spider","user-agent","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fget-user-agents.zip",92,{"attackSurface":135,"codeSignals":195,"taintFlows":225,"riskAssessment":328,"analyzedAt":333},{"hooks":136,"ajaxHandlers":182,"restRoutes":190,"shortcodes":191,"cronEvents":192,"entryPointCount":14,"unprotectedCount":26},[137,143,147,150,154,158,162,167,169,170,173,175,177,180],{"type":138,"name":139,"callback":140,"file":141,"line":142},"action","wp","onebutton_log_bot_visits","onebutton-log.php",145,{"type":138,"name":144,"callback":145,"file":141,"line":146},"admin_menu","onebutton_log_menu",183,{"type":138,"name":144,"callback":148,"file":141,"line":149},"onebutton_add_submenus",620,{"type":138,"name":151,"callback":152,"file":141,"line":153},"onebutton_auto_cleanup","onebutton_execute_auto_cleanup",767,{"type":138,"name":155,"callback":156,"file":141,"line":157},"admin_init","onebutton_clear_logs",798,{"type":138,"name":159,"callback":160,"file":141,"line":161},"wp_dashboard_setup","onebutton_add_dashboard_widget",1043,{"type":138,"name":163,"callback":164,"priority":165,"file":141,"line":166},"upgrader_process_complete","onebutton_upgrade_complete",10,1617,{"type":138,"name":139,"callback":140,"file":168,"line":142},"trunk\\onebutton-log.php",{"type":138,"name":144,"callback":145,"file":168,"line":146},{"type":138,"name":144,"callback":171,"file":168,"line":172},"onebutton_add_settings_submenu",198,{"type":138,"name":155,"callback":156,"file":168,"line":174},257,{"type":138,"name":159,"callback":160,"file":168,"line":176},502,{"type":138,"name":144,"callback":178,"file":168,"line":179},"onebutton_add_calendar_menu",972,{"type":138,"name":163,"callback":164,"priority":165,"file":168,"line":181},1075,[183,188],{"action":184,"nopriv":185,"callback":184,"hasNonce":186,"hasCapCheck":186,"file":141,"line":187},"onebutton_get_calendar_data",false,true,1471,{"action":184,"nopriv":185,"callback":184,"hasNonce":186,"hasCapCheck":186,"file":168,"line":189},928,[],[],[193],{"hook":151,"callback":151,"file":141,"line":194},685,{"dangerousFunctions":196,"sqlUsage":197,"outputEscaping":199,"fileOperations":222,"externalRequests":26,"nonceChecks":223,"capabilityChecks":222,"bundledLibraries":224},[],{"prepared":26,"raw":26,"locations":198},[],{"escaped":200,"rawEcho":201,"locations":202},163,9,[203,206,208,210,212,214,216,218,220],{"file":141,"line":204,"context":205},530,"raw output",{"file":141,"line":207,"context":205},655,{"file":141,"line":209,"context":205},656,{"file":141,"line":211,"context":205},664,{"file":141,"line":213,"context":205},665,{"file":141,"line":215,"context":205},666,{"file":141,"line":217,"context":205},667,{"file":168,"line":219,"context":205},220,{"file":168,"line":221,"context":205},221,6,8,[],[226,252,263,286,300,310],{"entryPoint":227,"graph":228,"unsanitizedCount":26,"severity":251},"onebutton_settings_page (onebutton-log.php:626)",{"nodes":229,"edges":248},[230,235,241,244],{"id":231,"type":232,"label":233,"file":141,"line":234},"n0","source","$_POST (x2)",629,{"id":236,"type":237,"label":238,"file":141,"line":239,"wp_function":240},"n1","sink","update_option() [Settings Manipulation]",630,"update_option",{"id":242,"type":232,"label":243,"file":141,"line":234},"n2","$_POST (x6)",{"id":245,"type":237,"label":246,"file":141,"line":207,"wp_function":247},"n3","echo() [XSS]","echo",[249,250],{"from":231,"to":236,"sanitized":186},{"from":242,"to":245,"sanitized":186},"low",{"entryPoint":253,"graph":254,"unsanitizedCount":26,"severity":251},"onebutton_log_page (onebutton-log.php:801)",{"nodes":255,"edges":261},[256,259],{"id":231,"type":232,"label":257,"file":141,"line":258},"$_GET (x2)",816,{"id":236,"type":237,"label":246,"file":141,"line":260,"wp_function":247},903,[262],{"from":231,"to":236,"sanitized":186},{"entryPoint":264,"graph":265,"unsanitizedCount":26,"severity":251},"\u003Conebutton-log> (onebutton-log.php:0)",{"nodes":266,"edges":281},[267,268,269,270,271,274,277,279],{"id":231,"type":232,"label":233,"file":141,"line":234},{"id":236,"type":237,"label":238,"file":141,"line":239,"wp_function":240},{"id":242,"type":232,"label":243,"file":141,"line":234},{"id":245,"type":237,"label":246,"file":141,"line":207,"wp_function":247},{"id":272,"type":232,"label":273,"file":141,"line":47},"n4","$_SERVER (x2)",{"id":275,"type":237,"label":246,"file":141,"line":276,"wp_function":247},"n5",889,{"id":278,"type":232,"label":257,"file":141,"line":258},"n6",{"id":280,"type":237,"label":246,"file":141,"line":260,"wp_function":247},"n7",[282,283,284,285],{"from":231,"to":236,"sanitized":186},{"from":242,"to":245,"sanitized":186},{"from":272,"to":275,"sanitized":186},{"from":278,"to":280,"sanitized":186},{"entryPoint":287,"graph":288,"unsanitizedCount":26,"severity":251},"onebutton_settings_page (trunk\\onebutton-log.php:204)",{"nodes":289,"edges":297},[290,293,295,296],{"id":231,"type":232,"label":291,"file":168,"line":292},"$_POST",207,{"id":236,"type":237,"label":238,"file":168,"line":294,"wp_function":240},208,{"id":242,"type":232,"label":233,"file":168,"line":292},{"id":245,"type":237,"label":246,"file":168,"line":219,"wp_function":247},[298,299],{"from":231,"to":236,"sanitized":186},{"from":242,"to":245,"sanitized":186},{"entryPoint":301,"graph":302,"unsanitizedCount":26,"severity":251},"onebutton_log_page (trunk\\onebutton-log.php:260)",{"nodes":303,"edges":308},[304,306],{"id":231,"type":232,"label":257,"file":168,"line":305},275,{"id":236,"type":237,"label":246,"file":168,"line":307,"wp_function":247},362,[309],{"from":231,"to":236,"sanitized":186},{"entryPoint":311,"graph":312,"unsanitizedCount":26,"severity":251},"\u003Conebutton-log> (trunk\\onebutton-log.php:0)",{"nodes":313,"edges":323},[314,315,316,317,318,319,321,322],{"id":231,"type":232,"label":291,"file":168,"line":292},{"id":236,"type":237,"label":238,"file":168,"line":294,"wp_function":240},{"id":242,"type":232,"label":233,"file":168,"line":292},{"id":245,"type":237,"label":246,"file":168,"line":219,"wp_function":247},{"id":272,"type":232,"label":273,"file":168,"line":47},{"id":275,"type":237,"label":246,"file":168,"line":320,"wp_function":247},348,{"id":278,"type":232,"label":257,"file":168,"line":305},{"id":280,"type":237,"label":246,"file":168,"line":307,"wp_function":247},[324,325,326,327],{"from":231,"to":236,"sanitized":186},{"from":242,"to":245,"sanitized":186},{"from":272,"to":275,"sanitized":186},{"from":278,"to":280,"sanitized":186},{"summary":329,"deductions":330},"The \"onebutton-log\" v1.10.0 plugin exhibits a generally strong security posture based on the provided static analysis. The absence of dangerous functions, SQL injection vulnerabilities (all queries are prepared), and a very high percentage of properly escaped output are commendable. The plugin also correctly implements nonce and capability checks on its entry points, and there are no identified critical or high severity taint flows. The lack of any historical vulnerabilities further bolsters confidence in its current security.\n\nHowever, there are a couple of areas that warrant attention. While the attack surface is small and all entry points appear to have authentication checks, the presence of file operations (6 instances) could potentially be a concern if not handled with extreme care. Without further details on how these file operations are implemented, it's difficult to definitively rule out risks. Similarly, while no external HTTP requests are made, this can be a common vector for vulnerabilities in other plugins. The absence of bundled libraries is a positive indicator, as outdated libraries can introduce significant security risks.\n\nIn conclusion, \"onebutton-log\" v1.10.0 appears to be a well-secured plugin. Its diligent use of prepared statements, output escaping, and security checks on its limited attack surface are significant strengths. The primary areas to monitor would be the implementation of its file operations to ensure they cannot be exploited. The complete lack of historical vulnerabilities and zero reported CVEs is a strong indicator of ongoing security diligence.",[331],{"reason":332,"points":69},"File operations present (potential risk)","2026-03-16T22:15:50.549Z",{"wat":335,"direct":340},{"assetPaths":336,"generatorPatterns":337,"scriptPaths":338,"versionParams":339},[],[],[],[],{"cssClasses":341,"htmlComments":342,"htmlAttributes":343,"restEndpoints":344,"jsGlobals":345,"shortcodeOutput":346},[],[],[],[],[],[]]