Troubleshooting and FAQ
Use this page when a connection, report, or workflow does not behave as expected.
Sign in
Section titled “Sign in”ReachLLM accepts the current password value from your browser or password manager and processes one sign-in attempt at a time. If a temporary connection or authentication service delay interrupts the attempt, the page asks you to try again without claiming that the password is incorrect. Check or reset the password only when the page specifically reports a credential problem.
Brand prompt setup
Section titled “Brand prompt setup”If you see Your prompt setup needs another try, select Try prompt research again to resume the saved project. ReachLLM only continues after all 50 setup prompts are ready.
After setup is complete, adding or archiving prompts does not restart onboarding. Add brand opens a new setup unless another project has genuinely unfinished setup. Your completed projects keep their current prompts.
Teammates with editing access can finish or retry a shared project's prompt setup when the workspace has an active plan and enough project and prompt capacity. The original creator does not need to sign in to finish it. Read-only teammates cannot change the prompt inventory. Before a workspace selects a plan, only the workspace owner or the account that created the onboarding project can initialize its prompts.
Integrations
Section titled “Integrations”If an integration does not connect:
- Confirm you are signed into the account that owns the property, site, repo, or workspace.
- Check that the brand website URL matches the external service property.
- Disconnect and reconnect from Account > Integrations.
- Refresh the page and confirm the card shows Connected.
Publishing
Section titled “Publishing”If publishing does not work:
- For WordPress, confirm the site URL, username, and Application Password.
- Install the ReachLLM Connector plugin for schema, llms.txt, robots.txt, metadata, and cache support.
- For GitHub, confirm the GitHub App is installed on the right repository and branch.
- For Webflow, confirm the API token has Site and CMS read/write access, and add the Site ID if the token can access multiple sites.
- For Shopify, confirm the store domain and Admin API access token can read and write Online Store pages, blogs, and articles.
Reports and audits
Section titled “Reports and audits”If a report or audit looks stale, re-run the underlying analysis first. Some surfaces are snapshot-based and only update after a new run or saved report.
Free-report requests that match abuse controls, including blocked domains or test contact details, are rejected before account creation, analysis, or request emails. Revoked reports are no longer available through their shared links. If a legitimate request is blocked, contact support instead of repeatedly submitting the form.
Support
Section titled “Support”Email team@reachllm.com for help.