Talk to Crawler.sh
Whether you're a developer, SEO specialist, or curious contributor - we'd love to hear from you.
Have a question about the CLI or desktop app? Found a bug during a crawl? Want to request a new export format or SEO check? We read every message and use your feedback to shape the product roadmap. You can also suggest features, report issues with specific websites, or ask for help setting up crawler.sh for your workflow.
What to reach out about
- Bug reports. Crashes, incorrect SEO results, broken exports, or pages that fail to render. Include your OS, your crawler.sh version (run
crawler --version), and the URL or steps needed to reproduce. - Feature requests. New SEO checks, additional export formats, dashboard cards, or CLI flags. Tell us the workflow you are trying to unblock and we will look at how to fit it into the roadmap.
- Partnerships and press. Integration ideas, media coverage, podcast or interview requests, and reseller or enterprise licensing inquiries.
- Account and billing. Subscription questions, plan changes, invoices, refunds, or trouble signing in to the desktop app or CLI.
Response times
crawler.sh is run by a small team and we do not offer live chat. Email is the most reliable channel and we typically respond within one business day, often the same day. Twitter/X DMs are good for quick questions but slower for anything that needs files or screenshots. Bug reports that include a reproducible URL, your OS, and the version string are easier to act on and almost always get a faster reply.
What we cannot help with
A few things sit outside the support scope. We do not crawl sites on your behalf, build custom dashboards, or write bespoke SEO reports as a paid service. We also do not offer phone support, ticket SLAs, or dedicated account managers, even on the Pro plan. For suspected security vulnerabilities, please email security@crawler.sh instead of the public address so we can triage and respond before the issue is discussed in the open. We currently provide support in English only, though you are welcome to write in any language and we will do our best to understand and reply.
Bug report template
The fastest path to a fix is a short, structured report. Tell us the operating system and architecture (for example, macOS 15 on Apple Silicon or Ubuntu 24.04 on x86_64), the crawler.sh version from crawler --version, the exact command or desktop action that triggered the problem, the URL of the site you were crawling if it is public, and the actual versus expected behavior. If the CLI produced a stack trace or the desktop app logged an error, paste it verbatim. Screenshots of the desktop dashboard or the relevant card help when the issue is visual. With that information we can usually reproduce locally on the first try and ship a fix in the next release.
