Troubleshoot common problems
Troubleshoot LLMIC installation, account access, crawls and provider connections using evidence without deleting saved data or making duplicate purchases.
Begin troubleshooting by identifying which stage failed: installation, sign-in, subscription access, crawling, a provider connection or exporting. These stages rely on different inputs. Capture the exact message and the smallest set of steps that reproduces it. A screenshot can help, but remove account secrets, private customer data and authentication links before sharing it.
What this guide helps you do
SEO troubleshooting starts by identifying the exact step that failed: sign-in, crawl, connection, analysis or export. Use this guide to preserve the error state, try the smallest safe check and collect useful support evidence.
App does not open
Check the requirements on the official download page and confirm that you launched the Applications copy. If the download appears incomplete or damaged, obtain a fresh official copy. Do not disable macOS security features or delete saved application data as a first response. Record the release and macOS version so support can distinguish a compatibility problem from a damaged download.
Payment succeeded but a feature is locked
First confirm the signed-in account and purchased plan in Account & License. Restore access if the displayed status has not refreshed. Solo does not unlock Pro-only AI tools or Google integrations, so compare the feature before purchasing again. A browser prompt to open LLMIC confirms navigation only; check the receipt and account status separately when diagnosing payment completion.
A crawl has fewer pages than expected
Check the selected source, domain, plan limit and available crawling settings. A URL list, sitemap and linked-site crawl can cover different groups of URLs. Failed access, robots rules, redirects or rendering limitations can affect what is observed. Inspect representative missing or failed URLs and the available evidence. Do not equate an incomplete crawl with proof that those pages do not exist.
A provider connection fails
Confirm the active client, credential format and property or model being requested. A key saved in the panel may still lack provider permission, billing access or quota. Use a connection test where available, remembering that it may consume provider quota. If you rotate a secret, save the replacement in the correct scope and test again. Never post the secret in a support message.
Results look inconsistent
Compare the website, crawl completion, evidence layer, reporting period and filters. Provider dashboards can differ when dates or scopes differ, and missing data should not be silently interpreted as zero. If you see another account’s workspace after switching, stop and report the switch sequence rather than deleting it. For export problems, inspect the saved file and note which view, selection and format produced it.
Send a useful support request
Include your app version, macOS version, affected feature, relevant time and a clear reproduction sequence. Describe what you expected and what happened instead. Add a sanitized screenshot or example URL where appropriate. Keeping this information precise helps separate a product defect from plan restrictions, incomplete evidence or a provider-side access problem without losing your saved work.
Quick reference
| Symptom | First check |
|---|---|
| Locked AI tool | Purchased plan and current account |
| Billing handoff error | Start a fresh action from the app |
| Saved key fails | Permissions, scope, model and quota |
| Unexpected page count | Crawl source and coverage |
| Unexpected account data | Identity and switch sequence |
Continue learning
Next, check subscription access, check crawl setup, test connections. Return to the documentation home to explore other guides. If the result differs from these instructions, contact support with your app version and the relevant steps. Remove private information from screenshots and never include API keys or passwords.
Frequently asked questions
Troubleshoot LLMIC installation, account access, crawls and provider connections using evidence without deleting saved data or making duplicate purchases.
Have the current LLMIC build, the account that should own the workspace, and any required subscription or provider access ready. Follow the prerequisites on this page before changing macOS security, account, or billing settings.
Check the app version, account email, selected plan or provider, permission state, and the exact message shown on screen. Those details are more useful than assuming that every setup problem has the same cause.
Follow the steps in order and stop at the first result that differs from the guide. Record that step and the exact message before retrying, reconnecting an account, or contacting support.
Confirm the expected screen or account state described in the Check the result section. Installation, authentication, provider connection, and subscription access are separate outcomes, so verify the one this guide covers.
This workflow confirms the visible setup result described here. It does not certify unrelated features, future updates, every Mac configuration, provider availability, or a payment outcome that was not completed.
Save or export the evidence, assign the approved action, and use the related guides linked on the page for the next check. After implementation, repeat the same workflow against a fresh crawl so the result is comparable.