masshome.com rank 1920 |
Number of domains linking to masshome.com 1 | semantic flow 0.07 |
Number of links to masshome.com 1 | semantic flow 0.07 |
Number of domains linked from masshome.com 263 | semantic flow 22.02 |
Number of links from masshome.com 385 | semantic flow 22.02 |
Relevant domains with most links to selected domain.
domain | |
---|---|
http://medfordlibrary.org/ | medfordlibrary.org |
Relevant domains with most links from selected domain.
Pages from domain with most relevant inbound links.
url | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
http://www.masshome.com/histsoc.html | 1 | 0.16 | 0.94 | 0.07 | 0.96 | yes | 665 | 425 | 410 | 284 | 1 | 1 | |
http://www.masshome.com/news.html | 1 | 0.15 | 0.89 | 0.07 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.masshome.com/histcwar.html | 1 | 0.15 | 0.87 | 0.07 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.masshome.com/libs.html | 1 | 0.15 | 0.78 | 0.06 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.masshome.com/govt.html | 1 | 0.15 | 0.74 | 0.06 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.masshome.com/schools.html | 1 | 0.15 | 0.73 | 0.06 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.masshome.com/hist.html | 1 | 0.15 | 0.63 | 0.05 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.masshome.com/bus.html | 1 | 0.15 | 0.58 | 0.04 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.masshome.com/histhouse.html | 1 | 0.15 | 0.56 | 0.04 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.masshome.com/sports.html | 1 | 0.15 | 0.3 | 0.02 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 |
Pages from domain with most likely on-topic outgoing links.
url | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
http://www.masshome.com/histsoc.html | 400 | 0.16 | 0.94 | 22.81 | 0.96 | yes | 665 | 425 | 410 | 284 | 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.