Troubleshooting — SEO Copilot AI Docs
Support

Troubleshooting

Common issues, expected behavior, and practical ways to resolve the most typical setup, workflow, API, scoring, and license-related problems in SEO Copilot AI.

Start by identifying the category

Most issues with SEO Copilot AI fall into one of three buckets. Before changing settings randomly, identify whether the issue is mainly about license verification, AI/API connectivity, or your WordPress environment. That usually gets you to the fix much faster.

License

Plan or activation issue

The plugin shows Free, the paid plan does not unlock, or your license appears to revert unexpectedly.

AI / API

Connection or model issue

Analysis fails, returns an error, times out, or does not produce suggestions as expected.

WordPress

Environment or conflict

Slow admin screens, stuck spinners, AJAX problems, or conflicts with hosting, themes, or plugins.

Good troubleshooting habit: change one thing at a time, then test again. If you change multiple settings at once, it becomes much harder to know what actually fixed the issue.

Quick diagnostic checklist

  • Confirm you are using the latest installed version of SEO Copilot AI
  • Make sure your license key is entered correctly and has been refreshed recently
  • Verify your AI provider key is valid and the selected model is available to your account
  • Check whether your server can make outbound HTTPS requests
  • Try the same workflow with one other plugin temporarily disabled if a conflict seems likely
  • Test on a different page or post to see whether the issue is global or content-specific

License and activation problems

The plugin still shows Free after purchase

License

This usually means the license has not been verified successfully yet, or the plugin is still showing a cached status from before the purchase or upgrade.

What to do

  • Go to SEO Copilot AI → Settings → License
  • Paste the correct key from your purchase email
  • Click Save & verify
  • Then click Refresh license to bypass the cache

Most likely cause

The license was never verified, the wrong key was entered, or the site has not yet refreshed its cached license response.

The paid plan keeps reverting to Free

Connectivity

This is most often caused by a server-side connectivity problem. If the site cannot reach the NordicDataTools license server, the plugin may temporarily fall back to Free mode until verification works again.

Check these first

  • Outbound HTTPS requests are allowed by your host
  • No firewall or security plugin is blocking remote requests
  • Your hosting environment is not restricting WordPress HTTP calls

Expected behavior

If verification later succeeds again, the correct paid plan should return automatically without re-buying or entering a new license.

Refresh license does not change anything

Still unresolved

If a forced refresh does nothing, the problem is usually not just stale cache. It is more likely a wrong key, an expired license, a site limit issue, or blocked connectivity.

Check What it means
Wrong key The key entered in the plugin does not match the actual purchased license.
Expired license The current billing period has ended and the license is no longer active.
Site limit reached The purchased plan has reached its allowed number of activations.
Remote request blocked Your server cannot contact the NordicDataTools license endpoint at all.

AI provider and API problems

Analysis does not run

AI / API

If you click analyze and nothing useful happens, the cause is usually the AI configuration rather than the content itself.

What to check

  • The API key is valid and fully copied
  • The configured endpoint is correct
  • The selected model is available to your account
  • Your AI account still has available usage or billing enabled

Practical test

Try a simpler or lighter model first. If a smaller model works but the intended one does not, the problem is usually model access, response size, or timeout sensitivity.

You get API errors or timeouts

Rate / Timeout

Temporary errors can happen because of provider-side rate limits, intermittent connectivity, long responses, or a model that is slower than your hosting environment tolerates.

Try this

  • Wait a few seconds and run the analysis again
  • Switch to a lighter model for testing
  • Reduce how many analyses you run at once
  • Check whether your host has aggressive timeout limits

Common pattern

If one page works but bulk analysis fails, the issue is often request volume, execution time, or server resource limits rather than a broken plugin setup.

No suggestions are generated

Sometimes expected

This is not always a bug. Sometimes the content already meets the plugin’s baseline well enough that there are fewer obvious suggestions to return. In other cases, the request may have failed quietly because of an API or JavaScript issue.

How to tell the difference

  • Run analysis on another page and compare
  • Check whether the page still gets a score and structured feedback
  • Open the browser console for visible JavaScript errors

Good next step

If the same content repeatedly returns nothing, test a different model and confirm the provider settings before assuming the page itself is the problem.

Scoring and result interpretation

The page score is high, but it still says “Needs attention”

Expected behavior

This is normal. The score reflects overall quality, while the attention state highlights whether there are still specific improvements worth making. A page can be strong overall and still have unresolved opportunities.

How to read it

  • The score tells you the overall level
  • The issues tell you what is still worth improving
  • Do not treat a high score as a signal to ignore missing structured improvements

Best focus areas

Start with missing or weak FAQ coverage, schema opportunities, clarity gaps, and on-page signals that improve how search engines and AI systems interpret the page.

The score seems lower or higher than expected

Interpretation

Scores are guidance, not a promise of rankings. They reflect how the page currently aligns with the plugin’s evaluation model across SEO, AEO, and related content quality signals.

Important: SEO Copilot AI helps identify and improve signals. It does not guarantee rankings, AI citations, traffic growth, or performance outcomes, even when scores improve.

WordPress environment and UX issues

The spinner never stops

AJAX / JS

A stuck spinner usually means the request did not complete cleanly. This is often caused by a failed AJAX response, a JavaScript error, a REST/AJAX block, or a plugin conflict.

What to check

  • Open browser developer tools and inspect the console
  • Look for failed network requests
  • Temporarily disable likely conflicting admin plugins
  • Make sure your security setup is not blocking admin AJAX

Most useful signal

If the UI gets stuck but the request never returns, the problem is usually environmental rather than content-related.

The plugin feels slow

Performance

AI-assisted analysis depends on both the selected model and the quality of your hosting environment. Slower models, limited PHP workers, weak hosting, or too many simultaneous requests can make the experience feel sluggish.

Speed improvements

  • Use a lighter model for routine work
  • Avoid running many bulk jobs at once
  • Check PHP memory and execution time limits
  • Test whether the slowness affects only one site or the whole admin

Expected behavior

Single-page analysis should generally feel more responsive than larger batch workflows. Bulk operations naturally take longer because they process more content.

What support needs from you

If the issue persists, sending a few concrete details usually shortens the support loop significantly.

  • The installed SEO Copilot AI version
  • Your WordPress version and PHP version
  • A short description of what you expected to happen
  • What actually happened instead
  • Any visible error text, screenshots, or console output
  • Whether the problem affects one page, many pages, or the entire plugin

Common questions

Should I reinstall the plugin to fix most problems?

Usually no. Most problems are related to license verification, API configuration, or environment conflicts — not broken installation files. Reinstalling is rarely the first or best fix.

Does clearing the license cache remove my settings?

No. Refreshing the license only forces a new verification check. It does not erase your main plugin settings or your content-related work.

Can a security plugin interfere with SEO Copilot AI?

Yes. Some security or firewall plugins can block outbound HTTP requests, AJAX calls, REST requests, or admin scripts. If troubleshooting points in that direction, test temporarily with the security layer adjusted or disabled.

When should I contact support?

After you have confirmed the license key, API key, provider settings, and basic connectivity — and the issue still remains. Support is especially helpful when you can provide screenshots, clear reproduction steps, and any visible error output.

Where to go next

← Multisite & Network Use Help & FAQ →