ProRank SEO

Advanced Settings

Fine-tune ProRank SEO with advanced configuration options. Access these settings from ProRank SEO → Support & Account → Advanced Settings tab.

Important

These settings can affect your site's functionality. Only modify if you understand the implications.

Debug & Development

Debug Mode

Enable detailed error logging for troubleshooting.

  • Default: Disabled
  • When to enable: Only when troubleshooting or requested by support
  • Scope: Admin and frontend

Log Level

Control the verbosity of ProRank's logging system.

  • error – Only critical errors
  • warning – Errors and warnings
  • info – General information
  • debug – Verbose debugging output

Performance Settings

API Timeout

Maximum time (in seconds) to wait for outbound WordPress HTTP requests used by ProRank integrations and services.

  • Default: 30 seconds
  • Range: 5–120 seconds

Cache Duration

How long (in seconds) to cache API responses and computed data.

  • Default: 3600 seconds (1 hour)
  • Range: 60–86400 seconds

Clear All Caches

Instantly clear all ProRank caches including API response, schema, SEO analysis, and module caches.

Security

Disable XML-RPC

Block XML-RPC requests to prevent brute-force attacks. Safe to enable unless you use XML-RPC clients.

  • Default: Enabled

Disable REST API for Non-Authenticated Users

Restrict public REST API access. Enable only if no external integrations rely on unauthenticated REST endpoints.

  • Default: Disabled

Remove Version Strings

Hide WordPress version from HTML source, RSS feeds, and script/style query strings.

  • Default: Enabled

Disable File Editing

Disable the theme and plugin file editor in WordPress admin.

  • Default: Enabled

WordPress Features

Disable Emojis

Remove WordPress emoji scripts and styles from the frontend.

  • Default: Disabled
  • Scope: Frontend and admin

Disable Gutenberg Block Editor

Revert to the Classic Editor. Only enable if you do not use Gutenberg blocks.

  • Default: Disabled

Disable Dashicons (Frontend)

Remove the Dashicon font from frontend pages for logged-out visitors. Safe unless your theme uses Dashicons on the public site.

  • Default: Disabled
  • Scope: Frontend only

Remove Global Styles

Remove the inline global styles and SVG filters that WordPress adds to every page.

  • Default: Disabled

Disable Password Strength Meter

Remove the zxcvbn password-strength script on account and checkout pages.

  • Default: Disabled

WooCommerce

Remove WooCommerce frontend overhead on pages that do not need it. Cart, checkout, and account pages always retain full WooCommerce functionality.

Disable WooCommerce Scripts

Remove WooCommerce scripts and styles from non-shop pages (homepage, blog posts, etc.).

  • Default: Disabled
  • Caveat: Enable only if non-shop pages do not use WooCommerce shortcodes or widgets

Disable Cart Fragments

Prevent AJAX cart-fragment calls on every page load. This removes the mini-cart update request that WooCommerce fires on non-transactional pages.

  • Default: Disabled

Disable WooCommerce Widgets

Deregister default WooCommerce sidebar widgets.

  • Default: Disabled

Disable WooCommerce Status Meta Box

Remove the WooCommerce status widget from the WordPress admin dashboard.

  • Default: Disabled
  • Scope: Admin only

Google Maps

Disable Google Maps Scripts

Block Google Maps API scripts from loading on the frontend. This dequeues any script whose source URL matches maps.googleapis.com or maps.google.com. It also strips matching script tags that bypass the WordPress enqueue system.

  • Default: Disabled
  • Scope: Frontend only – admin pages are never affected
  • When to use: When Google Maps is loaded by a plugin or theme but is not needed on most pages
  • When not to use: If your site relies on interactive Maps on every page

Exclusions

Comma-separated list of post IDs, post slugs, or URL substrings where Google Maps should remain loaded even when the disable toggle is on.

Example: contact, 3019, /our-clinics/

Third-Party Governance

Control when heavy third-party scripts load. When enabled, each category of scripts is delayed until user interaction (click, scroll, keypress, or touch). This reduces Total Blocking Time and improves Lighthouse performance scores without removing the scripts entirely.

How delay works

Delayed scripts are not removed. They are deferred until the visitor interacts with the page. Once interaction occurs, the scripts load and execute normally.

Delay Google Services

