by
mbskydis
1 (0 reviews)
TrafficPaywall
AI companies crawl your content. TrafficPaywall lets them pay for access instead of taking it for free.
TrafficPaywall ranks #62,065 among WordPress.org plugins with 1+ active installations, is #769 of 1,123 in the Advertising category, a 1/5 rating from 0 reviews, and was last updated Oct 6, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v1.0.2
Current Version v1.0.2
Updated 1 month ago
Last Update on 06 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
#769 of 1,123 in Advertising
Rank
#62,065
—
No change
Active Installs
1+
-50%
KW Avg Position
168.5
1 worse
Downloads
417
+1 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
49,128
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 8 more installs to reach 10+
Rank Changes
Current
#62,065
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.2
- Last Updated
- Oct 06, 2026
- Requires WP
- 6.2+
- Tested Up To
- 7.1
- PHP Version
- 7.4 or higher
- Author
- mbskydis
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
Site Kit by Google – Analytics, Search Console, AdSense, Speed
5M+ installs
#7
Google for WooCommerce
800K+ installs
#74
Popup Maker - Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popup Builder
600K+ installs
#91
Header Footer Code Manager
600K+ installs
#105
Meta for WooCommerce
400K+ installs
#138
Ad Inserter – Ad Manager & AdSense Ads
300K+ installs
#198
Pinterest for WooCommerce
200K+ installs
#208
Head, Footer and Post Injections
200K+ installs
#211
Frequently Asked Questions
Common questions about TrafficPaywall
No. Search engine crawlers (Googlebot, Bingbot, Applebot, DuckDuckBot and others) and ad crawlers (AdSense, Google Ads landing-page checks) always pass for free. Googlebot is verified by Google's published network ranges, so fake "Googlebots" are charged instead. robots.txt and sitemaps are never blocked.
No. People read exactly as before. Traffic from cloud and datacenter networks with a normal browser is only counted as a "possible bot", not stopped, unless you choose to charge it in your dashboard.
It depends on how much AI crawler traffic your site gets and your price. The TrafficPaywall screen shows how many AI requests your site gets and how many were stopped because the crawler did not pay. You can also switch to Monitor mode in your dashboard to count without stopping anything.
Your share (75% of what crawlers pay) accumulates in your TrafficPaywall balance and is paid out to your bank through Stripe. Set up payouts in your dashboard.
A crawler sends Authorization: Bearer <TrafficPaywall key> with its request. The plugin confirms the charge with TrafficPaywall and serves the page with an x-tp-charged header. A crawler is charged at most once per page per day. Crawlers without credits get a 402 response that explains how to buy them.
No. Requests are classified on your server in well under a millisecond, with no call to TrafficPaywall. Counters are written after the page is sent. Only paid crawler requests wait for TrafficPaywall to confirm the payment.
Your site keeps working. Unpaid AI crawlers are still stopped from the rules stored on your site, and paid requests are let through when payment cannot be confirmed.
Yes, with one step. A page cache that serves stored pages before WordPress loads also serves them to crawlers. The site check detects this and shows how to exclude AI crawlers from the cache; for WP Super Cache and W3 Total Cache it enables PHP page caching with Late Init so TrafficPaywall runs first. Cached reader pages are still served after WordPress starts. For WP Rocket it adds named-client exclusions; requests with a missing or changed User-Agent can bypass those exclusions. For complete enforcement, bypass page caching on protected pages or use Edge Protection. Host and CDN caches must bypass protected HTML and REST responses, including pages warmed by ordinary readers, or use Edge Protection. Protected reader responses also send no-store and X-Accel-Expires: 0 to prevent an origin microcache from warming content for unpaid crawlers. The managed InstaWP/BunnyCDN pilot required a site-wide CDN cache exclusion and purge; a cold site check alone did not prove that every CDN location or article was safe. Test an article as an unpaid crawler after warming it as a reader.
Yes, with the trafficpaywall_skip_request filter, for example to keep RSS feeds free: add_filter( 'trafficpaywall_skip_request', function ( $skip, $req ) { return $skip || false !== strpos( $req->path, '/feed' ); }, 10, 2 );
The License: line is added to the robots.txt that WordPress generates. If you have a physical robots.txt file, add the line yourself; the address is in your TrafficPaywall dashboard.
