Scanned sites / gloriannfarms.com

SEO report for gloriannfarms.com DR 6

The latest Site Spider scan of gloriannfarms.com, with 1 scan on record. Each scan is at its own address, for example /domain/gloriannfarms-com/2026-09-15-1300.

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

Latest scan

Scanned 2026-09-15 13:00:01 UTC, finished 2026-09-15 13:10:36 UTC. Found on page 1 of chatgpt for browser (api usage) results

Site: http://gloriannfarms.com/

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

70/ 100Needs work

On September 15, 2026 the Site Spider crawled 71 pages and 263 assets of gloriannfarms.com, starting from http://gloriannfarms.com/. It scored 70 out of 100, a result that needs work. 12 of 27 checks found something to fix, led by indexability (51), heavy assets (15), meta descriptions (49); 6 checks passed. Most of the points went to indexability (−7.6), heavy assets (−6), meta descriptions (−5.9). 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: High2 high, 3 medium, 2 low and 2 info findings. See the security findings ↓

Pages crawled
71
Assets fetched
263
Status
Completed
Checks with issues
12 of 27
CoverageComplete crawl

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

  • Title tags25 issues
    25 of 50 pages have title issues. 17 noindex or canonicalized pages excluded.
    −3.7 points
  • Meta descriptions49 issues
    49 of 50 pages have meta description issues. 17 noindex or canonicalized pages excluded.
    −5.9 points
  • Headings1 issue
    1 of 50 pages have heading issues. 17 noindex or canonicalized pages excluded.
    −0.1 points
  • Broken links1 issue
    4 internal links point at 1 broken URL.
    −0.3 points
  • Links to other sites83 noted
    0 destinations answered with an error, 11 could not be determined (timeouts, rate limits or refusals), of 23 destinations checked.
  • Redirects3 issues
    4 redirecting URLs, 0 of them chained.
    −0.2 points
  • Non-200 responses1 issue
    5 URLs did not return a 2xx response. 4 of them are pages, 1 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability51 issues
    51 of 51 indexable pages have indexability warnings. 16 pages noindex by design.
    −7.6 points
  • Image alt text134 issues
    134 of 249 image references have no alt attribute. 15 use an empty alt (decorative), which is fine.
    −3.2 points
  • Heavy assets15 issues
    15 assets larger than 500 KB among 263 fetched assets. 2 documents over that size are listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages7 issues
    7 pages have no internal links pointing at them.
    −0.4 points
  • Sitemap coverage10 issues
    6 sitemaps listing 47 URLs: 3 crawled pages missing, 0 listed URLs broken or redirecting, 7 reachable only via the sitemap.
    −0.9 points
  • Internal link counts16 noted
    Internal link counts for 67 pages; 16 worth a look.
  • Thin content16 issues
    16 of 50 pages have fewer than 200 words. 17 noindex or canonicalized pages excluded.
    −1.9 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format6 noted
    6 of 71 page URLs are harder to read, share or cache than they need to be.
  • Canonicals1 noted
    1 of 67 pages have a canonical worth checking.
  • Robots directives17 noted
    17 pages carry a robots directive; 50 carry none.
  • Anchor text3 noted
    3 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure44 noted
    44 of 50 pages could use the title, heading and snippet space better. 17 noindex or canonicalized pages excluded.
  • Image weight and alt length13 noted
    13 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 404sOK
    None of 67 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 334 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 67 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 87 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 site sits among all scanned sites

2873 sites, median 80%, average 79%