Delay Google Tag Manager, gtag.js, Google Analytics, Google Ads conversion scripts, and related measurement code until interaction.

  • Default: Enabled
  • Caveat: The first pageview may not be tracked if the visitor does not interact before leaving. If you need 100% pageview tracking, disable this toggle.

Delay Review Widgets

Delay review widget loaders such as Trustindex, Trustpilot, and similar embeds until interaction.

  • Default: Enabled

Keep Consent Scripts Non-Blocking

Apply ProRank non-blocking handling to consent management scripts such as CookieYes and Cookiebot. The consent banner still appears, but the loader script does not block the critical rendering path.

  • Default: Enabled
  • Caveat: If your consent manager relies on synchronous blocking to prevent other scripts from firing before consent, test thoroughly before enabling.

Delay Identity Widgets

Delay sign-in client scripts such as Google Sign-In until interaction.

  • Default: Enabled

Performance Profile

Profile

Controls which performance features are auto-enabled based on your site stack.

  • safe – Suppresses CSS/JS optimisation on page-builder sites (Elementor, Divi, Beaver Builder). Recommended for most sites.
  • balanced – Allows more optimisations but still suppresses high-risk CSS operations on certain builders.
  • aggressive – Enables all optimisations regardless of detected builder. Use only after thorough testing.
  • Default: Safe

Compatibility Mode

Auto-detect page builders and suppress risky optimisations. Disable only if you are confident your builder works with all ProRank performance modules.

  • Default: Enabled

Auto Rollback

Automatically revert performance changes if they cause errors on the frontend.

  • Default: Enabled

Performance Module Overrides

Force-enable specific performance modules that the compatibility profile would normally suppress on builder sites. Use these when you have tested a module and confirmed it works correctly on your site.

Expert use only

Overriding profile suppressions bypasses safety checks. If a module causes layout issues, disable the override and clear caches.

Available overrides:

  • CSS Optimisation (css_opt) – Force CSS minification and concatenation
  • JS Optimisation (js_opt) – Force JS defer/delay optimisation
  • Critical CSS – Force critical CSS generation
  • Unused CSS Removal – Force unused CSS detection and removal

Each override is independent. Enabling one does not affect the others.

Code Injection

Add custom code snippets to your site without editing theme files. Three injection points are available:

Head Code

Injected inside <head> at priority 1. Use for analytics tags, meta tags, or verification codes.

Body Open Code

Injected immediately after <body> opens via the wp_body_open hook. Use for GTM noscript fallbacks or consent manager placeholders.

Footer Code

Injected before </body> at priority 999. Use for chat widgets, tracking pixels, or deferred scripts.

Scope

Code injection runs on frontend page loads only. It is excluded from admin pages, login, REST API requests, AJAX, cron, WP-CLI, XML sitemaps, and RSS feeds.

Each snippet is output exactly once per page load (no duplicate output).

CDN URL Rewrite

Rewrite local static asset URLs (CSS, JS, images, fonts) to a CDN hostname for faster delivery.

CDN URL

The full CDN hostname including protocol, e.g. https://cdn.example.com. Leave blank to disable CDN rewriting.

Directories

Comma-separated list of directories to rewrite. Only URLs matching these directory prefixes are sent to the CDN.

  • Default: wp-content,wp-includes

Exclusions

Comma-separated URL substrings to exclude from CDN rewriting.

Cache invalidation

When the CDN URL setting changes, ProRank automatically clears its page cache, Elementor rendered cache, WP object cache, and WP Rocket cache (if active). You do not need to manually flush caches after enabling or disabling CDN rewriting.

Excluded contexts: Admin, login, REST, AJAX, cron, WP-CLI, sitemaps, and feeds are never rewritten.

Interaction with performance modules: CDN rewriting operates independently of the performance profile. It is not suppressed by compatibility mode or builder detection.

Debug Information

The bottom of the Advanced Settings tab displays:

  • Plugin Version – Currently installed version
  • Build Fingerprint – Unique identifier for the current build
  • Build Timestamp – When the current build was compiled
  • Build Commit – Git commit hash of the build

Share this information when filing support requests.

Troubleshooting

Admin page breaks after 1.1.0 update

If you updated to 1.1.0 and an admin page shows an error or blank content, update to 1.1.1 and hard-refresh your browser (Ctrl+Shift+R or Cmd+Shift+R). The 1.1.1 release fixes missing sprintf imports that affected some admin screens.