Scanned sites / www.williamsdingmann.com / 2026-09-26-1000

www.williamsdingmann.com scan from 9/26/2026, 10:00:01 AM

Scan 2026-09-26-1000

Scanned 9/26/2026, 10:00:01 AM, finished 9/26/2026, 11:21:14 AM. Found on page 3 of chatgpt for browser (api usage) results

Site: https://www.williamsdingmann.com/

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

83/ 100Good

On September 26, 2026 the Site Spider crawled 5000 pages and 60 assets of www.williamsdingmann.com, starting from https://www.williamsdingmann.com/. It scored 83 out of 100, a good result. 8 of 14 checks found something to fix, led by orphan pages (1680), thin content (1625), non-200 responses (500); 6 checks passed. 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: Medium6 medium, 1 low and 1 info findings. See the security findings ↓

Pages crawled
5000
Assets fetched
60
Status
Completed
Checks with issues
8 of 14
  • Title tags2 issues
    2 of 1625 pages have title issues. 55 noindex or canonicalized pages excluded.
  • Meta descriptionsOK
    0 of 1625 pages have meta description issues. 55 noindex or canonicalized pages excluded.
  • HeadingsOK
    0 of 1625 pages have heading issues. 55 noindex or canonicalized pages excluded.
  • Broken links1 issue
    1680 internal links point at 1 broken URL.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responses500 issues
    3320 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability55 issues
    55 of 1680 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 3360 image references have no alt attribute.
  • Heavy assets1 issue
    1 asset larger than 500 KB among the 60 heaviest.
  • Orphan pages1680 issues
    1680 pages have no internal links pointing at them.
  • Sitemap coverage500 issues
    14 sitemaps listing 11,306+ URLs (first 5,000 entries read): 0 crawled pages missing, 3320 listed URLs broken or redirecting, 1680 reachable only via the sitemap. 6,306 listed URLs not crawled within the 5000-page budget.
  • Thin content1625 issues
    1625 of 1625 pages have fewer than 200 words. 55 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1282 sites, median 82%, average 80%

www.williamsdingmann.com scores 83%, higher than 52% of the 1282 scanned sites. See the full ranking.

035690%: 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%: 1 site36%: 1 site37%: 0 sites38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 2 sites47%: 1 site48%: 1 site49%: 0 sites50%: 3 sites51%: 4 sites52%: 4 sites53%: 4 sites54%: 4 sites55%: 2 sites56%: 2 sites57%: 3 sites58%: 8 sites59%: 4 sites60%: 7 sites61%: 9 sites62%: 12 sites63%: 5 sites64%: 9 sites65%: 10 sites66%: 11 sites67%: 16 sites68%: 29 sites69%: 14 sites70%: 26 sites71%: 25 sites72%: 29 sites73%: 28 sites74%: 33 sites75%: 30 sites76%: 41 sites77%: 43 sites78%: 40 sites79%: 38 sites80%: 51 sites81%: 59 sites82%: 56 sites83%: 55 sites84%: 61 sites85%: 54 sites86%: 49 sites87%: 54 sites88%: 61 sites89%: 48 sites90%: 69 sites91%: 42 sites92%: 27 sites93%: 20 sites94%: 19 sites95%: 11 sites96%: 11 sites97%: 4 sites98%: 3 sites99%: 2 sites100%: 23 sites83% 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

