Scanned sites / forwardspokane.com / 2026-09-14-0714

forwardspokane.com scan from 2026-09-14 07:14:10 UTC DR 3

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

Scan 2026-09-14-0714

Scanned 2026-09-14 07:14:10 UTC, finished 2026-09-14 07:15:30 UTC. Found with openstreetmap overpass

Site: https://forwardspokane.com/

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 26 pages and 2 assets of forwardspokane.com, starting from https://forwardspokane.com/. It scored 62 out of 100, a result that needs work. 12 of 27 checks found something to fix, led by indexability (21), title tags (17), meta descriptions (19); 9 checks passed. Most of the points went to indexability (−9.5), title tags (−7.7), meta descriptions (−6.9). 6 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 1 low findings. See the security findings ↓

Pages crawled
26
Assets fetched
2
Status
Completed
Checks with issues
12 of 27
CoverageComplete crawl

28 of 28 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 5 link destinations on other sites were checked.

  • Title tags17 issues
    17 of 22 pages have title issues.
    −7.7 points
  • Meta descriptions19 issues
    19 of 22 pages have meta description issues.
    −6.9 points
  • Headings15 issues
    15 of 22 pages have heading issues.
    −4.1 points
  • Broken links1 issue
    2 internal links point at 1 broken URL.
    −0.9 points
  • Links to other sites14 noted
    0 destinations answered with an error, 1 could not be determined (timeouts, rate limits or refusals), of 3 destinations checked.
  • Redirects3 issues
    3 redirecting URLs, 0 of them chained.
    −0.5 points
  • Non-200 responses1 issue
    4 URLs did not return a 2xx response. 4 of them are pages, 1 with an error status; the rest are assets or redirects.
    −0.5 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability21 issues
    21 of 22 indexable pages have indexability warnings.
    −9.5 points
  • Image alt text3 issues
    3 of 205 image references have no alt attribute. 171 use an empty alt (decorative), which is fine.
    −0.1 points
  • Heavy assetsOK
    0 assets larger than 500 KB among 2 fetched assets.
  • Orphan pages2 issues
    2 pages have no internal links pointing at them.
    −0.4 points
  • Sitemap coverage22 issues
    1 sitemap listing 0 URLs: 22 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −6 points
  • Internal link countsOK
    Internal link counts for 22 pages; none is a dead end or buried.
  • Thin content3 issues
    3 of 22 pages have fewer than 200 words.
    −1.1 points
  • Duplicate content2 issues
    1 group of pages with identical HTML.
    −0.7 points
  • URL format1 noted
    1 of 26 page URLs are harder to read, share or cache than they need to be.
  • Canonicals21 noted
    21 of 22 pages have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 22 pages are open to search engines.
  • Anchor text7 noted
    7 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure22 noted
    22 of 22 pages could use the title, heading and snippet space better.
  • Image weight and alt lengthOK
    No image is over 100 KB or carries alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • 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 22 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; 8 response headers recorded across 28 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 22 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 63 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 scan sits among all scanned sites

2866 sites, median 80%, average 79%

forwardspokane.com 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%: 120 sites84%: 131 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.

