richmond.edu rank 1262 |
Number of domains linking to richmond.edu 6 | semantic flow 0.32 |
Number of links to richmond.edu 6 | semantic flow 0.32 |
Number of domains linked from richmond.edu 1 | semantic flow 0.07 |
Number of links from richmond.edu 1 | semantic flow 0.07 |
Pages with highest topical PageRank pointing to domain.
url / atext / target url | |
---|---|
https://www.veridiansoftware.com/collections/ university of richmond ↳https://collegian.richmond.edu/ | www.veridiansoftware.com |
Relevant domains with most links to selected domain.
Relevant domains with most links from selected domain.
domain | |||
---|---|---|---|
http://thecollegianur.com/ | 1 | 0.07 | thecollegianur.com |
Pages from domain with most relevant inbound links.
url | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
http://dlxs.richmond.edu/d/ddr/ | 2 | 0.15 | 0.96 | 0.07 | -1 | - | -1 | -1 | -1 | -1 | 2 | 2 | |
https://collegian.richmond.edu/ | 1 | 0.15 | 0.92 | 0.08 | 1 | yes | 13 | 4 | 2 | 2 | 1 | 1 | |
http://library.richmond.edu/ | 1 | 0.15 | 0.97 | 0.07 | -1 | - | -1 | -1 | -1 | -1 | 1 | 1 | |
http://library.richmond.edu/digital/projects.html | 1 | 0.19 | 0.92 | 0.07 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://library.richmond.edu/digital/contact.html | 1 | 0.19 | 0.92 | 0.07 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://dsl.richmond.edu/people/ | 1 | 0.15 | 0.89 | 0.06 | -1 | - | -1 | -1 | -1 | -1 | 1 | 1 | |
http://library.richmond.edu/about/ | 1 | 0.15 | 0.76 | 0.04 | -1 | - | -1 | -1 | -1 | -1 | 1 | 1 |
Pages from domain with most likely on-topic outgoing links.
url | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
https://collegian.richmond.edu/ | 3 | 0.15 | 0.92 | 0.2 | 1 | yes | 13 | 4 | 2 | 2 | 1 | 1 |
Similar domains to domain, based on inbound linking patterns from other relevant domains. This is also known in SEO as topical co-citation.
std::map::erase()
does not return an iterator to the next element, but an size_t
indicating the number of elements removed. This is actually a fairly common design pattern in the standard library, and it's not necessarily a problem. In this case, though, it is.