Compatibility Issues

Conflicts with Caching Plugins

Tracking not working with page cache enabledLiteSpeed Cache

1. LiteSpeed

Issue: Tracking not working with aggressive caching

Solution: LiteSpeed Cache → Cache → Excludes → Add to “URI Exclude List”:

/wp-admin/admin-ajax.php?action=pulserank_track

2. WP Rocket

Issue: tracker.js combined/minified breaks functionality

Solution: WP Rocket → File Optimization → Excluded JavaScript Files:

/wp-content/plugins/pulserank/assets/js/tracker.js

3. W3 Total Cache

Issue: AJAX requests cached

Solution: W3TC → Page Cache → Advanced → Never cache URLs:

wp-admin/admin-ajax.php

4. Cloudflare APO

Issue: Full page caching bypasses tracking

Solution: PulseRank’s JavaScript tracker handles this automatically. No configuration needed. Tracking works even on Cloudflare-cached pages.

Conflicts with Security Plugins

AJAX blocked or bot detection bypassedWordfence

1. Wordfence

Solutions:

1. Wordfence → Firewall → Rate Limiting: Add to “How to treat Google crawlers”: Verified Bots Allowed
2. Wordfence → Firewall → Advanced Rules: Ensure /pulserank/ not in block list

2. Sucuri

Issue: AJAX requests returning 403

Solution: Sucuri Dashboard → Firewall → Access Control: Whitelist /wp-admin/admin-ajax.php, allow POST requests to AJAX endpoint

3. iThemes Security

Issue: Database tables not created (security hardening)

Solution: iThemes Security → Database Security: Temporarily disable “Prefix Database Tables”, deactivate and reactivate PulseRank, re-enable iThemes setting after

Conflicts with SEO Plugins

Duplicate schema markup or compatibility concerns

1. Yoast SEO

No known conflicts – PulseRank and Yoast work together

Note: Both generate Schema.org markup. To avoid duplication:

• Use Yoast’s structured data (more comprehensive)
• Set PulseRank Schema Level to “Basic” or “Enhanced”
• Or disable PulseRank schema entirely:

add_filter( 'pulserank_schema_enabled', '__return_false' );

2. RankMath & All in One SEO

Compatible – PulseRank detects existing schema and adapts. No conflicts reported.

Best Practice: Let your SEO plugin handle schema. Use PulseRank for AI-specific optimizations (llms.txt, visibility controls, content audit).

Conflicts with Page Builders

Content optimization audit doesn’t analyze page builder content

Elementor, Beaver Builder, Divi, etc.

Status: Known limitation

Issue: PulseRank analyzes post_content (WordPress content). Page builders store in custom meta fields. May not be fully analyzed.

Workaround:

• Use editor metabox for manual review
• Or analyze HTML output (coming soon)
• Future update will add page builder support