Contact WideAngle support
Contact WideAngle by email for support and early access, or through GitHub issues for bugs and rule proposals. Email reaches a person, not a queue: WideAngle is maintained by one developer, so expect a considered reply within two working days rather than an instant one.
Early access and pricing
The hosted platform is in early access. If you want in, join the waitlist on the home page — founding users get three months of Pro at no cost when it opens. If you are an agency or you run more sites than a standard plan covers, email instead and say roughly how many sites and how often you need them crawled.
Bugs and false positives
A rule that fires on a site where it should not is a bug, and it is the most useful thing you can
report. Open a GitHub issue with the URL and the rule ID — for example
geo/retrieval-crawlers-allowed — and the finding will be reproduced against that page.
Proposing a rule
Rule proposals are welcome, especially for GEO, where the ground is still moving. A good proposal
names the signal, explains what an answer engine does differently when it is present, and points at
a page where the difference is observable. The full catalogue of all 126 rules ships with the tool
and is printed by wide-angle rules.
Security
Report suspected vulnerabilities by email rather than in a public issue, and allow time for a fix before disclosing. The crawler ships with an SSRF guard, a response-size cap and cancellation, and the test suite fails on any change that weakens them.
What to include in a report
The fastest reports to act on carry four things: the URL that was audited, the rule ID that fired,
what you expected instead, and the version of WideAngle you ran. Version comes from
wide-angle --version. If the site is behind authentication or a WAF, say so — a
surprising number of findings turn out to be a bot-protection rule answering the crawler with a
challenge page rather than the real HTML, which every auditor will then score as thin content.
For a suspected false positive, a link to the page beats a screenshot every time, because the finding is reproduced against the live response rather than against a rendering of it.
Agencies and teams
Agencies are priced per client workspace rather than per seat, so reviewer access is never something you have to ration. If you manage sites for more than a handful of clients, email with a rough count and a sense of how often each needs crawling, and you will get a straight answer about whether the hosted plans fit before anything is committed.
The same applies to in-house teams with unusual constraints — a private network, a staging environment that never faces the internet, or a compliance requirement about where crawl data is stored. Those are worth a conversation rather than a sign-up form.
Response times
Email is answered within two working days. Security reports are answered within one. GitHub issues are triaged weekly, and a reproducible false positive is usually fixed in the release that follows. There is no support queue, no ticket number and no first-line script, because there is one person reading everything.