Documentation
WP Technical Site Auditor
Find and Fix Every Technical Issue on Your WordPress Site
Guides
Getting Started
Getting Started with Technical Site Auditor
Install the plugin, find your way around the menu and run your first scan.
Running Scans
How the scan works, scan completeness, filters and re-checks.
Understanding Issues
Severity levels, fix types and the tabs on the Issues page.
One-Click Fixes and Undo
Which fixes are free, how to apply them and how to undo them.
License Activation
Activate, move and renew your Premium license - and what happens when it expires.
Backup and Restore
Undo data for fixes, backups of the database, themes and plugins (Premium), and safe restore.
WooCommerce
12 free checks for store setup and security, 41 checks and 12 fixes in Premium.
Scheduled Scans
Automatic scans, regression monitoring and scheduled maintenance (Premium).
E-mail Reports and Alerts
An HTML report after scheduled scans and plugin-status alerts (Premium).
CSV Export
Export the filtered issue list for analysis and reporting.
Redirect Manager
Manage 301/302/307 redirects directly in WordPress.
Troubleshooting
Solve common problems with scans and fixes.
Meta Manager
Learn how to use Meta Manager to manage SEO metadata on your WordPress site.
Breadcrumbs
Learn how to use the Breadcrumbs module to add SEO-friendly breadcrumbs to your site.
Questions & answers
Common Questions
A page counts as "could not be read" when the request fails (a timeout or connection error), when the page answers with HTTP 400 or higher, when its HTML cannot be parsed, or when processing it crashes twice in a row (one attempt plus one retry - then it is skipped).
The scan completeness report on the Overview and Issues pages says how many pages could not be read and why, so a "clean" result never hides pages that were never checked.
What you can do: open the page yourself to see whether it loads, run the scan again when the server is less busy, or adjust the batch size and timeout under Settings → Scanning (which also shows a recommendation based on your server limits).
The check fires when a page's HTML document is larger than 1 MB, and it counts as critical. The usual cause is CSS, scripts or images embedded directly in the page.
Common causes and fixes:
- Inline CSS from a page builder - in Divi, enable Static CSS File Generation; in Elementor, set the CSS Print Method to External File
- Base64 images (data:image/...) and inline SVG sprites - replace them with image files
- Very long listings - show fewer posts or products per page
- Unused or hidden page builder sections - remove them
A link points to an e-mail address but has no mailto: in front of it, so the browser treats the address as a page and the visitor lands on a broken page. For example:
- Wrong:
<a href="[email protected]"> - Correct:
<a href="mailto:[email protected]">
Solution: the one-click fix "Add mailto: to Email Links" (included in the free version) corrects these links in post and page content and can be undone under Fixes → Applied & history. Links in menus, widgets and templates need to be changed by hand.
Everything in the free version keeps working: all checks except the WooCommerce catalogue checks, and the 67 free fixes. Fixes you already applied stay in place, and undo never requires an active licence.
Without an active licence you cannot apply new Premium fixes (SEO/visibility and WooCommerce), and scheduled scans, scheduled maintenance and the Redirects, Meta and Breadcrumbs modules pause - enabled modules show as "Enabled, but paused". That means redirects from the Redirect Manager stop applying until the licence is renewed. You also stop receiving updates and support from pihlfelt.se. Everything comes back when you renew.
- Security (30) - HTTPS, security headers, HSTS, downloadable sensitive files, salts, PHP errors shown to visitors, XML-RPC, user enumeration
- Meta & head (25) - titles, meta descriptions, duplicates across the site, Open Graph, Twitter Cards, canonical
- Robots & indexing (20) - robots.txt, sitemaps, noindex, X-Robots-Tag, hreflang
- Performance (20) and CSS & JavaScript (9) - render-blocking files, speculative loading, DOM size, page size
- System health (18) - core file integrity, scheduled tasks, loopback, REST API and six e-mail deliverability checks
- Content (12) and Images (12) - headings, thin content, sample content, image dimensions, lazy loading, WebP/AVIF, alt text
- WooCommerce store setup & security (12) - pages, terms, payment, tax, caching, REST API and Store API
- Database health (11), Server & hosting (11), Schema (10), Accessibility (10)
- Internal links (6), External links (6), Plugin hygiene (6), Page builders (6), Cleanup (5), URL structure (5), 404 page (5)
- Redirects (4), Fonts (4), Iframes (4), Breadcrumbs (3), AI visibility (2), Pagination (1)
Scan results are stored in your own WordPress database and are not sent to us. During a scan your server makes these requests:
- To your own site: pages, robots.txt, sitemaps and a few probe URLs
- To api.wordpress.org: the WordPress version and locale for the core file checksums, and the directory slugs of installed plugins and themes that WordPress.org already serves updates for (never premium or custom plugins)
- DNS lookups for your domain and the sending domain (SPF, DMARC, MX, DKIM)
- To external links in your content, if the External Links check is enabled
"Send test e-mail" sends one message through your site's own mail setup when you click it. Only Premium contacts pihlfelt.se, for the licence and updates - the free version from WordPress.org never does.
wtsa_max_discovered_urls filter. Large sites are scanned in batches, and the scan tells you if the limit cut the URL list short.
*/private/*, for example, skips every URL containing /private/. That is also where you choose which content types are scanned. Useful for test pages, large archive sections and the like.
Warning: fix soon - the problem hurts performance, security or SEO.
Notice: consider addressing - a suggestion for improvement.
Every issue also has a fix type: One-click fix (a fix exists), Manual (step-by-step instructions), Developer (needs changes to code or templates) or Hosting (needs a change by your host).
- SEO and search-visibility fixes - indexing, post-name permalinks, attachment pages, canonical tags, noindex for empty archives, attachments and internal search results, the core sitemap, the sitemap line in robots.txt, llms.txt, AI crawler blocking, redirect chains and rules, links through redirects, the author archive and title-tag support - all with undo
- 41 WooCommerce checks for the catalogue, performance and store operations, plus 12 WooCommerce fixes
- Scheduled scans - daily, weekly, every two weeks or monthly, with an HTML e-mail report that can be limited to when new problems appear
- Regression monitoring - what is new, resolved or came back since the previous scan, issue history and a health score trend
- Scheduled maintenance - chosen database cleanups on a schedule, each run undoable for 30 days, with a summary e-mail
- Plugin-status alerts - an e-mail when an installed plugin is closed, removed or abandoned on WordPress.org
- Backups of the database, themes and plugins with a safe restore (uploads and wp-config.php are not included)
- Presets (Minimal, Balanced, Performance) that switch on a curated set of fixes in one go
- Modules: Redirect Manager, Meta Manager and Breadcrumbs
- Priority support and updates from pihlfelt.se
wp-content/tsa-backups/ with 32 random characters in their file names and are protected by .htaccess and web.config files; on nginx the Backups screen shows the rule to add to the server configuration. Backups older than 30 days are deleted automatically. They are kept on the same server as the site, so keep a copy elsewhere too. Undo data for fixes and the rows deleted by database cleanups (kept for 30 days) are handled by the plugin and exist in both versions.
location ^~ /wp-content/tsa-backups/ { deny all; }). A restore first creates a restore point, refuses damaged or truncated backups and archives with unsafe file names before anything is changed, runs only the kind of statements a backup made by the plugin contains, and swaps the database in as the last step. Backups cover the database, themes and plugins - not uploads or wp-config.php - and are kept on the same server, so keep a copy elsewhere too.
- Exact, prefix or regular-expression matching
- Loop detection when a redirect is saved
- Hit counts and the time of the last hit
- CSV import and export, and a test tool for your rules
- SEO title and meta description per post and page, in the "SEO Meta" box below the editor
- The same fields for categories, tags and other public taxonomies
- Open Graph title, description and image
- Robots (noindex, nofollow) and a canonical URL override per page
- The trail is built from the page hierarchy, categories, taxonomies, dates, authors and search
- Structured data (schema.org BreadcrumbList as JSON-LD)
- WooCommerce: Shop › Category › Product
- Placed with the
[wtsa_breadcrumbs]shortcode (in a Shortcode block, a widget or the editor) or withwtsa_the_breadcrumbs()in a theme template; the separator is set with theseparatorattribute
Need help?
Need more help?
Our support team is happy to help you with questions about the plugin.
Contact Us