ccga.edu rank 1782 |
Number of domains linking to ccga.edu 1 | semantic flow 0.09 |
Number of links to ccga.edu 1 | semantic flow 0.09 |
Number of domains linked from ccga.edu 7 | semantic flow 0.5 |
Number of links from ccga.edu 10 | semantic flow 0.5 |
Relevant domains with most links to selected domain.
domain | |
---|---|
http://georgialibraries.org/ | georgialibraries.org |
Relevant domains with most links from selected domain.
Pages from domain with most relevant inbound links.
url | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
http://www.ccga.edu/page.cfm?p=688 | 1 | 0.15 | 0.87 | 0.09 | 0.98 | yes | 68 | 31 | 11 | 8 | 1 | 1 | |
http://www.ccga.edu/page.cfm?p=891 | 1 | 0.15 | 0.88 | 0.06 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://libanswers.ccga.edu/ | 1 | 0.15 | 0.86 | 0.06 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.ccga.edu/page.cfm?p=695 | 1 | 0.15 | 0.85 | 0.06 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.ccga.edu/page.cfm?p=901 | 1 | 0.15 | 0.83 | 0.06 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.ccga.edu/page.cfm?p=2009 | 1 | 0.15 | 0.77 | 0.05 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.ccga.edu/page.cfm?p=1725 | 1 | 0.15 | 0.7 | 0.05 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.ccga.edu/page.cfm?p=506 | 1 | 0.15 | 0.67 | 0.05 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://libguides.ccga.edu/ | 1 | 0.15 | 0.67 | 0.05 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 | |
http://www.ccga.edu/page.cfm?p=1493 | 1 | 0.15 | 0.49 | 0.03 | -1 | - | -1 | -1 | -1 | -1 | 0 | 0 |
Pages from domain with most likely on-topic outgoing links.
url | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
http://www.ccga.edu/page.cfm?p=688 | 29 | 0.15 | 0.87 | 1.5 | 0.98 | yes | 68 | 31 | 11 | 8 | 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.