Scanned sites / spokane.wsu.edu

SEO report for spokane.wsu.edu DR 87

The latest Site Spider scan of spokane.wsu.edu, with 1 scan on record. Each scan is at its own address, for example /domain/spokane-wsu-edu/2026-09-14-0637.

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

Latest scan

Scanned 2026-09-14 06:37:34 UTC, finished 2026-09-14 07:06:02 UTC. Found on page 3 of brave web search results

Site: https://spokane.wsu.edu/

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

62/ 100Needs work

On September 14, 2026 the Site Spider crawled 545 pages and 383 assets of spokane.wsu.edu, starting from https://spokane.wsu.edu/. It scored 62 out of 100, a result that needs work. 12 of 27 checks found something to fix, led by broken links (129), meta descriptions (226), title tags (177); 6 checks passed. Most of the points went to broken links (−8.7), meta descriptions (−6.1), title tags (−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: Medium4 medium and 2 low findings. See the security findings ↓

Pages crawled
545
Assets fetched
383
Status
Completed
Checks with issues
12 of 27
CoverageComplete crawl

928 of 934 discovered URLs were fetched, 6 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 313 link destinations on other sites were checked, 692 left unchecked.

  • Title tags177 issues
    177 of 226 pages have title issues. 69 noindex or canonicalized pages excluded.
    −6 points
  • Meta descriptions226 issues
    226 of 226 pages have meta description issues. 69 noindex or canonicalized pages excluded.
    −6.1 points
  • Headings23 issues
    23 of 226 pages have heading issues. 69 noindex or canonicalized pages excluded.
    −0.5 points
  • Broken links129 issues
    582 internal links point at 129 broken URLs.
    −8.7 points
  • Links to other sites44 issues
    44 destinations answered with an error, 114 could not be determined (timeouts, rate limits or refusals), 692 were left unchecked by the per-scan cap, of 300 destinations checked.
    −4 points
  • Redirects99 issues
    98 redirecting URLs, 13 of them chained.
    −1.3 points
  • Non-200 responses152 issues
    291 URLs did not return a 2xx response. 250 of them are pages, 152 with an error status; the rest are assets or redirects.
    −5.2 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability23 issues
    23 of 254 indexable pages have indexability warnings. 41 pages noindex by design. 1 noindex page is listed in the sitemap, which asks search engines both to visit and to ignore it.
    −0.8 points
  • Image alt textOK
    0 of 578 image references have no alt attribute. 56 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among 383 fetched assets.
  • Orphan pages12 issues
    12 pages have no internal links pointing at them.
    −0.2 points
  • Sitemap coverage167 issues
    30 sitemaps listing 63 URLs: 165 crawled pages missing, 1 listed URL broken or redirecting, 0 reachable only via the sitemap.
    −3.4 points
  • Internal link counts113 noted
    Internal link counts for 295 pages; 113 worth a look.
  • Thin content33 issues
    33 of 226 pages have fewer than 200 words. 69 noindex or canonicalized pages excluded.
    −0.9 points
  • Duplicate content35 issues
    6 groups of pages with identical HTML.
    −0.9 points
  • URL format82 noted
    82 of 545 page URLs are harder to read, share or cache than they need to be.
  • Canonicals79 noted
    79 of 295 pages have a canonical worth checking.
  • Robots directives285 noted
    285 pages carry a robots directive; 10 carry none.
  • Anchor text72 noted
    72 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure2 noted
    2 of 226 pages could use the title, heading and snippet space better. 69 noindex or canonicalized pages excluded.
  • Image weight and alt length5 noted
    0 images over 100 KB; 5 with alt text over 100 characters.
  • Response anomalies35 noted
    35 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 295 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; 13 response headers recorded across 928 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 295 pages; 104 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 41 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

2866 sites, median 80%, average 79%

