Quality control for WordPress audio publishingEditorial teams
Keep episode quality consistent across multiple contributors without asking every editor to think like an audio engineer.
EBU R128 audio QC for WordPress
Know an episode hits broadcast loudness before it goes live.
AudioLinter analyzes podcast audio to EBU R128 and one-click-repairs it to -16 LUFS with true peak below -1 dBTP, right inside WordPress. Uploaded files are deleted within 48 hours on EU servers.
-16 LUFS
Integrated loudness target
<= -1 dBTP
True-peak ceiling
48 h
Auto-deletion on EU servers
Who it is for
Built for teams that publish audio from WordPress, not for isolated desktop workflows
The product fits radio stations, newsroom workflows, campus media and podcast teams that already manage posts, episodes and media inside WordPress.
Stations and campus radio
Catch loudness issues, clipping risk and dead air before a post goes out on the site or gets distributed downstream.
Podcast operations
Give producers a lighter QC layer inside the CMS while still leaving publishing decisions explicit and reviewable.
How it works
A workflow that matches how publishing teams already operate
The product does not try to replace editorial judgment. It adds analysis, optional repair and clearer release confidence.
01
Upload or pick from the media library
Editors can start from a local file or an existing WordPress media item without leaving the publishing flow.
02
Review the analysis result
AudioLinter checks loudness, peak levels and dead air so teams know whether a post is ready to publish.
03
Repair and re-check when needed
If audio needs work, teams can generate a repaired file, reanalyze it and decide explicitly how to publish it.
Why the site matters
The website should sell the product and teach the workflow
AudioLinter becomes more credible when the public site explains not only the plugin, but also what findings mean and how to resolve them.
Marketing layer
Landing, pricing and product positioning should help people understand the value fast and move toward the right plan.
Docs layer
Setup, first analysis, repair workflows, quotas and product rules should live in one calmer documentation system.
Help layer
Teams should be able to learn what `too loud`, `peak too high` and `dead air` mean, including manual fixes in tools like Audacity.
Next on the site
Pricing, docs and troubleshooting should feel like one product.
The new website foundation is meant to support both monetization and trust: buy the plugin, understand the results and find the right fix path in the same place.