Scanned sites / mqsbarn.com / 2026-09-28-0800

mqsbarn.com scan from 9/28/2026, 8:00:02 AM

Scan 2026-09-28-0800

Scanned 9/28/2026, 8:00:02 AM, finished 9/28/2026, 8:36:53 AM. Found on page 3 of chatgpt for browser (api usage) results

Site: https://mqsbarn.com/

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

75/ 100Good

On September 28, 2026 the Site Spider crawled 373 pages and 1473 assets of mqsbarn.com, starting from https://mqsbarn.com/. It scored 75 out of 100, a good result. 10 of 16 checks found something to fix, led by heavy assets (449), broken links (81), indexability (101); 5 checks passed. Most of the points went to heavy assets (−6), broken links (−5.6), indexability (−3.5). 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: Medium5 medium, 3 low and 2 info findings. See the security findings ↓

Pages crawled
373
Assets fetched
1473
Status
Completed
Checks with issues
10 of 16
CoverageJob finished, partial coverage

1,846 of 1,848 discovered URLs were fetched, 3,917 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. 300 link destinations on other sites were checked, 190 left unchecked.

  • Title tags55 issues
    55 of 107 pages have title issues. 182 noindex or canonicalized pages excluded.
    −1.9 points
  • Meta descriptions99 issues
    99 of 107 pages have meta description issues. 182 noindex or canonicalized pages excluded.
    −2.7 points
  • Headings7 issues
    7 of 107 pages have heading issues. 182 noindex or canonicalized pages excluded.
    −0.1 points
  • Broken links81 issues
    108 internal links point at 81 broken URLs.
    −5.6 points
  • Links to other sites5 issues
    5 destinations answered with an error, 191 could not be determined (timeouts, rate limits or refusals), 190 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.7 points
  • Redirects3 issues
    4 redirecting URLs, 0 of them chained.
  • Non-200 responses81 issues
    85 URLs did not return a 2xx response. 84 of them are pages, 81 with an error status; the rest are assets or redirects.
    −2.8 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability101 issues
    101 of 225 indexable pages have indexability warnings. 64 pages noindex by design.
    −3.5 points
  • Image alt textOK
    0 of 1471 image references have no alt attribute. 466 use an empty alt (decorative), which is fine.
  • Heavy assets449 issues
    449 assets larger than 500 KB among 1473 fetched assets. 1 document over that size is listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage107 issues
    1 sitemap listing 0 URLs: 107 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −2.2 points
  • Internal link countsOK
    Internal link counts for 289 pages.
  • Thin contentOK
    0 of 107 pages have fewer than 200 words. 182 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1328 sites, median 80%, average 79%

mqsbarn.com scores 75%, higher than 28% of the 1328 scanned sites. See the full ranking.

037740%: 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%: 1 site38%: 1 site39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 2 sites47%: 2 sites48%: 2 sites49%: 2 sites50%: 4 sites51%: 4 sites52%: 5 sites53%: 5 sites54%: 5 sites55%: 4 sites56%: 3 sites57%: 5 sites58%: 9 sites59%: 5 sites60%: 8 sites61%: 10 sites62%: 13 sites63%: 11 sites64%: 8 sites65%: 14 sites66%: 14 sites67%: 26 sites68%: 25 sites69%: 14 sites70%: 30 sites71%: 29 sites72%: 38 sites73%: 32 sites74%: 41 sites75%: 37 sites76%: 49 sites77%: 45 sites78%: 57 sites79%: 48 sites80%: 65 sites81%: 74 sites82%: 69 sites83%: 60 sites84%: 59 sites85%: 46 sites86%: 50 sites87%: 45 sites88%: 49 sites89%: 35 sites90%: 28 sites91%: 31 sites92%: 19 sites93%: 8 sites94%: 10 sites95%: 5 sites96%: 7 sites97%: 3 sites98%: 1 site99%: 1 site100%: 49 sites75% 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 SEO issues, primarily broken links, non-200 responses, and missing H1 headings. These issues should be prioritized for optimal performance. Improvements may enhance user experience and search rankings.

  1. 1

    Fix Broken Links

    Why: 108 internal links point to broken URLs, degrading user experience.

    How: Identify and update or remove the broken links on affected pages.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: 85 URLs returned non-200 responses, harming SEO and usability.

    How: Investigate and fix the 81 error status pages to return 200 responses.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: 55 pages have title issues, affecting visibility on search engines.

    How: Rewrite short or long title tags to meet the recommended length of 30-60 characters.

    Checks: titles

  4. 4

    Optimize Meta Descriptions

    Why: 99 pages have meta description issues, which can impact click-through rates.

    How: Revise to ensure descriptions are between 70-160 characters and relevant.

    Checks: meta-descriptions

  5. 5

    Add Missing H1 Headings

    Why: 7 pages are missing H1 tags, which are crucial for SEO.

    How: Add unique, descriptive H1 tags to the affected pages.

    Checks: headings

  6. 6

    Update Sitemap Coverage

    Why: 107 pages are missing from the sitemap which may prevent indexing.

    How: Ensure that all crawled pages are included in the sitemap file.

    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