spokane.wsu.edu scores 62%, higher than 6% of the 2866 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%: 6 sites52%: 9 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%: 75 sites73%: 81 sites74%: 83 sites75%: 86 sites76%: 95 sites77%: 109 sites78%: 131 sites79%: 112 sites80%: 127 sites81%: 124 sites82%: 132 sites83%: 119 sites84%: 132 sites85%: 105 sites86%: 96 sites87%: 95 sites88%: 80 sites89%: 75 sites90%: 55 sites91%: 58 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 17 sites97%: 16 sites98%: 7 sites99%: 3 sites100%: 149 sites62% 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 several critical issues affecting SEO, including broken links and redirects. Prioritizing fixes can significantly improve the site’s health score and user experience.

  1. 1

    Fix Broken Links

    Why: 582 internal links point to 129 broken URLs, impacting user experience and SEO.

    How: Identify broken links and update or remove them.

    Checks: broken-links

  2. 2

    Resolve Redirect Issues

    Why: 98 URLs redirect, making navigation inefficient, especially with 13 chained redirects.

    How: Review redirects and simplify or remove unnecessary chains.

    Checks: redirects

  3. 3

    Address Non-200 Responses

    Why: 291 URLs did not return a 2xx response, signaling potential errors.

    How: Check the status of these URLs and ensure they return a proper response.

    Checks: status-codes

  4. 4

    Optimize Title Tags

    Why: 177 pages have title issues, affecting search visibility.

    How: Revise titles to be concise, under 60 characters and relevant.

    Checks: titles

  5. 5

    Improve Meta Descriptions

    Why: 226 pages lack proper meta descriptions, missed opportunity for click-throughs.

    How: Create unique meta descriptions for each page, keeping them within 150-160 characters.

    Checks: meta-descriptions

  6. 6

    Review Indexability Issues

    Why: 22 indexable pages have warnings, potentially limiting their visibility in search results.

    How: Analyze the indexability settings and adjust any erroneously set noindex tags.

    Checks: indexability

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

Your website has several security issues that need attention, including missing protective headers and outdated JavaScript libraries. These issues could expose your visitors to attacks. Prioritizing these fixes will help improve your site's security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted on their first request using HTTP.

    Fix: Implement the header: Strict-Transport-Security: max-age=31536000; includeSubDomains

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Without CSP, browsers can load scripts from anywhere, increasing risk of XSS attacks.

    Fix: Implement the header: Content-Security-Policy: default-src 'self'

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: This allows your site to be embedded in frames, increasing clickjacking risks.

    Fix: Add the header: X-Frame-Options: SAMEORIGIN

    Evidence: Clickjacking protection

  4. 4

    Outdated jQuery LibrariesMedium

    Why it matters: Using outdated jQuery versions increases vulnerability to multiple types of attacks.

    Fix: Upgrade to jQuery 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may incorrectly process file types, risking security.

    Fix: Add the header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  6. 6

    Server Version DisclosureLow

    Why it matters: Revealing server/technology version can assist attackers in exploiting known vulnerabilities.

    Fix: Configure your server to hide version information.

    Evidence: Software version disclosure

