Scanned sites / www.mcananey.us / 2026-10-03-2213

www.mcananey.us scan from 10/3/2026, 10:13:32 PM

Scan 2026-10-03-2213

Scanned 10/3/2026, 10:13:32 PM, finished 10/4/2026, 12:15:35 AM. Found on page 3 of brave web search results

Site: https://www.mcananey.us/

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

83/ 100Good

On October 3, 2026 the Site Spider crawled 92 pages and 361 assets of www.mcananey.us, starting from https://www.mcananey.us/. It scored 83 out of 100, a good result. 10 of 16 checks found something to fix, led by meta descriptions (76), links to other sites (18), thin content (35); 4 checks passed. Most of the points went to meta descriptions (−7), links to other sites (−4), thin content (−3.2). 2 checks 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: Medium3 medium, 5 low and 1 info findings. See the security findings ↓

Pages crawled
92
Assets fetched
361
Status
Completed
Checks with issues
10 of 16
CoverageComplete crawl

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

  • Title tags13 issues
    13 of 83 pages have title issues. 4 noindex or canonicalized pages excluded.
    −1.5 points
  • Meta descriptions76 issues
    76 of 83 pages have meta description issues. 4 noindex or canonicalized pages excluded.
    −7 points
  • Headings2 issues
    2 of 83 pages have heading issues. 4 noindex or canonicalized pages excluded.
    −0.1 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites18 issues
    18 destinations answered with an error, 35 could not be determined (timeouts, rate limits or refusals), of 72 destinations checked.
    −4 points
  • Redirects5 issues
    26 redirecting URLs, 0 of them chained.
    −0.2 points
  • Non-200 responses28 noted
    28 URLs did not return a 2xx response. 5 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 83 indexable pages have indexability warnings. 4 pages noindex by design.
  • Image alt text10 issues
    10 of 723 image references have no alt attribute. 166 use an empty alt (decorative), which is fine.
    −0.1 points
  • Heavy assets3 issues
    3 assets larger than 500 KB among 361 fetched assets.
    −1.8 points
  • Orphan pages20 issues
    20 pages have no internal links pointing at them.
    −0.9 points
  • Sitemap coverage26 issues
    11 sitemaps listing 77 URLs: 6 crawled pages missing, 0 listed URLs broken or redirecting, 20 reachable only via the sitemap.
    −1.8 points
  • Internal link countsOK
    Internal link counts for 87 pages.
  • Thin content35 issues
    35 of 83 pages have fewer than 200 words. 4 noindex or canonicalized pages excluded.
    −3.2 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

2039 sites, median 80%, average 79%

www.mcananey.us scores 83%, higher than 63% of the 2039 scanned sites. See the full ranking.

0581150%: 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%: 1 site40%: 2 sites41%: 2 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 4 sites46%: 4 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 5 sites52%: 8 sites53%: 6 sites54%: 7 sites55%: 6 sites56%: 7 sites57%: 6 sites58%: 15 sites59%: 7 sites60%: 10 sites61%: 12 sites62%: 17 sites63%: 17 sites64%: 13 sites65%: 24 sites66%: 25 sites67%: 38 sites68%: 33 sites69%: 29 sites70%: 41 sites71%: 46 sites72%: 60 sites73%: 59 sites74%: 51 sites75%: 66 sites76%: 80 sites77%: 77 sites78%: 97 sites79%: 75 sites80%: 98 sites81%: 115 sites82%: 91 sites83%: 92 sites84%: 92 sites85%: 73 sites86%: 75 sites87%: 73 sites88%: 67 sites89%: 56 sites90%: 39 sites91%: 43 sites92%: 32 sites93%: 17 sites94%: 12 sites95%: 13 sites96%: 8 sites97%: 9 sites98%: 2 sites99%: 2 sites100%: 55 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

