All docs
Troubleshooting
Common problems
The messages people see most often in Rivelant, what they mean, and what to do.
If you don't find your message here, email support@rivelant.com with the exact text and what you were doing.
Credits and plan
| You see | What it means | What to do |
|---|---|---|
| Not enough credits · Buy credits | The action costs more credits than you have left. | Buy credits on Billing, upgrade, or wait for your monthly refill. See Plans and credits. |
| Last check skipped | A scheduled check (rank tracking, AI visibility) didn't run for lack of credits. | Add credits; the next check runs as scheduled. |
| This month's articles are used up | You've used this month's AI-written articles. | On Starter and up, use Write with credits. Otherwise upgrade or wait for next month. |
| Paid work is paused | Paid actions are on hold, usually for credits or billing. | Check Billing. |
| Not on your plan · Upgrade | The feature isn't on your plan. | Upgrade from Plans. See the pricing page for what each plan includes. |
| Your plan's limit for this is reached | You're at your plan's limit for sites, stores, members or tracking. | Remove something you no longer need, or upgrade. |
| Stores come with the paid plans | Local needs a paid plan. | Choose a paid plan. |
Search Console
| You see | What to do |
|---|---|
| Search Console connection was canceled | Click Connect again and allow access on Google's screen. |
| Search Console connection didn't finish | Try again in a single tab and finish within 10 minutes. |
| No verified access (next to a property) | You aren't verified for that property in Search Console. Get verified, or pick another property. |
| Rivelant asks you to ask an owner or admin | Only organization owners and admins can connect Search Console. |
More in Connect Google Search Console.
Publishing
| You see | What to do |
|---|---|
| No place to publish · Connect | Connect your site under Settings › General › Data sources. |
| Only the owner can publish | Ask your organization's owner to publish, or to change your role. |
| Only an organization owner can configure CMS connections | Payload and WordPress connections need the owner. GitHub only needs permission to publish. |
| Can't reach the CMS / CMS unreachable | Your site or GitHub didn't respond, or the key or token stopped working. Use Check connection in Data sources. |
| The website refused it | Your site doesn't support that action (for example a redirect on a GitHub site). |
| Branch is protected | Switch GitHub publishing to Pull request. See GitHub. |
| The site didn't update | The published post didn't appear on your site within 2 hours. Check that your site redeploys. See GitHub. |
| Changed on the website | Someone edited the article on your site after Rivelant read it. Rivelant didn't overwrite it; review the change first. |
| Unavailable for now | A rate limit was hit. Try again later. |
More in Publish to GitHub and Publish to Payload CMS.
AI agents
| Problem | What to do |
|---|---|
| "Needs authentication" or a 401 | Sign in again from your agent (for example /mcp in Claude Code), or check your API key. |
| Rivelant tools don't appear | Reload your agent's MCP servers or restart the agent. |
More in Use Rivelant from your AI agent.
Audits
| Problem | What to do |
|---|---|
| Pages show as blocked or rate-limited | Your site's bot protection challenged the crawler or asked it to slow down. Allow Rivelant's crawler, or run the audit with JavaScript rendering. |
| Website saved. The first scan could not start. | Your website was saved, but the audit didn't start. Start one from More pages › Site health. |
Updated November 17, 2026. Still stuck? support@rivelant.comView as Markdown