LLMIC Documentation

Troubleshoot common problems

Updated

Something isn’t working. Before you change several settings, identify the step that failed.

Is it installation, sign-in, payment access, a crawl, a provider connection or an export? That answer points you toward the checks most likely to help.

Work through the relevant section below. Keep the exact error message and a short record of what you tried so support can pick up where you left off.

Find the failing stage first

  1. Identify the symptom
    Installation, account, crawl, connection or export?
  2. Check the relevant input
    Version, identity, plan, scope or provider permissions.
  3. Repeat one small test
    Record the exact message and result.
  4. Escalate with evidence
    Send sanitized steps and version details to support.

Avoid deleting saved data, disabling security or making duplicate purchases as a first response.

If LLMIC will 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.

If you paid but a feature stays 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.

If the crawl misses expected pages

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.

If 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.

If results or exports 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.

Give support enough detail to reproduce the problem

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

SymptomFirst check
Locked AI toolPurchased plan and current account
Billing handoff errorStart a fresh action from the app
Saved key failsPermissions, scope, model and quota
Unexpected page countCrawl source and coverage
Unexpected account dataIdentity and switch sequence

Continue learning

Ready for the next step? Start here: check subscription access, check crawl setup.

If you still need help, contact support with your app version and the steps you tried. Leave out passwords, API keys and private account details.

Published by LLMIC. Documentation reviewed on 24 September 2026.