Bug reports, crawl-accuracy questions, feature requests and partnerships all go to the same inbox. The more precisely you describe what happened, the faster it gets fixed — the checklist below takes two minutes and usually removes an entire round of back-and-forth.
hello@fast-index-google.pages.dev
Typical response time: 2 business days. Reports that include the checklist items below are usually answered much faster because they can be reproduced on the first attempt.
When a crawl looks wrong — a bot reported as blocked but you believe it is allowed, a status that disagrees with your server logs, a job stuck in a state — include:
This turns "the crawler is broken" into a reproducible case. In most past reports the answer was a WAF rule, a CDN bot-management policy, or a rate limit triggering on parallel fetches — all visible once the job ID is known.
Yes — if it has a stable, documented user agent that fetches over plain HTTP, send the UA string and name and it can be added to the pool.
No. All fetches are anonymous, exactly like a search crawler's first visit.
Yes — the dashboard's own endpoints are public and documented; see the API reference and use batch submit with one URL per line.
The project is free and self-hostable; email for partnership and branding enquiries.
Not necessarily. It means the server served different bytes to that bot than to the browser. Start with the how it works page before assuming cloaking.