Troubleshoot setup, plans, and publishing

Start with the current state

Read the status and error beside the affected work before retrying. Keep the project and article in one browser tab where possible. A refresh can show progress; it should not be used to launch the same work repeatedly.

For support, note the website, page you were using, approximate time, action you tried, and exact visible error. A screenshot with private details removed can help. Never include passwords, Application Passwords, payment-card details, or access tokens.

The website profile cannot be completed

Check that the address is your public website and loads over HTTPS in a normal browser. Password-protected, private, or inaccessible sites cannot supply the expected page evidence. Confirm that the site’s key pages explain your business and product.

If the app cannot safely prefill the profile and offers a review form, enter the business essentials yourself. Confirm the audience and voice rather than accepting a vague fallback. If the form remains locked or repeatedly fails, contact support with the visible status.

Payment succeeded, but Growth is not active

Return to the app from the Checkout confirmation and inspect the website’s subscription status. Activation confirmation can arrive after the payment response. Avoid creating a second payment to force an unlock. If it remains pending, send support the website and approximate transaction time, without card details.

The plan or article needs attention

Preparing indicates work is still running. Needs attention indicates a problem you should read before proceeding. Use the retry or recovery action shown by the app, rather than submitting several generation requests.

For draft autopilot, check that the setting is on, the work is approved, the item is due, and the article has not already been prepared. The allowance is up to one article per day, not all approved items at once. Publication always remains separate.

A research-provider problem can reduce the evidence available for a draft. Read its limitations and review the claims accordingly. If a plan refresh cannot safely replenish topics, the last healthy plan remains available while the delay is reported.

Search Console has no data

Check the Google account’s access, the selected property, and the sync status. A new site can have little measured visibility. Google login alone does not authorize Search Console. Reconnect when the app says access has expired; repeated sync requests will not repair missing permission.

You can keep using site context and available research without Search Console. See the connection guide.

WordPress connection or publishing fails

• Authentication: check the WordPress username and separate Application Password. Do not use the normal login password.
• Permissions: a draft-only account may not be able to publish, schedule, or upload a featured image.
• Site access: ask your host whether the core REST API and Application Password authentication are available over public HTTPS.
• Wrong destination: confirm the selected site for this Growth project.
• Late scheduled post: inspect the future post in WordPress and ask the host to check WP-Cron.

A send says “Needs review”

Check WordPress Posts and Media first. A timed-out request may have created the remote post before its response was interrupted. Do not resend or create a manual duplicate until you know the outcome.

If a post exists, continue reviewing it in WordPress and tell support the destination URL. The app prevents a second send while the result is unclear. After a successful send, the same article cannot be sent again to the same site.

Next: review the WordPress publishing guide, or contact the Content Redefined AI team.