LogoOutrank

Command Palette

Search for a command to run...

Troubleshooting & FAQs

Resolving 'Something Went Wrong' Errors

Encountering a generic "Something went wrong" error can be frustrating, especially when you're in the middle of creating content or setting up a new integration. These messages are often "catch-all" alerts that appear when the system encounters an unexpected issue it can't specifically identify.

This guide will help you diagnose the root cause of these errors and provide step-by-step instructions to resolve them so you can get back to work.

Most generic errors are temporary and can be resolved with a simple page refresh or by waiting a few minutes before trying again.

How Errors Appear

Generic errors typically appear in two ways within the platform:

  • Full-Screen Error Page: A dedicated page with the message "Something went wrong 🥲" and buttons to Refresh, go Home, or contact Support.

  • Toast Notifications: Small pop-up alerts in the corner of your screen that say "Something went wrong..." followed by a brief description like "with generating keywords" or "during integration creation."

Immediate Troubleshooting Steps

Before diving into specific feature issues, try these universal fixes:

  1. Refresh the Page: Click the Refresh button on the error page or use your browser's reload button (F5 or Cmd+R). This often clears temporary connection glitches.

  2. Check Your Internet Connection: Ensure you have a stable connection. A brief drop in signal can interrupt API requests.

  3. Clear Browser Cache: Stale data in your browser can sometimes cause conflicts. Try clearing your cache or opening the platform in an Incognito/Private window.

  4. Wait and Retry: If the error occurred during a high-intensity task like generating a long article, the system might just need a moment to recover. Wait 1-2 minutes and try the action again.

Troubleshooting by Feature

Depending on what you were doing when the error appeared, the cause and solution may vary.

1. Article Generation Errors

If you see an error while creating new content, it is usually related to one of the following:

  • Timeouts: Generating long-form content can sometimes take longer than the system's 60-second limit. If this happens, wait a minute and check your Articles list—often the article was actually created successfully despite the error message.

  • Credit Limits: Ensure you haven't reached your monthly article credit limit. You can check this in your Account Settings.

  • AI Content Filters: Occasionally, the AI may refuse to generate content if the topic or keywords trigger safety filters. Try rephrasing your prompt or keywords.

2. Publishing Errors

Errors during the "Publish" or "Send to Draft" phase are often connection-related:

  • Server Timeouts (502 Errors): If your website's server takes too long to respond, you'll see a generic error. Simply clicking "Publish" again often works on the second attempt.

  • Expired Credentials: Your integration token or password may have expired. Go to Integrations, select your site, and try reconnecting or updating your credentials.

WordPress Users: Ensure your Permalinks are NOT set to "Plain." Go to WordPress Settings > Permalinks and select "Post name" to allow our API to connect correctly.

3. Integration Setup Errors

If you can't connect a new site (WordPress, Webflow, Shopify, etc.):

  • Credential Accuracy: Double-check that you are using the correct API keys or Application Passwords. For WordPress, remember to use your Username (not your email) and the 24-character Application Password.

  • Firewalls & Security: Security plugins (like Wordfence) or services (like Cloudflare) may be blocking our connection. Try temporarily disabling "Bot Fight Mode" in Cloudflare or whitelisting our service in your security plugin.

Advanced Troubleshooting

If the basic steps don't work, try these more advanced methods:

  • Check the Browser Console: Right-click anywhere on the page, select Inspect, and click the Console tab. Look for red text—these detailed error logs can provide specific clues (like "401 Unauthorized" or "403 Forbidden") that help our support team diagnose the issue faster.

  • Disable Extensions: Some browser extensions, especially ad-blockers or privacy tools, can interfere with site functionality. Try disabling them to see if the error persists.

  • Try a Different Browser: Switch from Chrome to Firefox or Safari to rule out browser-specific issues.

If you see a "403 Forbidden" error in the console, it usually means your subscription has lapsed or you've reached a limit. Check your Billing page to ensure your plan is active.

When to Contact Support

If you've tried the steps above and still see "Something went wrong," our team is here to help. To resolve your issue quickly, please provide the following information when you reach out:

  • The email address associated with your account.

  • A screenshot of the error message (and the browser console if possible).

  • What specific action you were taking (e.g., "I was clicking 'Publish' on a WordPress article").

  • Any troubleshooting steps you've already tried.

You can contact us via the Support button on the error page or by emailing our help desk directly.