Editorial Policy
How we choose topics, test what we recommend, disclose affiliate relationships, use AI in our content, and handle corrections. No fine print — just the full picture.
Our editorial standards
We publish on three topics: writing and productivity, text-analysis software, and adjacent tools — keyboards, reading glasses, ergonomic gear, and home office equipment.
Article topics are chosen based on real reader questions, our own daily workflow, and gaps we notice in existing coverage. We do not chase search volume for its own sake, and we do not publish on topics where we have no direct experience.
Every article is written by İsmail Günaydın or reviewed and substantially rewritten by him before publication. There is no contributor network, no outsourced content, and no "last updated by AI" policy.
How we test software tools
- Minimum 14 days of hands-on use before any review or recommendation.
- Real project test scenarios — for example, we ran a 50,000-word manuscript through every grammar checker we recommend.
- Side-by-side comparison against at least two direct competitors on the same test input.
- Scoring rubric: ease of use, output quality, pricing, privacy model, cross-platform support, and accuracy against a known-correct reference.
- Where we recommend a free tool over a paid one, we explain why. Where we recommend a paid tool, we say who it is and is not right for.
How we test hardware (Amazon affiliate products)
Honest disclosure: Not every product in our affiliate recommendations has been personally tested. We label tested products clearly.
Products marked "Hands-on tested" have been used personally for at least 30 days. Other products are recommended based on reader feedback, expert review aggregates, and verified buyer ratings on Amazon.
We never fabricate hands-on experience. If we have not used something, we say so. This honesty is intentional: a recommendation that overstates testing destroys trust the moment a reader has a different experience.
Affiliate disclosure
TextWordCount participates in the following affiliate programmes:
- Amazon Associates: We earn a small commission on qualifying purchases made through Amazon links on this site. The commission comes from Amazon, not from you — the price you pay is the same.
- Kinsta: We have an affiliate partnership with Kinsta for hosting recommendations. If you sign up via our link, we receive a commission.
- Gumroad (our store): Products sold through our digital store (/store-app) are our own — Claude Code skills, AI agent kits, SEO toolkits. We earn 100% of the sale price minus Gumroad's fees. This is not an affiliate arrangement; these are our own products.
Affiliate commissions never influence which products we recommend or how we rank them. We have recommended products that pay no commission and declined to recommend products that pay high commissions. The recommendation comes first; the affiliate relationship (if any) follows.
For the full legal disclosure, see our Affiliate Disclosure page.
AI content disclosure
We use AI tools — primarily Claude — as research and drafting assistants for blog posts and long-form articles. Every article is then human-edited by İsmail Günaydın: fact-checked, restructured where needed, and rewritten to reflect his direct experience and voice. We do not publish raw AI output.
Tool documentation, methodology pages, this editorial policy, and case studies are written entirely by humans. No AI involvement in these pages.
AI-generated images, when used, are labelled as such in the image caption or alt text.
Sources & citations policy
- Primary sources preferred: academic papers, official documentation, manufacturer specifications.
- Secondary sources cited with a link to the original. We do not cite secondary sources as if they are primary.
- We do not republish or paraphrase content from other sites without attribution.
- Where a claim cannot be sourced, we say so explicitly rather than presenting it as established fact.
Corrections policy
If you find a factual error, outdated information, or a broken link, email ismailgnydn28@gmail.com with the article URL, the specific claim, and the correct information with a source if possible.
We review correction requests within 48 hours. If the correction is valid, we update the article and note the correction at the bottom with the date.
We do not remove corrections after the fact — the update note stays on the page permanently.
Last updated: 2026-04-25 by İsmail Günaydın.
Related pages