SnagitPro publishes guides to screen capture, screenshot editing, recording, and documentation. This policy sets the requirements for that work. It does not certify that every older page already meets them. If a specific claim falls short, report the page and the problem.
Who creates the content
Adrian Foster is the site's editorial byline. The About page explains the publication's identity. A byline is not evidence of professional credentials or proof that its author personally tested a product.
The publishing workflow uses AI-assisted research, drafting, and editing. That assistance does not verify a claim. Prices, instructions, quotations, and recommendations still need evidence; an AI answer must not be cited as if it were a vendor's documentation or a real user's report.
What gets covered
A topic should answer a concrete question: which capture tool fits a job, why a screenshot failed, how to protect private information, or how to assemble a useful guide. Search questions and documented product problems help identify those needs.
A keyword variation is not a reason to publish another near-duplicate page. When an existing guide answers the same question, improve that answer or link to it. A comparison should explain the tradeoffs for the reader's platform and task, including when a free tool is enough.
Sources and fact-checking
The standard requires current primary evidence for claims that can change: official stores, product documentation, release notes, and operating-system instructions. A source link belongs beside the claim it supports, not in an unexplained list at the end.
- Instructions need the relevant product version, platform, and menu path.
- Prices and license rules need the country, currency, plan, and purchase route when those affect the answer.
- Conflicting sources or missing evidence need an explicit limitation, not an invented resolution.
Search results help identify questions and competing explanations. They do not establish that a technical claim is true. Google's guidance on useful content and clear authorship also distinguishes source-based work, actual experience, and explanations of how content was produced.
Research is not a hardware test
Reading documentation does not prove that a procedure was reproduced on a Windows PC or a Mac. A hands-on result must identify the app and operating-system versions, relevant hardware or settings, test date, and observed result. The research and verification method explains the evidence labels.
Generated or reconstructed interface graphics can explain a workflow. They must not be presented as official captures or proof of a test that did not happen. A useful illustration does not establish that its controls exactly match every installed version.
Community reports and quotations
A forum thread, issue report, or reader message can point to a problem worth investigating. It does not establish how common the problem is or prove that a workaround works for everyone. Public reports need a findable source and relevant version or setup context.
Do not invent a user, quote, support ticket, or test result. A summary of several reports must be identified as a summary, not attributed to an imaginary speaker. Private messages and identifying details require permission before publication.
Editorial independence
SnagitPro is an independent publication, not TechSmith's official support site. Recommendations must follow the product evidence and the reader's needs. A commission, discount, review copy, or commercial relationship must not buy a ranking, favorable verdict, or control over editorial conclusions.
Commercial links and relevant arrangements belong in the affiliate disclosure and, where applicable, beside the recommendation. This policy is not a claim that every past draft-sharing or financial arrangement has been independently audited.
Checks, updates, and corrections
The current review process requires complete checks of the saved page: its claims and usefulness, title and description, contextual links, visual presentation, and any structured data. A matching FAQ or schema answer must say the same thing as the visible article. Checking a few links does not complete that review.
Review labels must state what was checked and when. The original publication date stays separate from later edits; an Updated date alone does not prove a full fact-check. Dates must not be changed merely to make a page appear fresh.
The corrections policy explains how to report an error, distinguish a product update from a factual correction, and document a material change. It does not promise a response deadline.
Policy correction, September 12, 2026: removed the blanket testing promise from the page description, clarified the editorial byline and AI assistance, and replaced unsupported historical assurances with explicit evidence and independence requirements.
Last reviewed: September 12, 2026.