Reference
Troubleshooting
Symptoms, likely causes and the fastest fix.
Start here when something looks wrong and you need the fastest path to a fix rather than a conceptual explanation. Each row is a symptom you can see in the product; the fix column is the first thing to try.
| Symptom | Likely cause | Fix |
|---|---|---|
| Audit finds almost no pages | Crawl blocked by robots rules, a firewall or bot protection | Allow the crawler, then re-run the audit |
| Task deployment fails | WordPress application password revoked, or the SEO script removed | Reconnect the integration and re-verify installation |
| Articles publish but are not indexed | Thin content, noindex, or a canonical pointing elsewhere | Inspect the URL, fix the cause, then resubmit |
| Search Console data missing | Property not connected, or the wrong property selected | Reconnect and confirm the exact property |
| Business Profile not syncing | Authorization revoked or expired | Send a new authorization link to the business owner |
| Grid search returns nothing | Missing or wrong location coordinates | Fix the client location, then re-run |
| Outreach email lands in spam | Unverified sending domain | Verify the domain in Agency → Email |
| Client cannot open a report link | Custom domain not verified yet | Wait for verification or send the platform subdomain link |
| API returns 403 on GET | Key has no read scope | Create a key with read, or add the scope |
| API returns 403 with client not authorized | Client is not linked to that agency | Link the client, or use the correct agency's key |
| Generated content is generic | Empty AI Training knowledge base | Add services, pricing structure, credentials and tone rules |
| Dashboard widgets stay empty for a new client | No audit or rank check has completed yet | Wait for the first scheduled job or trigger one on demand |
| Bulk-approved tasks look wrong after deploying | Approved without spot-checking a filtered sample first | Revert the affected pages, review a sample before re-approving |
| Alert emails stopped arriving | Notification preference changed, or emails landing in spam | Check Notifications settings and the spam folder for the sending domain |
Diagnosing step by step
- 1
Reproduce the symptom
Confirm what is actually missing or wrong, and on which client, many "bugs" turn out to be a different client or an old cached report.
- 2
Check the activity feed
Failed jobs and broken integrations are recorded there with a reason, which usually points straight at the cause.
- 3
Check the relevant integration
Most silent data gaps trace back to a disconnected WordPress connection, an expired Business Profile authorization, or a missing Search Console property.
- 4
Retry the specific job
Re-run the audit, rank refresh or grid search on demand rather than waiting for the next scheduled cycle.
- 5
Escalate with specifics
If it still is not resolved, use the in-app Help button with the client, the screen, and the time it happened.
When to escalate
Use the Help button inside the app rather than email. It attaches your workspace, the screen you were on and recent activity, which usually removes a round of questions. Include the time it happened and what you expected instead.
Check the activity feed first
Failed jobs and broken integrations are recorded there with a reason. It answers most "why is this empty?" questions in seconds.