How Podcastools is built and reviewed
This methodology applies to tool explanations, guides, examples, internal recommendations, and structured data across Podcastools.
Last reviewed October 2, 2026
1. Define one job
Each page targets a specific creator task and states the input, output, workflow, and limitations. We avoid adding a tool simply to target a search phrase.
2. Prefer primary sources
Technical requirements and policy claims link to the platform, standards body, regulator, or measurement organization responsible for them whenever a primary source is available.
3. Separate facts, drafts, and estimates
Generated copy is a draft. Public rankings and reviews are point-in-time observations. Revenue figures are scenarios whose inputs should remain visible. None is presented as a guaranteed outcome.
4. Review the complete result
We test the path from page load through the tool’s main action and output. Content changes are checked for crawlability, internal links, structured data, mobile layout, and build errors.
5. Measure and update
We use aggregate search and product analytics to find broken journeys and declining pages. Material updates receive a real review date; sitemap dates are not changed on every request.
Processing and limits
The tool catalog is the source of truth for page explanations and software metadata. Noise cleanup, cover art, ID3 editing, quote cards, banners and document exports run in the browser where stated. Server renders handle audiograms and graphics ZIP files. Apple directory and public RSS lookups show their retrieval time and incomplete coverage. Text generation uses the existing Google integration.
Active AI drafting tools validate the response structure and selected factual constraints. Invalid or unavailable output falls back to a labeled deterministic template. These checks cannot prove every statement correct; creators must review their own facts, quotations, links and rights. Directory searches cannot establish legal name availability, historical review completeness or a verified audience size.
A shared platform rule limits expensive active-tool POST requests to 20 per IP per 10 minutes. It limits bursts and does not guarantee a global spending cap. Inputs stay in the page when blocked. Transcription and jingles retain their existing processing behavior and are excluded from this update.
Plausible measures traffic; PostHog measures product actions. Product events contain action metadata and attribution rather than names, transcripts, email addresses or file contents. Public source caching has stated freshness; user-specific API results are served with no-store.
Corrections
Send a correction to hello@podcastools.com with the page URL, the disputed statement, and a primary source when possible. We review corrections for both the page and any related tool guidance.