Your website has several issues that can improve SEO and user experience. Focus on fixing broken links, updating title tags, and addressing indexability warnings for optimal results.

  1. 1

    Fix Broken Links

    Why: Broken links negatively affect user experience and site authority.

    How: Remove or update the links pointing to https://forwardspokane.com/instagram.com.

    Checks: broken-links

  2. 2

    Update Title Tags

    Why: Improving title tags enhances relevance in search results.

    How: Revise titles to be concise and include target keywords (e.g., >30 characters).

    Checks: titles

  3. 3

    Address Indexability Issues

    Why: Pages need proper canonical tags to avoid indexing problems.

    How: Add a canonical tag for all affected pages, pointing to the preferred URL.

    Checks: indexability

  4. 4

    Improve Meta Descriptions

    Why: Optimized meta descriptions increase click-through rates.

    How: Revise meta descriptions to be unique and under 160 characters.

    Checks: meta-descriptions

  5. 5

    Correct Heading Structure

    Why: Proper headings improve content hierarchy and SEO.

    How: Ensure each page has a single H1 tag and appropriate H2/H3 tags.

    Checks: headings

  6. 6

    Update Sitemap Coverage

    Why: Ensuring all pages are in the sitemap aids in indexing.

    How: Add all crawled pages to the sitemap and resubmit it to search engines.

    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 forwardspokane.com lacks several important security headers, leaving it vulnerable to various attacks such as clickjacking and interception. Additionally, it uses an outdated version of jQuery with known vulnerabilities. Implementing the recommended changes will enhance the site's security and protect users.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Lack of HSTS allows interception of the initial HTTP request.

    Fix: Add 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: Absence of CSP increases risk of cross-site scripting (XSS) attacks.

    Fix: Add the header: Content-Security-Policy: default-src 'self'; script-src 'self';

    Evidence: Content Security Policy

  3. 3

    No Clickjacking ProtectionMedium

    Why it matters: Without X-Frame-Options, the site is vulnerable to clickjacking.

    Fix: Add the header: X-Frame-Options: DENY.

    Evidence: Clickjacking protection

  4. 4

    Outdated jQuery LibraryMedium

    Why it matters: jQuery 1.11.0 has known vulnerabilities that could be exploited.

    Fix: Upgrade jQuery to at least 3.5.0.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing MIME Sniffing ProtectionLow

    Why it matters: Absence of this header can allow browsers to misinterpret file types.

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

    Evidence: MIME sniffing protection

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://forwardspokane.com/ → no strict-transport-security
    • https://forwardspokane.com/home → no strict-transport-security
    • https://forwardspokane.com/programs → no strict-transport-security
    • https://forwardspokane.com/group-workout-spokane-washington → no strict-transport-security
    • https://forwardspokane.com/free-resources → no strict-transport-security
    • https://forwardspokane.com/transformation-kit → no strict-transport-security
    • https://forwardspokane.com/transformation-blueprint → no strict-transport-security
    • https://forwardspokane.com/21day-home-challenge → no strict-transport-security
    • https://forwardspokane.com/membership → no strict-transport-security
    • https://forwardspokane.com/schedule → no strict-transport-security
    • https://forwardspokane.com/about-us → no strict-transport-security
    • https://forwardspokane.com/reviews → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 22 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://forwardspokane.com/ → no content-security-policy
    • https://forwardspokane.com/home → no content-security-policy
    • https://forwardspokane.com/programs → no content-security-policy
    • https://forwardspokane.com/group-workout-spokane-washington → no content-security-policy
    • https://forwardspokane.com/free-resources → no content-security-policy
    • https://forwardspokane.com/transformation-kit → no content-security-policy
    • https://forwardspokane.com/transformation-blueprint → no content-security-policy
    • https://forwardspokane.com/21day-home-challenge → no content-security-policy
    • https://forwardspokane.com/membership → no content-security-policy
    • https://forwardspokane.com/schedule → no content-security-policy
    • https://forwardspokane.com/about-us → no content-security-policy
    • https://forwardspokane.com/reviews → no content-security-policy
  • FoundClickjacking protectionMedium

    No HTML page sends 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://forwardspokane.com/ → no x-frame-options
    • https://forwardspokane.com/home → no x-frame-options
    • https://forwardspokane.com/programs → no x-frame-options
    • https://forwardspokane.com/group-workout-spokane-washington → no x-frame-options
    • https://forwardspokane.com/free-resources → no x-frame-options
    • https://forwardspokane.com/transformation-kit → no x-frame-options
    • https://forwardspokane.com/transformation-blueprint → no x-frame-options
    • https://forwardspokane.com/21day-home-challenge → no x-frame-options
    • https://forwardspokane.com/membership → no x-frame-options
    • https://forwardspokane.com/schedule → no x-frame-options
    • https://forwardspokane.com/about-us → no x-frame-options
    • https://forwardspokane.com/reviews → 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://forwardspokane.com/ → no x-content-type-options
    • https://forwardspokane.com/home → no x-content-type-options
    • https://forwardspokane.com/programs → no x-content-type-options
    • https://forwardspokane.com/group-workout-spokane-washington → no x-content-type-options
    • https://forwardspokane.com/free-resources → no x-content-type-options
    • https://forwardspokane.com/transformation-kit → no x-content-type-options
    • https://forwardspokane.com/transformation-blueprint → no x-content-type-options
    • https://forwardspokane.com/21day-home-challenge → no x-content-type-options
    • https://forwardspokane.com/membership → no x-content-type-options
    • https://forwardspokane.com/schedule → no x-content-type-options
    • https://forwardspokane.com/about-us → no x-content-type-options
    • https://forwardspokane.com/reviews → no x-content-type-options
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 1.11.0 in https://code.jquery.com/jquery-1.11.0.min.js: 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.)

    • stcdn.leadconnectorhq.com (79 script tags)
    • code.jquery.com (6 script tags)
    • cdn.jsdelivr.net (3 script tags)
5 checks passed, 5 not applicable
  • OKHTTPS

    All 22 crawled pages were served over HTTPS.

  • OKSoftware version disclosure

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

  • OKMixed content

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

  • 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.

  • Not applicableForms over HTTPS

    No forms were found on the sampled pages.

  • Not applicableSensitive paths in robots.txt

    No robots.txt was fetched.

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.

Sites scoring near forwardspokane.com

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 forwardspokane.com from its pages as published, the way a search engine does. It shows summary figures only.

Own forwardspokane.com?

  • Claim this site to manage the listing, hide it from the public lists, or keep it.
  • Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming forwardspokane.com. Removal needs no account and no proof of purchase.