Skip to main content

​
Connecting

The workspace is on the Free plan. Connectors and publishing are Pro features — upgrade from Billing, then connect again.
The subscription lapsed. Existing connectors stay configured; publishing and syncing resume once billing is current.
Connecting requires the Admin or Owner role. Editors can publish to existing connectors but not create them.
The account’s email is unverified. Use the link in the verification email, or resend it from your account settings.

​
WordPress

We reached your REST API and it refused the login. Check that you used the WordPress username (not the email), and generate a fresh application password.
We tried /wp-json/ and ?rest_route= and neither returned JSON. Usual causes: a security plugin blocking the REST API, HTTP basic auth or a staging password in front of the site, Cloudflare “Under Attack” mode, or a site that isn’t publicly reachable.Check it directly: https://yoursite.com/wp-json/wp/v2/types should return JSON.
WordPress hides it on non-HTTPS sites. Serve the site over HTTPS, or check whether a security plugin has disabled the feature.

​
Webhook

Supply a longer secret, or leave the field blank and we’ll generate a strong one.
Nothing is listening on that host and port. Check the URL, the port, and that the service is running and reachable from the internet.
The hostname doesn’t resolve publicly. Internal-only hostnames and localhost won’t work against the hosted app.
Your endpoint took too long. Acknowledge with a 2xx immediately and process afterwards.
Almost always because the HMAC was computed over a re-serialized body. Sign the raw bytes exactly as received, and confirm you’re using the secret shown when the webhook was connected — reconnecting generates a new one.
Five or more deliveries failed within an hour. Fix the endpoint, then click Send test — a successful delivery clears the state.

​
Google Search Console and Analytics

Expected while the app is in Google’s verification review. Click Advanced, then Go to seosorted (unsafe), and approve the read-only scope. We only ever request webmasters.readonly and analytics.readonly.
You signed in with a Google account that has no access to the property. Disconnect, connect again, and choose the right account on Google’s screen.
The connector worked; the property has no data in the window. For GA4 this usually means the wrong property was chosen. Verify in Google Analytics that the property receives traffic.
OAuth completed but no property was chosen. Click Choose property and save one.
Search Console data lags 2–3 days and is sampled at Google’s end for some queries. Small differences against the Search Console UI are expected; large gaps usually mean a domain-property vs URL-prefix mismatch.

​
Webflow and Shopify

The store’s plan is paused, frozen or cancelled — Shopify blocks app installs until billing is active again. Reactivate the store, then connect.
You entered a custom domain. Use the yourstore.myshopify.com form.
The authorisation granted no site. Disconnect, connect again, and pick a site on Webflow’s authorisation screen.

​
Publishing

No publishing destination is connected yet. Use + Connect another destination in the dialog, or set one up in Project Settings → Integrations.
Webflow needs a collection and field mapping; Shopify needs a blog. Finish setup on the Integrations tab.
The article was never generated or its body was emptied. Generate or write the article first.
Check that the destination is still connected and not in Error, and that the plan is active. Scheduled runs skip workspaces that fail either check.
Still stuck? Email hello@seosorted.ai with the connector, the exact error text, and roughly when it happened — the delivery and job logs are keyed by timestamp.