wp-i18n-audit

To audit WordPress plugin PHP code for i18n bugs, scan files to check text-domain consistency, validate placeholder and pluralization patterns, and verify escaped translation helpers. This prevents broken translation extraction and runtime failures.

Translation strings go missing from a WordPress plugin .pot file when dynamic translation strings or variable text domains are used. Auditing code to ban variable domains and validate translation function usage resolves these extraction failures.

To check WordPress text-domain consistency during a theme migration, audit the PHP code to ensure all translation functions use the correct domain. This validates that text-domain loading hooks are properly configured and prevents runtime translation failures.

The best way to review WordPress internationalization correctness in contributor PRs is running an i18n audit that checks escaped output helpers, correct translation function selection, and pluralization patterns to produce a severity-sorted report.

Yes, the i18n audit checks WordPress escaped translation helpers and validates pluralization patterns. It ensures correct helper selection and verifies that placeholder formats match across singular and plural translation strings.

Yes, you can use this audit to diagnose translator-reported text-domain mismatches at runtime. It checks text-domain consistency, validates loading hooks, and identifies dynamic strings that break translation extraction and runtime display.