Troubleshooting

SEO plugin conflicts

When another SEO plugin (Yoast, Rank Math, All in One SEO, SEOPress, The SEO Framework, or Slim SEO) is active alongside CitedPro, the plugin automatically disables its own SEO meta output to prevent duplicate title tags and meta descriptions. All other CitedPro features (AI discovery files, bot tracking, analytics, Smart Generate) continue to work normally.

A yellow admin notice will appear identifying the conflicting plugin and providing a quick link to deactivate it. To resolve the conflict:

• Option A (recommended):Import your data from the existing SEO plugin, verify everything transferred correctly, then deactivate the old plugin
• Option B: Keep both plugins active. CitedPro's AI features will work alongside the other plugin's SEO output

Files not generating

AI discovery files (llms.txt, llms-full.txt) require a minimum amount of business data before they can be generated. CitedPro checks for at least a business name and business description (the has_basics check).

If files are not generating:

1. Go to CitedPro → Setup and verify both the business name and description fields are filled in
2. Save your changes
3. Return to the Dashboard and click Generate Files

If the fields are filled in but files still do not generate, check that the target directory is writable. CitedPro attempts to write to the WordPress root directory first, then falls back to wp-content/uploads/cited/.

llms.txt returning 404

If visiting yoursite.com/llms.txt returns a 404 error:

1. Flush rewrite rules: Go to Settings → Permalinks and click Save Changes. This refreshes WordPress's URL routing and registers CitedPro's virtual file handlers.
2. Check for plugin interference: Some security or caching plugins may intercept requests for .txt files before WordPress can handle them. Temporarily disable suspect plugins to test.
3. Check file location setting: In CitedPro → Settings, verify whether files are set to root or uploads directory, and confirm the files exist at the expected location.

robots.txt not showing CitedPro section

CitedPro manages robots.txt virtually through WordPress's built-in robots.txt handler. If a physical robots.txt file exists in your WordPress root directory, WordPress (and CitedPro) cannot modify it because the web server serves the static file directly.

CitedPro automatically detects and migrates physical robots.txt files to the virtual system. If the CitedPro section is missing:

1. Check if a physical robots.txt file exists in your site root
2. If it does, delete it or rename it (CitedPro will have already imported its contents)
3. Flush rewrite rules by visiting Settings → Permalinks and clicking Save

Bot tracking not recording visits

If the Analytics tab shows no bot visit data:

• Check tracking is enabled: Go to CitedPro → Settings and verify that bot tracking is toggled on
• Verify cron is running: CitedPro relies on wp_cron for data cleanup. If cron is disabled on your site, data may accumulate but not display correctly. Verify cron status with a plugin like WP Crontrol or check with your host.
• Check data retention: If your retention period is set very low, older records may have already been purged. Newly recorded visits should still appear.
• Give it time: AI bots visit sites on their own schedule. A new site may take days or weeks to receive its first AI bot visit.
• Check caching: Full-page caching that serves completely static HTML may bypass the PHP-level bot detection. Ensure bot requests are not served from cache.

Analytics showing no data

If the Analytics tab is empty even though tracking is enabled:

• Bot tracking data takes time to accumulate. Check back after a few days.
• Verify that your site is publicly accessible and not behind a maintenance mode or password gate.
• Confirm your robots.txt is not blocking all AI bots.
• Use the Generate Demo Data tool in CitedPro → Tools to test the analytics display with sample data.

Smart Generate errors

Daily limit reached

Smart Generate is limited to 50 uses per day, SEO Generate to 200 uses per day, and Analytics Summarize to 15 per day. Limits reset at midnight UTC. Plan your generation work accordingly or edit content manually when limits are reached.

Generation failed or returned poor results

• Check AI Context: Ensure you have filled out the business context field and selected reference pages in the Setup tab. More context produces significantly better results.
• Check your connection: Smart Generate requires communication with api.srworks.co. Verify your site can make outgoing HTTP requests.
• Verify license: An active license is required for AI generation features.
• Try again: Temporary API issues resolve on their own. Wait a moment and retry.

Schema not appearing

If JSON-LD structured data is not appearing in your page source:

1. Go to CitedPro → Settings and verify that Enable Schema Injection is toggled on
2. Ensure your business name and description are filled in (schema requires basic business data)
3. View the page source and search for <script type="application/ld+json">
4. Clear any caching layers (page cache, CDN, browser cache)
5. If another SEO plugin also outputs Organization schema, the markup may be duplicated rather than missing. Check for the other plugin's schema output as well.

License issues

License not activating

• Verify you are entering the correct license key (check for extra spaces)
• Ensure your site can make outgoing API calls to api.srworks.co
• License activation is rate-limited to 10 requests per 60 seconds. If you have been trying repeatedly, wait a moment before retrying.

License deactivated unexpectedly

• Your subscription may have expired or payment may have failed. Check your Polar account.
• You may have exceeded your site limit. Deactivate unused sites from CitedPro's settings on those sites.
• Revalidation runs automatically every 30 days. If the API was temporarily unreachable during validation, CitedPro allows up to 3 consecutive failures before temporarily bypassing validation.

Performance concerns

CitedPro is designed to add minimal overhead to your site:

• Bot blocking runs at plugins_loaded priority 1, before WordPress fully loads. Blocked bots are stopped before any theme or other plugin code executes.
• Bot detection uses fast string matching (stripos), not regular expressions.
• Blocked bot patterns are cached in an option rather than queried from the database on every request.
• LLM referral tracking adds a lightweight JavaScript file with no external dependencies and no cookies.

If you experience performance issues, enable debug logging in Settings to identify the source, or disable specific features (bot tracking, schema injection) one at a time to isolate the cause.

Debug mode

Enable debug mode in CitedPro → Settings to capture detailed logs. Debug logs record bot detection events, file generation operations, API calls, license validation attempts, and any errors encountered. Logs can be viewed and downloaded from the Tools tab.

When contacting support, include your debug log along with your WordPress version, CitedPro version, and PHP version.

Getting help

If the solutions above do not resolve your issue:

1. Enable debug mode and reproduce the problem
2. Download the debug log from CitedPro → Tools
3. Visit srworks.co/contact and include your license key for priority support
4. Attach your debug log, WordPress version, CitedPro version, PHP version, and a description of the issue