Scanned sites / bluebarn.com / 2026-09-22-0000

bluebarn.com scan from 2026-09-22 00:00:01 UTC DR 0

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

Scan 2026-09-22-0000

Scanned 2026-09-22 00:00:01 UTC, finished 2026-09-22 00:02:53 UTC. Found on page 1 of chatgpt for browser (api usage) results

Site: http://bluebarn.com/

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

77/ 100Good

On September 22, 2026 the Site Spider crawled 6 pages and 94 assets of bluebarn.com, starting from http://bluebarn.com/. It scored 77 out of 100, a good result. 7 of 27 checks found something to fix, led by meta descriptions (6), thin content (6), indexability (2); 11 checks passed. Most of the points went to meta descriptions (−8), thin content (−8), indexability (−3.3). 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: High1 high, 4 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
6
Assets fetched
94
Status
Completed
Checks with issues
7 of 27
CoverageComplete crawl

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

  • Title tags1 issue
    1 of 6 pages have title issues.
    −1.7 points
  • Meta descriptions6 issues
    6 of 6 pages have meta description issues.
    −8 points
  • HeadingsOK
    0 of 6 pages have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites1 issue
    1 destination answered with an error, of 6 destinations checked.
    −0.4 points
  • Redirects1 noted
    1 redirecting URL, 0 of them chained.
  • Non-200 responses4 noted
    4 URLs did not return a 2xx response. 0 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.
  • Indexability2 issues
    2 of 6 indexable pages have indexability warnings.
    −3.3 points
  • Image alt textOK
    0 of 23 image references have no alt attribute. 5 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among 94 fetched assets.
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
    −0.7 points
  • Sitemap coverage1 issue
    4 sitemaps listing 6 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 1 reachable only via the sitemap.
    −1 points
  • Internal link countsOK
    Internal link counts for 6 pages; none is a dead end or buried.
  • Thin content6 issues
    6 of 6 pages have fewer than 200 words.
    −8 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 6 page URLs are plain lowercase addresses without parameters.
  • Canonicals2 noted
    2 of 6 pages have a canonical worth checking.
  • Robots directives6 noted
    6 pages carry a robots directive; 0 carry none.
  • Anchor text1 noted
    1 destination are linked without useful anchor text, or with nofollow.
  • Title and heading structure6 noted
    6 of 6 pages could use the title, heading and snippet space better.
  • Image weight and alt length4 noted
    4 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • 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 404s2 noted
    2 pages answer 200 but say they are not there.
  • 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; 11 response headers recorded across 100 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 6 pages; 0 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 52 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.

Where this scan sits among all scanned sites

2873 sites, median 80%, average 79%

bluebarn.com scores 77%, higher than 35% of the 2873 scanned sites. See the full ranking.

0751500%: 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%: 0 sites34%: 0 sites35%: 2 sites36%: 1 site37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 80 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 111 sites80%: 128 sites81%: 125 sites82%: 132 sites83%: 119 sites84%: 130 sites85%: 106 sites86%: 95 sites87%: 96 sites88%: 80 sites89%: 75 sites90%: 55 sites91%: 59 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 150 sites77% 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.

The site has several areas for improvement, including non-200 responses and missing metadata. Addressing these can enhance SEO performance and user experience significantly.

  1. 1

    Fix Non-200 Responses

    Why: 404 errors reduce user experience and SEO ranking.

    How: Update or remove the URLs returning 404 errors.

    Checks: status-codes

  2. 2

    Add Meta Descriptions

    Why: Meta descriptions help improve click-through rates from search results.

    How: Provide concise, relevant meta descriptions for all pages.

    Checks: meta-descriptions

  3. 3

    Correct Title Tag Issues

    Why: Title tags impact SEO and user engagement.

    How: Modify the homepage title to exceed 30 characters and accurately reflect the content.

    Checks: titles

  4. 4

    Resolve Redirects

    Why: Redirects can hinder crawlers and slow down page load times.

    How: Change the 302 redirect of sitemap.xml to a permanent redirect if appropriate.

    Checks: redirects

  5. 5

    Address Indexability Warnings

    Why: Canonical issues may confuse search engines about which version of a page to index.

    How: Add canonical tags to the affected pages to prevent indexing issues.

    Checks: indexability

  6. 6

    Link to Orphan Page

    Why: Orphan pages have no internal links and may be overlooked by search engines.

    How: Create internal links to the orphan page from relevant content.

    Checks: orphan-pages

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 site lacks critical security headers and serves pages over HTTP, exposing sensitive data to interception. Immediate actions are essential to enhance security and protect user data.

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

    HTTP Pages ExposedHigh

    Why it matters: Six pages are served over HTTP, allowing data exposure to attackers.

    Fix: Implement HTTPS by obtaining an SSL certificate and ensuring all pages redirect from HTTP to HTTPS.

    Evidence: HTTPS

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: Absence of a CSP allows scripts from any source, risking XSS attacks.

    Fix: Add a Content-Security-Policy header: `Content-Security-Policy: default-src 'self';` to limit script sources.

    Evidence: Content Security Policy

  3. 3

    No Clickjacking ProtectionMedium

    Why it matters: Missing X-Frame-Options allows embedding the site in frames, risking clickjacking.

    Fix: Include the header: `X-Frame-Options: DENY` or implement a CSP frame-ancestors directive.

    Evidence: Clickjacking protection

  4. 4

    Forms Exposed Over HTTPMedium

    Why it matters: Three forms send data over HTTP, which can be intercepted.

    Fix: Serve all forms over HTTPS to secure user input and data.

    Evidence: Forms over HTTPS

  5. 5

    Leaked Google API KeyMedium

    Why it matters: A Google API key was found in the code, which can lead to misuse or unexpected costs.

    Fix: Restrict the API key using referrer restrictions in the Google Cloud console to limit its use.

    Evidence: Keys and secrets in page code

  6. 6

    Missing MIME Sniffing ProtectionLow

    Why it matters: No X-Content-Type-Options header presents a risk of MIME-type confusion attacks.

    Fix: Add the header: `X-Content-Type-Options: nosniff` to enhance security.

    Evidence: MIME sniffing protection

  7. 7

    No Referrer Policy SetLow

    Why it matters: Without a referrer policy, sensitive URL details are exposed on outbound requests.

    Fix: Set a referrer policy using: `Referrer-Policy: no-referrer-when-downgrade` for better privacy.

    Evidence: Referrer policy

  8. 8

    Software Version DisclosureLow

    Why it matters: The server version is disclosed, making the site vulnerable to known exploits.

    Fix: Configure the server to hide version information or set header: `Server: ` (empty value) to prevent disclosure.

    Evidence: Software version disclosure

  9. 9

    No Permissions Policy SetInfo

    Why it matters: Without this policy, unnecessary features could be accessible to potential attackers

    Fix: Add a Permissions-Policy header: `Permissions-Policy: camera=(), microphone=(), geolocation=()` to limit features.

    Evidence: Permissions policy

