Editorial guidelines

1. Authors are real people

Every published article is attributed to a named author with a public bio, expertise areas, and contact details on our authors page. We do not publish anonymous content. When a piece is written by more than one person, all contributors are credited; when an article is reviewed, the reviewer is credited separately.

2. AI assistance, human judgement

We use generative-AI tooling the same way our authors use a search engine, a spell-checker, or a code-formatter — to draft outlines, find alternative phrasings, and pull together facts that the author then verifies. We never publish unedited AI output. A human is responsible for every claim, every code sample, every recommendation. This is the same standard Google's own guidance asks publishers to follow.

3. Original perspective and information gain

An article only ships if it adds something the reader cannot easily find elsewhere — a benchmark we ran, a configuration we tested, a gotcha we hit, a pattern we noticed across many sites. Restating the first ten Google results in a fresh template is not publication; it is a draft we send back for revision.

4. Sourcing & citations

Statistics, quotes, technical specifications, and standards references link directly to the primary source — Google's developer documentation, RFCs, vendor changelogs, peer-reviewed papers, or the tool's own GitHub release notes. We avoid citing summary blogs as authoritative sources.

5. Dates we publish

Every article shows a published date and, when substantively revised, a last-updated date. Cosmetic edits (typos, tone) do not bump the update date. A factual revision, a tool behaviour change, or a recommendation change does. We do not backfill the publish date to make older content look newer.

6. Corrections policy

If we publish a factual error, we correct it as soon as we are alerted. The correction is appended to the bottom of the article in a dated note (so readers can see what changed) and the last-updated date is bumped. Reach the editorial team at info@krawly.io — we aim to acknowledge within one business day and publish the fix within five business days.

7. Tool descriptions and per-tool guides

Every tool on Krawly has an in-house written description, "how to use" walkthrough, and FAQ. These are not auto-generated from the API schema or the tool ID — they are written and reviewed by someone who has personally used the tool against real data and knows where it succeeds, fails, and rate-limits.

Tool guides are reviewed at minimum every six months, and immediately when the underlying behaviour changes (for example when a third-party source like a YouTube endpoint adds new fields or starts blocking requests).

8. Conflicts of interest & affiliates

Krawly does not currently run an affiliate program. If we comparatively reference another tool (e.g. "we use Hunter.io for email verification"), the recommendation is based on our actual usage and is disclosed inline. We do not accept payment for placement in our guides, comparison tables, or category pages.

9. Advertising

Krawly may display advertising via Google AdSense or similar networks. Ads are clearly labelled as advertising, never disguised as editorial content, and never influence the recommendations or rankings inside our guides. See our About page for the advertising disclosure in full.

10. Reader privacy in tool inputs

Tool inputs (URLs, text, files) are processed only to produce the result a reader requested and are not sold, shared, or used to build profiles. Detailed handling is described in our Privacy Policy.

11. What we will not publish

• Content designed to mislead readers about the source, author, or motivation behind it.
• Tool guides that would help someone bypass authentication, paywalls, or anti-fraud protections of third-party sites.
• Articles that exist only to host advertisements, with no meaningful information for readers.
• Auto-generated bulk pages targeting search-engine traffic without human review.
• Guides that we have not personally tested against real data.

12. How to reach the editorial team

For factual corrections, source updates, takedown requests, or to ask about a recommendation, please write to info@krawly.io. For general support questions about the tools themselves, the better address is info@krawly.io.