Help & Guides

Step-by-step guides for every tool, recipe, and setting

TroubleshootingCommon Issues

Common Issues

Authentication Errors (401)

If you see "401 Unauthorized" or "Token expired" errors: 1. Open Connections → Google. 2. Use the Test button on the affected account to confirm the failure, then Disconnect and Connect Google account again. 3. Complete the OAuth flow and accept all permissions.

Permission Denied

Ensure you granted all permissions during the OAuth flow. Reconnect the account from Connections → Google and accept all scopes, including Blogger, Drive, Docs, Sheets, Calendar, and Photos.

Tool Failures

Common causes: Google API quota exceeded (wait 24 hours), permission denied (reconnect account), or invalid folder ID. Check Settings → Activity for detailed error messages.

Cloud Upload Failures

Verify your cloud credentials. Ensure the bucket exists and your account has write permissions. Use the "Test Bucket" button before running Cloud Stacker.

Indexation: 'No properties' or scraping fallback

If a campaign keeps falling back to scraping for indexation results: - Confirm a Google account is connected (it auto-creates a GSC connection). - Open Connections → Google, expand the affected account row, and click Test on the GSC entry. - If you see "accessNotConfigured", enable the Search Console API in your Google Cloud project. - If the property list is empty, the connected Google account has no Search Console access — add it in https://search.google.com/search-console. - For per-campaign overrides, use the Search Console picker on the New/Edit campaign form.

Check Settings → Activity for detailed error logs on any failed operation.