Troubleshooting

Check install on the Sites page asks your homepage for a page as a crawler (Twitterbot, which publishes no IP ranges, so the check works from Intercrawl's own network) and looks at the answer.

"Your homepage answered a crawler with your own page"

The install did not reach Intercrawl, or Intercrawl did not serve this request. Check, in order:

1. The site is verified. Until it is, crawlers get your own pages.
2. The install file is saved at the path its guide gives, and the site was deployed again after adding it.
3. INTERCRAWL_TOKEN is set where the app runs, to a token that is not revoked, and the app was deployed again after setting it (most platforms read variables at deploy).
4. Nothing in front of your site (a CDN cache, a firewall, a bot rule) answers crawlers before your install does.

"The middleware reached Intercrawl, which served your own page this time"

The install works. That request got your own page because no renderer was free or the render failed; Intercrawl tries again in the background. Check again in a minute.

"Your homepage could not be reached from Intercrawl"

Your site did not answer. Check that it is online and that its address on the Sites page is right.

An audit shows crawler views served by your own server

Each crawler view in an audit says where its page came from. "Origin" for every view means the install is not answering crawlers (see the first section). "Origin" for some views only usually means those pages had no render yet; they are rendered in the background and the next audit shows them.

A crawler still gets an old page

Stored renders are refreshed after 7 days, when the page's scripts, stylesheets, title, description or canonical change, or when your sitemap shows a newer lastmod. To refresh a page now, use the re-cache API.

Still stuck

Write to hello@intercrawl.com with your site's domain, the install you used, and what Check install said. See Support.