by
ddoubs22
1 (0 reviews)
Inklatch - Email Gated Content
Server-side content gating behind email capture. Locked content never appears in your page source — not hidden with CSS, actually absent.
Inklatch ranks #68,796 among WordPress.org plugins with 1+ active installations, a 1/5 rating from 0 reviews, and was last updated Sep 13, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v0.15.1
Current Version v0.15.1
Updated 1 week ago
Last Update on 13 Sep, 2026
Refreshed 13 hours ago
Last Refreshed on
Downloads -66.1% this week
Actively maintained
Rank
#68,796
—
No change
Active Installs
1+
—
No change
KW Avg Position
73
0.7 better
Downloads
74
+4 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
62,794
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 9 more installs to reach 10+
Rank Changes
Current
#68,796
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
- 0.15.1
- Last Updated
- Sep 13, 2026
- Requires WP
- 6.2+
- Tested Up To
- 7.1
- PHP Version
- 7.4 or higher
- Author
- ddoubs22
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 Now
Frequently Asked Questions
Common questions about Inklatch - Email Gated Content
Yes. It is stripped before the page is served. View-source shows a placeholder, nothing more.
Yes, and you should leave caching on. Every visitor receives identical HTML, so your pages cache normally. The unlock decision happens in a separate request that is sent with standard no-store and Vary: Cookie headers, which virtually every cache respects without any configuration. If you run a CDN or a setup configured to cache everything regardless of those headers, use the caching self-check under Settings -> General to confirm in one click, and exclude /wp-json/inklatch/v1/ if needed.
By default search engines see the same placeholder every visitor sees, so a gated post has little indexable text. Turn on SEO mode (Settings -> General) and each gate publishes a short public excerpt, while the page declares the gated remainder with schema.org markup (isAccessibleForFree: false). Crawlers and readers see exactly the same words, which is what separates this from cloaking.
Only the excerpt, and only when you switch it on. It is off by default. The excerpt is taken from the opening words of the gated content, so set an excerpt="..." attribute on a gate (or fill in the Public excerpt field on the block) to publish different text instead. Gates marked require_verified are never excerpted automatically.
Yes. Settings -> Appearance holds the markup for both locked states, and you write the HTML. Tokens like {{email_input}} and {{submit_button}} become real, working elements wherever you place them — everything around them is yours, including wrappers and classes, so a modal triggered from your own button is just a different template. If a template is missing something readers need, the built-in markup is used instead.
Not natively yet, but the webhook under Settings -> General reaches them through Zapier, Make, n8n, or any automation tool that accepts a JSON POST. It fires when a reader submits an address, when they verify one, or both — verified is the safer feed for a mailing list, and is the default.
Your mail provider knows an address does not exist, but WordPress never hears about it — so a dead address sits in your list and every resend fails silently. Enable bounce handling under Settings -> General, paste the URL into your provider's bounce webhook, and those addresses are marked and skipped. Only hard bounces count; a full mailbox is ignored.
Yes. Settings -> General has a blocked domain list — put one domain per line and addresses there are refused, along with any subdomain. It ships empty, because blocking a domain your readers legitimately use is worse than the occasional junk signup. Add domains as you see them.
No. The Analytics tab counts how often each gate was shown and unlocked, as daily totals per gate. There is no per-visitor record, no identifier, and nothing leaves your site. You can switch it off entirely under Settings -> General.
Yes. Both the welcome and verification emails are HTML templates you can edit under Settings -> Emails, with merge tags for {{magic_link}}, {{site_name}} and {{email}}. Use inline styles — email clients ignore stylesheets. A plain-text version is generated from your HTML automatically and sent alongside it, so readers on text-only clients still get a working link.