Quick solutions to frequently encountered problems.
Authentication Issues
“Login Failed”
Causes:
- Incorrect email or password
- Account not verified
- Password expired
- Browser cache issues
Solutions:
- Verify email address (check for typos)
- Try password reset
- Check email for verification link
- Clear browser cache and cookies
- Try different browser
“Session Expired”
Cause: JWT token expired (after 24 hours)
Solution:
- Click “Refresh Session” if prompted
- Or simply log in again
- Enable “Remember Me” for longer sessions
“Account Locked”
Cause: Multiple failed login attempts (security measure)
Solution:
- Wait 30 minutes for automatic unlock
- Or use “Forgot Password” to reset immediately
- Contact support if urgent
Content Generation Issues
“Insufficient Credits”
Problem: Not enough credits for generation
Solutions:
- Check credit balance in dashboard
- Purchase additional credits
- Use lower-cost model (switch to Groq)
- Reduce word count
- Enable auto top-up to prevent future issues
“Generation Failed”
Possible causes:
- API timeout
- Invalid input
- Service temporarily unavailable
Solutions:
- Click “Retry Generation”
- Try different AI model
- Simplify keyword/instructions
- Check system status page
- Wait 5 minutes and retry
- Contact support if persists
“Poor Quality Content”
Problem: Generated content doesn’t meet expectations
Solutions:
- Use higher quality model:
- Switch from Groq to Gemini or Claude
- Premium models = better quality
- Improve input:
- Use more specific keywords
- Add detailed instructions
- Specify desired tone
- Select appropriate word count:
- Longer content (2000+ words) = more depth
- Shorter content may lack detail
- Post-generation editing:
- Review and edit AI content
- Add unique insights
- Enhance with examples
“Content Too Short/Long”
Problem: Generated content doesn’t match requested word count
Cause: AI models approximate word count (±10%)
Solutions:
- Adjust target word count:
- Want 1,500 words? Request 1,600
- Use “Regenerate” with adjusted count
- Edit to add/remove content manually
WordPress Publishing Issues
“Connection Failed”
Problem: Can’t connect WordPress site
Checklist:
- ✅ Plugin installed and activated?
- ✅ API key copied correctly (no spaces)?
- ✅ Site URL correct (include https://)?
- ✅ WordPress REST API enabled?
- ✅ Firewall/security plugin allowing API?
- ✅ SSL certificate valid?
Solutions:
- Test connection in plugin settings
- Regenerate API key
- Temporarily disable security plugins
- Check WordPress error logs
- Contact hosting support
“Publishing Failed”
Problem: Content generated but won’t publish to WordPress
Common causes:
Permission Issues:
- WordPress user lacks publish permissions
- Solution: Grant “publish_posts” capability
Plugin Conflicts:
- Security/optimization plugins blocking
- Solution: Temporarily disable and test
Server Timeout:
- Large content or slow server
- Solution: Increase PHP max_execution_time
Category/Tag Issues:
- Invalid category or tag ID
- Solution: Verify categories exist in WordPress
Steps to diagnose:
- Click “View Error” on failed post
- Read error message
- Follow suggested solution
- Test connection again
- Retry publishing
“Duplicate Content”
Problem: Same article published multiple times
Causes:
- Clicking “Publish” multiple times
- Network timeout causing retry
- Scheduler duplicate
Solutions:
- Check WordPress for duplicate posts
- Delete duplicates manually in WordPress
- When publishing, wait for confirmation
- Don’t refresh page during publishing
“Wrong Site Published”
Problem: Content published to incorrect WordPress site
Prevention:
- Always verify selected site before publishing
- Double-check when publishing to multiple sites
- Use site groups to organize
Recovery:
- Delete post from wrong site (in WordPress)
- Republish to correct site from ContentAI
- Content remains in ContentAI, no credits lost
Sitemap Issues
“Sitemap Not Found”
Problem: System can’t locate site’s sitemap
Solutions:
- Verify sitemap exists:
- Visit: yourdomain.com/sitemap.xml
- If 404 error, sitemap doesn’t exist
- Generate sitemap:
- Use SEO plugin (Yoast, RankMath)
- Or WordPress default sitemap (WP 5.5+)
- Check robots.txt:
- Visit: yourdomain.com/robots.txt
- Ensure not blocking sitemap
- Remove any “Disallow: /sitemap.xml”
- Use custom sitemap URL:
- Some sites use non-standard locations
- Enter full URL manually in ContentAI
“Crawl Timeout”
Problem: Sitemap crawl takes too long or fails
Causes:
- Very large sitemap (1000+ URLs)
- Slow server response
- Temporary server issues
Solutions:
- For large sitemaps:
- Normal for 1000+ URLs
- Wait up to 2-3 minutes
- Crawl during off-peak hours
- For slow servers:
- Check hosting performance
- Optimize WordPress (caching, etc.)
- Consider better hosting
- Retry crawl:
- Wait 10 minutes
- Try again
- If repeated failures, contact support
“No URLs Found”
Problem: Sitemap crawled but no URLs indexed
Solutions:
- Check sitemap format:
- Must be valid XML
- Use sitemap validator tool
- Fix XML syntax errors
- Verify sitemap has URLs:
- Open sitemap.xml in browser
- Should list URLs with
<loc>tags - Empty sitemap = no URLs to index
- Check sitemap type:
- Some sitemaps are “indexes” pointing to other sitemaps
- ContentAI automatically follows indexes
- Verify nested sitemaps exist
Scheduler Issues
“Post Didn’t Publish”
Problem: Scheduled post didn’t publish at scheduled time
Check these:
- Credits available?
- Scheduled posts need credits at publish time
- If insufficient, post fails
- Solution: Buy credits, reschedule post
- WordPress connection active?
- Test site connection
- Green status = active
- Red status = fix connection, then reschedule
- Correct timezone?
- Verify your timezone setting
- Check WordPress timezone
- Reschedule with correct time
- System status:
- Check status page for outages
- If system issue, posts auto-retry
View error details:
- Go to Scheduler → List
- Find failed post
- Click “View Error”
- Follow resolution steps
“Wrong Time Published”
Problem: Post published at unexpected time
Common causes:
Timezone mismatch:
- Your timezone: EST
- WordPress timezone: PST
- Result: 3-hour difference
Solution:
- Check timezone in Settings → Profile
- Verify WordPress timezone setting
- Reschedule future posts accounting for difference
- Or match both timezones
Daylight Saving Time:
- During DST changes, times may shift
- Solution: System auto-adjusts, verify after DST
“Can’t Edit Scheduled Post”
Problem: Scheduled post locked or can’t modify
Causes:
- Post currently publishing
- System processing
Solutions:
- Wait 2-3 minutes for process to complete
- Refresh page
- If persists, cancel schedule and recreate
Keyword Research Issues
“No Results Found”
Problem: Keyword research returns no results
Solutions:
- Try broader keyword:
- Instead of “best DSLR cameras under $500 for beginners”
- Try “DSLR cameras”
- Check spelling:
- Typos return no results
- Verify keyword spelling
- Use English:
- Keyword tool optimized for English
- Translate keywords if needed
- Try variations:
- Singular vs plural
- Different phrasing
“Search Volume Shows 0”
Problem: Keyword has 0 search volume
Interpretation:
- Doesn’t mean nobody searches it
- Means very low volume (<10/month)
- Consider:
- Very niche keyword (might still be valuable)
- Typo or uncommon phrasing
- Try related keywords
“High Competition Score”
Problem: All keywords show 60+ competition
Understanding:
- High competition = harder to rank
- Not impossible, just requires more effort
Strategies:
- Target long-tail variations:
- “content marketing” (90 competition)
- → “content marketing for B2B SaaS startups” (40 competition)
- Build authority first:
- Start with low-competition keywords
- Build site authority
- Then target harder keywords
- Focus on quality:
- Even high-competition keywords rankable with:
- Exceptional content quality
- Strong backlinks
- User engagement
- Even high-competition keywords rankable with:
Billing and Payment Issues
“Payment Failed”
Problem: Credit card or payment declined
Common causes:
- Insufficient funds
- Card expired
- Bank security block
- Payment processor issue
Solutions:
- Verify card details correct
- Check card expiration date
- Contact bank (may need to authorize)
- Try different payment method
- Use Paystack mobile app (if available)