Scanned sites / cul.colgate.edu

SEO report for cul.colgate.edu DR 75

The latest Site Spider scan of cul.colgate.edu, with 1 scan on record. Each scan is at its own address, for example /domain/cul-colgate-edu/2026-09-23-1846.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Latest scan

Scanned 2026-09-23 18:46:59 UTC, finished 2026-09-23 18:52:49 UTC

Site: https://cul.colgate.edu/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

60/ 100Needs work

On September 23, 2026 the Site Spider crawled 247 pages and 476 assets of cul.colgate.edu, starting from https://cul.colgate.edu/. It scored 60 out of 100, a result that needs work. 12 of 27 checks found something to fix, led by title tags (149), meta descriptions (153), heavy assets (16); 6 checks passed. Most of the points went to title tags (−9.6), meta descriptions (−7.9), heavy assets (−6). 9 checks found something the score does not count, listed as noted. 10 checks were not run because the crawl fetched nothing for them. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.

Security review: High1 high, 4 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
247
Assets fetched
476
Status
Completed
Checks with issues
12 of 27
CoverageComplete crawl

723 of 725 discovered URLs were fetched, 2 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 251 left unchecked.

  • Title tags149 issues
    149 of 153 pages have title issues. 2 noindex or canonicalized pages excluded.
    −9.6 points
  • Meta descriptions153 issues
    153 of 153 pages have meta description issues. 2 noindex or canonicalized pages excluded.
    −7.9 points
  • Headings152 issues
    152 of 153 pages have heading issues. 2 noindex or canonicalized pages excluded.
    −5.9 points
  • Broken links16 issues
    18 internal links point at 16 broken URLs.
    −2.1 points
  • Links to other sites1,104 noted
    0 destinations answered with an error, 12 could not be determined (timeouts, rate limits or refusals), 251 were left unchecked by the per-scan cap, of 300 destinations checked.
  • Redirects76 issues
    76 redirecting URLs, 0 of them chained.
    −2 points
  • Non-200 responses16 issues
    93 URLs did not return a 2xx response. 92 of them are pages, 16 with an error status; the rest are assets or redirects.
    −1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability2 issues
    2 of 155 indexable pages have indexability warnings.
    −0.1 points
  • Image alt text157 issues
    157 of 599 image references have no alt attribute. 6 use an empty alt (decorative), which is fine.
    −1.6 points
  • Heavy assets16 issues
    16 assets larger than 500 KB among 476 fetched assets. 1 document over that size is listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages3 issues
    3 pages have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage78 issues
    No sitemap found. Tried: https://cul.colgate.edu/sitemap.xml (404). Add one at /sitemap.xml or list it in robots.txt.
    −3 points
  • Internal link counts5 noted
    Internal link counts for 155 pages; 5 worth a look.
  • Thin content8 issues
    8 of 153 pages have fewer than 200 words. 2 noindex or canonicalized pages excluded.
    −0.4 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format10 noted
    10 of 247 page URLs are harder to read, share or cache than they need to be.
  • Canonicals2 noted
    2 of 155 pages have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 155 pages are open to search engines.
  • Anchor text5 noted
    5 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure1 noted
    1 of 153 pages could use the title, heading and snippet space better. 2 noindex or canonicalized pages excluded.
  • Image weight and alt length50 noted
    46 images over 100 KB; 4 with alt text over 100 characters.
  • Response anomalies2 noted
    2 URLs answered in a way worth looking at.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 155 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 11 response headers recorded across 723 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 155 pages; 0 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed Insights5 noted
    Mobile performance 55 on average across 5 pages; 5 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this site sits among all scanned sites

2868 sites, median 80%, average 79%

cul.colgate.edu scores 60%, higher than 5% of the 2868 scanned sites. See the full ranking.

0751490%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 2 sites36%: 1 site37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 42 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 80 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 111 sites80%: 128 sites81%: 126 sites82%: 132 sites83%: 119 sites84%: 130 sites85%: 104 sites86%: 96 sites87%: 95 sites88%: 81 sites89%: 75 sites90%: 55 sites91%: 58 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 17 sites97%: 16 sites98%: 7 sites99%: 3 sites100%: 149 sites60% here100%90%80%70%60%50%40%30%20%10%0%

Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).

Internal link map

Loading the link map...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

Written from an earlier version of the analysis. The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

The site has multiple issues affecting its health score. Prioritize fixing broken links, redirects, and missing title/meta tags. A sitemap is also essential for better indexing.

  1. 1

    Fix Broken Links

    Why: 18 broken internal links can harm user experience and SEO.

    How: Identify the broken URLs and update or remove links as necessary.

    Checks: broken-links

  2. 2

    Resolve Redirects

    Why: 76 redirects can slow down page loading and complicate crawling.

    How: Review and streamline redirects to point directly to the final URLs.

    Checks: redirects

  3. 3

    Address Non-200 Responses

    Why: 93 URLs returning non-200 responses can hinder site accessibility.

    How: Check and rectify URLs, ensuring they return a 2xx status.

    Checks: status-codes

  4. 4

    Improve Title Tags

    Why: 149 pages with title issues affect the site's SEO ranking.

    How: Create unique title tags for each page to enhance relevance.

    Checks: titles

  5. 5

    Enhance Meta Descriptions

    Why: 153 pages lack meta descriptions, impacting click-through rates.

    How: Add relevant meta descriptions for each page.

    Checks: meta-descriptions

  6. 6

    Create a Sitemap

    Why: A sitemap helps search engines understand site structure and index pages.

    How: Create a sitemap and submit it at /sitemap.xml.

    Checks: sitemap-coverage