Significant issues found on the site include many broken links and non-200 responses. Addressing these will improve user experience and SEO. Focus on resolving broken links first for the best impact.

  1. 1

    Fix Broken Links

    Why: 1680 internal links are broken, leading to a poor user experience.

    How: Identify the broken links using the crawl report and either remove them or update them to point to the correct URLs.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: 3320 URLs are returning errors instead of a 200 response, hindering accessibility.

    How: Check the URLs returning error codes and correct server settings or redirects as necessary.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: Two title tags exceed the recommended length, which can affect search engine display.

    How: Shorten the title lengths to under 60 characters to ensure proper display in search results.

    Checks: titles

  4. 4

    Address Indexability Warnings

    Why: 55 pages have indexability warnings, potentially reducing search visibility.

    How: Evaluate the warnings and correct any canonical issues or modify robots.txt file as needed.

    Checks: indexability

  5. 5

    Link to Orphan Pages

    Why: 1680 pages cannot be reached by users, risking valuable content being ignored.

    How: Create internal links to orphan pages from relevant existing pages to improve visibility.

    Checks: orphan-pages

  6. 6

    Reduce Hefty Assets

    Why: Heavy assets can slow down page loading times, impacting user experience.

    How: Optimize or compress assets larger than 500 KB, especially the 551 KB script, to enhance performance.

    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 website www.williamsdingmann.com has several critical security shortcomings, including missing HTTP headers and the use of outdated libraries. Implementing recommended headers and updating vulnerable components will significantly improve security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors may be intercepted on an insecure first request.

    Fix: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to HTTP responses.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows unrestricted loading of potentially harmful external resources.

    Fix: Include 'Content-Security-Policy: default-src 'self';' in HTTP headers.

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking Protection (X-Frame-Options)Medium

    Why it matters: Without X-Frame-Options, the site can be framed by malicious pages.

    Fix: Add 'X-Frame-Options: deny' or 'X-Frame-Options: sameorigin' to HTTP responses.

    Evidence: Clickjacking protection

  4. 4

    Missing Cookie FlagsMedium

    Why it matters: Cookies without Secure and HttpOnly flags can be vulnerable to attacks.

    Fix: Set 'Secure', 'HttpOnly', and 'SameSite' attributes on all cookies.

    Evidence: Cookie flags

  5. 5

    Vulnerable JavaScript LibraryMedium

    Why it matters: Using jQuery 2.2.4 exposes the site to known vulnerabilities.

    Fix: Update jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  6. 6

    Exposed Google API KeysMedium

    Why it matters: Exposing API keys can lead to unauthorized use of the API.

    Fix: Restrict exposed Google API keys by domain and add proper referrer restrictions.

    Evidence: Keys and secrets in page code

  7. 7

    Missing Referrer PolicyLow

    Why it matters: No referrer policy exposes full URLs, including sensitive information.

    Fix: Add 'Referrer-Policy: no-referrer' to HTTP headers.

    Evidence: Referrer policy

  8. 8

    No Permissions PolicyInfo

    Why it matters: Lack of Permissions-Policy can lead to unauthorized features being activated.

    Fix: Add 'Permissions-Policy: geolocation=(self), microphone=(), camera=()' to HTTP headers.

    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.williamsdingmann.com/obituaries/Sharon-Shari-L-Sandberg?obId=26021838 → no strict-transport-security
    • https://www.williamsdingmann.com/obituaries/Joyce-D-Blomker?obId=20485540 → no strict-transport-security
    • https://www.williamsdingmann.com/obituaries/Rozanna-F-Corgard?obId=20485068 → no strict-transport-security
    • https://www.williamsdingmann.com/obituaries/Helen-Jeanette-Mosleth?obId=20484090 → no strict-transport-security
    • https://www.williamsdingmann.com/obituaries/Donald-E-Pflipsen?obId=20480404 → no strict-transport-security
    • https://www.williamsdingmann.com/obituaries/George-Dave-David-Pauley?obId=20444840 → no strict-transport-security
    • https://www.williamsdingmann.com/obituaries/Fred-C-Kleine-Jr?obId=20444788 → no strict-transport-security
    • https://www.williamsdingmann.com/obituaries/Valerie-K-Meinz?obId=20439434 → no strict-transport-security
    • https://www.williamsdingmann.com/obituaries/Alice-E-Thompson?obId=20430368 → no strict-transport-security
    • https://www.williamsdingmann.com/obituaries/Gerald-L-Folkerts?obId=20430316 → no strict-transport-security
    • https://www.williamsdingmann.com/obituaries/Douglas-H-Ferguson?obId=20408129 → no strict-transport-security
    • https://www.williamsdingmann.com/obituaries/Daniel-J-Onofrey-Sr?obId=20401687 → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 1680 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://www.williamsdingmann.com/obituaries/Sharon-Shari-L-Sandberg?obId=26021838 → no content-security-policy
    • https://www.williamsdingmann.com/obituaries/Joyce-D-Blomker?obId=20485540 → no content-security-policy
    • https://www.williamsdingmann.com/obituaries/Rozanna-F-Corgard?obId=20485068 → no content-security-policy
    • https://www.williamsdingmann.com/obituaries/Helen-Jeanette-Mosleth?obId=20484090 → no content-security-policy
    • https://www.williamsdingmann.com/obituaries/Donald-E-Pflipsen?obId=20480404 → no content-security-policy
    • https://www.williamsdingmann.com/obituaries/George-Dave-David-Pauley?obId=20444840 → no content-security-policy
    • https://www.williamsdingmann.com/obituaries/Fred-C-Kleine-Jr?obId=20444788 → no content-security-policy
    • https://www.williamsdingmann.com/obituaries/Valerie-K-Meinz?obId=20439434 → no content-security-policy
    • https://www.williamsdingmann.com/obituaries/Alice-E-Thompson?obId=20430368 → no content-security-policy
    • https://www.williamsdingmann.com/obituaries/Gerald-L-Folkerts?obId=20430316 → no content-security-policy
    • https://www.williamsdingmann.com/obituaries/Douglas-H-Ferguson?obId=20408129 → no content-security-policy
    • https://www.williamsdingmann.com/obituaries/Daniel-J-Onofrey-Sr?obId=20401687 → 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://www.williamsdingmann.com/obituaries/Sharon-Shari-L-Sandberg?obId=26021838 → no x-frame-options
    • https://www.williamsdingmann.com/obituaries/Joyce-D-Blomker?obId=20485540 → no x-frame-options
    • https://www.williamsdingmann.com/obituaries/Rozanna-F-Corgard?obId=20485068 → no x-frame-options
    • https://www.williamsdingmann.com/obituaries/Helen-Jeanette-Mosleth?obId=20484090 → no x-frame-options
    • https://www.williamsdingmann.com/obituaries/Donald-E-Pflipsen?obId=20480404 → no x-frame-options
    • https://www.williamsdingmann.com/obituaries/George-Dave-David-Pauley?obId=20444840 → no x-frame-options
    • https://www.williamsdingmann.com/obituaries/Fred-C-Kleine-Jr?obId=20444788 → no x-frame-options
    • https://www.williamsdingmann.com/obituaries/Valerie-K-Meinz?obId=20439434 → no x-frame-options
    • https://www.williamsdingmann.com/obituaries/Alice-E-Thompson?obId=20430368 → no x-frame-options
    • https://www.williamsdingmann.com/obituaries/Gerald-L-Folkerts?obId=20430316 → no x-frame-options
    • https://www.williamsdingmann.com/obituaries/Douglas-H-Ferguson?obId=20408129 → no x-frame-options
    • https://www.williamsdingmann.com/obituaries/Daniel-J-Onofrey-Sr?obId=20401687 → no x-frame-options
  • 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://www.williamsdingmann.com/obituaries/Sharon-Shari-L-Sandberg?obId=26021838 → no referrer-policy
    • https://www.williamsdingmann.com/obituaries/Joyce-D-Blomker?obId=20485540 → no referrer-policy
    • https://www.williamsdingmann.com/obituaries/Rozanna-F-Corgard?obId=20485068 → no referrer-policy
    • https://www.williamsdingmann.com/obituaries/Helen-Jeanette-Mosleth?obId=20484090 → no referrer-policy
    • https://www.williamsdingmann.com/obituaries/Donald-E-Pflipsen?obId=20480404 → no referrer-policy
    • https://www.williamsdingmann.com/obituaries/George-Dave-David-Pauley?obId=20444840 → no referrer-policy
    • https://www.williamsdingmann.com/obituaries/Fred-C-Kleine-Jr?obId=20444788 → no referrer-policy
    • https://www.williamsdingmann.com/obituaries/Valerie-K-Meinz?obId=20439434 → no referrer-policy
    • https://www.williamsdingmann.com/obituaries/Alice-E-Thompson?obId=20430368 → no referrer-policy
    • https://www.williamsdingmann.com/obituaries/Gerald-L-Folkerts?obId=20430316 → no referrer-policy
    • https://www.williamsdingmann.com/obituaries/Douglas-H-Ferguson?obId=20408129 → no referrer-policy
    • https://www.williamsdingmann.com/obituaries/Daniel-J-Onofrey-Sr?obId=20401687 → 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://www.williamsdingmann.com/obituaries/Sharon-Shari-L-Sandberg?obId=26021838 → no permissions-policy
    • https://www.williamsdingmann.com/obituaries/Joyce-D-Blomker?obId=20485540 → no permissions-policy
    • https://www.williamsdingmann.com/obituaries/Rozanna-F-Corgard?obId=20485068 → no permissions-policy
    • https://www.williamsdingmann.com/obituaries/Helen-Jeanette-Mosleth?obId=20484090 → no permissions-policy
    • https://www.williamsdingmann.com/obituaries/Donald-E-Pflipsen?obId=20480404 → no permissions-policy
    • https://www.williamsdingmann.com/obituaries/George-Dave-David-Pauley?obId=20444840 → no permissions-policy
    • https://www.williamsdingmann.com/obituaries/Fred-C-Kleine-Jr?obId=20444788 → no permissions-policy
    • https://www.williamsdingmann.com/obituaries/Valerie-K-Meinz?obId=20439434 → no permissions-policy
    • https://www.williamsdingmann.com/obituaries/Alice-E-Thompson?obId=20430368 → no permissions-policy
    • https://www.williamsdingmann.com/obituaries/Gerald-L-Folkerts?obId=20430316 → no permissions-policy
    • https://www.williamsdingmann.com/obituaries/Douglas-H-Ferguson?obId=20408129 → no permissions-policy
    • https://www.williamsdingmann.com/obituaries/Daniel-J-Onofrey-Sr?obId=20401687 → no permissions-policy
  • FoundCookie flagsMedium

    1050 of 1052 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.

    • AWSALB (set by https://www.williamsdingmann.com/robots.txt) lacks Secure, HttpOnly, SameSite
    • AWSALBCORS (set by https://www.williamsdingmann.com/robots.txt) lacks HttpOnly
    • 26 Sep 2026 10:30:29 GMT (set by https://www.williamsdingmann.com/robots.txt) lacks Secure, HttpOnly, SameSite
    • 26 Sep 2026 10:30:30 GMT (set by https://www.williamsdingmann.com/sitemap.xml) lacks Secure, HttpOnly, SameSite
    • 26 Sep 2026 10:30:59 GMT (set by https://www.williamsdingmann.com/obituaries-sitemap/12.xml.gz) lacks Secure, HttpOnly, SameSite
    • 26 Sep 2026 10:31:00 GMT (set by https://www.williamsdingmann.com/obituaries-sitemap/11.xml.gz) lacks Secure, HttpOnly, SameSite
    • 26 Sep 2026 10:31:01 GMT (set by https://www.williamsdingmann.com/obituaries-sitemap/9.xml.gz) lacks Secure, HttpOnly, SameSite
    • 26 Sep 2026 10:31:02 GMT (set by https://www.williamsdingmann.com/obituaries-sitemap/8.xml.gz) lacks Secure, HttpOnly, SameSite
    • 26 Sep 2026 10:31:03 GMT (set by https://www.williamsdingmann.com/obituaries-sitemap/6.xml.gz) lacks Secure, HttpOnly, SameSite
    • 26 Sep 2026 10:31:04 GMT (set by https://www.williamsdingmann.com/obituaries-sitemap/4.xml.gz) lacks Secure, HttpOnly, SameSite
    • 26 Sep 2026 10:31:05 GMT (set by https://www.williamsdingmann.com/obituaries-sitemap/2.xml.gz) lacks Secure, HttpOnly, SameSite
    • 26 Sep 2026 10:31:06 GMT (set by https://www.williamsdingmann.com/static-sitemap.xml) lacks Secure, HttpOnly, SameSite
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 2.2.4 in https://www.williamsdingmann.com/DependencyHandler.axd/091114c7e19b7266659d8f1b…: 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
  • FoundKeys and secrets in page codeMedium

    2 credential-like values found in code served to every visitor: Google API key.

    • Google API key AIzaSy…ow (39 chars) in https://www.williamsdingmann.com/obituaries/Sharon-Shari-L-Sandberg?obId=260218…: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
    • Google API key AIzaSy…ac (39 chars) in https://www.williamsdingmann.com/obituaries/Sharon-Shari-L-Sandberg?obId=260218…: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • NoteThird-party scripts

    Scripts run from 5 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.)

    • cmp.osano.com (40 script tags)
    • cdn.optimizely.com (40 script tags)
    • d2zeeo94hsmapq.cloudfront.net (80 script tags)
    • www.google.com (40 script tags)
    • www.gstatic.com (80 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 2 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: /admin/
    • Disallow: /Administration/
6 checks passed
  • OKHTTPS

    All 1680 crawled pages were served over HTTPS.

  • OKMIME sniffing protection

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

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

  • OKForms over HTTPS

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

  • OKExposed files and listings

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

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

Own www.williamsdingmann.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.williamsdingmann.com. Removal needs no account and no proof of purchase.
www.williamsdingmann.com scan 2026-09-26-1000 | DIY SEO Hub