Scanned sites / www.bodyworksfargo.com

SEO report for www.bodyworksfargo.com DR 5

The latest Site Spider scan of www.bodyworksfargo.com, with 4 scans on record. Each scan is at its own address, for example /domain/www-bodyworksfargo-com/2026-09-13-0912.

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

Latest scan

Scanned 2026-09-13 09:12:20 UTC, finished 2026-09-13 12:00:19 UTC. Found on page 3 of brave web search results

Site: https://www.bodyworksfargo.com/

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

80/ 100Good

On September 13, 2026 the Site Spider crawled 278 pages and 1001 assets of www.bodyworksfargo.com, starting from https://www.bodyworksfargo.com/. It scored 80 out of 100, a good result. 12 of 27 checks found something to fix, led by heavy assets (63), title tags (110), image alt text (1,323); 6 checks passed. Most of the points went to heavy assets (−6), title tags (−4.2), image alt text (−3.5). 9 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: Medium5 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
278
Assets fetched
1001
Status
Completed
Checks with issues
12 of 27
CoverageJob finished, partial coverage

1,279 of 1,281 discovered URLs were fetched, 64 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 66 link destinations on other sites were checked.

  • Title tags110 issues
    110 of 226 pages have title issues. 38 noindex or canonicalized pages excluded.
    −4.2 points
  • Meta descriptions82 issues
    82 of 226 pages have meta description issues. 38 noindex or canonicalized pages excluded.
    −2.5 points
  • Headings52 issues
    52 of 226 pages have heading issues. 38 noindex or canonicalized pages excluded.
    −1.2 points
  • Broken links2 issues
    2 internal links point at 2 broken URLs.
    −0.2 points
  • Links to other sites2 issues
    2 destinations answered with an error, 22 could not be determined (timeouts, rate limits or refusals), of 65 destinations checked.
    −0.3 points
  • Redirects12 issues
    13 redirecting URLs, 5 of them chained.
    −0.2 points
  • Non-200 responses2 issues
    31 URLs did not return a 2xx response. 14 of them are pages, 2 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 232 indexable pages have indexability warnings. 32 pages noindex by design.
  • Image alt text1,323 issues
    1323 of 2276 image references have no alt attribute. 517 use an empty alt (decorative), which is fine.
    −3.5 points
  • Heavy assets63 issues
    63 assets larger than 500 KB among 1001 fetched assets.
    −6 points
  • Orphan pages20 issues
    20 pages have no internal links pointing at them.
    −0.3 points
  • Sitemap coverage56 issues
    5 sitemaps listing 194 URLs: 34 crawled pages missing, 1 listed URL broken or redirecting, 21 reachable only via the sitemap.
    −1.3 points
  • Internal link counts41 noted
    Internal link counts for 264 pages; 41 worth a look.
  • Thin contentOK
    0 of 226 pages have fewer than 200 words. 38 noindex or canonicalized pages excluded.
  • Duplicate content2 issues
    1 group of pages with identical HTML.
    −0.1 points
  • URL format9 noted
    9 of 278 page URLs are harder to read, share or cache than they need to be.
  • Canonicals38 noted
    38 of 264 pages have a canonical worth checking.
  • Robots directives264 noted
    264 pages carry a robots directive; 0 carry none.
  • Anchor text131 noted
    131 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure77 noted
    77 of 226 pages could use the title, heading and snippet space better. 38 noindex or canonicalized pages excluded.
  • Image weight and alt length165 noted
    164 images over 100 KB; 1 with alt text over 100 characters.
  • Response anomalies1 noted
    1 URL answered in a way worth looking at.
  • 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 264 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; 12 response headers recorded across 1279 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 264 pages; 67 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 62 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.

What changed since the last scan

Score unchanged

www.bodyworksfargo.com scored 80 out of 100 in both of its last two scans. The two crawls did not cover the same ground, so part of the difference is coverage rather than change. 579 URLs the earlier crawl reached were not reached this time. Across 4 scans on record the score has ended up where it started, at 80.

  • 579 URLs from the earlier crawl were not reached this time
  • Crawl coverage differed between the two scans; some differences may be coverage rather than change
  1. 2026-09-12 01:06:42 UTC80/100278 pages
  2. 2026-09-12 17:27:12 UTC80/100278 pages
  3. 2026-09-12 22:47:12 UTC80/100278 pages
  4. 2026-09-13 09:12:20 UTC80/100278 pages

