Skip to main content

​
Troubleshooting Overview

This comprehensive troubleshooting guide helps you resolve common issues with the LLMTAG WordPress plugin and provides solutions for various scenarios.

Quick Problem Resolution

Common Issues • Step-by-Step Solutions • Diagnostic Tools • Expert Support

​
Common Issues

​
llmtag.txt File Issues

​
File Not Accessible (404 Error)

Symptoms:
  • https://yourdomain.com/llmtag.txt returns 404 error
  • File not visible in browser
Possible causes:
  • File not uploaded to correct location
  • Incorrect file name
  • Server configuration issues
Solutions:
  1. Check file location: Ensure llmtag.txt is in your WordPress root directory
  2. Verify file name: Must be exactly “llmtag.txt” (case-sensitive)
  3. Check file permissions: Set to 644
  4. Clear caches: Clear all caching plugins and CDN caches
  5. Contact hosting provider: If issues persist
Symptoms:
  • https://yourdomain.com/llmtag.txt returns 403 Forbidden
  • File exists but not accessible
Possible causes:
  • File permissions issues
  • Server security settings
  • .htaccess rules blocking access
Solutions:
  1. Check file permissions: Set to 644
  2. Review .htaccess rules: Look for rules blocking .txt files
  3. Check server security: Review server security settings
  4. Contact hosting provider: For server-level issues
Symptoms:
  • https://yourdomain.com/llmtag.txt returns 500 Internal Server Error
  • Server logs show errors
Possible causes:
  • Server configuration issues
  • Plugin conflicts
  • Corrupted file
Solutions:
  1. Check server error logs: Look for specific error messages
  2. Deactivate other plugins: Test with other plugins temporarily disabled
  3. Recreate the file: Delete and regenerate the llmtag.txt file
  4. Check server resources: Ensure adequate server resources

​
AI Agent Blocking Issues

​
AI Agents Not Being Blocked

Symptoms:
  • AI agents still accessing content
  • No blocked requests in analytics
  • Protection appears inactive
Possible causes:
  • Protection not enabled
  • AI agent not in database
  • Server configuration issues
  • Caching problems
Solutions:
  1. Verify protection status: Check that protection is enabled in plugin settings
  2. Update AI agent database: Ensure database is up to date
  3. Check .htaccess rules: Verify server rules are properly configured
  4. Clear all caches: Clear WordPress, server, and CDN caches
  5. Test with different agents: Try blocking with various AI agent user-agents
Symptoms:
  • Legitimate users being blocked
  • Normal traffic affected
  • User complaints about access issues
Possible causes:
  • Overly broad user-agent matching
  • Incorrect agent identification
  • Browser extensions mimicking AI agents
Solutions:
  1. Review blocked requests: Check analytics for false positives
  2. Refine user-agent matching: Adjust matching rules to be more specific
  3. Add exceptions: Create whitelist for legitimate users
  4. Adjust blocking sensitivity: Make blocking rules less aggressive
Symptoms:
  • Slow page load times
  • High server resource usage
  • Timeout errors
Possible causes:
  • Large AI agent database
  • Inefficient blocking rules
  • Server resource limitations
Solutions:
  1. Optimize agent database: Remove unused agents
  2. Simplify blocking rules: Use more efficient rule patterns
  3. Enable caching: Use caching to reduce processing overhead
  4. Upgrade server resources: Consider server upgrade if needed

​
Analytics Issues

​
No Data in Analytics

Symptoms:
  • Empty analytics dashboard
  • No blocked requests shown
  • No activity data
Possible causes:
  • No AI agents accessing site
  • Analytics not enabled
  • Database issues
  • Plugin configuration problems
Solutions:
  1. Wait for traffic: Allow 24-48 hours for data to appear
  2. Enable analytics: Check that analytics are enabled in settings
  3. Check database connectivity: Verify database is accessible
  4. Test with simulated requests: Use tools to generate test data
  5. Check plugin configuration: Verify all settings are correct
Symptoms:
  • Partial analytics data
  • Missing information
  • Inconsistent reporting
Possible causes:
  • Caching issues
  • Partial blocking configuration
  • Time zone problems
  • Data processing errors
Solutions:
  1. Clear all caches: Clear WordPress, server, and CDN caches
  2. Review blocking configuration: Ensure all agents are properly configured
  3. Check time zone settings: Verify time zone configuration
  4. Review data processing logic: Check for errors in data processing
Symptoms:
  • Slow analytics loading
  • High database usage
  • Timeout errors in analytics
Possible causes:
  • Large amounts of data
  • Inefficient queries
  • Database optimization issues
Solutions:
  1. Optimize database queries: Review and optimize analytics queries
  2. Clean up old data: Remove old analytics data
  3. Enable query caching: Use database query caching
  4. Consider data archiving: Archive old data to improve performance

​
Diagnostic Tools

​
Built-in Diagnostics

​
System Health Check

1

Access Diagnostics

Go to LLMTAG > Tools > System Health in your WordPress admin.
2

Run Health Check

Click Run Health Check to scan for common issues.
3

Review Results

Review the diagnostic results and address any issues found.
4