Generated automatically; verify each change against your own site before relying on it.

Security review

Written by gpt-4o-mini from 16 checks over the crawl

The website has significant security issues that could expose sensitive data to interception. Key problems include missing HTTPS on many pages, no strict transport security, and the use of a vulnerable JavaScript library. Immediate action is recommended to secure user data and improve overall security posture.

  • 1 high
  • 4 medium
  • 2 low
  • 1 info
  1. 1

    Missing HTTPS on Multiple PagesHigh

    Why it matters: 76 pages served over plain HTTP can be read or modified in transit.

    Fix: Implement HTTPS and redirect all HTTP requests. Use a server config like: 'RewriteEngine On; RewriteCond %{HTTPS} off; RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]'.

    Evidence: HTTPS

  2. 2

    Lack of HTTP Strict Transport Security (HSTS)Medium

    Why it matters: HSTS protects against interception by enforcing HTTPS connections.

    Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains; preload' to all HTTPS responses.

    Evidence: HTTP Strict Transport Security

  3. 3

    Absence of Content Security Policy (CSP)Medium

    Why it matters: No CSP allows scripts and content to load from any source, increasing risk of XSS attacks.

    Fix: Include a CSP header such as 'Content-Security-Policy: default-src 'self';' to restrict content sources.

    Evidence: Content Security Policy

  4. 4

    Forms Not Using HTTPSMedium

    Why it matters: Sending forms over HTTP can expose personal user data.

    Fix: Ensure all forms are served over HTTPS and submit via HTTPS URL.

    Evidence: Forms over HTTPS

  5. 5

    Vulnerable JavaScript Library in UseMedium

    Why it matters: jQuery 3.2.1 has known vulnerabilities that may be exploited.

    Fix: Upgrade to jQuery version 3.5.0 or later to mitigate security risks.

    Evidence: Vulnerable JavaScript libraries

  6. 6

    Missing Referrer PolicyLow

    Why it matters: No referrer policy leaks full URLs including query strings to other sites.

    Fix: Implement a referrer policy with the header 'Referrer-Policy: no-referrer-when-downgrade'.

    Evidence: Referrer policy

  7. 7

    Mixed Content IssuesLow

    Why it matters: HTTPS pages are loading resources over HTTP, risking exposure.

    Fix: Update resource URLs to use HTTPS preferably or remove insecure requests.

    Evidence: Mixed content

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Without a permissions policy, the site may expose unnecessary features to scripts.

    Fix: Add a permissions policy header like 'Permissions-Policy: geolocation=(self)' to limit features.

    Evidence: Permissions policy