Where this site sits among all scanned sites

2327 sites, median 79%, average 78%

www.bodyworksfargo.com scores 80%, higher than 51% of the 2327 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%: 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%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 9 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 35 sites67%: 35 sites68%: 34 sites69%: 47 sites70%: 44 sites71%: 69 sites72%: 71 sites73%: 69 sites74%: 68 sites75%: 73 sites76%: 86 sites77%: 92 sites78%: 106 sites79%: 86 sites80%: 106 sites81%: 105 sites82%: 115 sites83%: 99 sites84%: 107 sites85%: 85 sites86%: 69 sites87%: 75 sites88%: 59 sites89%: 63 sites90%: 34 sites91%: 47 sites92%: 38 sites93%: 23 sites94%: 16 sites95%: 11 sites96%: 10 sites97%: 12 sites98%: 4 sites99%: 1 site100%: 70 sites80% 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.

For your site, prioritize fixing broken links, non-200 responses, and title/meta description issues to improve user experience and SEO. Following these steps will lead to better visibility and accessibility.

  1. 1

    Fix Broken Links

    Why: Two broken internal links prevent users from accessing content.

    How: Update or remove links for the URLs: /ergonomic-assessment/ and /bliss-massage/.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: 31 URLs aren’t accessible, impacting user experience and SEO.

    How: Identify the 31 URLs not returning a 2xx response and correct their issues.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: 110 pages have title issues affecting SEO.

    How: Shorten titles longer than 60 characters for 110 pages identified.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: 65 pages with missing or poor meta descriptions risk lower click-through rates.

    How: Add concise meta descriptions for the 65 affected pages.

    Checks: meta-descriptions

  5. 5

    Address Heading Issues

    Why: 52 pages have heading issues that may confuse both users and search engines.

    How: Ensure each page has one H1 tag and follows heading hierarchy properly.

    Checks: headings

  6. 6

    Improve Sitemap Coverage

    Why: 34 crawled pages are missing from the sitemap, hurting indexing.

    How: Update the sitemap to include all crawled pages and correct redirects for URLs listed in the sitemap.

    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

