Ordlo Catalog Audit
Bad catalogue data doesn’t show on the shop front. It shows up in disapproved Google Shopping feeds, unindexed product pages, cart drop-offs on missing weights, and the support tickets that follow. Ordlo Catalog Audit scans your WooCommerce product catalogue in a single pass and surfaces the data quality issues that quietly cost you sales: missing SKUs, missing GTIN/UPC/EAN/ISBN barcodes, missing or zero prices, empty descriptions, missing weights, missing images, missing brands, duplicate identifiers and broken/orphaned variations. The full audit is free. Detect every issue here, fix them by hand in the WooCommerce editor, or upgrade to Ordlo Catalog Audit Pro to resolve issues one click at a time or in bulk without leaving the audit screen. What it checks Every check runs in the same scan. There’s nothing to configure first — the audit reads what WooCommerce already stores and flags what’s missing or wrong. Missing SKU – Published products and variations with an empty SKU. Variable parents and grouped products are excluded; they don’t carry SKUs by design. Duplicate SKU – Two or more products sharing the same SKU value. Fulfilment, picking and feed exports all assume SKUs are unique. Missing GTIN / UPC / EAN / ISBN – Products with no barcode identifier set. Google Shopping requires this for most categories, and missing GTINs are a common feed rejection cause. Duplicate GTIN / UPC / EAN / ISBN – Products sharing the same barcode value. WooCommerce requires this identifier to be globally unique. Missing featured image – Products with no featured image, which appears in catalogue pages, cart line items, Shopping feeds and most theme product cards. Missing product brand – Products with no product_brand term assigned. Runs only when WooCommerce Brands (or a compatible product_brand taxonomy) is active. Missing price – Simple and external products with no regular price. WooCommerce won’t add them to the cart and they’re invisible in feed exports. Zero price – Products priced at 0.00 that may be unintentional. Empty description – Products missing the long description. Empty short description – Products missing the short description that sits above the add-to-cart button in most themes. Missing weight – Non-virtual products with no weight configured. Empty weights silently break shipping rate plugins and label printing. Orphaned variations – Variation records whose parent product is missing – invisible to customers, but a problem once reports start counting products. Plus expanded image checks (missing variation images, missing alt text, broken featured images, thin galleries), expanded catalogue checks (duplicate titles, missing categories, uncategorized-only products, external products without URLs, visible out-of-stock items) and variation configuration checks (missing variation prices, missing managed stock quantities, inconsistent attributes, incomplete variable parents). More than a checklist Catalog health score – A dashboard score weighted by open-issue severity and catalogue size, with a health trend over time. Channel & integration readiness – Free readiness scoring for Google Shopping, Meta Commerce, marketplace identifiers and fulfilment/API integrations, with the blockers listed per channel. Per-channel blocker export – Download a CSV of the blockers and warnings for any channel straight from the dashboard. Optional MPN audit – Configurable manufacturer part number checks for marketplace readiness. Feed plugin detection – Recognises Google Listings & Ads, Facebook for WooCommerce, CTX Feed and Product Feed Pro. How it works Install the plugin. The audit lives under Ordlo → Catalog Audit. There’s no setup wizard and no required configuration. Click Run Full Audit. The plugin scans your catalogue in the background, paginated so it doesn’t time out on large stores. Browse the issues. Each check has its own tab with a count badge and a table of affected products. Click a row to open the WooCommerce editor. Mark issues as Resolved or Ignore to keep the dashboard honest, then re-run the audit to confirm they’re cleared. A first pass on a typical thousand-product store takes about a minute, and re-runs after a fix session take the same. Free vs Pro The detection layer is the whole audit, free here on WordPress.org. The fix layer is what Pro adds. Included in the free plugin: The full audit across every check above. Per-check issue tabs with counts and filters. Catalog health score and health trend. Channel & integration readiness scoring with per-channel blocker CSV export. Optional MPN audit and feed plugin detection. Direct link to the WooCommerce editor for each issue. Mark as Resolved / Ignore, and re-run on demand. Settings to enable or disable individual audit types. Ordlo Catalog Audit Pro adds the fixes: One-click Fix per issue (SKU, GTIN/UPC/EAN/ISBN, price, weight, descriptions, featured image and brand). Bulk Fix All for a single check at once. Auto-generate SKUs from a configurable pattern, with collision checks. Assign a placeholder image or a default weight in bulk. Delete All Orphaned Variations in one go. CSV import for offline batch fixes. Priority email support. Free is permanent – no expiry, no nag. Pro is a separate plugin you install alongside the free one. Built for real stores Reads native WooCommerce data – no schema changes. HPOS-ready (WooCommerce High-Performance Order Storage compatible). Works with WooCommerce 8.0+.
VideoWhisper Security Audit
VideoWhisper Security Audit creates WordPress site health, exposure, vulnerability, integrity, readiness, and performance reports for site administrators. The plugin is designed to help administrators review site activity and configuration with AI agents or by using the built-in admin report. The free plugin is read-only. It reports findings and does not perform cleanup, quarantine, updates, file changes, role changes, or other remediation actions. Plugin homepage: https://promptaur.com/wordpress/security-audit/ Main features: Admin Scan tab with queued scan processing, live progress, per-task status, resume/retry controls, scan date, report summary, and report findings. Configurable scan execution mode: queued scans by default, or legacy synchronous scans for small/basic sites. Importance-based scan modes: full, critical/high/medium, and critical-only. Report filters for issues only or all check results, including passed informational checks when available. JSON and plain-text Markdown report output. Optional token-protected REST report endpoint. Optional token-protected MCP endpoint for read-only AI-agent reports. Optional WordPress 6.9+ Abilities for admin-only read-only security overview, vulnerability, exposure, integrity, readiness, performance risk, and Markdown audit reports. Optional exposure of those abilities through the official WordPress MCP Adapter when installed separately. Read-only integration with VideoWhisper AI Site Manager – Using ChatGPT Claude Codex when both plugins are active, including report reads and agent-friendly queued scan tools. Separate REST and MCP enable/disable settings. Generated local tokens with rotation controls and last-used metadata. REST/MCP per-minute rate limiting and optional exact IP allowlist. Admin scan cooldown, hourly scan limit, and separate agent scan cooldown. Category toggles for security, integrity, performance, readiness, commerce, community, and backup checks. Redacted AI report defaults, with optional exact version and path disclosure for MCP reports. Optional WPVulnerability API lookups for installed plugin vulnerability data. Disclaimers in the admin report and Agents tab about report limits, sensitive information, and third-party AI analysis. Queued scans Queued scanning is the default admin interface. It splits inventory, exposure, vulnerability, integrity, performance, and readiness checks into small AJAX-polled batches. This avoids browser, proxy, and PHP timeout issues on larger sites while showing progress and recent queue events. Failed tasks can be retried, and unfinished jobs can be resumed from the Scan tab. Administrators that prefer the original one-request scan flow can switch Scan execution to “Synchronous legacy scan” in Settings. Local checks Security Audit currently checks local WordPress signals including: Plugin and theme updates. Inactive plugins. Administrator account count. Expected WordPress database tables. Administrator role capabilities. Upload directory writability. Debug log file presence. Git metadata in the web root. XML-RPC availability. Common homepage security headers. Autoloaded option size. Expired transient count. WP-Cron disabled state. Permalink structure. Search engine visibility setting. Privacy Policy page presence. Basic WooCommerce page readiness when WooCommerce is active. Optional WPVulnerability plugin vulnerability lookups. Agent and API reports REST and MCP endpoints are disabled by default. When enabled, Security Audit automatically generates local tokens. Anyone with a valid token can read the selected report until the token is rotated, so treat tokens as sensitive secrets. The REST report endpoint supports: key: generated REST token. A bearer token can also be used. mode: full, important, critical, or changed. report: issues or all. format: omit for JSON, or use markdown for plain Markdown output. The MCP endpoint supports read-only tools for security summary, vulnerability, exposure, integrity, performance risk, readiness, and Markdown audit reports. Tool arguments include mode and report. When VideoWhisper AI Site Manager is active, Security Audit also registers agent tools for latest summary/report reads, synchronous scan refreshes for small sites, scan task discovery, queued scan creation, queue batch processing, queue status polling, and retrying failed scan tasks. On WordPress 6.9+, administrators can also enable WordPress Abilities. These abilities are admin-only, read-only, and permission-checked with manage_options by default. They can optionally be marked public for the official WordPress MCP Adapter, which must be installed separately. Existing REST and MCP endpoints remain available and are not replaced. Some sites use an OAuth, firewall, or bearer-auth layer that consumes Authorization: Bearer before the Security Audit route receives the request. If standalone Codex MCP bearer setup returns oauth_token_invalid or a similar upstream bearer-auth error, use the MCP path-token URL shown on the Agents tab instead of the bearer URL. Endpoint protection controls include: REST/MCP requests per minute per IP. Separate agent scan cooldown. Optional exact IPv4/IPv6 allowlist. Token rotation. Developer hooks Security Audit exposes generic hooks that any plugin can use to extend scan data, reports, admin UI, and Site Manager integration: vwsa_latest_snapshot filters the latest stored snapshot before reports use it. vwsa_scan_settings filters normalized scan settings for a scan context. vwsa_scan_inventory filters inventory data before findings are finalized. vwsa_scan_findings filters findings before snapshot lifecycle metadata is saved. vwsa_scan_queue_tasks filters task definitions shown and queued by the Scan tab. vwsa_scan_queue_process_task processes extension-owned queue tasks without coupling the extension to Free internals. vwsa_snapshot_before_save filters the completed snapshot before it is stored. vwsa_snapshot_saved fires after a snapshot is stored. vwsa_report filters built report output. vwsa_site_manager_integration filters the Site Manager integration definition. vwsa_admin_tabs filters admin tabs. vwsa_admin_render_tab lets extensions render custom admin tabs. vwsa_admin_scan_panel_after renders generic content after the scan panel. vwsa_admin_findings_before renders content before findings. vwsa_admin_finding_card_start renders content inside a finding card. vwsa_admin_finding_actions filters per-finding action links. vwsa_admin_findings_after renders content after findings. Important limitations and disclaimers Security Audit reports are informational only. Findings and AI-ready reports may be incomplete, inaccurate, outdated, or unsuitable for a specific site or legal situation. Security Audit does not provide legal advice, compliance certification, professional security advice, malware cleanup, incident response, or a guarantee that a site is secure. Administrators should verify findings and consult an experienced security, technical, or legal provider before making important changes. REST and MCP reports may expose sensitive operational information, including site configuration, component versions, possible vulnerabilities, paths, and other details. Enable agent endpoints only when you understand where the data will be sent and who can access the token. Third-party AI agents may produce incomplete, incorrect, unsafe, or unsuitable recommendations. Review all recommendations before acting and do not perform destructive changes without backups and appropriate professional review. This plugin is not a firewall, malware cleaner, legal compliance tool, vulnerability scanner guarantee, or replacement for backups, security monitoring, dedicated scanners, or experienced administrators. External services By default, Security Audit does not call external vulnerability services. If the administrator enables WPVulnerability lookups, the plugin sends installed plugin slugs to the public WPVulnerability API at https://www.wpvulnerability.net/ to retrieve vulnerability data. No API key is required for normal component lookups. Responses are cached locally. See: https://www.wpvulnerability.com/ https://docs.wpvulnerability.com/ https://www.wpvulnerability.com/privacy/ https://www.wpvulnerability.com/license/ During scans, Security Audit may also make a local HTTP HEAD request to the site’s own homepage URL to inspect response headers. This request is sent to the configured site URL, not to a third-party vulnerability service.
