b00rnb00rn
b00rnPLUS
Jun 14, 2026

Q: some missing features after testing (or bugs?) for bloggers only?

I work as agency with online stores in German language. Unfortunately, some features seem to only be useful for bloggers, just like many other tools out there. Because in serious SEO and long-form content, a lot of it is simply unusable.
On-page analysis: difference between singular & plural is not recognized! On top, word combinations are split into individual words and analyzed accordingly, which is just plain wrong.
0 monthly searches on average: But Google Search Console shows thousands of searches? There are too few H3 tags on the page. Insert between 2 and 30 H3 tags: why? What kind of nonsense is that, above all, since there are H3 tags? Unfortunately, there are quite a few more ridiculous warnings like this.
With the free credits provided, you can barely test the tool at all, making a thorough evaluation pretty much impossible.

Founder Team
Christophe_TextFocus

Christophe_TextFocus

Jun 14, 2026

A: Hi,
Thanks for the detailed feedback, this is useful.
On the H3 issue: this would help me to have an example URL where this happens. If H3 tags are present but not detected, it could be a real bug worth fixing quickly, or it could be related to how they're generated (loaded after page render, or non-standard markup). Either way, I'd rather check a concrete case than guess.
On singular/plural and word splitting: the semantic analysis works at the term level, and detecting inflected forms (plural, declension) is genuinely harder in German than in English or French due to compound words and grammatical cases. This is an area I know can be improved, and German-specific handling is something I want to refine further.
On search volume showing 0 while Search Console shows thousands: this is expected, though I understand it's confusing. The volume figures come from a third-party API (DataForSEO), which uses its own estimation methodology, different from Google Search Console's actual impression data. These are aggregate estimates, not a live reflection of your specific rankings or impressions, so discrepancies with GSC are common across all tools relying on this kind of data, not just Textfocus.
On free credits: yes, they're intentionally limited, and only a partial view of results is shown in the free tier. That's a deliberate constraint to keep the model sustainable, but I understand it makes a full evaluation harder upfront.
If you can share an example page (ideally German e-commerce, long-form), I'm happy to look at the H3 detection and the semantic output specifically for that case. Feedback from agency users working in non-English languages is exactly what helps me prioritize the right fixes.

Share
Helpful?
0
Log in to join the conversation
b00rnPLUS

Thanks for the explanation. But WriterZen and SheerSEO — well-known AppSumo tools I use myself — deliver accurate German keyword volumes via Google's own API. The issue isn't fundamental; it's your data source. AppSumo has a notably high volume of German-speaking buyers. If non-English languages don't work reliably, that should be disclosed before purchase.

I'm careful not to neglect German speakers (my wife is German!). Could you give me an example of a word with zero volume? I use the same API for volume as Neil Patel. I'll make sure to check the data and the code, and I assure you that I didn't intend for Textfocus to be solely for the English market. I designed it with a translation agency; our needs in a wide variety of languages ​​were numerous

b00rnPLUS

elektrische Außenborder

You're right, there was a bug related to the API initially searching through smoothed and not always up-to-date data. I've added a fallback; it's live, and it should improve the results. You can test it.

And the keyword "elektro außenborder" seems to have a higher search volume, FYI. This is also shown by the SERP.