Documentation

WP Technical Site Auditor

Find and Fix Every Technical Issue on Your WordPress 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:

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.

Yes. A scan only reads - nothing on your site changes until you apply a fix yourself. Every fix records what it changes and can be undone under Fixes → Applied & history. .htaccess changes are backed up, the site is tested after the change, and the change is rolled back automatically if the site stops working. Database cleanups save the deleted rows first, so they can be restored for 30 days. Three actions cannot be undone, and say so: optimizing database tables (the rows stay the same) and, in Premium, deleting expired WooCommerce sessions and WooCommerce logs older than 30 days. Fixes that change something visible ask you to confirm first.
No. Scanning only runs when you start it (or on a schedule, in Premium). For visitors the plugin loads nothing except the small hooks of the fixes you switched on - and, in Premium, the modules you enabled. The scanner, the checks and the backup system are not loaded on normal page views.
Yes. The plugin works with any WordPress theme, classic or block theme. Problems that come from the theme and repeat on most pages (header, footer, menus) are reported once for the whole site, with sample pages, instead of once per page. Theme hygiene also checks whether the active theme and its parent have been closed on WordPress.org, look abandoned or have a pending update. Elementor, Divi and WPBakery are recognised, and Elementor and Divi have dedicated checks.
No. Yoast SEO, Rank Math, All in One SEO, SEOPress and The SEO Framework are recognised and their data is used where available. The checks look at what your pages actually output, so they work with or without an SEO plugin. The premium Meta Manager module cannot be enabled while any of the first four is active, so you never get duplicate meta tags.

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.

The plugin includes 298 checks in 27 groups. The free version includes 257 of them in 26 groups - all except the WooCommerce catalogue checks. The page builder checks only run when Elementor or Divi is installed, and the WooCommerce checks only when WooCommerce is active.
  • 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)
Premium adds 41 WooCommerce checks for the catalogue, performance and store operations.
No, but the free version is not a trial: it has no time limit and includes 257 checks, step-by-step instructions for every issue and 67 one-click fixes with undo. It fixes everything except search visibility and WooCommerce. Premium adds the SEO and visibility fixes, 41 WooCommerce checks and 12 WooCommerce fixes, scheduled scans, regression monitoring, scheduled maintenance, plugin-status alerts, backups and the Redirects, Meta and Breadcrumbs modules.
It depends on how many URLs your site has, how fast the server responds and which checks are enabled - external link checking, for example, takes longer. The scan runs in batches and shows its progress on the Issues page. A manual scan is driven from the admin page: if you leave the page, the scan continues when you open it again. Settings → Scanning shows your server limits and a recommended batch size.
Yes, and everything can be reversed. Every one-click fix records what it changes before it runs and can be undone under Fixes → Applied & history. .htaccess changes are backed up, the site is tested after the change, and the change is rolled back automatically if something breaks; on nginx and other servers without .htaccess the fix says why it cannot be applied. Database cleanups save the deleted rows and can be restored for 30 days - in the free version too. Fixes that change something visible, such as the permalink structure or product reviews, show what will change and ask you to confirm first.
Yes. The free version checks the store setup and security with 12 checks: cart, checkout and account pages, terms and privacy pages, payment method, tax, that the cart and checkout are not cached or indexed, REST API and Store API exposure, the legacy REST API, webhooks and checkout HTTPS. Premium adds 41 checks for the catalogue, performance and store operations (among them payment methods in test mode, pending database updates, outdated templates, switched-off order e-mails, tax rates and logs) plus 12 WooCommerce fixes. The link checker never follows add-to-cart, cart-removal or logout links, so a scan does not put products in a cart.
Partly, and honestly. Every scan checks the DNS of the domain WordPress sends from (SPF, DMARC, a mail server that can receive bounces and replies, and a DKIM key at the common selectors) and reports when the last e-mail WordPress tried to send failed. Under Settings → Advanced, "Send test e-mail" sends one message to the address you type and shows whether WordPress handed it over, the error if not, the From address and name used, and whether PHP mail() or SMTP was used. Neither can see whether the message lands in the inbox or in spam - check the test message itself for that. The DKIM check is a heuristic: a key under an unusual selector is not found, so it is only reported as a notice.
The free version reports which AI crawlers (GPTBot, ClaudeBot, Google-Extended and others) your robots.txt allows, blocks or does not mention. In Premium you tick the crawlers to keep out under Settings → Advanced. Saving adds a two-line group for each ticked crawler (for example "User-agent: GPTBot" followed by "Disallow: /") to the robots.txt WordPress generates, recorded as a fix with undo - unticking everything removes the groups again. Crawlers you leave unticked follow your normal rules. robots.txt is a request, not a lock: well-behaved crawlers honour it, others may not. A physical robots.txt file on the server cannot be changed this way, and the setting says so.
llms.txt is a young, community-proposed convention (llmstxt.org): a Markdown file in your site root that gives AI assistants a summary of your most important pages. Major search engines have said they do not use it, and not having one is not a problem. The check only reports whether a file exists. Premium can generate one from your site title, tagline and key pages, leaving out password-protected and noindexed pages; an existing file is backed up first and the change can be undone.

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.

