[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f_jf4yJvQV88QfCE08OeAbE9UYUChL9_uH77OGyh8PZU":3,"$fa0eCbdKTJZWECDzU0h2LwHwZWgqAx9ZDsTQmdwXsd5I":299,"$fxRomX1exBVE4M7j9cgwptodzwBu8SLeJYgjIJruN8M8":303},{"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":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"discovery_status":29,"vulnerabilities":30,"developer":31,"crawl_stats":27,"alternatives":39,"analysis":144,"fingerprints":276},"tdmrep","TDMRep: TDM Reservation Protocol","1.0.2","Pierre Viéville","https:\u002F\u002Fprofiles.wordpress.org\u002Fimmolare\u002F","\u003Cp>TDMRep is a user-friendly WordPress plugin that lets you control how robots and artificial intelligences (AIs) like ChatGPT and Bard access your content. It integrates with the \u003Ca href=\"https:\u002F\u002Fwww.w3.org\u002Fcommunity\u002Freports\u002Ftdmrep\u002FCG-FINAL-tdmrep-20240202\u002F\" rel=\"nofollow ugc\">TDM Reservation Protocol\u003C\u002Fa> to help you safeguard your copyright and promote innovation.\u003C\u002Fp>\n\u003Ch3>Control Who Can Access Your Website Content with TDMRep\u003C\u002Fh3>\n\u003Cp>Think of all the effort you put into creating and organizing the content on your website. You want to share it with the world, but you also want to \u003Cstrong>control who can copy and use your work\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>That’s where TDMRep comes in!\u003C\u002Fp>\n\u003Ch3>How Does TDMRep Work?\u003C\u002Fh3>\n\u003Cp>Imagine TDMRep as a set of instructions for robots visiting your website. You can tell them exactly what you want them to do with your content, like:\u003C\u002Fp>\n\u003Cp>“Read my content, but don’t copy it.” This is useful for search engine robots that analyze your website to understand your content and rank it in search results.\u003C\u002Fp>\n\u003Cp>“Read and copy my content, but only for personal use.” This is helpful for students doing research or creators looking for inspiration.\u003C\u002Fp>\n\u003Cp>“This content is private! Stay out!” This is useful for sensitive information you don’t want shared publicly.\u003C\u002Fp>\n\u003Ch3>Why Use TDMRep?\u003C\u002Fh3>\n\u003Cp>There are two main reasons why TDMRep is important:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Protect Your Copyright:\u003C\u002Fstrong> By controlling access to your content, you prevent people from copying and using your work without permission.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Fuel Innovation:\u003C\u002Fstrong> TDMRep lets responsible robots and AIs access your content in a controlled way. This can help drive research and development of new technologies.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Examples of How Bots Use TDMRep\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Googlebot:\u003C\u002Fstrong> This is the robot that crawls websites for Google Search. It uses TDMRep to understand your content and rank your website in search results.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ChatGPT:\u003C\u002Fstrong> This AI can use TDMRep to learn from your content and create new text formats, poems, scripts, and more.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Bard:\u003C\u002Fstrong> Google’s AI can use TDMRep to translate your content, write blog posts, and answer your questions in an informative way.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Who can benefit from TDMRep?\u003C\u002Fh3>\n\u003Cp>TDMRep can benefit a variety of users, including:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Website owners:\u003C\u002Fstrong> TDMRep lets you control access to your content and protect your copyright.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Content creators:\u003C\u002Fstrong> TDMRep lets you share your content with the world while controlling who can copy and use it.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Robots and AIs:\u003C\u002Fstrong> TDMRep allows robots and AIs to access your content responsibly and use it to develop new technologies.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Students and researchers:\u003C\u002Fstrong> TDMRep allows students and researchers to access your content for their research.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>General public:\u003C\u002Fstrong> TDMRep makes it easier for the general public to find information on your website.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Here are some concrete examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A blogger can use TDMRep to allow robots to read their content and index it in search engines, while prohibiting the copying of their content without permission.\u003C\u002Fli>\n\u003Cli>A music publisher can use TDMRep to allow music streaming services to stream their music, while retaining control of the copyright.\u003C\u002Fli>\n\u003Cli>A university can use TDMRep to allow researchers to access its research data, while protecting the privacy of participants.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In short, TDMRep is a valuable tool for anyone who wants to control access to their content and protect their copyright.\u003C\u002Fp>\n\u003Ch3>TDM Reservation Protocol Techniques\u003C\u002Fh3>\n\u003Cp>TDMRep integrates 3 of the 4 complementary techniques offered by the TDM Reservation Protocol:\u003C\u002Fp>\n\u003Ch3>TDM File on the Origin Server (.well-known\u002Ftdmrep.json): files, images, pages, posts, sets of urls\u003C\u002Fh3>\n\u003Cp>The TDM File on the Origin Server technique allows publishers to declare site-wide rights holders’ choices in a machine-readable file hosted on the web server. TDMRep generates this file and provides an interface for publishers to manage their TDM reservation and licensing policies.\u003C\u002Fp>\n\u003Ch3>TDM Header Field in HTTP Responses (.htaccess): files, images, pages, posts, sets of urls\u003C\u002Fh3>\n\u003Cp>The TDM Header Field in HTTP Responses technique allows publishers to declare their TDM rights reservation and licensing policies in the HTTP header of the response to a GET or HEAD request. TDMRep integrates this technique by adding the necessary header fields to the HTTP responses generated by WordPress.\u003C\u002Fp>\n\u003Ch3>TDM Metatags in page, posts or set of urls\u003C\u002Fh3>\n\u003Cp>TDMRep also supports the use of meta tags to express TDM rights and licensing policies on individual pages and posts, providing a more granular level of control for publishers who want to specify different policies for different parts of their website.\u003C\u002Fp>\n\u003Ch3>Expressing a TDM Policy\u003C\u002Fh3>\n\u003Cp>TDMRep plugin allows publishers to express their TDM policies in a machine-readable format using the TDM Policy feature. This feature provides a way for TDM actors to contact content rightsholders and offers details about available TDM licenses, facilitating the acquisition of TDM licenses from rightsholders by TDM actors.\u003C\u002Fp>\n\u003Cp>The TDM Policy feature is integrated into the TDMRep plugin and includes the following:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Assigner\u003C\u002Fli>\n\u003Cli>Permissions\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>With this feature, publishers can easily express their TDM policies, including the type of permission granted, any constraints on the type of usage, and any duties required of the TDM actor, such as the duty to contact the rightsholder before getting permission or the duty to compensate financially the rightsholder.\u003C\u002Fp>\n","TDM Reservation Protocol. Control how bots and artificial intelligences like ChatGPT, GoogleBot and Bard access your content.",50,2140,0,"2024-08-23T13:47:00.000Z","6.6.5","5.3","",[19,20,21,22,23],"ai","copyright","data-mining","protocol","robots","https:\u002F\u002Fgithub.com\u002FImmolare\u002Ftdmrep","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftdmrep.v1.0.2.zip",85,null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":32,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":34,"avg_security_score":35,"avg_patch_time_days":36,"trust_score":37,"computed_at":38},"immolare",2,150,89,30,86,"2026-08-29T08:21:19.052Z",[40,61,84,102,123],{"slug":41,"name":42,"version":43,"author":44,"author_profile":45,"description":46,"short_description":47,"active_installs":36,"downloaded":48,"rating":13,"num_ratings":13,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":58,"download_link":59,"security_score":60,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"copyright-sh-ai-license","Copyright AI Content Licensing – Block AI Crawlers + Get Paid","1.7.0","Tyler Martin","https:\u002F\u002Fprofiles.wordpress.org\u002Fcopyrightsh\u002F","\u003Cp>\u003Cstrong>Block AI crawlers from scraping your site, or license your content and get paid. Your site, your choice.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>AI companies are crawling your WordPress site right now. ChatGPT, Claude, Gemini, Grok – they’re all here, training on your content without asking. This plugin gives you two options: either block them with robots.txt, or add machine-readable licensing terms so compliant AI companies can pay you.\u003C\u002Fp>\n\u003Cp>Here’s what makes this different: we do BOTH blocking AND licensing. Most services only do one or the other. We built the infrastructure to do both properly.\u003C\u002Fp>\n\u003Ch4>The Reality of AI Crawler Blocking\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>robots.txt is a voluntary standard\u003C\u002Fstrong> – While OpenAI and Anthropic claim to respect robots.txt, the reality is more complex. Recent investigations by TollBit and Cloudflare found evidence of major AI companies bypassing blocks, and Perplexity was caught using undisclosed IPs to scrape sites that blocked their official crawler. Industry data shows 12.9% of bots now ignore robots.txt (up from 3.3%), with 26 million bypasses in March 2025 alone.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Why blocking still matters\u003C\u002Fstrong>: Even as a voluntary measure, robots.txt raises the legal and technical barrier. It establishes clear notice of your access terms, strengthening your legal position if you need to enforce your rights. Most legitimate AI companies do respect it – but you need backup enforcement.\u003C\u002Fp>\n\u003Ch4>Coming Soon: HTTP 402 “Payment Required” Protocol\u003C\u002Fh4>\n\u003Cp>We’re implementing the HTTP 402 “Payment Required” status code protocol. When an AI bot hits your site without a valid license, we’ll serve a 402 response with your licensing terms in machine-readable format.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Transparency\u003C\u002Fstrong>: This is also a voluntary protocol. Cloudflare launched their “Pay Per Crawl” implementation on July 1, 2025, and now serves over 1 billion 402 responses daily – but it’s currently in private beta limited to select major publications. Like robots.txt, HTTP 402 requires AI companies to cooperate. The difference is it’s newer, more standardized, and creates clearer legal standing for enforcement.\u003C\u002Fp>\n\u003Ch4>The Stick AND The Carrot\u003C\u002Fh4>\n\u003Cp>This plugin already blocks AI crawlers via robots.txt (the stick). Soon we’ll add x402 protocol enforcement (bigger stick). But you can also license your content and earn money from AI companies that want to do the right thing (the carrot).\u003C\u002Fp>\n\u003Cp>Most creators don’t realize: News Corp got $250M+ from OpenAI. Reddit got $60M\u002Fyear. The EU AI Act now requires licensed training data. The licensing market exists – it’s just been locked to big publishers. Until now.\u003C\u002Fp>\n\u003Ch4>Why WordPress Creators Need This Now\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>The traffic apocalypse is real.\u003C\u002Fstrong> In 2025, 60% of Google searches end without any click to external sites – up from 44.2% just a year ago. When users do click, only 360 clicks per 1,000 searches go to the open web (374 in EU). The rest? 14.3% go to Google-owned properties like YouTube and Maps. For the first time in a decade, Google now keeps 90% of its ad revenue internally, with only 10% going to network publishers.\u003C\u002Fp>\n\u003Cp>This isn’t theoretical – it’s happening right now. ChatGPT and Gemini answer questions using your content, but users never visit your site. Your ad revenue collapses. Your subscription model breaks when AI gives your insights away for free.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>AI content licensing is the survival strategy.\u003C\u002Fstrong> The big publishers already figured this out. News Corp got over $250M from OpenAI (5-year deal). Reddit: $60M\u002Fyear. Nine major publishers have signed deals including Financial Times, Associated Press, Le Monde, and Axel Springer. Meanwhile, individual WordPress site owners – the backbone of the open web – get nothing while AI companies scrape freely.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WordPress is where we make our stand.\u003C\u002Fstrong> Dave Winer, who invented blogging 30 years ago and co-created RSS, is now championing WordPress as the foundation for the independent web’s renaissance. In his 2025 writings and WordCamp Canada keynote, he argues that WordPress represents the “read\u002Fwrite web” Tim Berners-Lee originally envisioned – where creators own their content and control their distribution. While social media captured one generation of creativity and tech giants bought up the rest, WordPress remains the last great bastion of independent publishing. It’s where 43% of the web lives. It’s where creators still own their content.\u003C\u002Fp>\n\u003Cp>That changes today.\u003C\u002Fp>\n\u003Ch4>EU AI Act Compliance\u003C\u002Fh4>\n\u003Cp>The EU AI Act now mandates that AI companies must respect opt-out mechanisms and maintain licensing documentation for training data. This plugin provides:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Enforceable crawl terms\u003C\u002Fstrong> via robots.txt and upcoming x402 protocol\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Opt-in training licenses\u003C\u002Fstrong> with clear pricing and attribution\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Compliant usage tracking\u003C\u002Fstrong> that meets EU reporting requirements\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Monetization infrastructure\u003C\u002Fstrong> so you get paid, not just compliance paperwork\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For WordPress sites serving EU audiences, this isn’t just about money – it’s about legal compliance for the AI companies that want to use your content.\u003C\u002Fp>\n\u003Ch4>The Technology Behind It\u003C\u002Fh4>\n\u003Cp>We’ve built the first true content licensing infrastructure for AI:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>License Grammar v1.5\u003C\u002Fstrong> – The emerging standard for machine-readable licensing. Our meta tag format works with ChatGPT, Claude, Gemini, Grok, and 100+ AI systems. It’s being adopted as the industry standard because it’s simple, parseable, and extensible.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Dual-axis licensing\u003C\u002Fstrong> – Control both the AI use case (training vs inference) and distribution level (private vs public). You can allow free private research while charging for commercial usage. Or block training entirely while allowing inference. Your content, your rules.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Immutable ledger\u003C\u002Fstrong> – When AI companies use your content, it’s logged with cryptographic verification. This creates legal standing if you need to enforce your terms. It’s not just “hoping they comply” – it’s building an audit trail.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Layered protection\u003C\u002Fstrong> – robots.txt provides the first barrier (voluntary but creates legal notice). Machine-readable licenses give compliant AI companies clear terms. The upcoming HTTP 402 protocol adds standardized payment signaling. Each layer strengthens your legal position.\u003C\u002Fp>\n\u003Ch4>How It Actually Works\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>1. Install the plugin\u003C\u002Fstrong> (literally 1 minute)\u003Cbr \u002F>\nSearch “Copyright.sh AI License” in your WordPress plugins, install, activate. Done.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>2. Pick your approach\u003C\u002Fstrong>\u003Cbr \u002F>\n– Want to block all AI crawlers? Set policy to “Deny” and enable the robots.txt blocker.\u003Cbr \u002F>\n– Want to get paid? Set “Allow”, pick a price (we suggest $0.10 per 1K tokens), and connect your account.\u003Cbr \u002F>\n– Want both? You can block most crawlers and whitelist specific ones you want to license to.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>3. It runs automatically\u003C\u002Fstrong>\u003Cbr \u002F>\nThe plugin adds machine-readable license declarations to every page:\u003Cbr \u002F>\n– HTML meta tags that AI systems check before crawling\u003Cbr \u002F>\n– \u002Fai-license.txt file at your domain root\u003Cbr \u002F>\n– robots.txt entries that block non-compliant crawlers (optional)\u003Cbr \u002F>\n– Coming soon: x402 HTTP responses that enforce payment requirements\u003C\u002Fp>\n\u003Cp>\u003Cstrong>4. Track what’s happening\u003C\u002Fstrong> (if you’re licensing)\u003Cbr \u002F>\nDashboard at dashboard.copyright.sh shows which AI companies are using your content and what you’ve earned. Set up PayPal, Venmo, or Stripe for payouts.\u003C\u002Fp>\n\u003Ch4>What You Get\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Blocking capabilities:\u003C\u002Fstrong>\u003Cbr \u002F>\n– robots.txt generator that blocks 100+ known AI crawlers (voluntary standard, but creates legal notice)\u003Cbr \u002F>\n– Preserves Google, Bing, and other search engines (won’t hurt your search rankings)\u003Cbr \u002F>\n– Optional – you can block all AI or just the ones that don’t pay\u003Cbr \u002F>\n– Coming soon: HTTP 402 protocol support for standardized payment signaling\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Licensing capabilities:\u003C\u002Fstrong>\u003Cbr \u002F>\n– Set prices per 1,000 tokens (industry standard pricing)\u003Cbr \u002F>\n– Different rates for private vs public usage\u003Cbr \u002F>\n– Per-post pricing overrides for premium content\u003Cbr \u002F>\n– Support for different AI use cases (training, inference, embedding, fine-tuning)\u003Cbr \u002F>\n– Works with OpenAI, Anthropic, Google, xAI, Meta, Perplexity, and 100+ other AI systems\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Technical stuff:\u003C\u002Fstrong>\u003Cbr \u002F>\n– Uses License Grammar v1.5 specification (the standard AI companies are adopting)\u003Cbr \u002F>\n– Magic link authentication – no passwords, no API keys to copy-paste\u003Cbr \u002F>\n– Clean code, minimal performance impact\u003Cbr \u002F>\n– Compatible with all major caching and SEO plugins\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Works seamlessly with:\u003C\u002Fstrong>\u003Cbr \u002F>\n– WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache\u003Cbr \u002F>\n– Yoast SEO, Rank Math, All in One SEO\u003Cbr \u002F>\n– Elementor, Divi, Beaver Builder\u003Cbr \u002F>\n– WooCommerce, Easy Digital Downloads\u003Cbr \u002F>\n– Multisite installations\u003C\u002Fp>\n\u003Ch4>Who Should Use This\u003C\u002Fh4>\n\u003Cp>Honestly? Anyone with a WordPress site that AI companies might be scraping.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Bloggers\u003C\u002Fstrong>: Your old posts are training ChatGPT right now. Either block that or get paid for it.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>News sites\u003C\u002Fstrong>: The big publishers are all licensing. You should too.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Niche experts\u003C\u002Fstrong>: Got specialized knowledge? That’s worth more to AI companies.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Anyone who wants to block AI\u003C\u002Fstrong>: You don’t have to license. You can just block all AI crawlers completely.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Why This Matters\u003C\u002Fh4>\n\u003Cp>The AI training data market is real. News Corp got $250M+. Reddit got $60M\u002Fyear. The EU AI Act now mandates licensed training data. This isn’t hypothetical – it’s happening.\u003C\u002Fp>\n\u003Cp>The difference is that until now, only massive publishers could negotiate these deals. This plugin gives individual site owners the same tools.\u003C\u002Fp>\n\u003Cp>But here’s the thing: you don’t have to license your content. If you just want to block AI companies from using your stuff, this plugin does that too. It’s your site, your content, your choice.\u003C\u002Fp>\n\u003Ch4>What Makes This Different: Competitor Comparison\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Cloudflare Pay Per Crawl\u003C\u002Fstrong>: Launched July 2025, enables website owners to charge AI crawlers per request. While technically sound, it’s limited to Cloudflare’s network infrastructure and uses a flat-rate pricing model that doesn’t account for content value variations. Major limitation: Only works if you’re already on Cloudflare’s platform and restricted to high value customers.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>TollBit\u003C\u002Fstrong>: AI content licensing platform that requires heavy configuration and subdomain setup (tollbit.example.com) and routes AI traffic through their infrastructure. Good for enterprise publishers but creates technical overhead and dependency on their network for content delivery.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Perplexity Comet Plus\u003C\u002Fstrong>: The $5\u002Fmonth subscription service that validates the whole business model of content licensing. Perplexity shares 80% of the revenue they charge Comet Plus customers with publishers based on human visits and AI interactions. Revenue-sharing model is innovative, but success depends entirely on user subscription adoption and limited to Perplexity’s ecosystem.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>RSL Protocol (Really Simple Licensing)\u003C\u002Fstrong>: Open standard for publishers to set explicit licenses and fees for AI content use. Supported by Reddit, Yahoo, and other major platforms. Technically solid but again requires learning a custom XML schema and lacks customizability on a per page basis. RSL is still in early adoption phase (i.e. not available) and requires AI companies to implement the protocol.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What we do differently\u003C\u002Fstrong>: We provide both content protection (robots.txt blocking) and monetization (licensing with payment) in a single WordPress plugin. No subdomain required, no network dependency, no platform lock-in. Works with any hosting provider you run WordPress from. Install, configure (or don’t), done.\u003C\u002Fp>\n\u003Cp>If\u002Fwhen RSL Protocol becomes widely adopted, we’ll support it too. Until then, we give you the most accessible and comprehensive AI content licensing solution available today.\u003C\u002Fp>\n\u003Ch4>AI Systems That Work With This\u003C\u002Fh4>\n\u003Cp>The plugin uses the Copyrightish AI-License Grammar v1.5, which is becoming the standard format for AI licensing:\u003C\u002Fp>\n\u003Cp>Served via MCP plugin, compatible with OpenAI (ChatGPT, GPT models), Anthropic (Claude), Google (Gemini), xAI (Grok), Meta (Llama), Perplexity, Microsoft (Copilot), DeepSeek, Alibaba (Qwen), and 100+ other AI systems.\u003C\u002Fp>\n\u003Cp>As new AI companies launch, they’re adopting the same standard. Your protection scales automatically.\u003C\u002Fp>\n","AI content licensing for WordPress. Block AI crawlers or license your content and get paid. Works with ChatGPT, Claude, Gemini, and more.",714,"2026-01-15T18:28:00.000Z","6.9.5","6.2","7.4",[54,55,56,20,57],"ai-license","chatgpt","content-licensing","robots-txt","https:\u002F\u002Fcopyright.sh\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcopyright-sh-ai-license.1.7.0.zip",100,{"slug":62,"name":63,"version":64,"author":65,"author_profile":66,"description":67,"short_description":68,"active_installs":69,"downloaded":70,"rating":71,"num_ratings":72,"last_updated":73,"tested_up_to":74,"requires_at_least":75,"requires_php":52,"tags":76,"homepage":17,"download_link":81,"security_score":82,"vuln_count":33,"unpatched_count":13,"last_vuln_date":83,"fetched_at":28},"better-robots-txt","Better Robots.txt – AI-Ready Crawl Control & Bot Governance","3.1.2","Pagup","https:\u002F\u002Fprofiles.wordpress.org\u002Fpagup\u002F","\u003Cp>Better Robots.txt replaces the default WordPress robots.txt workflow with a smarter, structured version you can configure and preview before publishing.\u003C\u002Fp>\n\u003Cp>Instead of a blank textarea, you get a guided wizard with presets, plain-language explanations, and a final Review & Save step so you can inspect the generated robots.txt before it goes live.\u003C\u002Fp>\n\u003Cp>Built for beginners and advanced users alike, Better Robots.txt helps you control how search engines, AI crawlers, SEO tools, archive bots, bad bots, social preview bots, and other automated agents interact with your site.\u003C\u002Fp>\n\u003Cp>Trusted by thousands of WordPress sites, Better Robots.txt is designed for the AI era without resorting to hype, vague promises, or hidden rules.\u003C\u002Fp>\n\u003Cp>Better Robots.txt is available in Free, Pro, and Premium editions. The free plugin covers the guided workflow and essential crawl control features, while Pro and Premium unlock additional governance, protection, and AI-ready modules. Some screenshots on the plugin page show features from all three editions.\u003C\u002Fp>\n\u003Ch3>A quick overview\u003C\u002Fh3>\n\u003Cp>\u003Ciframe loading=\"lazy\" title=\"Better robots.txt Video — AI-Ready Crawl Control for WordPress\" src=\"https:\u002F\u002Fplayer.vimeo.com\u002Fvideo\u002F1169756981?dnt=1&app_id=122963\" width=\"750\" height=\"372\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\">\u003C\u002Fiframe>\u003C\u002Fp>\n\u003Ch3>Why Better Robots.txt is different\u003C\u002Fh3>\n\u003Cp>Most robots.txt plugins fall into one of three categories:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Simple text editor\u003C\u002Fli>\n\u003Cli>Virtual robots.txt manager\u003C\u002Fli>\n\u003Cli>Single-purpose AI or policy add-on\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Better Robots.txt goes further.\u003C\u002Fp>\n\u003Cp>It gives you a complete, guided crawl control workflow so you can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Choose a preset that matches your goals\u003C\u002Fli>\n\u003Cli>Control major crawler categories without writing everything by hand\u003C\u002Fli>\n\u003Cli>Keep core WordPress protection rules visible and editable\u003C\u002Fli>\n\u003Cli>Clean up low-value crawl paths that waste crawl budget\u003C\u002Fli>\n\u003Cli>Generate a cleaner robots.txt output\u003C\u002Fli>\n\u003Cli>Preview the final result before saving\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>What you can control\u003C\u002Fh3>\n\u003Cp>Better Robots.txt helps you manage:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Search engine visibility\u003C\u002Fli>\n\u003Cli>AI and LLM crawler behavior\u003C\u002Fli>\n\u003Cli>AI usage signals such as search, ai-input, and ai-train preferences\u003C\u002Fli>\n\u003Cli>SEO tool crawlers\u003C\u002Fli>\n\u003Cli>Bad bots and abusive crawlers\u003C\u002Fli>\n\u003Cli>Archive and Wayback access\u003C\u002Fli>\n\u003Cli>Feed crawlers and crawl traps\u003C\u002Fli>\n\u003Cli>WooCommerce crawl cleanup\u003C\u002Fli>\n\u003Cli>CSS, JavaScript, and image crawling rules\u003C\u002Fli>\n\u003Cli>Social media preview crawlers\u003C\u002Fli>\n\u003Cli>ads.txt and app-ads.txt allowance\u003C\u002Fli>\n\u003Cli>llms.txt generation\u003C\u002Fli>\n\u003Cli>Advanced directives such as crawl-delay and custom rules\u003C\u002Fli>\n\u003Cli>Final review before publishing\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Editions\u003C\u002Fh3>\n\u003Cp>Better Robots.txt is available in three editions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Free – Includes the guided setup, the Essential preset, core crawl control features, and the final Review & Save workflow.\u003C\u002Fli>\n\u003Cli>Pro – Adds more advanced governance and protection modules, including additional AI, crawler, and cleanup controls.\u003C\u002Fli>\n\u003Cli>Premium – Unlocks the most restrictive and advanced protection options, including the Fortress preset and additional high-control modules.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Some options shown in the interface are marked Free, Pro, or Premium so users can immediately understand which modules belong to each edition.\u003C\u002Fp>\n\u003Ch3>AI crawler controls by edition\u003C\u002Fh3>\n\u003Cp>The Free edition lets site owners choose a basic global policy for AI search and discovery crawlers: allow or block. AI training crawlers remain separated from AI search crawlers, so a site can block training use while still allowing AI-powered search and answer discovery.\u003C\u002Fp>\n\u003Cp>The Pro and Premium editions add advanced controls, including per-bot AI crawler rules, custom user agents, AI usage signals, llms.txt, and additional machine-readable governance files.\u003C\u002Fp>\n\u003Cp>Better Robots.txt separates AI-related agents into three practical families:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>AI training crawlers, such as GPTBot, Google-Extended, and ClaudeBot.\u003C\u002Fli>\n\u003Cli>AI search and discovery crawlers, such as OAI-SearchBot, PerplexityBot, and Claude-SearchBot.\u003C\u002Fli>\n\u003Cli>User-action fetchers, such as ChatGPT-User, Perplexity-User, and Claude-User.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>User-action fetchers are triggered by user requests. Depending on the provider, robots.txt may not apply to those fetches in the same way as it applies to automated crawlers. For stronger enforcement, combine robots.txt with server logs, WAF rules, provider verification, or IP-based controls where available.\u003C\u002Fp>\n\u003Ch3>Presets\u003C\u002Fh3>\n\u003Cp>Setup starts with four modes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Essential – A clean, practical configuration for most websites that want a better robots.txt without complexity.\u003C\u002Fli>\n\u003Cli>AI-First – For publishers and content sites that want AI-ready governance without shutting down discovery.\u003C\u002Fli>\n\u003Cli>Fortress – For websites that want stronger protection against scraping, archive capture, and unnecessary crawl activity.\u003C\u002Fli>\n\u003Cli>Custom – For users who prefer to configure each module manually.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For many sites, one preset plus a quick review is enough.\u003C\u002Fp>\n\u003Ch3>Built for beginners and experts\u003C\u002Fh3>\n\u003Cp>Beginners get:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A guided setup instead of a raw robots.txt box\u003C\u002Fli>\n\u003Cli>Preset-based configuration\u003C\u002Fli>\n\u003Cli>Plain-language explanations for important choices\u003C\u002Fli>\n\u003Cli>A safer workflow with a final preview step\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Advanced users get:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Editable core WordPress protection rules\u003C\u002Fli>\n\u003Cli>Fine-grained crawler controls by category\u003C\u002Fli>\n\u003Cli>WooCommerce-oriented cleanup options\u003C\u002Fli>\n\u003Cli>Consolidated output options\u003C\u002Fli>\n\u003Cli>Advanced directives and custom rules\u003C\u002Fli>\n\u003Cli>A final output they can inspect before publishing\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>AI-ready, without hype\u003C\u002Fh3>\n\u003Cp>Better Robots.txt includes features for modern AI-related crawl governance, including:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>AI crawler handling\u003C\u002Fli>\n\u003Cli>Optional llms.txt support\u003C\u002Fli>\n\u003Cli>AI usage signals for compliant systems\u003C\u002Fli>\n\u003Cli>Optional machine-readable governance signals for advanced use cases\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>These features help you express how you want automated systems to use your content.\u003C\u002Fp>\n\u003Cp>However, Better Robots.txt does not claim to control AI by force. Like robots.txt itself, these signals are most useful with compliant systems and good-faith crawlers.\u003C\u002Fp>\n\u003Ch3>What Better Robots.txt is\u003C\u002Fh3>\n\u003Cp>Better Robots.txt is:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A robots.txt governance plugin for WordPress\u003C\u002Fli>\n\u003Cli>A guided configuration workflow instead of a raw text editor\u003C\u002Fli>\n\u003Cli>A crawl control layer to reduce wasteful crawling\u003C\u002Fli>\n\u003Cli>A practical bridge between SEO, crawl hygiene, and AI-era policy signaling\u003C\u002Fli>\n\u003Cli>A way to keep your crawl policy clearer for humans and machines\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Technical reference for advanced users: Better Robots.txt also maintains a public \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FGautierDorval\u002Fbetter-robots-txt\" rel=\"nofollow noopener noreferrer ugc\">GitHub repository\u003C\u002Fa> with product definition, governance notes, and machine-readable artefacts.\u003C\u002Fp>\n\u003Ch3>What Better Robots.txt is not\u003C\u002Fh3>\n\u003Cp>Better Robots.txt is not:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A firewall or Web Application Firewall (WAF)\u003C\u002Fli>\n\u003Cli>An anti-scraping enforcement engine\u003C\u002Fli>\n\u003Cli>A legal compliance engine\u003C\u002Fli>\n\u003Cli>A guarantee that every bot will obey your rules\u003C\u002Fli>\n\u003Cli>A replacement for server-level security or access control\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>It helps you publish a clearer crawl policy.\u003C\u002Fp>\n\u003Cp>It does not replace infrastructure-level protection.\u003C\u002Fp>\n\u003Ch3>Typical use cases\u003C\u002Fh3>\n\u003Cp>Use Better Robots.txt if you want to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Clean up a weak or noisy default robots.txt\u003C\u002Fli>\n\u003Cli>Reduce crawl waste on WordPress or WooCommerce\u003C\u002Fli>\n\u003Cli>Keep major search engines allowed while restricting other bots\u003C\u002Fli>\n\u003Cli>Control whether archive bots can snapshot your site\u003C\u002Fli>\n\u003Cli>Publish AI usage preferences more clearly\u003C\u002Fli>\n\u003Cli>Keep social preview bots allowed while limiting scrapers\u003C\u002Fli>\n\u003Cli>Review the final file before making it live\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Key Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Guided step-by-step wizard\u003C\u002Fli>\n\u003Cli>Preset-based setup: Essential, AI-First, Fortress, Custom\u003C\u002Fli>\n\u003Cli>Search engine visibility controls\u003C\u002Fli>\n\u003Cli>AI and LLM crawler governance\u003C\u002Fli>\n\u003Cli>AI usage signals support\u003C\u002Fli>\n\u003Cli>SEO tool crawler controls\u003C\u002Fli>\n\u003Cli>Bad bot and abusive crawler options\u003C\u002Fli>\n\u003Cli>Archive and Wayback access controls\u003C\u002Fli>\n\u003Cli>Spam, feed, and crawl trap cleanup\u003C\u002Fli>\n\u003Cli>WooCommerce crawl cleanup options\u003C\u002Fli>\n\u003Cli>CSS, JavaScript, and image crawling rules\u003C\u002Fli>\n\u003Cli>Social media preview crawler controls\u003C\u002Fli>\n\u003Cli>ads.txt and app-ads.txt allowance\u003C\u002Fli>\n\u003Cli>Optional llms.txt generation\u003C\u002Fli>\n\u003Cli>Consolidated output option\u003C\u002Fli>\n\u003Cli>Core WordPress protection rules remain visible and editable\u003C\u002Fli>\n\u003Cli>Final Review & Save preview screen\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>About the publisher\u003C\u002Fh4>\n\u003Cp>Better Robots.txt is developed and maintained by \u003Ca href=\"https:\u002F\u002Fpagup.com\u002F\" rel=\"nofollow ugc\">Pagup\u003C\u002Fa>, a digital readability firm based in Quebec, Canada. Pagup helps organizations become correctly understood by search engines, generative AI systems, and autonomous agents.\u003C\u002Fp>\n\u003Cp>The robots.txt file is the first surface that AI crawlers read when they discover a site. A well-structured robots.txt that references governance files such as llms.txt, ai-manifest.json, and interpretation policies helps AI systems understand your site faster and more accurately.\u003C\u002Fp>\n\u003Cp>Better Robots.txt is one component of a broader digital readability practice that includes \u003Ca href=\"https:\u002F\u002Fpagup.com\u002Fen\u002Fservices\u002Fsemantic-content-architecture\u002F\" rel=\"nofollow ugc\">semantic content architecture\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fpagup.com\u002Fen\u002Fservices\u002Fai-governance-and-machine-readability\u002F\" rel=\"nofollow ugc\">AI governance and machine readability\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Fpagup.com\u002Fen\u002Fglossary\u002Finterpretive-seo\u002F\" rel=\"nofollow ugc\">interpretive SEO\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Part of the Pagup ecosystem\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fpagup.com\u002F\" rel=\"nofollow ugc\">pagup.com\u003C\u002Fa> — Digital readability firm. Diagnostic, semantic architecture, AI governance.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgautierdorval.com\u002F\" rel=\"nofollow ugc\">gautierdorval.com\u003C\u002Fa> — Doctrine, canonical definitions, interpretive governance research.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Finterpretive-governance.org\u002F\" rel=\"nofollow ugc\">interpretive-governance.org\u003C\u002Fa> — Formal versioned standard for interpretive governance.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbetter-robots.com\u002F\" rel=\"nofollow ugc\">better-robots.com\u003C\u002Fa> — Documentation and resources for Better Robots.txt.\u003C\u002Fli>\n\u003C\u002Ful>\n","Replace the default WordPress robots.txt workflow with a smarter, structured version you can preview before publishing, with Free, Pro, and Premium ed …",5000,321566,90,102,"2026-07-04T14:07:00.000Z","7.0.2","5.0",[77,78,79,57,80],"ai-crawlers","bot-blocker","llms-txt","seo","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbetter-robots-txt.3.1.2.zip",99,"2023-02-14 00:00:00",{"slug":85,"name":86,"version":87,"author":88,"author_profile":89,"description":90,"short_description":91,"active_installs":92,"downloaded":93,"rating":94,"num_ratings":95,"last_updated":96,"tested_up_to":74,"requires_at_least":97,"requires_php":98,"tags":99,"homepage":17,"download_link":101,"security_score":60,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"block-ai-crawlers","Block AI Crawlers","1.5.8","lastsplash (a11n)","https:\u002F\u002Fprofiles.wordpress.org\u002Flastsplash\u002F","\u003Cp>Protect Your Content from AI Scraping\u003C\u002Fp>\n\u003Cp>This plugin helps you prevent AI crawlers from using your content as training data for their products. By updating your site’s \u003Ccode>robots.txt\u003C\u002Fcode>, it blocks common AI crawlers and scrapers, aiming to protect your content from being used in the training of Large Language Models (LLMs).\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Ch3>Blocks AI Crawlers\u003C\u002Fh3>\n\u003Cp>Includes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>OpenAI\u003C\u002Fstrong> – Blocks crawlers used for ChatGPT\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Google\u003C\u002Fstrong> – Blocks crawlers used by Google’s Gemini AI products\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Meta\u003C\u002Fstrong> – Blocks FacebookBot and Meta training crawlers\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Anthropic\u003C\u002Fstrong> – Blocks crawlers used by Claude\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Perplexity\u003C\u002Fstrong> – Blocks crawlers used by Perplexity\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Apple\u003C\u002Fstrong> – Blocks Applebot-Extended\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Amazon\u003C\u002Fstrong> – Blocks Amazonbot\u003C\u002Fli>\n\u003Cli>…and 150+ more via ai.robots.txt\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The blocked crawler list is generated at build time from \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fai-robots-txt\u002Fai.robots.txt\" rel=\"nofollow ugc\">ai.robots.txt\u003C\u002Fa> (\u003Ccode>robots.json\u003C\u002Fcode>, MIT). See the plugin’s \u003Ccode>THIRD-PARTY.md\u003C\u002Fcode> for license attribution.\u003C\u002Fp>\n\u003Ch3>Experimental Meta Tags\u003C\u002Fh3>\n\u003Cp>The plugin adds the “noai, noimageai” directive to your site’s meta tags, instructing AI bots not to use your content in their datasets. Please note that these tags are experimental and have not been standardized.\u003C\u002Fp>\n\u003Ch3>Custom robots.txt Rules\u003C\u002Fh3>\n\u003Cp>Have custom entries for your robots.txt file? You can now add them directly through the plugin!\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>After activation, the plugin will automatically update your \u003Ccode>robots.txt\u003C\u002Fcode> and add the necessary meta tags. No further configuration is required, but you can check the settings page for a full list of blocked crawlers.\u003C\u002Fp>\n\u003Ch3>Limitations\u003C\u002Fh3>\n\u003Cp>While this plugin aims to block specified crawlers, it cannot guarantee complete protection against all forms of scraping, as some bots may disregard \u003Ccode>robots.txt\u003C\u002Fcode> directives.\u003C\u002Fp>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>For questions or support, \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fblock-ai-crawlers\u002F\" rel=\"ugc\">please post on the forums\u003C\u002Fa>.\u003C\u002Fp>\n","Tell AI (Artificial Intelligence) companies not to scrape your site for their AI products.",1000,17841,92,7,"2026-07-18T12:43:00.000Z","6.9","8.2",[19,55,100,57],"crawlers","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fblock-ai-crawlers.1.5.8.zip",{"slug":103,"name":104,"version":105,"author":106,"author_profile":107,"description":108,"short_description":109,"active_installs":92,"downloaded":110,"rating":111,"num_ratings":112,"last_updated":113,"tested_up_to":114,"requires_at_least":115,"requires_php":17,"tags":116,"homepage":17,"download_link":120,"security_score":121,"vuln_count":33,"unpatched_count":33,"last_vuln_date":122,"fetched_at":28},"wp-gmail-smtp","WP Gmail SMTP","1.0.7","inkthemes","https:\u002F\u002Fprofiles.wordpress.org\u002Finkthemes\u002F","\u003Cp>With WP Gmail SMTP plugin you can connect Gmail to your WordPress website for sending emails. It bypasses the normal WP mail function and sends email using Gmail service.\u003C\u002Fp>\n\u003Cp>Simply Add Username and Password and start delivering emails through Gmail.\u003C\u002Fp>\n\u003Cp>You can also change the From Email address and From Name.\u003C\u002Fp>\n\u003Ch3>Below are the list of settings that you have to add to start using the plugin:\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Hostname: Hostname field will be automatically pre-filled.\u003C\u002Fli>\n\u003Cli>Username: Add SMTP username that’s been provided by Gmail for sending emails.\u003C\u002Fli>\n\u003Cli>Password: Add SMTP password to connect with Gmail.\u003C\u002Fli>\n\u003Cli>Protocol: Protocol field will be automatically pre-filled.\u003C\u002Fli>\n\u003Cli>If you need more help, Refer the “Changes in Gmail settings” heading in this article: \u003Ca href=\"https:\u002F\u002Fwww.formget.com\u002Fconnect-gmail-smtp-with-mailget\u002F\" rel=\"nofollow ugc\">Gmail SMTP\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>But there is a limitation of sending 500 bulk emails via Gmail. So if you want to send bulk emails then you have to purchase SMTP services.\u003C\u002Fp>\n\u003Cp>Here are Few SMTP service providers that you can choose.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.pabbly.com\u002Fsmtp-service-providers\u002F\" rel=\"nofollow ugc\">Top SMTP Service Providers\u003C\u002Fa>\u003Cbr \u002F>\n\u003Ca href=\"https:\u002F\u002Fwww.formget.com\u002Fsmtp-service-providers\u002F\" rel=\"nofollow ugc\">Best SMTP Service Provider\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>You can also try sending a test email with the plugin to check whether all your configurations are working correctly.\u003C\u002Fp>\n\u003Cp>If you want to do hassel free email marketing then you can also try bulk email marketing service that is reliable and cost effective.\u003C\u002Fp>\n\u003Cp>Unlimited Emails $4 for 5000 emails\u003Cbr \u002F>\n\u003Ca href=\"https:\u002F\u002Fwww.inkthemes.com\u002Fcheap-email-marketing-services\u002F\" rel=\"nofollow ugc\">Cheap Email Marketing services\u003C\u002Fa>\u003Cbr \u002F>\n\u003Ca href=\"https:\u002F\u002Fwww.formget.com\u002Fcheap-email-marketing-services\u002F\" rel=\"nofollow ugc\">Cheapest Email Marketing Service\u003C\u002Fa>\u003Cbr \u002F>\n\u003Ca href=\"https:\u002F\u002Fwww.pabbly.com\u002Femail-marketing-services\u002F\" rel=\"nofollow ugc\">Email Marketing Services\u003C\u002Fa>\u003C\u002Fp>\n","With WP Gmail SMTP plugin you can connect Gmail to your WordPress website for sending emails. It bypasses the normal WP mail function and sends email  …",48938,64,5,"2018-08-21T12:52:00.000Z","4.9.29","3.0.1",[117,118,119,103],"gmail-protocol","gmail-smtp","smtp","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-gmail-smtp.1.0.7.zip",42,"2025-12-31 00:00:00",{"slug":124,"name":125,"version":126,"author":127,"author_profile":128,"description":129,"short_description":130,"active_installs":131,"downloaded":132,"rating":133,"num_ratings":134,"last_updated":135,"tested_up_to":50,"requires_at_least":136,"requires_php":52,"tags":137,"homepage":142,"download_link":143,"security_score":60,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"cryptex","Cryptex | E-Mail Address Protection","7.2.0","Andi Dittrich","https:\u002F\u002Fprofiles.wordpress.org\u002Fandi-dittrich\u002F","\u003Cp>\u003Cstrong>NOTE: this plugin is targeted to advanced users and professionals – it requires some configuration tasks and won’t work out-of-the-box!\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The plugin is used to display Email addresses \u003Cstrong>as an image\u003C\u002Fstrong> – automatically.\u003Cbr \u002F>\nThis will stop harvesters and crawlers from gathering sensitive data from your website.\u003Cbr \u002F>\nIt works with emails, telephone numbers, postal addresses or any other text-content.\u003Cbr \u002F>\nJust wrap your E-Mail-Address into a shortcode like \u003Ccode>[email]youraddress@example.com[\u002Femail]\u003C\u002Fcode> – that’s it.\u003Cbr \u002F>\nOr use the \u003Cstrong>Autodetect\u003C\u002Fstrong> filter to transform every E-Mail-Address on your page automatically into an image!\u003C\u002Fp>\n\u003Ch3>Plugin Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Protects \u003Cstrong>Email Adresses\u003C\u002Fstrong>, \u003Cstrong>Telephone Numbers\u003C\u002Fstrong> or any other content\u003C\u002Fli>\n\u003Cli>Fully customizable appearance: you can configure font-family, font-size and font-color – everything looks like your theme style\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Retina\u002FHD\u002FHigh-Dpi Images\u003C\u002Fstrong> – best appearance on all devices (2x, 3x or 4x resolution enhancement)\u003C\u002Fli>\n\u003Cli>Shortcode and\u002For Autodetection usage!\u003C\u002Fli>\n\u003Cli>Build-In \u003Cstrong>E-Mail-Address-Autodetection\u003C\u002Fstrong> – all addresses on your page are protected automatically (if you want it – you can also just use shortcodes!)\u003C\u002Fli>\n\u003Cli>Autodetection filters configurable for \u003Cstrong>the_content\u003C\u002Fstrong>, \u003Cstrong>the_excerpt\u003C\u002Fstrong>, \u003Cstrong>comments\u003C\u002Fstrong>, \u003Cstrong>comments_excerpt\u003C\u002Fstrong>, \u003Cstrong>text-widget\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Reversible Address-Autodetection Process – your content is modified as long as the plugin is activated\u003C\u002Fli>\n\u003Cli>Postal-addresses, telephone-numbers, names and other sensitive information`s can be protected too\u003C\u002Fli>\n\u003Cli>Protects E-Mail hyperlinks (mailto) by using javascript based \u003Cstrong>key-shifting encryption\u002Fdecryption\u003C\u002Fstrong> with dynamic keys – but you can use images only\u003C\u002Fli>\n\u003Cli>Suitable for high traffic sites – automated caching of dynamic generated images and CSS\u003C\u002Fli>\n\u003Cli>Automatic font-search (standard system font-paths)\u003C\u002Fli>\n\u003Cli>Supports the new modern UI style of WordPress 3.8\u003C\u002Fli>\n\u003Cli>Native support for \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fenlighter\u002F\" rel=\"ugc\">Enlighter Syntax Highlighter\u003C\u002Fa> to display E-Mail Addresses within highlighted content (requires Enlighter v2.7)\u003C\u002Fli>\n\u003Cli>Includes the \u003Ca href=\"https:\u002F\u002Ffedorahosted.org\u002Fliberation-fonts\u002F\" rel=\"nofollow ugc\">Liberation(tm) Fonts\u003C\u002Fa> package\u003C\u002Fli>\n\u003Cli>TrueType as well as OpenType Fonts are supported\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Text-Transformations\u003C\u002Fh3>\n\u003Cp>The @-sign as well as dot’s within the e-mail-addresses can be automatically replaced by different placeholders, e.g. \u003Ccode>mail(at)example{dot}org\u003C\u002Fcode>, to match your website’s corporate design.\u003C\u002Fp>\n\u003Ch3>Security Modes\u003C\u002Fh3>\n\u003Cp>Cryptex provides various obfuscation modes for E-Mail-Addresses:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Plain Text – only text-transformations are applied – no use of images\u003C\u002Fli>\n\u003Cli>Single Image – the e-mail-address is expressed as a single image \u003C\u002Fli>\n\u003Cli>Multipart Image – the e-mail-address is splitted into two images, seperated by the @-sign in plain text\u003C\u002Fli>\n\u003Cli>Advanced Multipart Image – the craziest one: each part (divided by dot’s and @ sign) is displayed as a seperate image, the dividers as plain text\u003C\u002Fli>\n\u003C\u002Ful>\n","Cryptex transforms plain-text E-Mail-Addresses into Images - automatically - No scrapers. No harvesters. No spambots. That's our goal!",900,20956,80,4,"2026-04-12T15:19:00.000Z","6.4",[138,139,140,141,23],"e-mail","email","grabbing","privacy","https:\u002F\u002Fcodeberg.org\u002FAenonDynamics\u002Fwp-cryptex","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcryptex.7.2.0.zip",{"attackSurface":145,"codeSignals":194,"taintFlows":229,"riskAssessment":266,"analyzedAt":275},{"hooks":146,"ajaxHandlers":183,"restRoutes":191,"shortcodes":192,"cronEvents":193,"entryPointCount":33,"unprotectedCount":33},[147,153,156,158,161,164,167,170,172,175,178],{"type":148,"name":149,"callback":150,"file":151,"line":152},"action","plugins_loaded","anonymous","includes\\class-tdmrep.php",195,{"type":148,"name":154,"callback":150,"file":151,"line":155},"admin_enqueue_scripts",210,{"type":148,"name":154,"callback":150,"file":151,"line":157},211,{"type":148,"name":159,"callback":150,"file":151,"line":160},"admin_menu",213,{"type":148,"name":162,"callback":150,"file":151,"line":163},"admin_post_tdmrep_save_policy",214,{"type":148,"name":165,"callback":150,"file":151,"line":166},"admin_post_tdmrep_delete_policy",216,{"type":148,"name":168,"callback":150,"file":151,"line":169},"admin_post_nopriv_tdmrep_delete_policy",217,{"type":148,"name":165,"callback":150,"file":151,"line":171},222,{"type":148,"name":173,"callback":150,"file":151,"line":174},"rest_api_init",224,{"type":148,"name":176,"callback":150,"file":151,"line":177},"admin_post_tdmrep_save_protocol",226,{"type":148,"name":179,"callback":180,"file":181,"line":182},"wp_head","add_meta_tags_rules","public\\class-tdmrep-public.php",76,[184,188],{"action":185,"nopriv":186,"callback":150,"hasNonce":186,"hasCapCheck":186,"file":151,"line":187},"get_policy_form",false,219,{"action":185,"nopriv":189,"callback":150,"hasNonce":186,"hasCapCheck":186,"file":151,"line":190},true,220,[],[],[],{"dangerousFunctions":195,"sqlUsage":196,"outputEscaping":198,"fileOperations":13,"externalRequests":13,"nonceChecks":112,"capabilityChecks":33,"bundledLibraries":228},[],{"prepared":13,"raw":13,"locations":197},[],{"escaped":199,"rawEcho":200,"locations":201},68,13,[202,206,208,210,212,214,216,217,219,221,223,225,226],{"file":203,"line":204,"context":205},"admin\\partials\\tdmrep-admin-display.php",21,"raw output",{"file":203,"line":207,"context":205},22,{"file":203,"line":209,"context":205},27,{"file":203,"line":211,"context":205},51,{"file":203,"line":213,"context":205},54,{"file":215,"line":112,"context":205},"admin\\partials\\tdmrep-admin-policy-table-display.php",{"file":215,"line":200,"context":205},{"file":215,"line":218,"context":205},14,{"file":215,"line":220,"context":205},15,{"file":215,"line":222,"context":205},16,{"file":215,"line":224,"context":205},43,{"file":215,"line":11,"context":205},{"file":215,"line":227,"context":205},56,[],[230,256],{"entryPoint":231,"graph":232,"unsanitizedCount":254,"severity":255},"save_protocol (admin\\class-tdmrep-admin.php:376)",{"nodes":233,"edges":251},[234,240,244],{"id":235,"type":236,"label":237,"file":238,"line":239},"n0","source","$_POST","admin\\class-tdmrep-admin.php",386,{"id":241,"type":242,"label":243,"file":238,"line":239},"n1","transform","→ save_protocol()",{"id":245,"type":246,"label":247,"file":248,"line":249,"wp_function":250},"n2","sink","update_option() [Settings Manipulation]","includes\\class-tdmrep-protocol-data.php",20,"update_option",[252,253],{"from":235,"to":241,"sanitized":186},{"from":241,"to":245,"sanitized":186},1,"low",{"entryPoint":257,"graph":258,"unsanitizedCount":254,"severity":255},"\u003Cclass-tdmrep-admin> (admin\\class-tdmrep-admin.php:0)",{"nodes":259,"edges":263},[260,261,262],{"id":235,"type":236,"label":237,"file":238,"line":239},{"id":241,"type":242,"label":243,"file":238,"line":239},{"id":245,"type":246,"label":247,"file":248,"line":249,"wp_function":250},[264,265],{"from":235,"to":241,"sanitized":186},{"from":241,"to":245,"sanitized":186},{"summary":267,"deductions":268},"The \"tdmrep\" plugin v1.0.2 exhibits a mixed security posture. On the positive side, it demonstrates good practices by utilizing prepared statements for all SQL queries and performing output escaping on a high percentage of its outputs. The absence of dangerous functions, file operations, and external HTTP requests is also commendable. Furthermore, the plugin has no recorded vulnerability history (CVEs), suggesting a generally well-maintained codebase. However, a significant concern arises from the presence of two AJAX handlers that lack authentication checks. This creates direct entry points into the plugin's functionality that could be exploited by unauthenticated users. While taint analysis did not reveal critical or high severity vulnerabilities, the identified flows with unsanitized paths, though not rated critical, warrant attention as they could potentially lead to issues if not handled properly.\n\nDespite the lack of historical vulnerabilities and the sound use of prepared statements and output escaping, the unprotected AJAX handlers represent a clear and present risk. These entry points could be leveraged for various attacks, depending on the functionality they expose. The vulnerability history, or lack thereof, is a positive indicator, but it does not negate the risks presented by the current code analysis. The plugin has strengths in its secure handling of database queries and output, but its security is significantly undermined by the unprotected AJAX endpoints. A balanced conclusion would highlight the developer's efforts in secure coding practices in some areas, but strongly emphasize the critical need to address the authentication gaps in the AJAX handlers to mitigate potential exploits.",[269,272],{"reason":270,"points":271},"AJAX handlers without auth checks",10,{"reason":273,"points":274},"Flows with unsanitized paths (non-critical)",3,"2026-03-16T22:02:50.656Z",{"wat":277,"direct":286},{"assetPaths":278,"generatorPatterns":281,"scriptPaths":282,"versionParams":283},[279,280],"\u002Fwp-content\u002Fplugins\u002Ftdmrep\u002Fadmin\u002Fcss\u002Ftdmrep-admin.css","\u002Fwp-content\u002Fplugins\u002Ftdmrep\u002Fadmin\u002Fjs\u002Ftdmrep-policy-form.js",[],[280],[284,285],"tdmrep-admin.css?ver=","tdmrep-policy-form.js?ver=",{"cssClasses":287,"htmlComments":288,"htmlAttributes":289,"restEndpoints":293,"jsGlobals":296,"shortcodeOutput":298},[],[],[290,291,292],"data-tdmrep-nonce","data-tdmrep-ajax-url","data-tdmrep-wp-path",[294,295],"\u002Fwp-json\u002Ftdmrep\u002Fv1\u002Fpolicies","\u002Fwp-json\u002Ftdmrep\u002Fv1\u002Fpolicies\u002F(?P\u003Cuid>[a-f0-9\\-]+)",[297],"tdmrep_object",[],{"error":189,"url":300,"statusCode":301,"statusMessage":302,"message":302},"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Ftdmrep\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":274,"versions":304},[305,311,318],{"version":306,"download_url":25,"svn_tag_url":307,"released_at":27,"has_diff":186,"diff_files_changed":308,"diff_lines":27,"trac_diff_url":309,"vulnerabilities":310,"is_current":186},"v1.0.2","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ftdmrep\u002Ftags\u002Fv1.0.2\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ftdmrep%2Ftags%2Fv1.0.1&new_path=%2Ftdmrep%2Ftags%2Fv1.0.2",[],{"version":312,"download_url":313,"svn_tag_url":314,"released_at":27,"has_diff":186,"diff_files_changed":315,"diff_lines":27,"trac_diff_url":316,"vulnerabilities":317,"is_current":186},"v1.0.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftdmrep.v1.0.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ftdmrep\u002Ftags\u002Fv1.0.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ftdmrep%2Ftags%2Fv1.0.0&new_path=%2Ftdmrep%2Ftags%2Fv1.0.1",[],{"version":319,"download_url":320,"svn_tag_url":321,"released_at":27,"has_diff":186,"diff_files_changed":322,"diff_lines":27,"trac_diff_url":27,"vulnerabilities":323,"is_current":186},"v1.0.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftdmrep.v1.0.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ftdmrep\u002Ftags\u002Fv1.0.0\u002F",[],[]]