Your website has several security vulnerabilities that need urgent attention, such as missing HTTP headers for secure communications and outdated libraries. Implementing these fixes will enhance your site's protection against various attacks.

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

    Missing HSTS HeaderMedium

    Why it matters: Absence of HTTP Strict Transport Security allows potential interception of connections on first request over HTTP.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: No Content Security Policy header or tag increases vector for attacks like XSS by allowing unrestricted resource loading.

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

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: Absence of X-Frame-Options lets sites embed your pages in iframes, risking clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Outdated JavaScript LibraryMedium

    Why it matters: Using jQuery 3.1.1 includes vulnerabilities that could be exploited depending on its use.

    Fix: Upgrade jQuery to version 3.5.0 or higher.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Exposed Google API KeyMedium

    Why it matters: A Google API key is visible in the code, risking abuse if not properly restricted.

    Fix: Restrict the API key in the Google Cloud console by referrer and domain.

    Evidence: Keys and secrets in page code

  6. 6

    Missing MIME Sniffing ProtectionLow

    Why it matters: No X-Content-Type-Options header exposes browsers to content type sniffing vulnerabilities.

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

    Evidence: MIME sniffing protection

  7. 7

    Lack of Subresource Integrity for Third-Party ScriptsLow

    Why it matters: Scripts from external domains are vulnerable to modification, which could change site behavior.

    Fix: Implement a Content-Security-Policy that specifies allowed script sources and consider using SRI where applicable.

    Evidence: Third-party scripts

  8. 8

    Sensitive Path in robots.txtInfo

    Why it matters: The public robots.txt reveals a private path which can help attackers probe your site.

    Fix: Ensure the /wp-admin/ path is secured with proper access controls beyond robots.txt.

    Evidence: Sensitive paths in robots.txt

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.bodyworksfargo.com/ → no strict-transport-security
    • https://www.bodyworksfargo.com/about/ → no strict-transport-security
    • https://www.bodyworksfargo.com/gallery/ → no strict-transport-security
    • https://www.bodyworksfargo.com/services/ → no strict-transport-security
    • https://www.bodyworksfargo.com/aquatic-therapy/ → no strict-transport-security
    • https://www.bodyworksfargo.com/blood-flow-restriction-training/ → no strict-transport-security
    • https://www.bodyworksfargo.com/concussion-management-therapy-in-fargo/ → no strict-transport-security
    • https://www.bodyworksfargo.com/cupping-therapy/ → no strict-transport-security
    • https://www.bodyworksfargo.com/dry-needling/ → no strict-transport-security
    • https://www.bodyworksfargo.com/flywheel-training/ → no strict-transport-security
    • https://www.bodyworksfargo.com/headaches-migraines-relief/ → no strict-transport-security
    • https://www.bodyworksfargo.com/knee-pain-treatment-fargo/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 264 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.bodyworksfargo.com/ → no content-security-policy
    • https://www.bodyworksfargo.com/about/ → no content-security-policy
    • https://www.bodyworksfargo.com/gallery/ → no content-security-policy
    • https://www.bodyworksfargo.com/services/ → no content-security-policy
    • https://www.bodyworksfargo.com/aquatic-therapy/ → no content-security-policy
    • https://www.bodyworksfargo.com/blood-flow-restriction-training/ → no content-security-policy
    • https://www.bodyworksfargo.com/concussion-management-therapy-in-fargo/ → no content-security-policy
    • https://www.bodyworksfargo.com/cupping-therapy/ → no content-security-policy
    • https://www.bodyworksfargo.com/dry-needling/ → no content-security-policy
    • https://www.bodyworksfargo.com/flywheel-training/ → no content-security-policy
    • https://www.bodyworksfargo.com/headaches-migraines-relief/ → no content-security-policy
    • https://www.bodyworksfargo.com/knee-pain-treatment-fargo/ → 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.bodyworksfargo.com/ → no x-frame-options
    • https://www.bodyworksfargo.com/about/ → no x-frame-options
    • https://www.bodyworksfargo.com/gallery/ → no x-frame-options
    • https://www.bodyworksfargo.com/services/ → no x-frame-options
    • https://www.bodyworksfargo.com/aquatic-therapy/ → no x-frame-options
    • https://www.bodyworksfargo.com/blood-flow-restriction-training/ → no x-frame-options
    • https://www.bodyworksfargo.com/concussion-management-therapy-in-fargo/ → no x-frame-options
    • https://www.bodyworksfargo.com/cupping-therapy/ → no x-frame-options
    • https://www.bodyworksfargo.com/dry-needling/ → no x-frame-options
    • https://www.bodyworksfargo.com/flywheel-training/ → no x-frame-options
    • https://www.bodyworksfargo.com/headaches-migraines-relief/ → no x-frame-options
    • https://www.bodyworksfargo.com/knee-pain-treatment-fargo/ → 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.bodyworksfargo.com/ → no x-content-type-options
    • https://www.bodyworksfargo.com/about/ → no x-content-type-options
    • https://www.bodyworksfargo.com/gallery/ → no x-content-type-options
    • https://www.bodyworksfargo.com/services/ → no x-content-type-options
    • https://www.bodyworksfargo.com/aquatic-therapy/ → no x-content-type-options
    • https://www.bodyworksfargo.com/blood-flow-restriction-training/ → no x-content-type-options
    • https://www.bodyworksfargo.com/concussion-management-therapy-in-fargo/ → no x-content-type-options
    • https://www.bodyworksfargo.com/cupping-therapy/ → no x-content-type-options
    • https://www.bodyworksfargo.com/dry-needling/ → no x-content-type-options
    • https://www.bodyworksfargo.com/flywheel-training/ → no x-content-type-options
    • https://www.bodyworksfargo.com/headaches-migraines-relief/ → no x-content-type-options
    • https://www.bodyworksfargo.com/knee-pain-treatment-fargo/ → no x-content-type-options
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 3.1.1 in https://www.bodyworksfargo.com/wp-content/plugins/gravityforms/js/placeholders.…: 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

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…ow (39 chars) in https://www.bodyworksfargo.com/contact/: 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.)

    • privacy-proxy.usercentrics.eu (40 script tags)
    • app.usercentrics.eu (40 script tags)
    • www.google.com (4 script tags)
    • verify.authorize.net (1 script tag)
    • policies.termageddon.com (3 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 1 path 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: /wp-admin/
5 checks passed, 3 not applicable
  • OKHTTPS

    All 264 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.

  • OKForms over HTTPS

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

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

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.bodyworksfargo.com

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

Own www.bodyworksfargo.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.bodyworksfargo.com. Removal needs no account and no proof of purchase.