A WordPress plugin (called Technical Site Auditor on WordPress.org) that scans your website for technical problems in SEO, performance, security, accessibility, database health, e-mail deliverability and WooCommerce. Every issue comes with step-by-step instructions, and the free version can fix everything except search visibility and WooCommerce with one click - every fix can be undone. Premium adds the search-visibility and WooCommerce fixes, automation, backups and the Redirects, Meta and Breadcrumbs modules.
Unlike cloud-based tools, the scan runs on your own server and the results stay in your own database. The plugin sees what external tools cannot - database health, plugin hygiene, settings, scheduled tasks - and it can fix what it finds, with undo. Results are rule-based, not AI guesses, and honest: the scan says how many pages could not be read, and an external link that does not answer is reported as "could not be verified" rather than broken.
WordPress 5.8 and higher, tested with WordPress 7.1. We recommend keeping WordPress updated to the latest version for security and compatibility.
PHP 7.4 and higher, tested with PHP 8.4. We recommend a PHP version that still receives security updates - PHP 8.1 stopped receiving them on 31 December 2025, and PHP 8.2 receives them until 31 December 2026. The plugin's own server check judges your version by the official dates.
Yes. The scanner fetches your pages like a visitor, in small batches, so the load is limited. On a weak server you can lower the batch size under Settings → Scanning, or (Premium) schedule the scan for a low-traffic time.
No, the limit is the same in both versions: up to 5,000 URLs per scan by default. Developers can raise or lower the limit with the wtsa_max_discovered_urls filter. Large sites are scanned in batches, and the scan tells you if the limit cut the URL list short.
We recommend: after significant changes and after plugin and theme updates, weekly for active sites with frequent new content, and monthly for stable sites. Issues that are new since the previous scan are marked "New", so you see straight away what has appeared. In Premium the scan can be scheduled, and the report e-mail can be limited to when new problems appear.
Yes. Settings → Scanning has an "Exclude URLs" field: one pattern per line, where * matches any characters - */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.
Critical: fix immediately - the problem significantly harms your site.
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).
The plugin checks what your pages actually output, not just whether an SEO plugin is installed. If a page has no meta description, has a canonical that points to a redirect, or is marked noindex although it is important, it is flagged - whichever plugin is responsible. "How to fix" tells you where the setting usually lives.
Yes. "Ignore" hides a single issue, and "Ignore this check everywhere" hides a check on every page, in this scan and in future ones. If you fixed something yourself, use "Mark as resolved". Ignored and resolved issues are listed under the Ignored and Resolved tabs on the Issues page and can be brought back at any time ("Restore", "Reopen" or "Stop ignoring").
Often, yes. Problems that come from the theme and repeat on most pages are already reported once for the whole site. Most one-click fixes are site-wide settings, so one fix resolves the problem on every page. In the "By check" view of the Issues page you handle one check at a time for all affected pages: "Fix" where a fix exists, or "Mark all as resolved" and "Ignore all".
The instructions are written for WordPress in general and name where the setting lives in common plugins and page builders. The issue details list the actual pages, files or products that were found. Some theme-specific problems may still require your theme documentation and adapting the steps to your setup.
Go to Fixes → Applied & history and click "Undo" for the fix - the change is removed and the original state restored. Undo never requires an active licence. .htaccess changes are also tested automatically and rolled back immediately if the site stops responding, and the switch to post-name permalinks (Premium) is rolled back if posts stop loading. Database cleanups can be restored for 30 days. Note that deactivating the plugin does not undo fixes - use Undo, or the setting that deletes all plugin data on uninstall.
Yes. Undo never requires a licence - not for Premium fixes either, and not after the licence has expired. Every applied fix and restorable database cleanup is listed under Fixes → Applied & history, and that is where you undo it.
Some issues need server-level changes (fix type Hosting, such as the PHP version or SSL certificate), changes to theme files or code (Developer), or content decisions (Manual, such as writing better meta descriptions). They come with step-by-step instructions under "How to fix". In the free version, issues with an SEO/visibility or WooCommerce fix also show the instructions instead of a Fix button.
There is no separate preview, but every fix has a description of what it changes, and fixes that change something visible show a dialog with what will change before they run. Everything can be undone under Fixes → Applied & history, and .htaccess changes are tested and rolled back automatically if anything goes wrong.
Fixes that change something visitors or search engines notice show a dialog that says what will change: switching on search engine indexing on a staging or development site, post-name permalinks, product reviews, hiding out-of-stock products, switching off a redirect rule, the author archive redirect and cleaning WooCommerce logs. The server refuses to run these fixes without the confirmation.
The plugin does not purge your page cache for you. With a caching plugin, a server cache or a CDN, the old version of a page can be served for a while after a fix. Clear the cache, then use "Re-check this URL" on the issue or run a new scan.
Results come from the last scan. Clear page caches and use "Re-check this URL" on the issue, or run a new scan. If the scan still finds the problem, the issue moves to the "Fix active, still detected" tab: the fix is on, but something else on your site (the theme, another plugin, the server) still produces the problem. Follow "How to fix" in that case.
Everything in the free version, plus:
  • 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