The website mqsbarn.com has several critical security issues. It lacks essential HTTP response headers that protect against various attacks, such as man-in-the-middle and clickjacking. Additionally, it uses an outdated and vulnerable version of jQuery. A Google API key found in the page code could also be exploited if not properly secured. Immediate action is recommended to enhance security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted on their first unsecure request.

    Fix: Implement HSTS by adding 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to your HTTP response headers.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: No CSP means scripts, styles, and frames can be loaded from anywhere, increasing the risk of XSS attacks.

    Fix: Add a Content-Security-Policy header with appropriate directives to restrict resources, e.g., 'Content-Security-Policy: default-src 'self';'

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, your site is vulnerable to clickjacking attacks.

    Fix: Add 'X-Frame-Options: DENY' or 'X-Frame-Options: SAMEORIGIN' to your HTTP response headers.

    Evidence: Clickjacking protection

  4. 4

    Outdated jQuery LibraryMedium

    Why it matters: Using jQuery 1.7.0 exposes you to multiple known vulnerabilities.

    Fix: Upgrade jQuery to at least version 3.5.0 to resolve known issues and improve security.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Leaked Google API KeyMedium

    Why it matters: A public API key can be abused, leading to unauthorized access to your Google services.

    Fix: Restrict the API key by setting the HTTP referrer in the Google Cloud console, or use an environment variable to keep it hidden.

    Evidence: Keys and secrets in page code

  6. 6

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this, browsers might execute files as scripts based on their content, leading to potential attacks.

    Fix: Add 'X-Content-Type-Options: nosniff' to your HTTP response headers.

    Evidence: MIME sniffing protection

  7. 7

    Missing Referrer-Policy HeaderLow

    Why it matters: Absence of this policy means full URL information is sent to third-party sites, which might leak sensitive data.

    Fix: Add 'Referrer-Policy: no-referrer' or similar to your HTTP response headers.

    Evidence: Referrer policy

  8. 8

    Third-Party Scripts Without Subresource IntegrityLow

    Why it matters: Exfiltration of data can occur through unverified scripts if compromised.

    Fix: Implement Subresource Integrity (SRI) tags on all third-party scripts where possible, or use a restrictive CSP.

    Evidence: Third-party scripts

  9. 9

    Missing Permissions-Policy HeaderInfo

    Why it matters: Not having a Permissions-Policy allows scripts access to unnecessary browser features, increasing risk.

    Fix: Include 'Permissions-Policy: geolocation=(self), microphone=()' to limit feature usage.

    Evidence: Permissions policy

  10. 10

    Sensitive Path in robots.txtInfo

    Why it matters: The presence of private paths in robots.txt can assist attackers in targeting sensitive areas.

    Fix: Implement real access control instead of relying solely on robots.txt to protect sensitive paths.

    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://mqsbarn.com/ → no strict-transport-security
    • https://mqsbarn.com/about-us/ → no strict-transport-security
    • https://mqsbarn.com/building-process/ → no strict-transport-security
    • https://mqsbarn.com/faq/ → no strict-transport-security
    • https://mqsbarn.com/commercial-pole-barns/ → no strict-transport-security
    • https://mqsbarn.com/commercial-gallery/ → no strict-transport-security
    • https://mqsbarn.com/equestrian-pole-barns/ → no strict-transport-security
    • https://mqsbarn.com/equestrian-gallery/ → no strict-transport-security
    • https://mqsbarn.com/residential-pole-barns/ → no strict-transport-security
    • https://mqsbarn.com/garages-hobby-shop-gallery/ → no strict-transport-security
    • https://mqsbarn.com/agricultural-pole-barns/ → no strict-transport-security
    • https://mqsbarn.com/agricultural-gallery/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 289 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://mqsbarn.com/ → no content-security-policy
    • https://mqsbarn.com/about-us/ → no content-security-policy
    • https://mqsbarn.com/building-process/ → no content-security-policy
    • https://mqsbarn.com/faq/ → no content-security-policy
    • https://mqsbarn.com/commercial-pole-barns/ → no content-security-policy
    • https://mqsbarn.com/commercial-gallery/ → no content-security-policy
    • https://mqsbarn.com/equestrian-pole-barns/ → no content-security-policy
    • https://mqsbarn.com/equestrian-gallery/ → no content-security-policy
    • https://mqsbarn.com/residential-pole-barns/ → no content-security-policy
    • https://mqsbarn.com/garages-hobby-shop-gallery/ → no content-security-policy
    • https://mqsbarn.com/agricultural-pole-barns/ → no content-security-policy
    • https://mqsbarn.com/agricultural-gallery/ → 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://mqsbarn.com/ → no x-frame-options
    • https://mqsbarn.com/about-us/ → no x-frame-options
    • https://mqsbarn.com/building-process/ → no x-frame-options
    • https://mqsbarn.com/faq/ → no x-frame-options
    • https://mqsbarn.com/commercial-pole-barns/ → no x-frame-options
    • https://mqsbarn.com/commercial-gallery/ → no x-frame-options
    • https://mqsbarn.com/equestrian-pole-barns/ → no x-frame-options
    • https://mqsbarn.com/equestrian-gallery/ → no x-frame-options
    • https://mqsbarn.com/residential-pole-barns/ → no x-frame-options
    • https://mqsbarn.com/garages-hobby-shop-gallery/ → no x-frame-options
    • https://mqsbarn.com/agricultural-pole-barns/ → no x-frame-options
    • https://mqsbarn.com/agricultural-gallery/ → 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://mqsbarn.com/ → no x-content-type-options
    • https://mqsbarn.com/about-us/ → no x-content-type-options
    • https://mqsbarn.com/building-process/ → no x-content-type-options
    • https://mqsbarn.com/faq/ → no x-content-type-options
    • https://mqsbarn.com/commercial-pole-barns/ → no x-content-type-options
    • https://mqsbarn.com/commercial-gallery/ → no x-content-type-options
    • https://mqsbarn.com/equestrian-pole-barns/ → no x-content-type-options
    • https://mqsbarn.com/equestrian-gallery/ → no x-content-type-options
    • https://mqsbarn.com/residential-pole-barns/ → no x-content-type-options
    • https://mqsbarn.com/garages-hobby-shop-gallery/ → no x-content-type-options
    • https://mqsbarn.com/agricultural-pole-barns/ → no x-content-type-options
    • https://mqsbarn.com/agricultural-gallery/ → no x-content-type-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://mqsbarn.com/ → no referrer-policy
    • https://mqsbarn.com/about-us/ → no referrer-policy
    • https://mqsbarn.com/building-process/ → no referrer-policy
    • https://mqsbarn.com/faq/ → no referrer-policy
    • https://mqsbarn.com/commercial-pole-barns/ → no referrer-policy
    • https://mqsbarn.com/commercial-gallery/ → no referrer-policy
    • https://mqsbarn.com/equestrian-pole-barns/ → no referrer-policy
    • https://mqsbarn.com/equestrian-gallery/ → no referrer-policy
    • https://mqsbarn.com/residential-pole-barns/ → no referrer-policy
    • https://mqsbarn.com/garages-hobby-shop-gallery/ → no referrer-policy
    • https://mqsbarn.com/agricultural-pole-barns/ → no referrer-policy
    • https://mqsbarn.com/agricultural-gallery/ → 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://mqsbarn.com/ → no permissions-policy
    • https://mqsbarn.com/about-us/ → no permissions-policy
    • https://mqsbarn.com/building-process/ → no permissions-policy
    • https://mqsbarn.com/faq/ → no permissions-policy
    • https://mqsbarn.com/commercial-pole-barns/ → no permissions-policy
    • https://mqsbarn.com/commercial-gallery/ → no permissions-policy
    • https://mqsbarn.com/equestrian-pole-barns/ → no permissions-policy
    • https://mqsbarn.com/equestrian-gallery/ → no permissions-policy
    • https://mqsbarn.com/residential-pole-barns/ → no permissions-policy
    • https://mqsbarn.com/garages-hobby-shop-gallery/ → no permissions-policy
    • https://mqsbarn.com/agricultural-pole-barns/ → no permissions-policy
    • https://mqsbarn.com/agricultural-gallery/ → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 1.7.0 in https://mqsbarn.com/wp-content/themes/salient/js/build/third-party/hoverintent.…: CVE-2012-6708 (selector XSS), CVE-2015-9251, CVE-2019-11358, CVE-2020-11022, CVE-2020-11023; 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…OU (39 chars) in https://mqsbarn.com/event/mqs-spring-sale-boise-id-pop-up/: 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 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 (40 script tags)
    • s.ksrndkehqnwntyxlhgto.com (40 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, 1 not applicable
  • OKHTTPS

    All 289 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

    54 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 applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

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

Own mqsbarn.com?

mqsbarn.com scan 2026-09-28-0800 | DIY SEO Hub