Earlier quoted context omitted.
> Would being able to set cookies or sending custom headers help? I don't think so. And if it's for SEO purposes, I don't care; these pages won't get crawled by Google anyway. I'm ok ignoring the URLs, but it'd be nice if maybe for example you detect there's a bunch of redirects to a pattern that contains "~login~" and ask the user if they want to add the login URL to the blocklist. I didn't have much success adding…
> these pages won't get crawled by Google anyway. Hmm, how do you indicate this to Google? I'm thinking about how you could tell Checkbot to ignore pages like this. > I didn't have much success adding it myself. The "URL patterns to ignore" setting is just a JavaScript regex string if that helps. It needs some help text at a minimum. A common scenario I see as well is you start a crawl, see the URLs flying by and thi…
I don't. I'm not sure how Google picks up on the fact that they're login walls. Maybe it's heuristics? Someone better at SEO than me could explain.
Re URLs to ignore: Ok, I see, that wasn't clear though. My two-fold suggestion is 1. Add a way to specify plain loose matching (eg. just /account/login/, skip the url parameters, etc) and 2. let me add that pattern after the urls have already been crawled (and make sure I can see which URLs are affected).
Keep in mind that this is pretty raw feedback and you know your product better than me, but I definitely don't think the URLs to ignore is usable right now.
I'm off to bed, I hope all that helped. :)