What the checks found

  • 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://spokane.wsu.edu/ → no strict-transport-security
    • https://spokane.wsu.edu/news/events/ → no strict-transport-security
    • https://spokane.wsu.edu/library/ → no strict-transport-security
    • https://spokane.wsu.edu/wsu-spokane-request-for-information/ → no strict-transport-security
    • https://spokane.wsu.edu/campus-space-reservations/ → no strict-transport-security
    • https://spokane.wsu.edu/contact-us/ → no strict-transport-security
    • https://spokane.wsu.edu/news/ → no strict-transport-security
    • https://spokane.wsu.edu/commencement/ → no strict-transport-security
    • https://spokane.wsu.edu/advisory-council/ → no strict-transport-security
    • https://spokane.wsu.edu/leadership/ → no strict-transport-security
    • https://spokane.wsu.edu/facility-hours/ → no strict-transport-security
    • https://spokane.wsu.edu/academic-programs/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 295 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://spokane.wsu.edu/ → no content-security-policy
    • https://spokane.wsu.edu/news/events/ → no content-security-policy
    • https://spokane.wsu.edu/library/ → no content-security-policy
    • https://spokane.wsu.edu/wsu-spokane-request-for-information/ → no content-security-policy
    • https://spokane.wsu.edu/campus-space-reservations/ → no content-security-policy
    • https://spokane.wsu.edu/contact-us/ → no content-security-policy
    • https://spokane.wsu.edu/news/ → no content-security-policy
    • https://spokane.wsu.edu/commencement/ → no content-security-policy
    • https://spokane.wsu.edu/advisory-council/ → no content-security-policy
    • https://spokane.wsu.edu/leadership/ → no content-security-policy
    • https://spokane.wsu.edu/facility-hours/ → no content-security-policy
    • https://spokane.wsu.edu/academic-programs/ → no content-security-policy
  • FoundClickjacking protectionMedium

    11 of 295 HTML pages send x-frame-options. Without X-Frame-Options (or a CSP frame-ancestors directive) the pages can be embedded in a frame on another site and overlaid with invisible controls.

    • https://spokane.wsu.edu/ → no x-frame-options
    • https://spokane.wsu.edu/news/events/ → no x-frame-options
    • https://spokane.wsu.edu/library/ → no x-frame-options
    • https://spokane.wsu.edu/wsu-spokane-request-for-information/ → no x-frame-options
    • https://spokane.wsu.edu/campus-space-reservations/ → no x-frame-options
    • https://spokane.wsu.edu/contact-us/ → no x-frame-options
    • https://spokane.wsu.edu/news/ → no x-frame-options
    • https://spokane.wsu.edu/commencement/ → no x-frame-options
    • https://spokane.wsu.edu/advisory-council/ → no x-frame-options
    • https://spokane.wsu.edu/leadership/ → no x-frame-options
    • https://spokane.wsu.edu/facility-hours/ → no x-frame-options
    • https://spokane.wsu.edu/academic-programs/ → no x-frame-options
  • FoundMIME sniffing protectionLow

    No HTML page sends x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.

    • https://spokane.wsu.edu/ → no x-content-type-options
    • https://spokane.wsu.edu/news/events/ → no x-content-type-options
    • https://spokane.wsu.edu/library/ → no x-content-type-options
    • https://spokane.wsu.edu/wsu-spokane-request-for-information/ → no x-content-type-options
    • https://spokane.wsu.edu/campus-space-reservations/ → no x-content-type-options
    • https://spokane.wsu.edu/contact-us/ → no x-content-type-options
    • https://spokane.wsu.edu/news/ → no x-content-type-options
    • https://spokane.wsu.edu/commencement/ → no x-content-type-options
    • https://spokane.wsu.edu/advisory-council/ → no x-content-type-options
    • https://spokane.wsu.edu/leadership/ → no x-content-type-options
    • https://spokane.wsu.edu/facility-hours/ → no x-content-type-options
    • https://spokane.wsu.edu/academic-programs/ → no x-content-type-options
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • server: nginx (778 responses)
    • server: awselb/2.0 (150 responses)
  • FoundVulnerable JavaScript librariesMedium

    2 libraries with published vulnerabilities: jQuery 1.12.4, jQuery 2.6.3. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.12.4 in https://spokane.wsu.edu/news/wp-content/plugins/wsuwp-plugin-jquery-migrate-cus…: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
    • jQuery 2.6.3 in https://spokane.wsu.edu/wp-content/plugins/gravityforms/js/placeholders.jquery.…: CVE-2015-9251 (XSS via cross-domain AJAX), 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.)

    • cdn.web.wsu.edu (84 script tags)
    • kit.fontawesome.com (40 script tags)
    • player.vimeo.com (30 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 1 path 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: /wp-admin/
5 checks passed, 3 not applicable
  • OKHTTPS

    All 295 crawled pages were served over HTTPS.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    83 forms found, all on HTTPS pages posting to HTTPS addresses.

  • 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 applicableReferrer policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicablePermissions policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicableCookie flags

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

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 spokane.wsu.edu

No other scans of this site yet.

Sites scoring near spokane.wsu.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 spokane.wsu.edu from its pages as published, the way a search engine does. It shows summary figures only.

Own spokane.wsu.edu?