Vistralo/Help/Troubleshooting

"Couldn't analyze" a website

Why a website analysis fails with Couldn't analyze, and what to try before recording the page yourself.

A website project that failed shows "Couldn't analyze" on its frame, with the reason underneath and a "Retry" button.

The usual reasons

  • The site turned the visit away. Many sites block visitors that are not a person in a browser. The capture runs on a server, so it is one of those.
  • The page needs a sign-in. The capture visits as a stranger and cannot sign in.
  • The page did not load in time, or the site was down at that moment.
  • The address was wrong. A typo can lead to a page that does not exist.

What to try

  1. Open the address in your own browser, signed out, in a private window. What you see there is what the capture sees.
  2. If the page loads, press "Retry" on the project, or "Retry website capture" on its page. A site that was briefly slow often works the second time.
  3. Try a different public page on the same site. A home page is sometimes protected when an inner page is not.

Vistralo does not try to get round a site's block, and you should not either.

When it will not work

Record the page yourself. Choose "Record an AI walkthrough", share the tab, and scroll through the page. Give the page's address in "Website URL (optional)" and Vistralo will still try to read its code for the narration. See Record your first walkthrough.

Before you start, the form refuses the address

That is a different problem, caught before anything runs. See What "public pages only" means.

Nothing is happening at all

If the project sits on "Waiting for a free capture worker" for a long time, the worker may be offline. The app says so when it knows: "The capture and render worker is offline. Your project is saved; try again when it reconnects."

Still stuck? Write to contact@vistralo.com and say what you did and what you saw. Or go back to all help articles.