greenlakelibrary.org rank 1620 |
Number of domains linking to greenlakelibrary.org 1 | semantic flow 0.08 |
Number of links to greenlakelibrary.org 1 | semantic flow 0.08 |
Number of domains linked from greenlakelibrary.org 2 | semantic flow 0.14 |
Number of links from greenlakelibrary.org 2 | semantic flow 0.14 |
Relevant domains with most links to selected domain.
domain | |
---|---|
http://lib-web.org/ | lib-web.org |
Relevant domains with most links from selected domain.
domain | |||
---|---|---|---|
http://pinterest.com/ | 1 | 0.07 | pinterest.com |
http://winnefox.org/ | 1 | 0.07 | winnefox.org |
Pages from domain with most relevant inbound links.
url | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
https://www.greenlakelibrary.org/ | 1 | 0.15 | 0.96 | 0.08 | 1 | yes | 34 | 10 | 2 | 2 | 1 | 1 | |
https://www.greenlakelibrary.org/aboutus/foundation | 1 | 0.16 | 0.96 | 0.07 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
https://www.greenlakelibrary.org/node/2841 | 1 | 0.16 | 0.95 | 0.07 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
https://www.greenlakelibrary.org/aboutus/trustees | 1 | 0.16 | 0.95 | 0.07 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
https://www.greenlakelibrary.org/node/2842 | 1 | 0.16 | 0.95 | 0.07 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
https://www.greenlakelibrary.org/friends | 1 | 0.16 | 0.95 | 0.07 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
https://www.greenlakelibrary.org/services/ill | 1 | 0.16 | 0.77 | 0.06 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
https://www.greenlakelibrary.org/shoutbomb | 1 | 0.16 | 0.76 | 0.06 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 |
Pages from domain with most likely on-topic outgoing links.
url | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
https://www.greenlakelibrary.org/ | 9 | 0.15 | 0.96 | 0.6 | 1 | yes | 34 | 10 | 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.