Still deleting spam comments and form submissions by hand? You’re wasting time.
I’ve burned too many hours cleaning spam out of comments and contact forms. It’s pure busywork. With SiteSqueeze launching, I need real registrations and inquiries—not bot noise. So I bought WP Captcha PRO on AppSumo.
I flipped on Cloudflare Turnstile, protected every supported form, and the spam stopped. No more manual cleanup.
Protect all of your forms, all of the time. That’s the goal. WP Captcha gets you most of the way there on standard WordPress forms. Custom setups take extra work.
WP Captcha Overall Score
Why 4.4/5? Universal Form Captcha needed real troubleshooting, and turning on AI monitoring on Tier 1 cut me down to one website.
Affiliate disclosure: If you purchase through my link, I may earn a small commission at no additional cost to you. I only share tools I have used myself.
The 30-Second Decision
Buy it if: You run WordPress, hate spam, and want one plugin that covers logins, comments, forms, and extra security—without another monthly bill.
Skip it if: Your site lives on custom forms and you need zero-config protection. Test yours first.
For most site owners, $49 lifetime is cheap insurance against endless spam cleanup.
What WP Captcha Does
WP Captcha PRO (WebFactory Ltd) packs CAPTCHA plus real security tools:
Enough to replace a few single-purpose plugins—if you need the extras.
What I Liked
1. Six CAPTCHA Methods in One Plugin
Pick one method and apply it across every form you’ve enabled. No juggling separate plugins. Built-in and Icon need no API keys. The rest (Google, hCaptcha, Turnstile) give you stronger options. I went with Turnstile.
2. Cloudflare Turnstile Protects Without Getting in the Way
Legitimate visitors barely notice it. No endless image puzzles. It just works. Since I turned it on, the spam that started this whole search has disappeared. That’s the win.
3. Activity Reporting Makes Protection Visible
Failed CAPTCHAs, logins, and locks—all visible, with trends by country, browser, device, and traffic type. You see patterns instead of guessing. Transparency matters.
4. Security Features Beyond CAPTCHA
Login protection, firewall rules, country blocks, temporary access. The interface keeps everything organized. You can consolidate security without drowning in plugins—just don’t blindly stack overlapping tools.
5. AI Security Audit Adds Another Layer of Insight
It promises pattern analysis and recommendations instead of raw logs. I’ve enabled it on MarketingWithDave.com and am waiting for enough data. If the reports deliver actionable insight, this becomes a real differentiator.
1. Universal Form Captcha Requires More Technical Setup
Standard forms? Fine. Custom forms (like my SiteSqueeze registration via admin-post.php)? You hand-enter HTML field names with zero confirmation it matched anything.
Support confirmed it worked on my normal forms but never appeared on the custom one. We never pinned down the exact conflict. Test every non-standard form yourself.
2. A PHP Error Interrupted Troubleshooting
Creating a temporary admin account for support triggered a fatal error twice from the Universal Form Captcha handler. We got past it, but security software shouldn’t throw fatals in the admin. Worth noting.
3. AI Monitoring Could Be Easier to Activate
The plugin says “enable in the dashboard.” The actual toggle lives in the separate online license portal. Took several attempts to find.
Also: enabling AI monitoring on Tier 1 dropped my website allowance to one. Confirm the exact license rules before you buy extra codes.
WP Captcha Pricing and AppSumo Tiers
Tier 1 is the sweet spot for a single site.
Tier 2 makes sense for agencies.
Higher tiers are for volume or white-label needs. Website slots and AI monitors are not fully interchangeable—check the fine print. AppSumo’s 60-day refund window lets you test your actual forms risk-free.
Feature
Tier 1
Tier 2
Tier 3
Tier 4
Lifetime Price
$49
$98
$147
$196
Websites
3
100
Unlimited
Unlimited
AI Monitors
1
10
30
55
White Label
No
Yes
Yes
Yes
Plugin Rebranding
No
No
Yes
Yes
These figures reflect the AppSumo offer reviewed. Check the current listing for any changes.
Bottom Line
If you’re still cleaning spam by hand, buy WP Captcha.
$49 lifetime gets you six CAPTCHA methods, solid coverage for standard WordPress forms, useful activity data, and a pile of extra security tools. Turnstile has been frictionless and effective on my site.
The real caveats: Universal Form Captcha needs technical work (and may still fail on some custom setups), and AI activation is clumsier than it should be. Neither kills the core value for typical WordPress sites.
Protect all of your forms, all of the time. WP Captcha gets most owners close enough—without another subscription. Test the forms that matter to you, then decide. For a normal WordPress site, this is a strong buy.
This content is for educational purposes and reflects my hands-on experience using the product and the information publicly available at the time of writing. Always evaluate tools based on your specific business needs, goals, and workflows before making a decision.
RSS feeds may not be as sexy as AI, but they are still one of the best ways to keep up with websites and information you care about.
follow.it is a modern take on Feedly-style readers, with more built in. You can follow websites, YouTube channels and podcasts, monitor numbers and data, filter with AI, send updates to email or Slack, and publish a feed for your own site.
I beta tested follow.it before the AppSumo launch, and the product has improved a lot since then.
follow.it Overall Score
Why 4.5/5: Migration and onboarding process wasn’t consistently successful.
Affiliate disclosure: If you purchase through my link, I may earn a small commission at no additional cost to you. I only share tools I have used myself.
The 30-Second Version
Best for: Anyone who wants information to come to them instead of visiting dozens of sources.
Biggest strength: Control over what reaches you and where it lands.
Biggest weakness: That control takes setup. Without a plan, you’ve built another digital mess you will likely abandon.
My take: It didn’t wow me at first but the more I started making this mine, it grew on me.
What Makes It Different
Most people will start with regular feeds, but follow.it covers four feed types:
Regular feeds: Websites, YouTube channels and podcasts, generally RSS-based.
API feeds: Software updates, security issues, financial data and social platforms. Limits vary by feed.
Number feeds: Track a number and get alerted when it changes or hits a threshold.
Course feeds: Pick a topic and a schedule, and get lessons delivered.
The founder is upfront that Feedly is still more mature for folder organization and managing thousands of traditional feeds. follow.it is the broader monitoring and alerting platform. That matches my experience as well.
What I Like
1. Plenty of ways to follow things. Search by site, domain or keyword, use AI to find feeds, paste multiple URLs, or have the team help import an OPML file. Follow with default settings or configure each source individually.
2. Delivery is the standout. Choose individual emails, a daily Newspaper, a weekly Magazine, mobile alerts, Telegram, browser push, Slack or RSS output. This is where follow.it starts to feel like more than a traditional feed reader. You aren’t just choosing what information to follow. You can also decide how and where you want to receive it.
3. Filtering turns volume into signal. Filter by keyword, tag or author, or describe what you want in plain language and let AI check each new item. I need more real-world time before I can say how consistently it includes the right stories and skips the wrong ones.
4. You can publish too. Create a feed for your own site with subscription forms, buttons, pop-ups and widgets, and notify followers automatically. The basic plan includes unlimited emails and followers. Ad and premium-feed monetization are marked Coming Soon, so I’m not counting them.
5. The reading experience covers the basics well. Free iOS and Android apps, plus Save, Share, Mark as Read and AI Summary. I’d still love Pocket-style archiving and text-to-speech.
Getting the most from it will be an investment. follow.it gives you a lot of control over what you follow, how you filter it, how you organize it and where it gets delivered. That’s a strength, but it also means this isn’t necessarily a one-click, set-it-and-forget-it product. The more feeds you add, the more important it becomes to have a plan for how you’re going to manage them.
Migration could be smoother. My bulk URL import failed without saying why. My test list was 77 rows of URLs. OPML import currently means emailing the file to the team.
The One Rule: Don’t Import Everything
I have 500+ saved URLs from years of digital hoarding. Moving them all in would probably be the wrong move. Don’t automatically pour old wine into new bottles.
Start with what you actually care about today. Build categories on purpose. Set sensible default delivery. Expand when there’s a reason.
Which Tier?
Tier
Price
RSS feeds
Number feeds
Course feeds
AI summaries
AI filter/month
1
$49
500
10
10
5
500
2
$99
1,000
25
25
20
2,000
3
$199
3,000
50
50
50
5,000
4
$299
8,000
Unlimited
100
100
10,000
Tier 1 gives most individual users plenty of room. Five hundred RSS feeds is plenty, and it includes the core features.
Tier 2 is the sweet spot for heavier users. Beyond doubling feeds, you get 4x the daily AI summaries, 4x the AI filtering, up to 5x faster delivery, Premium support and ad-free emails.
Tiers 3 and 4 make sense only when your real usage demands those limits, not because you might need them someday.
API feed capability also rises across tiers, and individual API feeds have their own limits, so check the ones you plan to use first.
One more thing: This is the kind of product where every user will probably find something they’d like changed. I’ve been testing follow.it since beta and have already seen meaningful improvements. The team has been great to work with and receptive to feedback. Be patient, tell them what isn’t working for you, and give them a chance to improve it.
Bottom Line
I went in lukewarm. There’s no single flashy feature, but there’s a lot more here than I first gave it credit for.
follow.it combines traditional feeds with AI filtering, monitoring, flexible delivery, publishing tools and mobile apps. Its greatest strength is flexibility. So is its greatest risk.
Here’s how to get your money’s worth. Pick 10 to 20 sources you truly need. Add filters. Send the results somewhere you already work. Then grow from there.
At $49, Tier 1 offers real lifetime value. If AI filtering, summaries and email delivery will be central to your workflow, step up to Tier 2 at $99.
I’d buy for what exists today, not the roadmap. What exists today is already enough.
This content is for educational purposes and reflects my hands-on experience using the product and the information publicly available at the time of writing. Always evaluate tools based on your specific business needs, goals, and workflows before making a decision.
WPSmartPay is built for WordPress sites that need to accept payments without a traditional online store, such as businesses selling software, services, subscriptions, memberships, registrations, or donations.
I needed one-time and recurring Stripe payments for a software product, with a separate WordPress system handling licensing and fulfillment. I tested that workflow through August and September 2026, entirely in Stripe’s test environment: one-time and recurring purchases, multiple-license purchases, refunds, cancellations, and the handoff to our licensing system.
Test mode lets me verify much of the workflow without charging real cards, but it doesn’t reproduce every live-payment scenario. Live card declines, authentication requirements such as 3D Secure, and actual payouts aren’t covered by the results below.
WPSmartPay Overall Score
Why 3.6/5: A capable, well-priced WordPress payment solution held back by setup friction, unresolved issues, and reliability concerns that still need verification.
Affiliate disclosure: If you purchase through my link, I may earn a small commission at no additional cost to you. I only share tools I have used myself.
The 30-Second Decision
Good fit now: one-time payments and initial subscriptions that hand off to another system for fulfillment. In Stripe test mode, a three-license purchase, a monthly subscription, and a refund all worked.
Verify first: renewals, failed payments, card changes, and end-of-term cancellation are still being tested. If recurring billing is central to your business, test those during the refund window.
Update carefully: update Core and Pro together. A version mismatch once locked me out of my WordPress admin.
Not a fit: physical products that need inventory, shipping, or a complex cart.
Testing Status and Known Issues
A webhook is an automatic message one system sends another when something happens. Here, it tells our licensing system what a customer bought.
Statuses reflect the versions I tested. Items marked Needs Retest haven’t been checked on the latest release.
Test or issue
Status
Cause
What happened
One-time, three-license purchase
Passed
N/A
A $147 Stripe test payment completed and our licensing system created and emailed three separate license keys.
One-time card payment in Pro 3.4.3
Passed
N/A
A $49 one-time purchase completed successfully with Stripe’s 4242 test card after Link was disabled.
Initial monthly subscription
Passed
N/A
A $7.99 test subscription and payment were created in Stripe and the software license was provisioned.
Refund
Passed
N/A
A Stripe test refund completed and the corresponding licenses were disabled by our reconciliation process.
Billing portal cancellation
Passed
N/A
The customer portal successfully sent a cancellation to Stripe. A later test-clock simulation confirmed cancellation at the paid period end and delivery of the cancellation event to MWD Software Manager; post-expiration enforcement remains a separate check.
Webhook handoff to licensing system
Passed
N/A
Failed during earlier testing; successful purchases now reach our licensing system for fulfillment.
Duplicate subscription records
Fixed
WPSmartPay
One Stripe subscription originally created duplicate WPSmartPay records. A later update addressed the duplication; regression verification is still planned.
Stripe credential problems
Fixed
WPSmartPay integration/configuration
Earlier testing showed WPSmartPay passing or retrieving an invalid API key. After updated packages and reconfiguration, test payments succeeded.
Form name missing from confirmation
Fixed
WPSmartPay
Earlier confirmations could show a missing or generic form name. The latest successful test correctly displayed the form name.
Link payment-method mismatch
Open
WPSmartPay / Stripe integration
With Link enabled, Stripe rejected five checkout confirmations because the PaymentIntent expected card + Link while confirmation supplied card only. Disabling Link allowed the same 4242 card payment to succeed.
Failed payments remain as Pending orders
Open
WPSmartPay
Five Stripe-rejected checkout attempts remained visible in the customer dashboard as $49 Pending orders after no charge was completed.
Unexpected payment methods at checkout
Resolved
Stripe / WPSmartPay configuration
Earlier testing displayed Klarna and other unexpected payment methods despite configuration changes. Subsequent checkout testing displayed the intended card payment option; the issue is no longer reproducible.
Core/Pro version mismatch
Monitoring
WPSmartPay update process
An August mismatch locked me out of WordPress admin. The site was recovered, and Pro 3.5.0 is now installed with Core 3.3.5, but prevention of another mismatch has not been confirmed.
Payment form sometimes failed to load
Monitoring
Primarily third party
A cookie-consent script was identified as the primary source of the instability. Disabling that configuration stabilized the Stripe payment field.
Rejected Stripe webhooks
Monitoring
Unknown
Four webhooks were rejected during a September 18 test, although the payment still processed. More recent subscription renewal and cancellation events successfully reached MWD Software Manager. The original rejections have not been conclusively explained; continue monitoring.
Billing period and cancellation information missing
Needs Retest
WPSmartPay
Stripe contained subscription information that was not displayed in an earlier WPSmartPay record. More recent Stripe renewal and cancellation data reached MWD Software Manager, but this does not establish that the WPSmartPay customer-facing record now displays the missing billing details.
Valid + email address rejected
Needs Retest
WPSmartPay
A valid Gmail plus-address was rejected during checkout.
Customer name missing from some records
Fixed
WPSmartPay
Earlier records sometimes omitted the customer’s name. The latest successful payment correctly populated the customer name on the confirmation.
Webhook editor difficult to use on shorter screens
Needs Retest
WPSmartPay
Lower controls were previously clipped on shorter browser windows.
Stripe Tax
Pending Registration
N/A
Stripe Tax Basic is configured, and Utah tax registration remains pending. Enabling automatic tax caused a subscription checkout error because Stripe lacked a valid customer tax address. Checkout succeeded with automatic tax disabled; address collection and tax-enabled checkout still need verification.
Successful subscription renewal
Passed
N/A
A Stripe test-clock simulation advanced the $7.99 monthly subscription to November 8. Stripe recorded a second paid invoice and advanced the billing period through December 8. MWD Software Manager extended the existing license through December 8 without creating a duplicate key.
Failed subscription payment
Still Testing
N/A
Failed-renewal handling remains untested. A Stripe decline test card was rejected during initial checkout, which does not simulate failure of an existing subscription renewal. Retry behavior, customer notices, and eventual license access still need verification.
End-of-term cancellation
Partially Passed
N/A
Stripe test-clock simulation confirmed cancellation at the December 8 period end. MWD Software Manager received and recorded the cancellation and retained the correct paid-through date. Because Stripe’s simulated clock does not advance the WordPress server clock, actual post-expiration license enforcement remains unverified; a licensing safeguard was added in MWD Software Manager 0.6.55 and still needs integration testing.
Customer billing self-service
Limited
WPSmartPay
WPSmartPay support confirmed that its customer dashboard does not provide a front-facing link to Stripe’s Billing Portal. Customers need a separately supplied portal link or Stripe recovery emails to update billing details.
Subscription quantity and plan changes
Limited
WPSmartPay
WPSmartPay support confirmed that an existing subscription’s quantity, tier, or amount cannot be changed with automatic proration. The subscription must be canceled and the customer must complete a new checkout.
Customer email notifications
Limited
WPSmartPay
Customer emails are customizable, but the available shortcodes don’t currently expose enough purchase, subscription, or action-link information for us to replace our existing transactional emails. Support has been asked whether additional shortcodes are available or planned.
With Card fields on your page selected, the monthly subscription redirects to Stripe-hosted checkout after card details have already been entered, requiring the customer to enter them again. Vendor clarification is pending.
Fixed website quantities require separate forms
Limited
WPSmartPay
The checkout form does not provide a customer-selectable subscription quantity. Five fixed-quantity forms are needed for monthly plans and another five for lifetime purchases.
Automatic tax checkout address error
Open
WPSmartPay / Stripe Tax integration
When automatic tax was enabled for a monthly subscription, Stripe rejected checkout with customer_tax_location_invalid because the customer had no valid tax address. Disabling automatic tax allowed the subscription to complete. Support has been contacted.
Payment and license email delivery
Passed
Site SMTP configuration
After correcting FluentSMTP outgoing server settings, retries of the payment receipt and SiteSqueeze license email succeeded and both messages arrived. FluentSMTP’s separate test-email screen still produces an error.
A previous problem isn’t necessarily present in the current release, but an item marked Needs Retest isn’t assumed fixed either. I’ll update those statuses only after retesting them. The tracker confirms the September 18 webhook errors, incomplete subscription information, plus-address rejection, missing customer-name issue, and remaining subscription tests.
Customers choose what they’re buying, enter their details, and pay without a shopping-cart process. WPSmartPay handles the transaction and passes the purchase to our licensing system for fulfillment. In the $147 test, one payment produced three separate licenses and one email with all three keys. That suits businesses where payment is one step in a larger process.
A clean WordPress interface
The dashboard is easy to navigate despite the plugin’s size. When troubleshooting a subscription, I could move from the payment to the customer to the subscription record without going through an order-and-inventory system. Data completeness is a separate question: some subscription records were missing the billing period and cancellation date that Stripe showed (see table).
Where WPSmartPay Is Limited
Once a subscription exists, changing it is harder than creating it.
Plan changes: you can’t change an existing subscription’s quantity, tier, or amount with automatic proration. If a customer goes from one license to three, I can’t raise the subscription from $7.99 to $23.97 per month. I have to cancel it and have the customer complete a new checkout.
Billing self-service: the customer dashboard has no button or link to Stripe’s Billing Portal, according to WPSmartPay support. A customer with an expired card needs a portal link from me, or has to rely on Stripe’s recovery emails.
Core and Pro Update Failure
WPSmartPay has two plugins: the main plugin (Core) and Pro, which adds paid features. During an August update, Pro updated but Core failed to, and the version mismatch caused a fatal WordPress error that blocked the Plugins page, even in recovery mode. I regained access through my host’s file manager and installed compatible versions. The error came from functionality tied to another payment gateway, although I only use Stripe.
It hasn’t recurred, but I haven’t confirmed that WPSmartPay now prevents mismatched versions, so I’m not marking it resolved. It’s relevant again now: WPSmartPay announced Pro 3.4.3 while the downloads available to me still provide 3.4.1. I’ve asked for clarification rather than forcing an update.
Development and Support
Development has been active. Several problems I reported, including duplicate subscription records, were fixed in later releases. On August 31, after I reported checkout, webhook, and update problems on AppSumo, a WPSmartPay founder replied that the team was investigating. Responses to other reports sometimes took several days. I judge fixes by retesting, not by release notes.
What I Haven’t Tested
The AppSumo listing also advertises invoices, donations, coupons, event registrations, additional payment gateways, and reporting. I haven’t tested those, so this review isn’t a recommendation of them.
WPSmartPay Pricing
The AppSumo offer captured for this review lists WPSmartPay at $99 for lifetime access on five websites and includes a 60-day money-back guarantee.
That window gives buyers time to test more than the initial checkout. A normal monthly subscription renewal takes a billing cycle to observe in live use. Stripe also offers testing tools that can simulate time-dependent subscription events, but I haven’t yet confirmed that my WPSmartPay-created subscriptions can use that process cleanly, so I’m not treating it as verified functionality here.
Bottom Line
WPSmartPay is a strong option to consider for businesses that want to accept payments through WordPress without operating a traditional eCommerce store. The one-time purchase, initial subscription, refund, cancellation, webhook, and fulfillment workflows I’ve tested are working in Stripe’s test environment.
Recurring-subscription lifecycle testing and Core/Pro update safety are the two areas I’m still watching most closely. If renewals and failed-payment handling are central to your business, I’d use the refund window to test those workflows against your own setup before relying on them.
I’ll continue updating the tracker as those tests are completed.
Review Updates
August 31, 2026: A Core/Pro version mismatch caused a critical WordPress error and required recovery through my hosting account. My AppSumo review at the time said I was close to ending my WPSmartPay testing and looking for another solution. The public listing confirms both the review and WPSmartPay’s response. WPSmartPay – WordPress payments…
September 18, 2026: One-time purchases, initial monthly subscriptions, multi-license fulfillment, refunds, webhook delivery, and basic cancellation were working. Several subscription lifecycle tests remained unfinished.
September 29, 2026: WPSmartPay announced Pro 3.4.3 while the download sources available to me continued providing Pro 3.4.1. I asked WPSmartPay to clarify the current release before installing anything further.
This content is for educational purposes and reflects my hands-on experience using the product and the information publicly available at the time of writing. Always evaluate tools based on your specific business needs, goals, and workflows before making a decision.
I spend a lot of time in Google Analytics, looking at traffic sources, landing pages, and increasingly, how AI platforms are sending visitors my way. But the way most of us use GA4 has a blind spot: it doesn’t show us everything that’s actually requesting files from our server.
That’s the gap HoneyLog is built to fill. It analyzes server and CDN logs to identify AI crawlers, search bots, malicious bots, spoofed traffic, and real human visitors.
Want a better feel for what HoneyLog actually shows you? I’ve also shared a PDF of my HoneyLog dashboard using real MarketingWithDave.com data.
HoneyLog Overall Score
Why 3.6/5: Powerful insights and strong value, held back by a rough onboarding experience and limited guidance on what to do with the data.
The easiest way to explain HoneyLog is to say what it isn’t. It’s not a replacement for Google Analytics or Search Console, and it’s not an SEO crawler like Screaming Frog. It isn’t another AI-visibility platform guessing whether ChatGPT mentions your brand for a set of prompts, either. HoneyLog sits underneath all of that, looking directly at requests hitting your server: Googlebot crawling a page, ChatGPT-User pulling a file, a bot hitting robots.txt, a request generating a 404. When I want all of that noise stripped away, I can pull a report for human visitors only.
AppSumo’s listing describes HoneyLog as connecting bot crawling with the human visits that come from the platforms behind those bots. After using it, I’d call that a fairer description than treating it as a GA4 or Screaming Frog “alternative.” They’re not competing tools. They’re different lenses on the same website.
Watching Google actually find my content
This turned into my favorite use case, and it corrected something about my own habits. I don’t routinely submit new content to Search Console. I publish frequently and have basically trusted that my sitemap updates and Google visits often enough to find new pages on its own. I’d never had an easy way to verify that assumption, so I never did.
HoneyLog gave me one. I publish frequently and have trusted that my sitemap updates and Google visits often enough to discover new content. With HoneyLog, I can actually see when Googlebot and other crawlers find my pages, turning something I’d assumed was happening into something I can observe.
The bots showed up faster than I expected
It didn’t take long for HoneyLog to start finding traffic: ChatGPT-User, OAI-SearchBot, PerplexityBot, DuckAssistBot, and Claude-User all showed up in my early data. But HoneyLog goes deeper than “OpenAI visited.” I isolated OAI-SearchBot and found four requests, then added URL and status-code dimensions. All four were for robots.txt. Three returned 200, one returned 301.
That distinction matters. Seeing “OAI-SearchBot: 4 requests” could easily lead me to assume OpenAI was crawling my content. It wasn’t, at least not in that window. HoneyLog gave me enough data to disprove the conclusion I was about to draw from HoneyLog’s own headline number, which is one of the things I like most about it.
A stranger case came from Singapore. GA4 had been showing a surge of Singapore traffic, and HoneyLog showed substantial Singapore activity too. When I filtered HoneyLog’s data to Singapore, every page view in the selected period was classified as Fake Human. That doesn’t prove my GA4 Singapore sessions were bots; the two tools aren’t measuring identical populations, and I don’t want to overstate the connection. But it gave me another angle on something that already looked suspicious, and some of those requests were presenting completely normal-looking browser user agents before HoneyLog flagged them.
That raises the obvious question: how does HoneyLog know? And that’s where my biggest criticism of the product starts.
Good at showing suspicious. Not great at explaining why
HoneyLog’s classifications include Fake Human, Malicious Bot, Suspicious Bot, Generic Bot, Unknown Bot, AI Citation, AI Indexing, and more. That’s a lot of useful categorization, and it’s also a lot to ask an average marketer to understand without help. I looked through HoneyLog’s documentation for an explanation of what triggers a Fake Human classification and couldn’t find one.
If a tool tells me a request came from Googlebot, I understand exactly what that means. If it tells me traffic presenting itself as a normal Chrome browser is actually malicious, I need to understand what signals produced that conclusion before deciding what to do about it. That gap between the sophistication of the data and how well the product teaches you to use it is the biggest weakness I found.
My favorite report might be the simplest one
This is a strange thing to say about a product I bought to investigate bots, but after spending time in Googlebot, ChatGPT-User, Fake Human, Generic Bot, and everything else, the report I keep coming back to is Human Visitors. Just show me the people. In a web full of crawlers, agents, and automated requests, there’s something clarifying about a report built to strip all of that away. GA4 is still more useful for understanding what those visitors actually do once they land, but HoneyLog gives me another way to separate likely human activity from everything else hitting the server, but there’s an important caveat. HoneyLog confirmed that Human Visitors can still include bots sophisticated enough to mimic human behavior, so I wouldn’t treat this report as a definitive count of actual people.
A world of 404s I normally never see
The Status Codes report produced its own surprise: within roughly my first day of data, I saw more 404 activity than I’m used to seeing in GA4 over much longer stretches. That’s not a knock on GA4, just the difference between client-side analytics and raw server requests. A bot can hit a URL that hasn’t existed in years, guess at a WordPress path that never existed, or follow an outdated link from elsewhere on the web, and none of it becomes a meaningful analytics session.
The harder question is which 404s are worth caring about. HoneyLog’s Raw Logs feature is built for exactly that kind of investigation, letting me narrow a traffic spike by IP, country, bot, and status code. I can already picture building a standing report for 404s from verified crawlers and checking it periodically, which is far more useful than scrolling a giant list of broken requests.
The report builder is the best feature I almost missed
This didn’t jump out at first. It did once I started asking sharper questions. Instead of “Googlebot visited nine times,” I can ask which URLs it requested, what status codes came back, and how long each request took. Instead of “this article got 12 bot requests,” I can ask which bot made them. I ran into that exact case: a URL showed 12 requests that looked interesting until I filtered it and found all 12 were Fake Human. That one filter completely changed what the number meant.
HoneyLog also exports report data to CSV in parts of the app, which made it much easier to dig into Googlebot’s individual requests outside the interface. For anyone willing to dig, there’s a lot here, and that qualifier is doing real work in that sentence.
The average marketer will stall out on “now what?”
This is HoneyLog’s biggest challenge. It hands me information I haven’t had easy access to before, and then leaves me staring at it: my AI bots averaged slower response times than some other crawlers, but is that a problem? I found a Googlebot 404. Should I fix it? HoneyLog flagged something as Fake Human. Should I block it? Googlebot hasn’t crawled today’s article yet. How long is normal before that becomes a concern?
Those are the questions that turn data into action, and right now HoneyLog is much better at supplying the data than answering them. For a technical SEO or developer comfortable digging through logs, that’s probably enough. For the average marketer, HoneyLog needs more interpretation, education, and guidance before the product lives up to what it’s collecting.
After speaking with the HoneyLog team, I have a better starting point. Check error status codes, identify which bots and URLs are responsible, watch how crawlers interact with the sitemap, and create alerts for unusual traffic or error spikes. That’s exactly the kind of workflow I’d like HoneyLog to teach inside the product.
Do you even need this if you already have Cloudflare or an MCP?
Some of what HoneyLog shows may already exist in server logs, CDN platforms like Cloudflare, or other technical tools. But that’s not really the point for me. I wasn’t looking at that data before HoneyLog, and I certainly wasn’t using it to answer questions about Googlebot, AI crawlers, suspicious traffic, or 404s. HoneyLog organizes that information in a way that has already helped me find insights and potential actions I wasn’t getting from the rest of my marketing stack.
Bot Conversions is fascinating. I’d rename one metric
HoneyLog attempts to connect crawler activity to actual human referrals, attributing visits by UTM parameters first and referrer data when UTM isn’t available. The idea is compelling: if OpenAI crawls my site 14 times and ChatGPT later sends me a visitor, I want to see both halves of that story.
One thing bothers me, though. HoneyLog calls one metric Conversion Rate. In my data, Microsoft showed two bot requests and five referred human visits, for a 250% conversion rate. The math works. The label doesn’t. Those five people weren’t “converted” from two crawls; it’s a ratio between two different measurements, and I’d rather see it called something like Referral Ratio or Human Visits per Bot Request. The underlying signal is interesting. I just wouldn’t read that number as a conventional conversion rate.
Onboarding needs work
My first night with HoneyLog wasn’t impressive. After connecting it, I could see that HoneyLog was capturing data in Raw Logs, but the rest of the app still wasn’t ready. About half an hour later, I was still seeing: “Hang tight! Waiting for first aggregation, check raw logs for real-time data! This is necessary to see your aggregated insights.” The message told me what was happening, but not how long I should expect to wait. As a new user, I wasn’t sure whether I needed to wait another five minutes, another five hours, or whether something had gone wrong. I eventually contacted support and called it a night.
The next day felt like a different product. Once enough data had accumulated, HoneyLog became dramatically more interesting. That rocky start matters some context: HoneyLog was founded in June 2026, according to its AppSumo profile. This is a young product, and the onboarding experience shows it. I’d like to see a guided first-run flow that explains what’s happening, how long initial processing normally takes, and three or four useful questions a new customer can answer once the data arrives.
What I’d like to see improved
Documentation tops the list. I want a searchable data dictionary that explains every bot classification and metric, Fake Human included, and then goes a step further to suggest what to actually do about what I’m seeing. If Googlebot keeps hitting 404s, tell me why that’s worth investigating. If an AI crawler’s response times look unusually high, give me context for that. If HoneyLog flags malicious fake-human traffic, point me toward next steps, including where a CDN or security service like Cloudflare fits in.
I’d also like more consistent CSV exporting, clearer empty-result states, better sitemap discovery, and more polished field descriptions. Report templates would help a lot here too: New Content Discovery, AI Crawler Errors, Most-Crawled Content, Verified Bot 404s, AI Crawler Response Time. Don’t just hand marketers a report builder. Teach them which reports are worth building. HoneyLog told me they’re already working on better documentation, including explanations of its traffic classifications, introductory videos, and links from the dashboard to relevant help content, so this is an area I expect to improve as the product matures.
Tier 1 offers plenty of value for $49
AppSumo’s Tier 1 gives you one website, 150,000 monthly events, six months of data retention, Sitemap Intelligence, and Bot Conversions Analysis for $49. That’s enough capacity for a decent amount of traffic on a single website, while still giving you the features that made HoneyLog valuable during my testing.
For me, there’s plenty of value at that price. I’m already getting insights and identifying potential actions I wasn’t getting from the rest of my marketing stack. If you manage larger or multiple websites and HoneyLog proves equally useful for you, the higher tiers provide more events, sites, users, and retention. But Tier 1 doesn’t feel like a stripped-down entry plan. It gives you enough of HoneyLog to find out whether this kind of server-level visibility is genuinely useful for your website.
So what is HoneyLog actually good for?
I bought HoneyLog expecting to learn more about AI crawlers, and I did. The bigger discovery was realizing how much activity on my own website I normally never see at all. That’s why I’m keeping it: when I have a specific question, I now have somewhere to look. Did Google find yesterday’s article? Is ChatGPT actually crawling my content, or just checking robots.txt? Why did my 404s spike this week? Was that strange traffic real?
Those are questions I’d either struggled to answer before or never thought to ask. HoneyLog makes them observable. The next challenge for the product is making them actionable, and it’s not quite there yet.
I’m already comfortable saying I’m keeping Tier 1. HoneyLog is producing insights, and pointing me toward potential actions, that I’m not getting anywhere else in my current stack. That’s exactly the kind of product AppSumo’s 60-day return window was made for. You can’t fully judge HoneyLog on day one, because its value comes from watching your own traffic accumulate over time. Install it, let it collect real data, start asking questions of that data, and see whether it tells you something you can act on. In my case, it already has.
This content is for educational purposes and reflects my hands-on experience using the product and the information publicly available at the time of writing. Always evaluate tools based on your specific business needs, goals, and workflows before making a decision.
Most AI Search visibility tools follow a similar playbook: enter prompts, run them through AI models, and see if your brand shows up. Subsig does that too, but prompt tracking isn’t the most interesting part of the platform.
Subsig combines AI visibility with citations, competitors, reviews, brand mentions, sentiment, keyword intelligence, and AI Agents designed to turn that data into recommendations. It’s less a dedicated AI Search tool than a broader brand-intelligence platform that includes AI visibility.
That makes Subsig one of the more unusual platforms I’ve tested, and also harder to evaluate. Some features were genuinely impressive, others need more explanation, and several make far more sense for an established brand generating regular reviews and online conversations than they do for Marketing With Dave.
Subsig Overall Score
Why 3.8/5: Subsig combines strong AI Search reporting with unusually broad brand intelligence, but confusing UX, opaque data processing, and restrictive Tier 1 limits hold it back.
Affiliate disclosure: If you purchase through my link, I may earn a small commission at no additional cost to you. I only share tools I have used myself.
The 30-Second Decision
Buy Subsig if: You run a SaaS company or established brand with products people actively review, mention, and discuss online. It makes the most sense when you have recognizable brand or product names to track and want AI visibility, citations, competitors, reviews, mentions, sentiment, and keyword conversations in one platform.
Skip it if: Your brand is still too small to generate meaningful reviews or online discussion, or you primarily want high-volume prompt tracking across multiple AI models. Tier 1 limits you to 10 prompts, 5 keywords, and ChatGPT, making a dedicated AI Search tool a better fit for that use case.
The bottom line: Subsig gets more compelling as your brand gets more visible. Its advantage isn’t simply tracking whether AI mentions you. It’s connecting AI visibility with what customers, review sites, competitors, and the broader web are saying about your brand.
What Subsig Actually Does
Subsig splits into several connected areas:
AI Visibility tracks whether your brand appears in AI answers, how often, where it ranks, share of voice against competitors, citations used, and sentiment.
Review Monitoring pulls in reviews from supported platforms for reputation and feedback analysis.
Brand Mentions tracks conversations about your brand across supported online and social sources.
Keyword Intelligence tracks conversations around topics you care about, even without a brand mention.
Agents analyze the collected data and turn it into recommendations instead of leaving you with more dashboards.
That combination separates Subsig from tools focused entirely on AI Search Visibility. It’s part AI Search visibility platform, part reputation manager, part brand monitor. Whether those pieces add up to more than the sum of their parts is still an open question, but the idea is compelling.
The Wait for Data Needs to Be Clearer
Setup itself wasn’t hard. Not knowing what was happening after setup was the problem.
I added Marketing With Dave, configured what to monitor, added prompts and competitors, then waited. Some sections populated hours later, with almost no indication of how long that should take. That’s a UX problem, not a performance one.
If Subsig told me “we’re analyzing your brand, initial results typically take 2-4 hours,” I’d close the browser and come back later. Without it, an empty dashboard just leaves you guessing whether it’s processing, misconfigured, or broken. Subsig needs better processing indicators and a real estimated timeframe.
Once data started arriving, the product got a lot more interesting.
What I Liked
1. The AI Visibility Reporting Is Surprisingly Complete
I ran the same set of 10 prompts I use to benchmark every AI Search platform I test. Marketing With Dave appeared in only one of them, which is my visibility problem, not Subsig’s.
For “Who is Marketing With Dave?”:
Brand rank: #1
Brand mentions: 16.7%
Brand sentiment: Positive
Multiple MarketingWithDave.com URLs retrieved as sources
Subsig also preserved the actual AI response, not just an aggregate score. ChatGPT described Marketing With Dave as a digital marketing resource led by an experienced professional with 25+ years in the field, focused on SEO, analytics, and software reviews. A fair representation.
More importantly, that result exposed the real gap. ChatGPT recognizes Marketing With Dave, retrieves the site directly, and understands what the brand is about. I’m just not yet showing up for broader category questions around AI Search resources, marketing software reviews, or measuring AI traffic. That’s more actionable than simply knowing my visibility score is 6.7%.
The sentiment score was 80/100, entirely positive, but based on a single response. Subsig does display the response count, so you can weigh the number appropriately, but an 80/100 built on one data point isn’t something to make decisions around yet.
2. Citation Analysis Goes Deeper Than a List of Links
Across tracked responses, Subsig identified 52 domains and 62 URLs, with MarketingWithDave.com contributing 5.3% of both. It categorizes citation sources by type (corporate, UGC, editorial, owned, institutional, and other), and corporate sources dominated my early dataset at 72.4% of retrievals.
That surfaces a useful question: if AI systems keep retrieving certain sites to answer the questions I care about, what can I learn from those sources? One Subsig recommendation pointed toward getting Marketing With Dave included on a site that was already being retrieved frequently. Whether every recommendation holds up remains to be seen, but the underlying citation intelligence is genuinely useful.
3. Competitor Reporting Gives the Numbers Context
A 6.7% visibility score means little on its own. Adding competitors (AppSumo, HubSpot, RevLocal, Search Engine Journal, Search Engine Land, WebFX) changed that:
Brand
Visibility
Share of Voice
Avg. Position
AppSumo
20%
60%
2.1
Marketing With Dave
6.7%
20%
2.0
HubSpot
6.7%
20%
2.5
RevLocal
0%
0%
—
Search Engine Journal
0%
0%
—
Search Engine Land
0%
0%
—
WebFX
0%
0%
—
Ten prompts and one AI model is too small a sample to treat this as real competitive intelligence, but it shows the reporting’s value: Marketing With Dave trailed AppSumo on visibility but had the best average position of any brand that appeared. That’s a far more useful signal than a bare visibility percentage. Subsig also suggests additional competitors worth monitoring.
4. The Prompt-Level Drilldown Is Where the Real Story Lives
The dashboard reported a 6.7% AI Visibility Score, #2 visibility rank, 20% share of voice, and #2 share-of-voice rank. Useful for tracking change over time, but not for optimization decisions on their own.
That distinction matters more than I initially realized. I tested the same prompt across six AI Search tools, including Subsig, and found dramatically different visibility scores depending on the platform measuring it. The experiment reinforced why I put more weight on the underlying responses, citations, and prompt-level data than any single visibility score.
The real value is in the individual prompts. Nine told me I have a visibility problem. One told me something better: when someone directly asks who Marketing With Dave is, ChatGPT knows the brand, describes it accurately, ranks it first, and pulls pages straight from the site. That’s a starting point. The real opportunity isn’t “raise 6.7%,” it’s figuring out why the site has strong entity recognition on a branded query but isn’t surfacing for the broader category questions I actually want it associated with. That’s exactly what I want AI Search software to help me investigate.
5. The Agents Are One of Subsig’s Most Interesting Features
Subsig doesn’t stop at dashboards. Its Agents turn your visibility data into standalone reports: root-cause analysis, prompt discovery, competitive benchmarking, even a 180-day AI visibility roadmap.
The Root Cause Analysis Agent was the standout. It examined where Marketing With Dave was and wasn’t appearing, dug into citation sources, and prioritized actions. The Prompts Discovery Agent suggested new questions to track, organized by buyer intent, which matters because deciding what to track is half the battle. The reports are polished, too: my 180-day roadmap broke recommendations into phases with separate tactics for ChatGPT, Perplexity, and Gemini.
I hadn’t added competitors to this project. The Competitive Benchmark Agent correctly flagged that it couldn’t run a true comparison, then speculated that the absence of tracked competitors might mean Marketing With Dave operates in a niche without real rivals. Another report skipped the caveat entirely and invented generic “Competitor A,” “Competitor B,” and “Competitor C” profiles. Neither conclusion is supported by my data.
Treat the Agents as AI-assisted analysis, not a finished analyst’s report. Read it, question it, and verify before acting on it.
Several more Agents are marked “coming soon”: Social Mentions Plan, Reputation Playbook, Review and Listings Plan, Keyword Strategy, Authority Building, Review Response, and a Custom Agent for building your own workflows. If those deliver, the Agents could become the platform’s biggest differentiator.
6. Review Monitoring Could Be Valuable for the Right Business
Marketing With Dave showed zero review data at first, unsurprising for a site that doesn’t generate hundreds of customer reviews. I added AppSumo as a second brand specifically to see what Subsig does when review data exists. A local business, SaaS company, eCommerce brand, or established product with real review volume will get far more out of this feature than I can demonstrate here, which is part of why I wouldn’t judge Subsig purely against dedicated AI visibility platforms.
7. Keyword Intelligence Has Potential, but I Couldn’t Properly Test It
Keyword Intelligence is one of Subsig’s more interesting features because it can track conversations around topics even when your brand isn’t mentioned. I configured all five keywords available on Tier 1, including “AI Search Visibility,” “SiteSqueeze,” and “Marketing With Dave,” but Subsig had not returned any results by the time I completed this review.
That leaves a significant part of the platform I can’t fairly evaluate yet. The setup also needs clearer guidance around how keyword matching works, particularly the distinction between “All of these keywords” and “Any of these keywords.” I’ll revisit this feature once I have enough data to judge what it actually finds.
Tier 1 gives you 10 tracked prompts, ChatGPT as the only AI provider, 5 keywords, 5 brands, 2,000 reviews, and 1,000 mentions. Ten prompts were enough to run my standard benchmark, but not much more, and meaningful cross-platform AI visibility requires moving up to Tier 3.
Some limits also aren’t obvious until you hit them. Review and mention capacities don’t reset, and deleting records doesn’t restore capacity. Subsig also limits monitoring to its supported platforms rather than letting you add any source. None of these are dealbreakers, but buyers should understand them before choosing a tier or configuring broad monitoring.
2. Data Processing Needs Much Better Communication
Data taking time is fine; making users guess whether the system is processing, broken, or misconfigured is not. During my testing, some data took hours to appear with little indication of what was happening. Something as simple as “7 of 10 prompts processed” or “next mention scan scheduled for…” would solve much of the problem.
3. The Product Needs More Explanation and Guidance
Subsig has a lot going on, and it sometimes assumes you understand how everything works together. Metrics such as Citation Rate, Retrieval, and Contribution need better explanation. Keyword Intelligence’s All/Any matching wasn’t clear. The distinction between competitors configured in different parts of the platform can also be confusing.
The same applies to the Agents. They’re promising, but I’d like to see more context showing which underlying data produced a recommendation, especially after seeing some reports make conclusions the data didn’t support.
Pricing and Tier 1
Subsig is currently on AppSumo across four lifetime tiers, all with unlimited users and all Agents included:
Tier 1
Tier 2
Tier 3
Tier 4
Price
$49
$119
$269
$499
Workspaces
2
3
10
20
Tracked prompts
10
25
50
100
Lifetime AI credits
240
450
900
1,500
Review capacity
2,000
3,500
7,000
13,000
Mention capacity
1,000
3,000
5,500
12,000
Keywords
5
15
25
50
Brands
5
15
25
50
Trackable review platforms
12
18
32
64
Supported review platforms
4
6
10
15
Social platforms
5
7
7
7
AI providers
OpenAI
OpenAI
OpenAI, Perplexity, Google AI Overview
OpenAI, Perplexity, Google AI Overview
Notifications
Email & Slack
Email & Slack
Email & Slack
Email & Slack
Tier 3 is where the biggest unlock happens. It’s the first tier to add Perplexity and Google AI Overview alongside OpenAI, while increasing prompt capacity to 50. If cross-platform AI visibility is a priority, that’s the tier I’d look at.
Tier 1 makes more sense if you’re interested in Subsig’s broader brand-intelligence capabilities and can live with ChatGPT-only visibility and 10 tracked prompts. That’s an important distinction: the value looks considerably different depending on whether you’re buying Subsig as an AI Search tracker or as a broader brand-monitoring platform.
Bottom Line
Subsig is hard to put in a neat category, and that’s what makes it interesting. As a pure AI Search visibility tracker, its reporting, citation analysis, competitor tracking, and prompt-level data hold their own, but Tier 1’s 10-prompt limit and ChatGPT-only access are restrictive.
The bigger story is the combination of AI visibility with reviews, brand mentions, sentiment, keywords, citations, competitors, and Agents designed to turn that data into recommendations. Not every part was a natural fit for Marketing With Dave today, and the platform still needs better guidance and transparency around data processing.
Most AI visibility platforms essentially ask, “Does AI mention my brand?” Subsig is aiming at a bigger question: “What does the digital world know and say about my brand, and what should I do about it?” If that’s the problem you’re trying to solve, Subsig is considerably more interesting than another AI visibility dashboard.
This content is for educational purposes and reflects my hands-on experience using the product and the information publicly available at the time of writing. Always evaluate tools based on your specific business needs, goals, and workflows before making a decision.
AI tools that write LinkedIn posts are everywhere, so I went into FeedBoss skeptical. The usual pattern: you give it a topic, it spits out something vaguely post-shaped, and you spend the rest of your time making it sound like you.
FeedBoss broke that pattern. Its best features barely involve generating content at all. It analyzes your LinkedIn history, builds a detailed writer profile, refines drafts conversationally, creates images and editable slide decks, audits your profile, and delivers analytics that beat what LinkedIn gives you natively.
It also has real gaps. Some AI editing functions failed outright, navigation buries key features, and Tier 1 skips functionality teams will want. I also encountered an error with Trending Topics, but the support team corrected it within minutes of my reporting it.
Net result: more interesting than I expected, with rough edges that need fixing. I also put FeedBoss through my six-question framework for evaluating social media software, adapted for one important distinction: FeedBoss is built entirely for LinkedIn.
FeedBoss Overall Score
Why 4/5? Inconsistent AI editing, frustrating navigation, launch-day bugs, and Tier 1 limitations keep an otherwise impressive LinkedIn platform from feeling fully polished.
Affiliate disclosure: If you purchase through my link, I may earn a small commission at no additional cost to you. I only share tools I have used myself.
The 30-Second Decision
Buy FeedBoss if: You want an AI-powered content and optimization platform built specifically for LinkedIn. It combines writing assistance, scheduling, carousels and images, LinkedIn analytics, profile auditing, engagement tools, and content research in one workspace, with surprisingly strong personalization to your brand and writing style.
Skip it if: You need a multi-channel social media management platform, or LinkedIn is only one small part of your social strategy. FeedBoss is not trying to manage Facebook, Instagram, X, TikTok, or your other social channels. It is a LinkedIn tool.
The biggest reason to consider FeedBoss is how much of the LinkedIn workflow it brings together. It can learn how you write, help develop and refine content, create supporting visuals and carousels, schedule posts, analyze what is working, audit your LinkedIn presence, and surface ideas for what to do next. Some features still have rough edges, but FeedBoss is much more than another AI LinkedIn post generator.
The Onboarding Analysis Nailed Who I Am
FeedBoss spent real time analyzing my LinkedIn history before generating anything, and the output showed it. It labeled me “The AI-Search Auditor” and correctly identified my recurring strengths: original frameworks, first-hand testing, consistent publishing.
It pulled my actual background (nearly 30 years in digital marketing, Verisk, Nelson Nexus, my MBA, MarketingWithDave.com, my book) and correctly mapped the intersection of SEO, AI-search visibility, and analytics that drives my recent content.
The writing-style analysis was the strongest part. It recognized that I open with tension or a contrarian claim, then back it with my own testing data. It cited real examples and flagged specific patterns: short declarative hooks, functional over decorative formatting, minimal emoji, named frameworks, a preference for evidence over vendor claims.
Best of all: it described me as an “anti-hype analyst of AI-search marketing” and correctly picked up on my documented/observed/inferred/unknown distinction, plus my recurring warning against chasing AI visibility while ignoring the traffic that still comes from everywhere else.
The broad topic tags (“AI,” “Leadership,” “Innovation”) felt generic next to that detailed persona work, but overall this is the best onboarding analysis I’ve seen from an AI content platform.
The Writing Workflow Asks Instead of Inventing
I tested it with a real idea: before asking a customer to fill in a field, ask whether you’re requesting information they already gave you or information your company should already know.
The first draft was polished but leaned into data-governance and enterprise CRM language, more consultant than me. Then FeedBoss did something I liked: instead of calling the draft done, it told me the post stayed general because it needed a specific example only I had, and it wouldn’t invent one. It asked me for a real customer story.
I gave it a rant involving Audible, Netflix, Costco prescriptions, the IRS, and my HOA. FeedBoss worked those into the piece. The result sounded substantially more like something I would publish.
Most AI writing tools work like this: prompt, generate, here’s your post, good luck. FeedBoss works like this: understand the writer, draft, identify what’s missing, ask for it, revise, keep refining. That difference matters.
One Gap: No Easy Way to Trim for LinkedIn’s Limit
The revised post landed at 3,762 characters. LinkedIn caps posts at 3,000. FeedBoss flagged the overage correctly but gave me no one-click way to send it back through and say “cut this to 3,000 without losing the point.” If FeedBoss knows the destination is LinkedIn, it should either respect the limit automatically or surface a prominent “Trim to 3,000” option.
Slide Decks: Enough to Finally Get Me Publishing a Carousel
I’ve never published a LinkedIn carousel because the production work never felt worth it. FeedBoss got me closer than any tool has.
I prompted it to build a myth-busting carousel separating documented, observed, inferred, and unknown claims in AI-search visibility reporting, and to explain why confusing those categories leads to bad decisions. It returned an eight-slide deck that got the framework right: each category defined correctly, a slide on how reporting breaks down when observation becomes fact and inference becomes certainty, and a closing slide that turned the framework into a four-step process.
That’s a strong first draft from a short prompt.
The Slide Editor Struggles With Images
The slide deck itself was a strong starting point, but the AI editing tools were much less capable than I expected. My logo rendered at roughly 50×36 pixels on every slide, far too small to read. I asked FeedBoss to enlarge it across all eight slides, then tried again with a specific instruction to triple its size. Neither request changed the logo. I saw the same limitation when asking the AI to remove image elements.
Text edits worked much better. FeedBoss could resize, rewrite, and replace text, so the editor is useful for copy and typography. Visual-element editing is where it currently falls short. If I have to manually resize the same logo across eight slides and then verify that every slide matches, some of the time savings disappear.
I still see real potential here. FeedBoss can import an existing PDF or slide deck, so once I create a polished MarketingWithDave carousel template with the right logo size, typography, and spacing, I should be able to reuse that structure instead of fixing the same design issues every time.
One smaller UX issue: finished decks appear in a Your decks section below the creation interface. Because that section is off-screen, a newly created deck can briefly feel like it disappeared until you know to scroll down.
Image Studio: Good Output, One Credit Bug
I asked FeedBoss to build an infographic around another idea I’m writing about: AI search visibility has a sampling problem, where checking too few prompts across too few models produces misleading scores. It generated a clean, on-brand infographic using my blue/navy/white kit, correctly incorporating prompts tested, models tested, test frequency, and response variation, with a solid closing line about sample size.
Output: a 1024×1024 PNG, about 1.38 MB, text rendering cleanly. Good first-generation quality, though some text ran small for mobile.
One problem: the infographic illustrated the sampling issue with invented numbers (72% visibility from 10 prompts and 2 models, 38% from 100+ prompts and 6+ models). Those weren’t my real numbers. For a graphic specifically about evidence quality, fabricated stats are the wrong move. I’d strip the percentages or label them illustrative before publishing.
I also hit a credit error trying to remove an element from the image, despite having 2,355 credits available. Likely a bug or an undocumented Tier 1 limit, but it shouldn’t happen with that much headroom.
LinkedIn Analytics Is Probably the Best Feature
This nearly stayed hidden. Analytics, Engagement, Popular Posts, Authority Map, and LinkedIn Audit all sit under an “Optimize” section buried deep in the left nav. I almost finished testing without finding it.
Once I did, it became my favorite part of the product. Native LinkedIn analytics are thin. FeedBoss turns your posting history into an actual dashboard: total engagement, reactions, comments, shares, engagement-rate trends, follower growth, performance by date, and it goes further by turning that data into decisions.
It identified Thursday afternoon as my strongest posting window and faded out results where it didn’t have enough data yet, rather than presenting a thin sample with the same confidence as a strong one. Good instinct.
It also broke down engagement rate by format across my last 25 posts: articles at 0.24% (13 posts), text at 0.21% (11 posts), image at 0.11% (1 post). I wouldn’t act on that last number, and neither should you, since one post isn’t a sample. Showing the post count next to the rate is exactly the right call.
It also analyzes posts you published outside FeedBoss, checking for new activity every 24 hours. You get useful analytics immediately instead of waiting weeks for FeedBoss to build its own history.
The LinkedIn Profile Audit Delivers Real Substance
The audit generated a four-page PDF, gave me a Personal Brand Score (73/100), and broke that down across Core Health, SEO/Discoverability, Content/Engagement, and Authority/Leadership. It then produced specific recommendations for my headline, About section, experience, skills, and profile image, correctly referencing real accomplishments from my history like eCommerce results and Google Ads ROAS.
I don’t agree with every call. It flagged zero skill endorsements as a major red flag and tied that to a lack of recommendations, but endorsements and recommendations aren’t the same thing. Treat the audit as input for judgment, not a checklist to follow blindly. Even so, it’s one of the strongest features in the product.
Two annoyances: the audit asked me to re-enter my LinkedIn URL, even though FeedBoss already has my connected profile, imported posts, and follower count. And there’s no obvious place to find your most recent audit or track score changes over time. Both should be easy fixes.
Navigation buries Analytics, Audit, and Engagement below the fold with no clear signal there’s more to scroll to.
Slide Deck editor can resize and rewrite text but can’t reliably resize or remove images and logos.
Generated posts can exceed LinkedIn’s 3,000-character limit with no one-click way to trim them.
Image Studio invents illustrative data without labeling it as such.
Image editing hit a credit error despite a large available balance.
Emoji picker is missing basic bullet characters, a real gap for a LinkedIn-focused tool.
Tier 1 excludes Video Studio, Lead Magnets, Authority Map, API access, and post-approval workflows, the last of which matters most for agencies and teams.
Most of these are fixable UX and QA issues, not fundamental design problems. In fact, I initially encountered an error that prevented Trending Topics research from working at all. I reported it, the support team responded, and the issue was corrected within minutes. That’s exactly the kind of responsiveness I want to see when testing a newly launched product. The remaining issues are worth knowing before you buy, but they’re not reasons I’d write the product off.
Tier 1 and Credits
Tier 1 ($59) includes 400 monthly AI credits, 2,000 lifetime credits, 5 profile audits per month, 1 LinkedIn connection, 1 workspace, 1 member, 10 tracked engagement profiles, 25 GB storage, 2K image resolution, voice/text Knowledge Base, Bring Your Own AI Key, and profile voice matching.
Credits by action: a post costs 5, an image costs 25, a slide deck costs 20 regardless of slide count, an image carousel costs 50 regardless of slide count, and video costs 100 regardless of length. Editing individual slides is free. Charging decks and carousels as a flat fee instead of per-slide is the right model.
FeedBoss draws from monthly credits before touching your lifetime balance, and the dashboard shows the split clearly (355/400 monthly, 2,000 lifetime, 2,355 total after my test). That transparency is well done.
Brand Kit and Content Styles
The Brand Kit (handle, tagline, logo, fonts, colors) applies consistently to generated images but inconsistently to slide decks, where my logo rendered too small despite the same settings. One central brand config is the right idea; the execution needs to actually honor it everywhere.
FeedBoss also auto-generated writing styles from my LinkedIn history (My LinkedIn Voice, Lesson Learned, Build in Public, Observational, Reflection, Milestone, Tactical, Story, Contrarian). Starting from a predefined style beats re-explaining tone in every prompt. I didn’t test each style deeply enough to say how distinct the outputs really are.
Bottom Line
I expected another AI LinkedIn writer. That undersells it. The strongest parts of FeedBoss are where it works with information that already exists: my LinkedIn history becomes a real persona, my published posts become analytics, my profile becomes an audit, my writing patterns become reusable styles, and one real example turns a generic article into something I’d actually publish.
The product still has launch-stage bugs, and several Tier 1 gaps will matter more to teams than solo creators. But between the analytics, the profile audit, and a writing workflow that asks for missing information instead of fabricating it, there’s enough real value here to keep using it and watch where it goes.
This content is for educational purposes and reflects my hands-on experience using the product and the information publicly available at the time of writing. Always evaluate tools based on your specific business needs, goals, and workflows before making a decision.
