Scanned sites / www.kurtishawkins.com

SEO report for www.kurtishawkins.com

The latest Site Spider scan of www.kurtishawkins.com, with 2 scans on record. Each scan is at its own address, for example /domain/www-kurtishawkins-com/2026-10-01-0846.

Latest scan

Scanned 10/1/2026, 8:46:26 AM, finished 10/1/2026, 9:18:40 PM. Found on page 5 of brave web search results

Site: https://www.kurtishawkins.com/

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

35/ 100Poor

On October 1, 2026 the Site Spider crawled 732 pages and 766 assets of www.kurtishawkins.com, starting from https://www.kurtishawkins.com/. It scored 35 out of 100, a poor result. 13 of 16 checks found something to fix, led by broken links (274), non-200 responses (276), title tags (206); 2 checks passed. Most of the points went to broken links (−19.6), non-200 responses (−9.9), title tags (−7.4). 1 check found something the score does not count, listed as noted. 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, 2 low and 1 info findings. See the security findings ↓

Pages crawled
732
Assets fetched
766
Status
Completed
Checks with issues
13 of 16
CoverageComplete crawl

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

  • Title tags206 issues
    206 of 258 pages have title issues. 21 noindex or canonicalized pages excluded.
    −7.4 points
  • Meta descriptions235 issues
    235 of 258 pages have meta description issues. 21 noindex or canonicalized pages excluded.
    −6.7 points
  • Headings5 issues
    5 of 258 pages have heading issues. 21 noindex or canonicalized pages excluded.
    −0.1 points
  • Broken links274 issues
    274 internal links point at 274 broken URLs.
    −19.6 points
  • Links to other sites12 issues
    12 destinations answered with an error, 47 could not be determined (timeouts, rate limits or refusals), of 179 destinations checked.
    −1.7 points
  • Redirects59 issues
    178 redirecting URLs, 0 of them chained.
    −0.8 points
  • Non-200 responses276 issues
    462 URLs did not return a 2xx response. 453 of them are pages, 276 with an error status; the rest are assets or redirects.
    −9.9 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability176 issues
    176 of 258 indexable pages have indexability warnings. 21 pages noindex by design.
    −6.3 points
  • Image alt text1 issue
    1 of 659 image references have no alt attribute. 122 use an empty alt (decorative), which is fine.
  • Heavy assets35 issues
    35 assets larger than 500 KB among 766 fetched assets.
    −6 points
  • Orphan pages172 issues
    172 pages have no internal links pointing at them.
    −2.5 points
  • Sitemap coverage357 issues
    7 sitemaps listing 246 URLs: 184 crawled pages missing, 172 listed URLs broken or redirecting, 1 reachable only via the sitemap.
    −6 points
  • Internal link countsOK
    Internal link counts for 279 pages.
  • Thin content2 issues
    2 of 258 pages have fewer than 200 words. 21 noindex or canonicalized pages excluded.
    −0.1 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this site sits among all scanned sites

1645 sites, median 80%, average 79%

www.kurtishawkins.com scores 35%, higher than 0% of the 1645 scanned sites. See the full ranking.

0511020%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 0 sites15%: 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%: 2 sites38%: 2 sites39%: 0 sites40%: 2 sites41%: 0 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 5 sites50%: 3 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 6 sites55%: 3 sites56%: 5 sites57%: 6 sites58%: 11 sites59%: 6 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 16 sites64%: 10 sites65%: 18 sites66%: 18 sites67%: 31 sites68%: 25 sites69%: 24 sites70%: 34 sites71%: 37 sites72%: 47 sites73%: 41 sites74%: 46 sites75%: 53 sites76%: 61 sites77%: 59 sites78%: 76 sites79%: 58 sites80%: 80 sites81%: 102 sites82%: 80 sites83%: 77 sites84%: 71 sites85%: 56 sites86%: 58 sites87%: 53 sites88%: 56 sites89%: 49 sites90%: 31 sites91%: 34 sites92%: 22 sites93%: 11 sites94%: 13 sites95%: 7 sites96%: 6 sites97%: 7 sites98%: 2 sites99%: 2 sites100%: 54 sites35% 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

