Closed changecourse closed 5 years ago
also, lets add the rel="nofollow"
on the outbound link, so we don't give them any SEO points.
Per Google's own https://support.google.com/webmasters/answer/96569?hl=en
What are Google's policies and some specific examples of nofollow usage?
Here are some cases in which you might want to consider using nofollow:
- Untrusted content: If you can't or don't want to vouch for the content of pages you link to from your site — for example, untrusted user comments or guestbook entries — you should nofollow those links. This can discourage spammers from targeting your site, and will help keep your site from inadvertently passing PageRank to bad neighborhoods on the web. In particular, comment spammers may decide not to target a specific content management system or blog service if they can see that untrusted links in that service are nofollowed. If you want to recognize and reward trustworthy contributors, you could decide to automatically or manually remove the nofollow attribute on links posted by members or users who have consistently made high-quality contributions over time.
Another casual observation... We only get a breach.Domain
back from HIBP API, which is a protocol-less "evite.com":
// via https://haveibeenpwned.com/api/v2/breach/Evite
{
Name: "Evite",
Title: "Evite",
Domain: "evite.com",
...
}
We'd need to prefix that domain with http:// (and not https:// or protocol-less //${Domain}
).
I tried with http://${breach.Domain}
and got 56 results with a non 2xx or 3xx response code.
When I tried to make the default protocol HTTPS (a la https://${breach.Domain}
), the number of HTTP errors went from 56 to 125:
Make it easier for folks to navigate to the website of a given breach, via the breach detail page.
Zeplin: https://zpl.io/a7WP5m8