Scanned sites / www.mcananey.us / 2026-10-02-1017

www.mcananey.us scan from 10/2/2026, 10:17:32 AM

Scan 2026-10-02-1017

Scanned 10/2/2026, 10:17:32 AM, finished 10/2/2026, 12:01:29 PM. 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 2, 2026 the Site Spider crawled 92 pages and 360 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, 4 low and 1 info findings. See the security findings ↓

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

452 of 452 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 721 image references have no alt attribute. 164 use an empty alt (decorative), which is fine.
    −0.1 points
  • Heavy assets3 issues
    3 assets larger than 500 KB among 360 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

1764 sites, median 80%, average 79%

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

0521030%: 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%: 1 site42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 6 sites57%: 6 sites58%: 11 sites59%: 6 sites60%: 10 sites61%: 11 sites62%: 15 sites63%: 16 sites64%: 12 sites65%: 20 sites66%: 19 sites67%: 34 sites68%: 27 sites69%: 25 sites70%: 39 sites71%: 38 sites72%: 50 sites73%: 50 sites74%: 48 sites75%: 57 sites76%: 71 sites77%: 63 sites78%: 84 sites79%: 60 sites80%: 86 sites81%: 103 sites82%: 82 sites83%: 82 sites84%: 79 sites85%: 59 sites86%: 65 sites87%: 55 sites88%: 60 sites89%: 52 sites90%: 32 sites91%: 34 sites92%: 24 sites93%: 14 sites94%: 12 sites95%: 11 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 54 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 has several minor SEO issues that can improve visibility and user experience. Prioritize fixing meta descriptions, title tags, and redirects for better optimization.

  1. 1

    Fix Meta Descriptions

    Why: 76 pages lack meta descriptions, improving them boosts click-through rates.

    How: Create unique meta descriptions for each of the 76 affected pages, summarizing content effectively.

    Checks: meta-descriptions

  2. 2

    Revise Title Tags

    Why: Title issues exist on 13 pages; correcting them enhances SEO and relevance.

    How: Update titles to ensure they are unique and under 60 characters for clarity and impact.

    Checks: titles

  3. 3

    Address Redirects

    Why: 26 URLs are redirecting; fixing these improves page load times and user experience.

    How: Eliminate unnecessary redirects by updating links to point directly to the final URLs.

    Checks: redirects

  4. 4

    Add Heading Tags

    Why: 2 pages are missing heading tags which structure content for better readability.

    How: Add appropriate H1 tags to the affected pages, ensuring they each have one unique H1 tag.

    Checks: headings

  5. 5

    Optimize Image Alt Text

    Why: 10 images lack alt attributes; adding them enhances accessibility and SEO.

    How: Add descriptive alt text to each of the 10 identified images.

    Checks: images-alt

  6. 6

    Reduce Heavy Assets

    Why: 3 large assets can slow down page loading speed, impacting user experience.

    How: Optimize or compress the identified assets to reduce their size.

    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 has several security issues that could expose users to risks. Key concerns include missing security headers that protect against attacks and sensitive information disclosure. Implementing appropriate headers and securing resources can mitigate these risks effectively.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Lack of HSTS allows users to connect via HTTP, risking interception.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Clickjacking Protection (X-Frame-Options)Medium

    Why it matters: Without this header, your pages can be embedded in harmful frames.

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

    Evidence: Clickjacking protection

  3. 3

    Cookie Lacking Protective FlagsMedium

    Why it matters: Cookies without these flags can be hijacked by scripts.

    Fix: Set these cookie flags: Set-Cookie: wordpress_test_cookie; SameSite=None; Secure; HttpOnly

    Evidence: Cookie flags

  4. 4

    Missing MIME Sniffing Protection (X-Content-Type-Options)Low

    Why it matters: Without this header, browsers may incorrectly execute files.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: The absence of this policy exposes full URL information when navigating away.

    Fix: Add the following header: Referrer-Policy: no-referrer

    Evidence: Referrer policy

  6. 6

    Server Version DisclosureLow

    Why it matters: Exposing server details can help attackers target known vulnerabilities.

    Fix: Configure your web server to hide or alter the server banner.

    Evidence: Software version disclosure

  7. 7

    Mixed Content IssuesLow

    Why it matters: Loading resources over HTTP on HTTPS pages can expose users to attacks.

    Fix: Update resource URLs to use HTTPS instead of HTTP.

    Evidence: Mixed content

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Without this, potentially harmful browser features may be accessible.

    Fix: Add the following header: Permissions-Policy: geolocation=(), microphone=(), camera=()

    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 (314 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-02-1017 | DIY SEO Hub