Site Launch Audit

Site Launch Audit scans your published content and settings for the small problems that embarrass a launch: an image without alt text, a "Sample Page" still published, a debug flag left on from staging. It is a launch readiness checklist, not a full site inspector, and it runs entirely on your server.

How to turn it on

1. Go to Divi Torque > Extensions.
2. Switch Site Launch Audit on. The change applies immediately.
3. Open Site Launch Audit from the Divi Torque menu.

Site Launch Audit is off by default.

The six checks

Missing alt text. Counts images without alt text in published content. An empty alt attribute counts as missing. You get one finding per page, with the number of images. Graded warning.

Placeholder content. Flags the default "Sample Page" and "Hello world!" if they are still published (warning), and any "Lorem ipsum" text found in published content (critical).

Staging and debug indicators. Warns when WP_DEBUG and WP_DEBUG_DISPLAY are both on, so PHP errors could reach visitors (critical). Warns when "Discourage search engines from indexing this site" is still checked in Reading Settings (warning). Notes when the site address looks like a staging or local hostname, such as a staging, dev, test or local subdomain, a .local or .test domain, or localhost (notice).

Unused modules. Lists Divi Torque modules that are enabled but not used on any page, so you can disable them in Module Manager. Graded notice. This check waits until the module usage scan has finished, so a very large site may not show it on the first run.

Broken integrations. Flags an active SMTP Mailer that still has the placeholder host (smtp.example.com) or a blank username, and a Google Places API key with no place added for Google Reviews. Graded warning.

Caching. Notes when no page caching or external object caching is detected. Some hosts cache at the server level where WordPress cannot see it, so this one is a notice, not a warning.

Reading the report

The report opens with three counters: Critical, Warning, and Notice. Below them, findings are sorted by severity. When a finding points at a specific page, it carries an Edit button that opens that page. Fix the criticals first, then work down.

Rescanning

Results are cached for one hour. Saving a post or page clears the cache, so the next time you open the report it runs again. The Rescan button in the report header runs everything immediately. Repeat fix and rescan until the report says no issues found.

What it deliberately does not do

The audit does not crawl links, check SEO titles, run color contrast or ARIA checks, or profile performance. Those need dedicated tools and human review. For accessibility and performance checks, see the Accessibility Inspector and Performance Inspector extensions.

The scan never makes outbound HTTP requests. The image check reads up to 300 published items, and each check keeps at most 50 findings, so the report stays fast on large sites.

Frequently asked questions

Who can see the report?
Users who can manage options, which means administrators on most sites. Both the report and the rescan require the manage_options capability.

Does the scan slow down my site?
No. It runs on the server when you open the report or press Rescan, and the result is cached for an hour. Visitors never trigger it.

Is Site Launch Audit part of Divi Torque Pro?
Yes. It is a Divi Torque Pro extension. See pricing.