Your site is in good shape but requires some attention to meta descriptions and titles. Fixing these will enhance SEO performance significantly.

  1. 1

    Add Missing Meta Descriptions

    Why: 76 pages lack meta descriptions, crucial for SERP visibility.

    How: Craft concise and relevant descriptions for each page, ideally 150-160 characters.

    Checks: meta-descriptions

  2. 2

    Fix Title Tag Issues

    Why: 13 pages have title issues affecting search visibility.

    How: Adjust titles to be unique and under 60 characters for affected pages.

    Checks: titles

  3. 3

    Resolve Redirects

    Why: 26 URLs are redirecting, potentially causing slow load times.

    How: Audit the redirects and remove unnecessary ones, linking pages directly.

    Checks: redirects

  4. 4

    Address Thin Content

    Why: 35 pages have less than 200 words, impacting SEO.

    How: Enhance content by adding valuable information to meet word count thresholds.

    Checks: thin-content

  5. 5

    Add Missing Headings

    Why: 2 pages are missing H1 headings, crucial for SEO structure.

    How: Ensure each page has a unique and relevant H1 heading.

    Checks: headings

  6. 6

    Add Alt Attributes to Images

    Why: 10 out of 723 images lack alt text, affecting accessibility and SEO.

    How: Add descriptive alt attributes to missing images.

    Checks: images-alt

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 several security issues that could expose it to attacks. Key concerns include missing HTTP headers that protect against data interception, clickjacking, and scripts running insecurely. Immediate actions such as adding HTTP Strict Transport Security and other protective headers are recommended to enhance site security.

  • 0 high
  • 3 medium
  • 5 low
  • 1 info
  1. 1

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: No strict-transport-security header prevents interception of unsecured connections.

    Fix: Add the header `Strict-Transport-Security: max-age=31536000; includeSubDomains` to your server responses.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Clickjacking ProtectionMedium

    Why it matters: Not setting x-frame-options allows your pages to be embedded on other sites, increasing vulnerability to clickjacking.

    Fix: Add the header `X-Frame-Options: DENY` to your server responses.

    Evidence: Clickjacking protection

  3. 3

    Cookie Flags MissingMedium

    Why it matters: Without proper flags, cookies can be vulnerable to theft and insecure transfers.

    Fix: Set `HttpOnly`, `Secure`, and `SameSite=Strict` for cookies like `wordpress_test_cookie`.

    Evidence: Cookie flags

  4. 4

    Missing MIME Sniffing ProtectionLow

    Why it matters: Absence of x-content-type-options allows browsers to potentially misinterpret file types.

    Fix: Add the header `X-Content-Type-Options: nosniff` to your server responses.

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Without a referrer-policy, sensitive URL information may be leaked to third-party sites.

    Fix: Add the header `Referrer-Policy: no-referrer` to your server responses.

    Evidence: Referrer policy

  6. 6

    Software Version DisclosureLow

    Why it matters: Revealing server version information facilitates targeted attacks on known vulnerabilities.

    Fix: Configure your server to hide version details, for example, by setting `ServerTokens Prod` in Apache.

    Evidence: Software version disclosure

  7. 7

    Mixed Content DetectedLow

    Why it matters: Loading resources over HTTP on HTTPS pages can lead to man-in-the-middle attacks.

    Fix: Update URLs to load resources over HTTPS instead of HTTP.

    Evidence: Mixed content

  8. 8

    Third-Party Scripts Without SRILow

    Why it matters: Lacking SRI means compromised external scripts could inject malicious code.

    Fix: Implement Subresource Integrity for third-party scripts or use a Content-Security-Policy that restricts script sources.

    Evidence: Third-party scripts

  9. 9

    Missing Permissions PolicyInfo

    Why it matters: Lack of permissions-policy may lead to unnecessary exposure of browser features to scripts.

    Fix: Consider adding the header `Permissions-Policy: geolocation=(), microphone=(), camera=()` to your server responses.

    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.mcananey.us/ → no strict-transport-security
    • https://www.mcananey.us/who-we-are/ → no strict-transport-security
    • https://www.mcananey.us/what-we-do/ → no strict-transport-security
    • https://www.mcananey.us/contact/ → no strict-transport-security
    • https://www.mcananey.us/newsletters/ → no strict-transport-security
    • https://www.mcananey.us/david-p-mcananey-j-d-ll-m-cpa/ → no strict-transport-security
    • https://www.mcananey.us/jennifer-mcananey-swajkoski/ → no strict-transport-security
    • https://www.mcananey.us/brenda-emmanuel/ → no strict-transport-security
    • https://www.mcananey.us/taylor-mcananey/ → no strict-transport-security
    • https://www.mcananey.us/lynda-anderson/ → no strict-transport-security
    • https://www.mcananey.us/post-with-vimeo-video/ → no strict-transport-security
    • https://www.mcananey.us/post-with-slideshow/ → no strict-transport-security
  • FoundClickjacking protectionMedium

    2 of 87 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://www.mcananey.us/ → no x-frame-options
    • https://www.mcananey.us/who-we-are/ → no x-frame-options
    • https://www.mcananey.us/what-we-do/ → no x-frame-options
    • https://www.mcananey.us/contact/ → no x-frame-options
    • https://www.mcananey.us/newsletters/ → no x-frame-options
    • https://www.mcananey.us/david-p-mcananey-j-d-ll-m-cpa/ → no x-frame-options
    • https://www.mcananey.us/jennifer-mcananey-swajkoski/ → no x-frame-options
    • https://www.mcananey.us/brenda-emmanuel/ → no x-frame-options
    • https://www.mcananey.us/taylor-mcananey/ → no x-frame-options
    • https://www.mcananey.us/lynda-anderson/ → no x-frame-options
    • https://www.mcananey.us/post-with-vimeo-video/ → no x-frame-options
    • https://www.mcananey.us/post-with-slideshow/ → 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://www.mcananey.us/ → no x-content-type-options
    • https://www.mcananey.us/who-we-are/ → no x-content-type-options
    • https://www.mcananey.us/what-we-do/ → no x-content-type-options
    • https://www.mcananey.us/contact/ → no x-content-type-options
    • https://www.mcananey.us/newsletters/ → no x-content-type-options
    • https://www.mcananey.us/david-p-mcananey-j-d-ll-m-cpa/ → no x-content-type-options
    • https://www.mcananey.us/jennifer-mcananey-swajkoski/ → no x-content-type-options
    • https://www.mcananey.us/brenda-emmanuel/ → no x-content-type-options
    • https://www.mcananey.us/taylor-mcananey/ → no x-content-type-options
    • https://www.mcananey.us/lynda-anderson/ → no x-content-type-options
    • https://www.mcananey.us/post-with-vimeo-video/ → no x-content-type-options
    • https://www.mcananey.us/post-with-slideshow/ → no x-content-type-options
  • FoundReferrer policyLow

    2 of 87 HTML pages send 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.mcananey.us/ → no referrer-policy
    • https://www.mcananey.us/who-we-are/ → no referrer-policy
    • https://www.mcananey.us/what-we-do/ → no referrer-policy
    • https://www.mcananey.us/contact/ → no referrer-policy
    • https://www.mcananey.us/newsletters/ → no referrer-policy
    • https://www.mcananey.us/david-p-mcananey-j-d-ll-m-cpa/ → no referrer-policy
    • https://www.mcananey.us/jennifer-mcananey-swajkoski/ → no referrer-policy
    • https://www.mcananey.us/brenda-emmanuel/ → no referrer-policy
    • https://www.mcananey.us/taylor-mcananey/ → no referrer-policy
    • https://www.mcananey.us/lynda-anderson/ → no referrer-policy
    • https://www.mcananey.us/post-with-vimeo-video/ → no referrer-policy
    • https://www.mcananey.us/post-with-slideshow/ → 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.mcananey.us/ → no permissions-policy
    • https://www.mcananey.us/who-we-are/ → no permissions-policy
    • https://www.mcananey.us/what-we-do/ → no permissions-policy
    • https://www.mcananey.us/contact/ → no permissions-policy
    • https://www.mcananey.us/newsletters/ → no permissions-policy
    • https://www.mcananey.us/david-p-mcananey-j-d-ll-m-cpa/ → no permissions-policy
    • https://www.mcananey.us/jennifer-mcananey-swajkoski/ → no permissions-policy
    • https://www.mcananey.us/brenda-emmanuel/ → no permissions-policy
    • https://www.mcananey.us/taylor-mcananey/ → no permissions-policy
    • https://www.mcananey.us/lynda-anderson/ → no permissions-policy
    • https://www.mcananey.us/post-with-vimeo-video/ → no permissions-policy
    • https://www.mcananey.us/post-with-slideshow/ → 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: Apache (315 responses)
    • server: nginx/1.29.8 (138 responses)
  • FoundCookie flagsMedium

    1 of 1 cookie 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.

    • wordpress_test_cookie (set by https://www.mcananey.us/wp-login.php) lacks SameSite
  • FoundMixed contentLow

    34 resources on HTTPS pages are loaded over plain HTTP.

    • https://www.mcananey.us/post-with-vimeo-video/ loads image http://gt3demo.com/wp/wizelaw/wp-content/uploads/sites/10/2017/01/widget_author.jpg
    • https://www.mcananey.us/post-with-vimeo-video/ loads image http://gt3demo.com/wp/wizelaw/wp-content/uploads/sites/10/2017/01/widget_banner.jpg
    • https://www.mcananey.us/post-with-image/ loads image http://gt3demo.com/wp/wizelaw/wp-content/uploads/sites/10/2017/01/blog_post_img.jpg
    • https://www.mcananey.us/post-with-image/ loads image http://gt3demo.com/wp/wizelaw/wp-content/uploads/sites/10/2017/01/widget_author.jpg
    • https://www.mcananey.us/post-with-image/ loads image http://gt3demo.com/wp/wizelaw/wp-content/uploads/sites/10/2017/01/widget_banner.jpg
    • https://www.mcananey.us/services/ loads image http://gt3demo.com/wp/wizelaw/wp-content/uploads/sites/10/2017/01/logo-dark.png
    • https://www.mcananey.us/newsletters/the-mcananey-report-issue-39/ loads image http://h/
    • https://www.mcananey.us/practice/ loads image http://gt3demo.com/wp/wizelaw/wp-content/uploads/sites/10/2017/01/O733PY0-300x200.jpg
    • https://www.mcananey.us/practice/family-law/ loads image http://gt3demo.com/wp/wizelaw/wp-content/uploads/sites/10/2017/01/O733PY0-300x200.jpg
    • https://www.mcananey.us/practice/justice-fight/ loads image http://gt3demo.com/wp/wizelaw/wp-content/uploads/sites/10/2017/01/O733PY0-300x200.jpg
    • https://www.mcananey.us/practice/taxation-accounts/ loads image http://gt3demo.com/wp/wizelaw/wp-content/uploads/sites/10/2017/01/O733PY0-300x200.jpg
    • https://www.mcananey.us/practice/corporate-fraud/ loads image http://gt3demo.com/wp/wizelaw/wp-content/uploads/sites/10/2017/01/O733PY0-300x200.jpg
  • NoteThird-party scripts

    Scripts run from 1 other domain 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)
7 checks passed
  • OKHTTPS

    All 87 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set.

  • OKForms over HTTPS

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

  • OKVulnerable JavaScript libraries

    1 library version recognised, none with known vulnerabilities.

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

Sites scoring near www.mcananey.us

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

Own www.mcananey.us?

www.mcananey.us scan 2026-10-03-2213 | DIY SEO Hub