Export Report

Export the health check report for support purposes.

​
Connection Test

1

Test llmtag.txt Access

Use the built-in connection test to verify file accessibility.
2

Test AI Agent Blocking

Test blocking functionality with simulated AI agent requests.
3

Test Analytics

Verify analytics data collection is working properly.
4

Review Test Results

Address any issues identified in the test results.

​
External Diagnostic Tools

​
Online Validators

LLMTAG Validator

Validate your llmtag.txt file syntax and format

HTTP Status Checker

Check HTTP status codes and response headers

User-Agent Tester

Test different user-agent strings

Performance Tester

Test website performance and loading times

​
Browser Developer Tools

1

Open Developer Tools

Press F12 or right-click and select “Inspect Element”.
2

Check Network Tab

Look for requests to llmtag.txt and any error responses.
3

Check Console Tab

Look for JavaScript errors or warnings.
4

Test User-Agent

Use the Network Conditions tab to test different user-agents.

​
Step-by-Step Troubleshooting

​
Issue: llmtag.txt Not Accessible

1

Check File Existence

Verify the file exists in your WordPress root directory.
2

Check File Permissions

Ensure file permissions are set to 644.
3

Check Server Configuration

Verify your web server is configured to serve .txt files.
4

Clear Caches

Clear all caching plugins, CDN caches, and browser caches.
5

Test with Different Tools

Use multiple tools to test file accessibility.
6

Contact Hosting Provider

If issues persist, contact your hosting provider for assistance.

​
Issue: AI Agents Not Being Blocked

1

Verify Protection Status

Check that AI protection is enabled in plugin settings.
2

Update Agent Database

Ensure the AI agent database is up to date.
3

Check .htaccess Rules

Verify that .htaccess rules are properly configured.
4

Test with Simulated Requests

Use tools to simulate AI agent requests and test blocking.
5

Review Server Logs

Check server logs for blocked requests and any errors.
6

Adjust Blocking Rules

Fine-tune blocking rules based on test results.

​
Issue: Analytics Not Working

1

Enable Analytics

Ensure analytics are enabled in plugin settings.
2

Check Database Connectivity

Verify database connection and permissions.
3

Wait for Data

Allow 24-48 hours for analytics data to appear.
4

Generate Test Data

Use diagnostic tools to generate test analytics data.
5

Review Configuration

Check all analytics-related settings and configurations.
6

Check for Conflicts

Test with other plugins deactivated to identify conflicts.

​
Performance Optimization

​
Common Performance Issues

Slow Page Loads

Causes: Heavy blocking rules, large agent database Solutions: Optimize rules, enable caching, upgrade server

High Memory Usage

Causes: Large analytics data, inefficient queries Solutions: Clean old data, optimize queries, increase memory limit

Database Overload

Causes: Frequent analytics writes, complex queries Solutions: Optimize queries, enable query caching, archive old data

Server Timeouts

Causes: Complex blocking logic, server resource limits Solutions: Simplify rules, increase timeout limits, upgrade server

​
Optimization Strategies

1

Enable Caching

Enable WordPress caching and CDN for better performance.
2

Optimize Database

Clean up old analytics data and optimize database queries.
3

Simplify Rules

Use simpler, more efficient blocking rules.
4

Monitor Performance

Use performance monitoring tools to track improvements.
5

Upgrade Resources

Consider upgrading server resources if needed.

​
Plugin Conflicts

​
Common Conflicts

Conflicting plugins:
  • WP Rocket
  • W3 Total Cache
  • WP Super Cache
Solutions:
  • Clear all caches after plugin changes
  • Configure cache exclusions for llmtag.txt
  • Update cache settings for AI agent blocking
Conflicting plugins:
  • Wordfence
  • Sucuri Security
  • iThemes Security
Solutions:
  • Whitelist LLMTAG plugin files
  • Configure security rules to allow llmtag.txt
  • Adjust firewall settings if needed
Conflicting plugins:
  • Google Analytics
  • MonsterInsights
  • Jetpack Analytics
Solutions:
  • Configure analytics to work together
  • Avoid duplicate tracking
  • Use different tracking methods

​
Conflict Resolution

1

Identify Conflicts

Deactivate other plugins one by one to identify conflicts.
2

Configure Settings

Adjust settings in conflicting plugins to work with LLMTAG.
3

Update Plugins

Ensure all plugins are updated to latest versions.
4

Contact Support

Contact plugin developers for compatibility assistance.

​
Getting Help

​
Self-Help Resources

Documentation

Complete plugin documentation and guides

FAQ

Frequently asked questions and answers

Video Tutorials

Step-by-step video guides

Community Forum

Community support and discussions

​
Professional Support

Email Support

Response time: 1-2 business days Best for: Complex technical issues Contact: [email protected]

Live Chat

Availability: Business hours Best for: Quick questions Access: Available in plugin dashboard

Priority Support

Response time: 4-8 hours Best for: Critical issues Available: Pro users only

Custom Development

Timeline: Varies by project Best for: Custom implementations Contact: [email protected]

​
Support Information

When contacting support, please include: