Troubleshooting
Use these checks to resolve common setup and report issues before requesting help.
Before you start
- 1Confirm that you are signed into the intended workspace and the relevant tracked brand is selected.
- 2Open project settings to confirm the website, brand profile, audience, location, language, Topics, and selected Prompts were saved.
- 3Check the workspace notifications and report history. This shows whether a report is still processing, completed, or failed.
Common issues
Your website could not be analysed
Geolity collects publicly available website content while respecting the website’s robots.txt and llms.txt rules. A site may not be available for analysis when those rules block access. A report can also lack usable content when the site is unavailable, protected by a challenge or login, or returns no useful public content. Check that the website URL is public and resolves normally, then try the setup again.
What to know: Review robots.txt and llms.txt if you expect AI crawlers to access the relevant public pages.
No Prompts were generated
Prompt generation needs a usable brand profile and settings such as audience, location, language, and Topics. Complete the missing project setup fields, save the configuration, then regenerate or select Prompts.
What to know: Start with a focused set of Topics so generated questions represent real buyer intent.
You reached the Prompt limit
Each plan limits the number of Prompts used in a report. Remove less useful selected Prompts, keep the strongest buyer questions, or change to a plan with a larger allowance before generating another report.
What to know: The active plan cap is applied at report generation, including scheduled reports.
A report is delayed or failed
Reports can take time while prompts are processed and results are analysed. Check workspace notifications and your report history first. A failure notification is created when a scheduled item does not complete.
What to know: If the report remains unavailable, include your workspace, tracked domain, and report time when you contact support.
A saved change is not visible in an older report
Completed reports keep the configuration used at the time they were generated. Changes to your profile, Topics, or Prompts apply to a new report or the next eligible scheduled run; they do not rewrite historical results.
What to know: Use report history to distinguish a genuine result change from a configuration change.
Contact support
If the issue persists, contact us with the workspace name, tracked domain, approximate report time, and a screenshot or error message where possible. This helps the team identify the affected report run.