Troubleshooting
The site could not be read
The site blocked our reader, was down, or is not a normal website. Check the address, try again, and if the site blocks bots, allow ours or describe the business instead.
The profile run reads about twenty pages of the site. When it cannot, it says so on the site page with the error.
Common causes
- The address is wrong or points at a redirect loop. Open it in a browser; if it does not load for you, it does not load for us.
- Bot protection. Some hosts and firewalls block automated readers. If you control the site, allow the Firecrawl user agent, or temporarily lower the protection while the profile is read.
- The site is down or very slow. Try again in a few minutes.
- Not a website. A single-page app that renders nothing without JavaScript, a PDF, a login-only site or a social profile cannot be read as a site.
What to do
- Press Try Again on the site page after fixing the cause.
- If the site cannot be made readable, add it as a planned site instead and describe the business; the research then runs from your description. See Can I research a site that is not built yet?.
Reading a site is free, so a failed profile run costs nothing.
Was this helpful?
Still stuck?
Tell us what you were trying to do and which site or page it concerns. A person replies from help@legiit.com, usually within one working day.