Scanned sites / 21degreesestate.com

SEO report for 21degreesestate.com

The latest Site Spider scan of 21degreesestate.com, with 1 scan on record. Each scan is at its own address, for example /domain/21degreesestate-com/2026-09-19-1500.

Latest scan

Scanned 9/19/2026, 3:00:01 PM, finished 9/19/2026, 3:28:41 PM. Found on page 3 of chatgpt for browser (api usage) results

Site: https://21degreesestate.com/

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

84/ 100Good

On September 19, 2026 the Site Spider crawled 39 pages and 577 assets of 21degreesestate.com, starting from https://21degreesestate.com/. It scored 84 out of 100, a good result. 8 of 14 checks found something to fix, led by heavy assets (88), redirects (13), sitemap coverage (12); 6 checks passed. 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: Medium4 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
39
Assets fetched
577
Status
Completed
Checks with issues
8 of 14
  • Title tags7 issues
    7 of 21 pages have title issues. 5 noindex or canonicalized pages excluded.
  • Meta descriptions3 issues
    3 of 21 pages have meta description issues. 5 noindex or canonicalized pages excluded.
  • Headings1 issue
    1 of 21 pages have heading issues. 5 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Redirects13 issues
    136 redirecting URLs, 0 of them chained.
  • Non-200 responsesOK
    310 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 21 indexable pages have indexability warnings. 5 pages noindex by design.
  • Image alt textOK
    0 of 52 image references have no alt attribute. 1 use an empty alt (decorative), which is fine.
  • Heavy assets88 issues
    88 assets larger than 500 KB among the 100 heaviest.
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
  • Sitemap coverage12 issues
    3 sitemaps listing 10 URLs: 11 crawled pages missing, 0 listed URLs broken or redirecting, 1 reachable only via the sitemap.
  • Thin content4 issues
    4 of 21 pages have fewer than 200 words. 5 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this site sits among all scanned sites

1107 sites, median 82%, average 80%

21degreesestate.com scores 84%, higher than 57% of the 1107 scanned sites. See the full ranking.