What the checks found

  • FoundHTTPSHigh

    6 pages answered 200 over plain HTTP with no redirect to HTTPS. Anyone on the network path can read or alter these pages.

    • http://bluebarn.com/ → 200 over http
    • http://bluebarn.com/employment/ → 200 over http
    • http://bluebarn.com/cattle/ → 200 over http
    • http://bluebarn.com/contact-us/ → 200 over http
    • http://bluebarn.com/partner-view/kansas-potatoes-ltd/ → 200 over http
    • http://bluebarn.com/author/croenbaugh/ → 200 over http
  • FoundContent Security PolicyMedium

    None of the 6 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.

    • http://bluebarn.com/ → no content-security-policy
    • http://bluebarn.com/employment/ → no content-security-policy
    • http://bluebarn.com/cattle/ → no content-security-policy
    • http://bluebarn.com/contact-us/ → no content-security-policy
    • http://bluebarn.com/partner-view/kansas-potatoes-ltd/ → no content-security-policy
    • http://bluebarn.com/author/croenbaugh/ → 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.

    • http://bluebarn.com/ → no x-frame-options
    • http://bluebarn.com/employment/ → no x-frame-options
    • http://bluebarn.com/cattle/ → no x-frame-options
    • http://bluebarn.com/contact-us/ → no x-frame-options
    • http://bluebarn.com/partner-view/kansas-potatoes-ltd/ → no x-frame-options
    • http://bluebarn.com/author/croenbaugh/ → 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.

    • http://bluebarn.com/ → no x-content-type-options
    • http://bluebarn.com/employment/ → no x-content-type-options
    • http://bluebarn.com/cattle/ → no x-content-type-options
    • http://bluebarn.com/contact-us/ → no x-content-type-options
    • http://bluebarn.com/partner-view/kansas-potatoes-ltd/ → no x-content-type-options
    • http://bluebarn.com/author/croenbaugh/ → 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.

    • http://bluebarn.com/ → no referrer-policy
    • http://bluebarn.com/employment/ → no referrer-policy
    • http://bluebarn.com/cattle/ → no referrer-policy
    • http://bluebarn.com/contact-us/ → no referrer-policy
    • http://bluebarn.com/partner-view/kansas-potatoes-ltd/ → no referrer-policy
    • http://bluebarn.com/author/croenbaugh/ → 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.

    • http://bluebarn.com/ → no permissions-policy
    • http://bluebarn.com/employment/ → no permissions-policy
    • http://bluebarn.com/cattle/ → no permissions-policy
    • http://bluebarn.com/contact-us/ → no permissions-policy
    • http://bluebarn.com/partner-view/kansas-potatoes-ltd/ → no permissions-policy
    • http://bluebarn.com/author/croenbaugh/ → 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: openresty/1.27.1.2 (100 responses)
  • FoundForms over HTTPSMedium

    3 forms would send what visitors type over plain HTTP, where it can be read or changed on the way.

    • http://bluebarn.com/employment/ has 1 form on a page served over plain HTTP
    • http://bluebarn.com/contact-us/ has 1 form on a page served over plain HTTP
    • http://bluebarn.com/author/croenbaugh/ has 1 form on a page served over plain HTTP
  • FoundKeys and secrets in page codeMedium

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

    • Google API key AIzaSy…dQ (39 chars) in http://bluebarn.com/contact-us/: 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 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.)

    • maps.google.com (1 script tag)
  • 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/
2 checks passed, 3 not applicable
  • OKVulnerable JavaScript libraries

    1 library version recognised, none with known vulnerabilities.

  • OKExposed files and listings

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

  • Not applicableHTTP Strict Transport Security

    No page was served over HTTPS, so this header does not apply yet.

  • Not applicableCookie flags

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

  • Not applicableMixed content

    No page was served over HTTPS, so mixed content does not apply yet.

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

Own bluebarn.com?