What the checks found

  • FoundHTTPSHigh

    76 pages answered 200 over plain HTTP with no redirect to HTTPS, while 79 were served over HTTPS. Anyone on the network path can read or alter these pages.

    • http://cul.colgate.edu/government-document-policy → 200 over http
    • http://cul.colgate.edu/printing-policy → 200 over http
    • http://cul.colgate.edu/floor-plans → 200 over http
    • http://cul.colgate.edu/SCUAOverview → 200 over http
    • http://cul.colgate.edu/AboutCurrentExhibit → 200 over http
    • http://cul.colgate.edu/ → 200 over http
    • http://cul.colgate.edu/node/3481 → 200 over http
    • http://cul.colgate.edu/about-libraries → 200 over http
    • http://cul.colgate.edu/staffdirectory → 200 over http
    • http://cul.colgate.edu/hours → 200 over http
    • http://cul.colgate.edu/technology-libraries → 200 over http
    • http://cul.colgate.edu/borrowing-rules → 200 over http
  • FoundHTTP Strict Transport SecurityMedium

    No HTML page sends strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://cul.colgate.edu/ → no strict-transport-security
    • https://cul.colgate.edu/floor-plans → no strict-transport-security
    • https://cul.colgate.edu/hours → no strict-transport-security
    • https://cul.colgate.edu/node/3481 → no strict-transport-security
    • https://cul.colgate.edu/about-libraries → no strict-transport-security
    • https://cul.colgate.edu/staffdirectory → no strict-transport-security
    • https://cul.colgate.edu/technology-libraries → no strict-transport-security
    • https://cul.colgate.edu/borrowing-rules → no strict-transport-security
    • https://cul.colgate.edu/policies → no strict-transport-security
    • https://cul.colgate.edu/node/3491 → no strict-transport-security
    • https://cul.colgate.edu/zotero → no strict-transport-security
    • https://cul.colgate.edu/scua → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 155 HTML pages send a Content-Security-Policy header or meta tag, so the browser has no restriction on where scripts, styles and frames may load from.

    • https://cul.colgate.edu/ → no content-security-policy
    • https://cul.colgate.edu/floor-plans → no content-security-policy
    • https://cul.colgate.edu/hours → no content-security-policy
    • https://cul.colgate.edu/node/3481 → no content-security-policy
    • https://cul.colgate.edu/about-libraries → no content-security-policy
    • https://cul.colgate.edu/staffdirectory → no content-security-policy
    • https://cul.colgate.edu/technology-libraries → no content-security-policy
    • https://cul.colgate.edu/borrowing-rules → no content-security-policy
    • https://cul.colgate.edu/policies → no content-security-policy
    • https://cul.colgate.edu/node/3491 → no content-security-policy
    • https://cul.colgate.edu/zotero → no content-security-policy
    • https://cul.colgate.edu/scua → no content-security-policy
  • FoundReferrer policyLow

    No HTML page sends referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.

    • https://cul.colgate.edu/ → no referrer-policy
    • https://cul.colgate.edu/floor-plans → no referrer-policy
    • https://cul.colgate.edu/hours → no referrer-policy
    • https://cul.colgate.edu/node/3481 → no referrer-policy
    • https://cul.colgate.edu/about-libraries → no referrer-policy
    • https://cul.colgate.edu/staffdirectory → no referrer-policy
    • https://cul.colgate.edu/technology-libraries → no referrer-policy
    • https://cul.colgate.edu/borrowing-rules → no referrer-policy
    • https://cul.colgate.edu/policies → no referrer-policy
    • https://cul.colgate.edu/node/3491 → no referrer-policy
    • https://cul.colgate.edu/zotero → no referrer-policy
    • https://cul.colgate.edu/scua → no referrer-policy
  • FoundPermissions policyInfo

    No HTML page sends permissions-policy. A Permissions-Policy header turns off browser features the site does not use (camera, microphone, geolocation), limiting what an injected script could do.

    • https://cul.colgate.edu/ → no permissions-policy
    • https://cul.colgate.edu/floor-plans → no permissions-policy
    • https://cul.colgate.edu/hours → no permissions-policy
    • https://cul.colgate.edu/node/3481 → no permissions-policy
    • https://cul.colgate.edu/about-libraries → no permissions-policy
    • https://cul.colgate.edu/staffdirectory → no permissions-policy
    • https://cul.colgate.edu/technology-libraries → no permissions-policy
    • https://cul.colgate.edu/borrowing-rules → no permissions-policy
    • https://cul.colgate.edu/policies → no permissions-policy
    • https://cul.colgate.edu/node/3491 → no permissions-policy
    • https://cul.colgate.edu/zotero → no permissions-policy
    • https://cul.colgate.edu/scua → no permissions-policy
  • FoundMixed contentLow

    4 resources on HTTPS pages are loaded over plain HTTP.

    • https://cul.colgate.edu/connecting loads image http://www.adobe.com/images/getacro.gif
    • https://cul.colgate.edu/connecting loads image http://www.macromedia.com/images/shared/download_buttons/get_flash_player.gif
    • https://cul.colgate.edu/connecting loads image http://www.adobe.com/images/getacro.gif
    • https://cul.colgate.edu/connecting loads image http://www.macromedia.com/images/shared/download_buttons/get_flash_player.gif
  • FoundForms over HTTPSMedium

    3 forms would send what visitors type over plain HTTP, where it can be read or changed on the way.

    • http://cul.colgate.edu/government-document-policy has 1 form on a page served over plain HTTP
    • http://cul.colgate.edu/printing-policy has 1 form on a page served over plain HTTP
    • http://cul.colgate.edu/floor-plans has 1 form on a page served over plain HTTP
  • FoundVulnerable JavaScript librariesMedium

    1 library with published vulnerabilities: jQuery 3.2.1. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 3.2.1 in https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • NoteThird-party scripts

    Scripts run from 3 other domains without Subresource Integrity, so a compromise of any of them changes what runs on this site. (Tag managers and analytics rarely support SRI; a Content-Security-Policy that names these hosts is the usual control.)

    • www.googletagmanager.com (40 script tags)
    • ajax.googleapis.com (40 script tags)
    • v2.libanswers.com (1 script tag)
  • NoteSensitive paths in robots.txt

    robots.txt lists 5 paths that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.

    • Disallow: /web.config
    • Disallow: /admin/
    • Disallow: /user/login
    • Disallow: /index.php/admin/
    • Disallow: /index.php/user/login
5 checks passed, 1 not applicable
  • OKClickjacking protection

    x-frame-options is set on all 155 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 155 HTML pages.

  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.

Earlier scans of cul.colgate.edu

No other scans of this site yet.

Sites scoring near cul.colgate.edu

Their neighbours in the SEO rank table, which orders every scanned site by health score.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

This report was produced by the DIY SEO Hub Site Spider crawling cul.colgate.edu from its pages as published, the way a search engine does. It shows summary figures only.

Own cul.colgate.edu?