gloriannfarms.com scores 70%, higher than 16% 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 sites70% 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 requires attention with broken links, redirects, and title/meta description issues. Prioritize fixing broken links and reviewing title and meta description tags for better SEO performance.

  1. 1

    Fix Broken Links

    Why: Correcting broken links improves user experience and site credibility.

    How: Update internal links pointing to the broken URL with valid URLs.

    Checks: broken-links

  2. 2

    Address Non-200 Responses

    Why: Ensure all pages return successful responses to users and search engines.

    How: Redirect or fix any URL returning a non-200 status code.

    Checks: status-codes

  3. 3

    Revise Title Tags

    Why: Optimized title tags improve click-through rates from search results.

    How: Shorten titles under 60 characters and ensure uniqueness.

    Checks: titles

  4. 4

    Update Meta Descriptions

    Why: Well-crafted meta descriptions can significantly improve visibility.

    How: Add relevant, engaging meta descriptions of 150-160 characters for all pages.

    Checks: meta-descriptions

  5. 5

    Add H1 to Homepage

    Why: A primary heading (H1) is important for content structure and SEO.

    How: Include a clear, descriptive H1 tag on the homepage.

    Checks: headings

  6. 6

    Improve Image Alt Text

    Why: Adding alt text helps with SEO and accessibility.

    How: Add descriptive alt attributes to all images missing them.

    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 gloriannfarms.com has several serious security issues, primarily related to the absence of HTTPS, which exposes data to interception. Other findings include the lack of security headers that would limit risks from script and frame vulnerabilities. Immediate action is needed to enhance security.

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

    HTTP Not Secured (HTTPS)High

    Why it matters: 67 pages are served over HTTP, making them vulnerable to interception.

    Fix: Implement an HTTPS certificate and configure server to redirect HTTP requests to HTTPS.

    Evidence: HTTPS

  2. 2

    Unsecured FormsHigh

    Why it matters: Forms are submitted over HTTP, exposing sensitive user information.

    Fix: Ensure all forms are on HTTPS pages, configure correct routing.

    Evidence: Forms over HTTPS

  3. 3

    Missing Content Security PolicyMedium

    Why it matters: Without a CSP, the site is vulnerable to Cross-Site Scripting (XSS) attacks.

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

    Evidence: Content Security Policy

  4. 4

    No Clickjacking ProtectionMedium

    Why it matters: Lack of X-Frame-Options allows pages to be embedded in unauthorized frames.

    Fix: Add an X-Frame-Options header: `X-Frame-Options: DENY`.

    Evidence: Clickjacking protection

  5. 5

    Vulnerable JavaScript LibrariesMedium

    Why it matters: Outdated jQuery versions have known vulnerabilities that could be exploited.

    Fix: Upgrade jQuery to the latest stable version (≥ 3.5.0).

    Evidence: Vulnerable JavaScript libraries

  6. 6

    Lack of MIME Sniffing ProtectionLow

    Why it matters: Absence of X-Content-Type-Options may allow execution of malicious files.

    Fix: Add an X-Content-Type-Options header: `X-Content-Type-Options: nosniff`.

    Evidence: MIME sniffing protection

  7. 7

    No Referrer PolicyLow

    Why it matters: Full URLs may be leaked when users navigate away from the site.

    Fix: Add a Referrer-Policy header: `Referrer-Policy: no-referrer`.

    Evidence: Referrer policy

  8. 8

    No Permissions PolicyInfo

    Why it matters: Without a Permissions-Policy, features like geolocation can be misused.

    Fix: Add a Permissions-Policy header: `Permissions-Policy: geolocation=()`.

    Evidence: Permissions policy

  9. 9

    Sensitive Paths in robots.txtInfo

    Why it matters: Robots.txt may expose sensitive paths, potentially aiding attackers.

    Fix: Implement proper access controls for sensitive directories.

    Evidence: Sensitive paths in robots.txt