All of them except two categories. The 67 free one-click fixes cover security hardening and headers (including .htaccess changes with a site test and automatic rollback), database cleanups whose deleted rows can be restored for 30 days, performance, cleanup, content rewrites (http:// URLs, staging URLs, e-mail links, sample content) and accessibility. The SEO and search-visibility fixes (indexing, permalinks, canonical and noindex tags, sitemaps, robots.txt, llms.txt, AI crawlers, redirects, title tags) and the WooCommerce fixes are Premium. In the free version those issues show their step-by-step instructions instead of a Fix button. Every fix, free or Premium, can be undone.
Your license key activates Premium on your websites: Personal: 1 site. Professional: up to 5 sites. Agency: unlimited sites. Licenses renew annually. You activate the key under Settings → License in the plugin.
Yes. Click "Deactivate licence" under Settings → License on the old site (or deactivate the site under My Licenses in your account), then activate the key on the new site. Undo of applied fixes keeps working on the old site without a licence.
Yes. Yoast SEO is recognised and its data is used where available. The premium Meta Manager module cannot be enabled while Yoast is active, so you get no duplicate meta tags.
Yes. Rank Math is recognised and its data, such as per-page robots settings, is used where available. The premium Meta Manager module cannot be enabled while Rank Math is active.
Yes. WP Rocket is recognised as a caching plugin, and the checks about page caching take it into account - for example that the cart and checkout must not be cached. Help → Integrations in the plugin shows which integrations are active on your site and what they change. The plugin does not clear the WP Rocket cache for you after a fix.
Yes. There are six dedicated page builder checks, among them Elementor CSS printed inline, Google Fonts without font-display: swap and Divi static CSS files. Two one-click fixes are included in the free version: "Elementor: External CSS and font-display: swap" and "Divi: Enable Static CSS File Generation". WPBakery is recognised too.
Each site in a multisite network is scanned on its own. Backups and restores (Premium) change files and tables of every site in the network, so only a network super admin can use them.
No. The plugin has no telemetry and sends no usage statistics or personal data to us. The external requests it makes are: api.wordpress.org for core file, plugin hygiene and theme hygiene checks (during scans), DNS lookups for the e-mail checks, external link checking (if enabled) and, in Premium only, licence and update checks to pihlfelt.se.
Backups (Premium) are stored in 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.
Backups (Premium) have random file names and are only offered for download to administrators, through WordPress. The folder is protected with .htaccess and web.config files; nginx ignores those, so on nginx the Backups screen shows the one-line rule to add to the server configuration (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.
The plugin sends no personal data to us, and scan results stay in your own database. The test e-mail stores the time, the result, the From address and the mailer used, but not the recipient or the subject. Keep in mind that database backups (Premium) contain the whole database, including users, comments and any orders - they are kept on your server and should be handled like other personal data. Whether the site as a whole meets the GDPR is for you, as the data controller, to decide.
Redirect Manager is a premium module for 301, 302 and 307 redirects directly in WordPress. You enable it under Tools → Redirects. Features:
  • 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
The module cannot be enabled while Redirection, Safe Redirect Manager or 301 Redirects is active - use one redirect tool, not two. Without an active licence the module pauses and the redirects stop applying until the licence is renewed.
Meta Manager is a premium module for SEO metadata without a separate SEO plugin. You enable it under Tools → Meta. Features:
  • 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 module cannot be enabled while Yoast SEO, Rank Math, All in One SEO or SEOPress is active - they already do this.
Breadcrumbs is a premium module that adds breadcrumbs to your site. You enable it under Tools → Breadcrumbs. Features:
  • 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 with wtsa_the_breadcrumbs() in a theme template; the separator is set with the separator attribute
Google can show breadcrumbs in search results instead of the full address.

Need help?

Need more help?

Our support team is happy to help you with questions about the plugin.

Contact Us