Your website has serious SEO issues impacting visibility. Focus on fixing broken links, non-200 responses, and title/meta description problems to improve health. Consider optimizing your sitemap and addressing heavy assets for better performance.

  1. 1

    Fix Broken Links

    Why: 274 internal links to broken URLs damage user experience and SEO.

    How: Identify the broken links, replace them with correct URLs, or remove them.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: 462 URLs not returning a 2xx response can negatively affect site indexing.

    How: Review the URLs, correct or remove those that return errors.

    Checks: status-codes

  3. 3

    Write Title Tags

    Why: 176 pages are missing title tags, harming discoverability.

    How: Create unique and relevant title tags for the affected pages.

    Checks: titles

  4. 4

    Update Meta Descriptions

    Why: 235 pages have meta description issues, impacting click-through rates.

    How: Write compelling meta descriptions for pages lacking them.

    Checks: meta-descriptions

  5. 5

    Address Sitemap Coverage

    Why: The sitemap shows 184 missing URLs, hindering indexing.

    How: Update the sitemap to ensure all pages are properly listed.

    Checks: sitemap-coverage

  6. 6

    Optimize Heavy Assets

    Why: Large assets slow down site loading, affecting user experience.

    How: Reduce file sizes of heavy assets without losing quality or relocate if appropriate.

    Checks: heavy-assets

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 site has several security weaknesses that could expose it to various attacks, including session hijacking and clickjacking. Key areas for improvement include implementing security headers, upgrading to secure library versions, and setting proper cookie flags to enhance protection.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors typing the address without HTTPS could be intercepted on their first request.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Lack of Clickjacking Protection (X-Frame-Options)Medium

    Why it matters: Without X-Frame-Options, the site can be embedded in a frame on another site, exposing users to clickjacking attacks.

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

    Evidence: Clickjacking protection

  3. 3

    Insecure Cookie FlagsMedium

    Why it matters: Cookies lacking Secure and HttpOnly attributes can be accessed by scripts and transmitted over insecure connections.

    Fix: Set cookies with flags: Secure, HttpOnly, and SameSite=Strict.

    Evidence: Cookie flags

  4. 4

    Use of Vulnerable JavaScript LibrariesMedium

    Why it matters: The outdated jQuery version may expose the site to known vulnerabilities.

    Fix: Upgrade jQuery to version 3.5.0 or higher.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Server Version Information DisclosedLow

    Why it matters: Detailed server banners can reveal vulnerabilities that might be exploited.

    Fix: Hide version details by configuring the server to: Server: nginx.

    Evidence: Software version disclosure

  6. 6

    Third-party Scripts Lack Subresource IntegrityLow

    Why it matters: This could lead to the execution of compromised scripts.

    Fix: Implement a Content-Security-Policy that explicitly allows only trusted sources.

    Evidence: Third-party scripts

  7. 7

    Missing Permissions-Policy HeaderInfo

    Why it matters: Lack of this header allows potentially harmful interactions from injected scripts.

    Fix: Add the header: Permissions-Policy: interest-cohort=(), geolocation=(self).

    Evidence: Permissions policy

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://www.kurtishawkins.com/ → no strict-transport-security
    • https://www.kurtishawkins.com/property-organizer-login/ → no strict-transport-security
    • https://www.kurtishawkins.com/search-lethbridge-real-estate/ → no strict-transport-security
    • https://www.kurtishawkins.com/neighborhoods/ → no strict-transport-security
    • https://www.kurtishawkins.com/neighborhoods/suited-home-lethbridge/ → no strict-transport-security
    • https://www.kurtishawkins.com/neighborhoods/lethbridge-and-area-acreages/ → no strict-transport-security
    • https://www.kurtishawkins.com/homes-for-sale-featured/ → no strict-transport-security
    • https://www.kurtishawkins.com/market-reports/ → no strict-transport-security
    • https://www.kurtishawkins.com/email-alerts/ → no strict-transport-security
    • https://www.kurtishawkins.com/popular-neighbourhoods-in-lethbridge/ → no strict-transport-security
    • https://www.kurtishawkins.com/buyers/ → no strict-transport-security
    • https://www.kurtishawkins.com/pros-cons-of-living-in-lethbridge/ → no strict-transport-security
  • 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://www.kurtishawkins.com/ → no x-frame-options
    • https://www.kurtishawkins.com/property-organizer-login/ → no x-frame-options
    • https://www.kurtishawkins.com/search-lethbridge-real-estate/ → no x-frame-options
    • https://www.kurtishawkins.com/neighborhoods/ → no x-frame-options
    • https://www.kurtishawkins.com/neighborhoods/suited-home-lethbridge/ → no x-frame-options
    • https://www.kurtishawkins.com/neighborhoods/lethbridge-and-area-acreages/ → no x-frame-options
    • https://www.kurtishawkins.com/homes-for-sale-featured/ → no x-frame-options
    • https://www.kurtishawkins.com/market-reports/ → no x-frame-options
    • https://www.kurtishawkins.com/email-alerts/ → no x-frame-options
    • https://www.kurtishawkins.com/popular-neighbourhoods-in-lethbridge/ → no x-frame-options
    • https://www.kurtishawkins.com/buyers/ → no x-frame-options
    • https://www.kurtishawkins.com/pros-cons-of-living-in-lethbridge/ → no x-frame-options
  • FoundPermissions policyInfo

    277 of 279 HTML pages send 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://www.kurtishawkins.com/dashboard/ → no permissions-policy
    • https://www.kurtishawkins.com/dashboard/?action=lostpassword → no permissions-policy
  • FoundSoftware version disclosureLow

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

    • server: Flywheel/5.1.0 (1497 responses)
    • server: Varnish (1 response)
  • FoundCookie flagsMedium

    4 of 4 cookies are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • ihf_lead_capture_user_id (set by https://www.kurtishawkins.com/property-organizer-login/) lacks Secure, HttpOnly, SameSite
    • ihf_session_id (set by https://www.kurtishawkins.com/property-organizer-login/) lacks Secure, HttpOnly, SameSite
    • ihf_last_search_url (set by https://www.kurtishawkins.com/homes-for-sale-featured/) lacks Secure, HttpOnly, SameSite
    • wordpress_test_cookie (set by https://www.kurtishawkins.com/dashboard/) lacks SameSite
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 3.1.2 in https://www.kurtishawkins.com/wp-content/plugins/gravityforms/js/placeholders.j…: 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 2 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 (39 script tags)
    • kestrel.idxhome.com (40 script tags)
9 checks passed
  • OKHTTPS

    All 279 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set on 2 of 279 pages.

  • OKMIME sniffing protection

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

  • OKReferrer policy

    referrer-policy is set on all 279 HTML pages.

  • OKMixed content

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

  • OKForms over HTTPS

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

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

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 www.kurtishawkins.com

Sites scoring near www.kurtishawkins.com

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

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

Own www.kurtishawkins.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 www.kurtishawkins.com. Removal needs no account and no proof of purchase.
www.kurtishawkins.com SEO report | DIY SEO Hub