What the checks found

  • FoundHTTPSHigh

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

    • http://gloriannfarms.com/ → 200 over http
    • http://gloriannfarms.com/history/ → 200 over http
    • http://gloriannfarms.com/growing-regions/ → 200 over http
    • http://gloriannfarms.com/retail/ → 200 over http
    • http://gloriannfarms.com/food-service/ → 200 over http
    • http://gloriannfarms.com/quality-assurance/ → 200 over http
    • http://gloriannfarms.com/packaging-process/ → 200 over http
    • http://gloriannfarms.com/faq/ → 200 over http
    • http://gloriannfarms.com/corn-on-the-cob-cooking-instructions/ → 200 over http
    • http://gloriannfarms.com/national-breast-cancer-foundation/ → 200 over http
    • http://gloriannfarms.com/intrepid-fallen-heroes-fund/ → 200 over http
    • http://gloriannfarms.com/news/ → 200 over http
  • FoundContent Security PolicyMedium

    None of the 67 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://gloriannfarms.com/ → no content-security-policy
    • http://gloriannfarms.com/history/ → no content-security-policy
    • http://gloriannfarms.com/growing-regions/ → no content-security-policy
    • http://gloriannfarms.com/retail/ → no content-security-policy
    • http://gloriannfarms.com/food-service/ → no content-security-policy
    • http://gloriannfarms.com/quality-assurance/ → no content-security-policy
    • http://gloriannfarms.com/packaging-process/ → no content-security-policy
    • http://gloriannfarms.com/faq/ → no content-security-policy
    • http://gloriannfarms.com/corn-on-the-cob-cooking-instructions/ → no content-security-policy
    • http://gloriannfarms.com/national-breast-cancer-foundation/ → no content-security-policy
    • http://gloriannfarms.com/intrepid-fallen-heroes-fund/ → no content-security-policy
    • http://gloriannfarms.com/news/ → 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://gloriannfarms.com/ → no x-frame-options
    • http://gloriannfarms.com/history/ → no x-frame-options
    • http://gloriannfarms.com/growing-regions/ → no x-frame-options
    • http://gloriannfarms.com/retail/ → no x-frame-options
    • http://gloriannfarms.com/food-service/ → no x-frame-options
    • http://gloriannfarms.com/quality-assurance/ → no x-frame-options
    • http://gloriannfarms.com/packaging-process/ → no x-frame-options
    • http://gloriannfarms.com/faq/ → no x-frame-options
    • http://gloriannfarms.com/corn-on-the-cob-cooking-instructions/ → no x-frame-options
    • http://gloriannfarms.com/national-breast-cancer-foundation/ → no x-frame-options
    • http://gloriannfarms.com/intrepid-fallen-heroes-fund/ → no x-frame-options
    • http://gloriannfarms.com/news/ → 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://gloriannfarms.com/ → no x-content-type-options
    • http://gloriannfarms.com/history/ → no x-content-type-options
    • http://gloriannfarms.com/growing-regions/ → no x-content-type-options
    • http://gloriannfarms.com/retail/ → no x-content-type-options
    • http://gloriannfarms.com/food-service/ → no x-content-type-options
    • http://gloriannfarms.com/quality-assurance/ → no x-content-type-options
    • http://gloriannfarms.com/packaging-process/ → no x-content-type-options
    • http://gloriannfarms.com/faq/ → no x-content-type-options
    • http://gloriannfarms.com/corn-on-the-cob-cooking-instructions/ → no x-content-type-options
    • http://gloriannfarms.com/national-breast-cancer-foundation/ → no x-content-type-options
    • http://gloriannfarms.com/intrepid-fallen-heroes-fund/ → no x-content-type-options
    • http://gloriannfarms.com/news/ → 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://gloriannfarms.com/ → no referrer-policy
    • http://gloriannfarms.com/history/ → no referrer-policy
    • http://gloriannfarms.com/growing-regions/ → no referrer-policy
    • http://gloriannfarms.com/retail/ → no referrer-policy
    • http://gloriannfarms.com/food-service/ → no referrer-policy
    • http://gloriannfarms.com/quality-assurance/ → no referrer-policy
    • http://gloriannfarms.com/packaging-process/ → no referrer-policy
    • http://gloriannfarms.com/faq/ → no referrer-policy
    • http://gloriannfarms.com/corn-on-the-cob-cooking-instructions/ → no referrer-policy
    • http://gloriannfarms.com/national-breast-cancer-foundation/ → no referrer-policy
    • http://gloriannfarms.com/intrepid-fallen-heroes-fund/ → no referrer-policy
    • http://gloriannfarms.com/news/ → 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://gloriannfarms.com/ → no permissions-policy
    • http://gloriannfarms.com/history/ → no permissions-policy
    • http://gloriannfarms.com/growing-regions/ → no permissions-policy
    • http://gloriannfarms.com/retail/ → no permissions-policy
    • http://gloriannfarms.com/food-service/ → no permissions-policy
    • http://gloriannfarms.com/quality-assurance/ → no permissions-policy
    • http://gloriannfarms.com/packaging-process/ → no permissions-policy
    • http://gloriannfarms.com/faq/ → no permissions-policy
    • http://gloriannfarms.com/corn-on-the-cob-cooking-instructions/ → no permissions-policy
    • http://gloriannfarms.com/national-breast-cancer-foundation/ → no permissions-policy
    • http://gloriannfarms.com/intrepid-fallen-heroes-fund/ → no permissions-policy
    • http://gloriannfarms.com/news/ → no permissions-policy
  • FoundForms over HTTPSHigh

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

    • http://gloriannfarms.com/press-room/ has a password field on a page served over plain HTTP
  • FoundVulnerable JavaScript librariesMedium

    3 libraries with published vulnerabilities: jQuery 1.12.4, jQuery 1.3.2, jQuery 2.0.0. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.12.4 in http://gloriannfarms.com/wp-includes/js/jquery/jquery.js?ver=1.12.4: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
    • jQuery 1.3.2 in http://gloriannfarms.com/wp-content/themes/gaf/lib/frontend/javascripts/jquery.…: CVE-2012-6708 (selector XSS), CVE-2015-9251, CVE-2019-11358, CVE-2020-11022, CVE-2020-11023; fixed in 3.5.0
    • jQuery 2.0.0 in http://gloriannfarms.com/wp-content/plugins/wpStickies/js/wpstickies.kreaturame…: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • 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/
4 checks passed, 3 not applicable
  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

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

  • OKThird-party scripts

    The sampled pages load no scripts from other domains.

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

Earlier scans of gloriannfarms.com

No other scans of this site yet.

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

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