Common Issues

Solutions for frequently encountered problems in IndexMind.

Below are the most frequently reported problems and their resolutions. Each entry includes the symptom you will see, the likely cause, and the steps to fix it.

Analysis and data

Analysis stuck in progress

Symptom: An analysis has been running for an extended period and does not appear to be completing.

Likely Cause: The crawl may be processing a large site with many pages, or a network interruption may have stalled the job.

Resolution:

1. Navigate to the Project Overview page and check the crawl status indicator.
2. If the crawl has been running for less than 30 minutes, allow it to complete. Large sites take longer.
3. If the crawl has been stuck for more than 30 minutes, cancel it and re-run the analysis from the project dashboard.

No visibility data showing

Symptom: The AI Visibility tab is empty or shows no probe results.

Likely Cause: AI probes have not run yet, or the query configuration for your project is empty (no target keywords defined).

Resolution:

1. Open Project Settings and confirm that target keywords are configured.
2. If keywords are present, navigate to the AI Visibility tab and trigger a manual probe run.
3. Wait for the probe cycle to complete. Results will populate once probes finish querying AI models.

Score not updating after changes

Symptom: You have made changes to your website but your AI Optimization Score has not changed.

Likely Cause: Scores recalculate only after a new crawl completes. The score reflects the state of your site at the time of the last crawl.

Resolution:

1. Trigger a new crawl from the project dashboard by clicking Run Crawl or Run Full Analysis.
2. Wait for the crawl to finish.
3. Your score and pillar breakdowns will update once the new crawl data is processed.

Agents and autonomy

Bob not responding to messages

Symptom: Messages sent to Bob in the agent chat interface receive no response, or Bob appears offline.

Likely Cause: The agent service may be misconfigured or your plan tier may not support the configured autonomy level.

Resolution:

1. Verify that AGENT_OS_ENABLED is set to true in the backend configuration.
2. Confirm that AI_SERVICE_URL is accessible and the AI service is running.
3. Check that your plan tier supports the configured autonomy level. The Free plan supports advisory mode only.

MCP access

MCP connection failed

Symptom: Your IDE or MCP client cannot connect to the IndexMind MCP server.

Likely Cause: The most common causes are an incorrect path in the IDE configuration, a missing npm build step, or an expired API key.

Resolution:

1. Verify the MCP server path in your IDE configuration points to the correct location.
2. Ensure you have run npm run build in the MCP server directory.
3. Check that your API key is valid and has not expired. Regenerate it from Settings > API Keys if needed.
4. See the MCP Health Checks page for detailed verification steps.

Project setup

Domain verification failed

Symptom: The domain verification step fails when setting up a new project.

Likely Cause: DNS records may not be properly configured, or the robots.txt file is not accessible.

Resolution:

1. Check that the required DNS records (TXT or CNAME) are properly configured with your domain registrar.
2. Confirm that robots.txt is publicly accessible at https://yourdomain.com/robots.txt.
3. Allow up to 24 hours for DNS changes to propagate.
4. Re-run the verification from Project Settings > Domain Verification.

Reports

Report generation failed

Symptom: Clicking "Generate Report" produces an error or the report does not appear.

Likely Cause: Reports require crawl data to generate. If no crawl has completed for the project, the report engine has no data to work with.

Resolution:

1. Navigate to the Project Overview and confirm that at least one crawl has completed successfully.
2. If no crawl exists, run one first from the project dashboard.
3. Once a crawl completes, return to the Reports tab and try generating the report again.
4. If the error persists, check the Reports tab for specific error details and share them with support.

Login and email

Login OTP not received

Symptom: After entering your email address to log in, the one-time password (OTP) email does not arrive.

Likely Cause: The email may have been caught by a spam filter, or the email address may not match an existing account.

Resolution:

1. Check your spam or junk folder for an email from IndexMind.
2. Verify that the email address you entered matches the one associated with your account.
3. Wait a few minutes. Delivery can sometimes be delayed.
4. Request a new OTP code if the original has not arrived after 5 minutes.