028560%: 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%: 0 sites38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 1 site47%: 1 site48%: 0 sites49%: 0 sites50%: 3 sites51%: 4 sites52%: 1 site53%: 1 site54%: 2 sites55%: 1 site56%: 2 sites57%: 3 sites58%: 6 sites59%: 3 sites60%: 5 sites61%: 8 sites62%: 12 sites63%: 5 sites64%: 9 sites65%: 9 sites66%: 9 sites67%: 15 sites68%: 28 sites69%: 12 sites70%: 24 sites71%: 21 sites72%: 24 sites73%: 24 sites74%: 31 sites75%: 26 sites76%: 39 sites77%: 37 sites78%: 35 sites79%: 33 sites80%: 43 sites81%: 55 sites82%: 49 sites83%: 46 sites84%: 55 sites85%: 48 sites86%: 45 sites87%: 49 sites88%: 56 sites89%: 38 sites90%: 52 sites91%: 38 sites92%: 25 sites93%: 17 sites94%: 16 sites95%: 8 sites96%: 10 sites97%: 4 sites98%: 2 sites99%: 1 site100%: 10 sites84% 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 website has several SEO issues that need attention, particularly with redirects and non-200 responses. Focus on fixing these high-priority items to enhance performance and visibility.

  1. 1

    Fix Non-200 Responses

    Why: 310 URLs returning non-200 responses can harm user experience and SEO.

    How: Identify these URLs and ensure they return a 200 status. Update or remove broken links.

    Checks: status-codes

  2. 2

    Resolve Redirect Issues

    Why: 136 redirecting URLs may slow down site performance and confuse users.

    How: Review and reduce the number of redirects, ideally direct to final URLs.

    Checks: redirects

  3. 3

    Update Title Tags

    Why: 7 title issues limit clarity and relevance for search engines.

    How: Shorten titles to under 60 characters to improve click-through rates.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: 3 meta description issues may reduce click-through rates.

    How: Revise the meta descriptions to be compelling and within the optimal length.

    Checks: meta-descriptions

  5. 5

    Add H1 Heading

    Why: Lack of H1 can confuse search engines about page focus.

    How: Add a relevant H1 tag to the page without an H1 (best-chocolate-farm-tour-on-oahu).

    Checks: headings

  6. 6

    Improve Thin Content

    Why: 4 pages with thin content may not rank well.

    How: Enhance content to ensure each page has 200+ words and valuable information.

    Checks: thin-content

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 has several security issues that need addressing to protect user data and ensure safe browsing. Key findings include the lack of important HTTP headers and exposure of a Google API key, which could be exploited by attackers. Implementing suggested security headers and controlling API access are essential steps.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users may be vulnerable to man-in-the-middle attacks if they type the address without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP allows scripts from any location, increasing the risk of cross-site scripting (XSS) attacks.

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

    Evidence: Content Security Policy

  3. 3

    No Clickjacking ProtectionMedium

    Why it matters: Lack of X-Frame-Options allows clickjacking attacks that can trick users into performing actions they did not intend.

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

    Evidence: Clickjacking protection

  4. 4

    Leaked Google API KeyMedium

    Why it matters: An exposed Google API key can be abused by malicious users, leading to potential service overages or unauthorized access.

    Fix: Restrict the API key usage by referring it to specific HTTP referrers in the Google Cloud console.

    Evidence: Keys and secrets in page code

  5. 5

    Missing MIME Sniffing ProtectionLow

    Why it matters: Without X-Content-Type-Options, browsers may treat files as scripts based on content instead of their declared type.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Absence of a referrer policy may lead to sensitive URLs being shared without consent.

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

    Evidence: Referrer policy

  7. 7

    Server and Framework Version DisclosureLow

    Why it matters: Revealing the server types and versions can help attackers exploit known vulnerabilities.

    Fix: Remove or hide the 'Server' and 'X-Powered-By' headers.

    Evidence: Software version disclosure

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Not using a Permissions-Policy may allow misusing browser features that the site does not need.

    Fix: Add the header: Permissions-Policy: geolocation=(self).

    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://21degreesestate.com/ → no strict-transport-security
    • https://21degreesestate.com/tours/ → no strict-transport-security
    • https://21degreesestate.com/events/ → no strict-transport-security
    • https://21degreesestate.com/our-story/ → no strict-transport-security
    • https://21degreesestate.com/gallery/ → no strict-transport-security
    • https://21degreesestate.com/faq/ → no strict-transport-security
    • https://21degreesestate.com/contact-us/ → no strict-transport-security
    • https://21degreesestate.com/blog/ → no strict-transport-security
    • https://21degreesestate.com/chocolate-storage/ → no strict-transport-security
    • https://21degreesestate.com/shipping-info/ → no strict-transport-security
    • https://21degreesestate.com/refund_returns/ → no strict-transport-security
    • https://21degreesestate.com/terms-conditions/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 26 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://21degreesestate.com/ → no content-security-policy
    • https://21degreesestate.com/tours/ → no content-security-policy
    • https://21degreesestate.com/events/ → no content-security-policy
    • https://21degreesestate.com/our-story/ → no content-security-policy
    • https://21degreesestate.com/gallery/ → no content-security-policy
    • https://21degreesestate.com/faq/ → no content-security-policy
    • https://21degreesestate.com/contact-us/ → no content-security-policy
    • https://21degreesestate.com/blog/ → no content-security-policy
    • https://21degreesestate.com/chocolate-storage/ → no content-security-policy
    • https://21degreesestate.com/shipping-info/ → no content-security-policy
    • https://21degreesestate.com/refund_returns/ → no content-security-policy
    • https://21degreesestate.com/terms-conditions/ → 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://21degreesestate.com/ → no x-frame-options
    • https://21degreesestate.com/tours/ → no x-frame-options
    • https://21degreesestate.com/events/ → no x-frame-options
    • https://21degreesestate.com/our-story/ → no x-frame-options
    • https://21degreesestate.com/gallery/ → no x-frame-options
    • https://21degreesestate.com/faq/ → no x-frame-options
    • https://21degreesestate.com/contact-us/ → no x-frame-options
    • https://21degreesestate.com/blog/ → no x-frame-options
    • https://21degreesestate.com/chocolate-storage/ → no x-frame-options
    • https://21degreesestate.com/shipping-info/ → no x-frame-options
    • https://21degreesestate.com/refund_returns/ → no x-frame-options
    • https://21degreesestate.com/terms-conditions/ → 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://21degreesestate.com/ → no x-content-type-options
    • https://21degreesestate.com/tours/ → no x-content-type-options
    • https://21degreesestate.com/events/ → no x-content-type-options
    • https://21degreesestate.com/our-story/ → no x-content-type-options
    • https://21degreesestate.com/gallery/ → no x-content-type-options
    • https://21degreesestate.com/faq/ → no x-content-type-options
    • https://21degreesestate.com/contact-us/ → no x-content-type-options
    • https://21degreesestate.com/blog/ → no x-content-type-options
    • https://21degreesestate.com/chocolate-storage/ → no x-content-type-options
    • https://21degreesestate.com/shipping-info/ → no x-content-type-options
    • https://21degreesestate.com/refund_returns/ → no x-content-type-options
    • https://21degreesestate.com/terms-conditions/ → 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://21degreesestate.com/ → no referrer-policy
    • https://21degreesestate.com/tours/ → no referrer-policy
    • https://21degreesestate.com/events/ → no referrer-policy
    • https://21degreesestate.com/our-story/ → no referrer-policy
    • https://21degreesestate.com/gallery/ → no referrer-policy
    • https://21degreesestate.com/faq/ → no referrer-policy
    • https://21degreesestate.com/contact-us/ → no referrer-policy
    • https://21degreesestate.com/blog/ → no referrer-policy
    • https://21degreesestate.com/chocolate-storage/ → no referrer-policy
    • https://21degreesestate.com/shipping-info/ → no referrer-policy
    • https://21degreesestate.com/refund_returns/ → no referrer-policy
    • https://21degreesestate.com/terms-conditions/ → 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://21degreesestate.com/ → no permissions-policy
    • https://21degreesestate.com/tours/ → no permissions-policy
    • https://21degreesestate.com/events/ → no permissions-policy
    • https://21degreesestate.com/our-story/ → no permissions-policy
    • https://21degreesestate.com/gallery/ → no permissions-policy
    • https://21degreesestate.com/faq/ → no permissions-policy
    • https://21degreesestate.com/contact-us/ → no permissions-policy
    • https://21degreesestate.com/blog/ → no permissions-policy
    • https://21degreesestate.com/chocolate-storage/ → no permissions-policy
    • https://21degreesestate.com/shipping-info/ → no permissions-policy
    • https://21degreesestate.com/refund_returns/ → no permissions-policy
    • https://21degreesestate.com/terms-conditions/ → 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 (616 responses)
    • x-powered-by: PHP/8.1.34 (314 responses)
  • FoundKeys and secrets in page codeMedium

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

    • Google API key AIzaSy…WQ (39 chars) in https://21degreesestate.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 3 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 (26 script tags)
    • fareharbor.com (25 script tags)
    • www.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/
5 checks passed, 1 not applicable
  • OKHTTPS

    All 26 crawled pages were served over HTTPS.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

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

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

Earlier scans of 21degreesestate.com

No other scans of this site yet.

This report was produced by the DIY SEO Hub Site Spider crawling 21degreesestate.com from its public pages. Anyone can run a scan of any site they own or are authorised to check. Is this your site? Claim it to manage the listing, or ask for removal through the support form.

21degreesestate.com SEO report | DIY SEO Hub