Scanned sites / cateyheritage.com

SEO report for cateyheritage.com DR 1

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

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

Latest scan

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

Site: https://cateyheritage.com/

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

54/ 100Needs work

On September 20, 2026 the Site Spider crawled 16 pages and 77 assets of cateyheritage.com, starting from https://cateyheritage.com/. It scored 54 out of 100, a result that needs work. 8 of 27 checks found something to fix, led by title tags (13), indexability (13), meta descriptions (16); 10 checks passed. Most of the points went to title tags (−8.1), indexability (−8.1), meta descriptions (−8). 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: Medium3 medium, 4 low and 1 info findings. See the security findings ↓

Pages crawled
16
Assets fetched
77
Status
Completed
Checks with issues
8 of 27
CoverageComplete crawl

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

  • Title tags13 issues
    13 of 16 pages have title issues.
    −8.1 points
  • Meta descriptions16 issues
    16 of 16 pages have meta description issues.
    −8 points
  • Headings9 issues
    9 of 16 pages have heading issues.
    −3.4 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites30 noted
    0 destinations answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 4 destinations checked.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responsesOK
    0 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability13 issues
    13 of 16 indexable pages have indexability warnings.
    −8.1 points
  • Image alt textOK
    0 of 35 image references have no alt attribute. 6 use an empty alt (decorative), which is fine.
  • Heavy assets10 issues
    10 assets larger than 500 KB among 77 fetched assets.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage16 issues
    1 sitemap listing 0 URLs: 16 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −6 points
  • Internal link counts1 noted
    Internal link counts for 16 pages; 1 worth a look.
  • Thin content8 issues
    8 of 16 pages have fewer than 200 words.
    −4 points
  • Duplicate content4 issues
    1 group of pages with identical HTML.
    −2 points
  • URL format5 noted
    5 of 16 page URLs are harder to read, share or cache than they need to be.
  • Canonicals6 noted
    6 of 16 pages have a canonical worth checking.
  • Robots directives9 noted
    9 pages carry a robots directive; 7 carry none.
  • Anchor text1 noted
    1 destination are linked without useful anchor text, or with nofollow.
  • Title and heading structure11 noted
    11 of 16 pages could use the title, heading and snippet space better.
  • Image weight and alt length16 noted
    16 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 16 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; 10 response headers recorded across 93 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 16 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 Insights4 noted
    Mobile performance 81 on average across 5 pages; 4 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

2877 sites, median 80%, average 79%

cateyheritage.com scores 54%, higher than 3% of the 2877 scanned sites. See the full ranking.

0761510%: 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%: 10 sites55%: 10 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 30 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 42 sites68%: 42 sites69%: 53 sites70%: 47 sites71%: 80 sites72%: 76 sites73%: 82 sites74%: 83 sites75%: 86 sites76%: 94 sites77%: 109 sites78%: 131 sites79%: 113 sites80%: 127 sites81%: 124 sites82%: 133 sites83%: 119 sites84%: 131 sites85%: 105 sites86%: 95 sites87%: 95 sites88%: 81 sites89%: 74 sites90%: 55 sites91%: 59 sites92%: 43 sites93%: 28 sites94%: 25 sites95%: 15 sites96%: 19 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 151 sites54% 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.

Your site needs significant SEO improvements. Prioritize fixing title tags, meta descriptions, and headings to boost visibility. Also, update your sitemap and address thin content for better user experience.

  1. 1

    Fix Title Tags

    Why: 13 out of 16 pages have short or duplicate title tags, hindering SEO.

    How: Update title tags to be descriptive and between 30-60 characters. Ensure each page has a unique title.

    Checks: titles

  2. 2

    Add Meta Descriptions

    Why: All pages lack meta descriptions, impacting click-through rates.

    How: Write unique meta descriptions for all pages, around 150-160 characters long.

    Checks: meta-descriptions

  3. 3

    Improve Headings Structure

    Why: Missing or multiple H1 tags on pages confuse search engines.

    How: Assign one H1 per page. Make sure H1s are relevant and clear.

    Checks: headings

  4. 4

    Update Sitemap

    Why: Current sitemap does not include any listed URLs, leading to indexing issues.

    How: Generate a new sitemap including all indexable pages and submit it to search engines.

    Checks: sitemap-coverage

  5. 5

    Enhance Thin Content

    Why: 8 pages have fewer than 200 words, which can harm rankings.

    How: Add meaningful content to these pages, ensuring relevance to the topic.

    Checks: thin-content

  6. 6

    Address Duplicate Content

    Why: Duplicate content across multiple pages can dilute SEO efforts.

    How: Merge similar pages or differentiate them with unique content.

    Checks: duplicate-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

Your website has several security headers missing, which could expose it to certain risks, such as clickjacking and interception of unencrypted traffic. Implementing security measures such as strict transport security and content security policy will help protect user data and enhance the overall security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: HSTS prevents man-in-the-middle attacks by ensuring that browsers only communicate over 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: CSP helps to prevent cross-site scripting (XSS) and other code injection attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options for Clickjacking ProtectionMedium

    Why it matters: Without this header, your pages can be embedded in frames on malicious sites, leading to clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options for MIME Sniffing ProtectionLow

    Why it matters: This header helps prevent browsers from interpreting files as a different MIME type than intended.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-PolicyLow

    Why it matters: Without this policy, sensitive information in URLs can be sent to third-party sites.

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

    Evidence: Referrer policy

  6. 6

    Exposed Server InformationLow

    Why it matters: The X-Powered-By header reveals the use of a framework, which could provide attackers with useful information.

    Fix: Remove or change the value of the header: X-Powered-By.

    Evidence: Software version disclosure

  7. 7

    Third-Party Scripts Without Subresource IntegrityLow

    Why it matters: Using third-party scripts without integrity checks can lead to security risks if these scripts are compromised.

    Fix: Consider implementing a CSP that allows only trusted hosts or use Subresource Integrity (SRI) where possible.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions-PolicyInfo

    Why it matters: This policy restricts which browser features are available to scripts, reducing potential attack vectors.

    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://cateyheritage.com/ → no strict-transport-security
    • https://cateyheritage.com/our-farm → no strict-transport-security
    • https://cateyheritage.com/contact → no strict-transport-security
    • https://cateyheritage.com/shop → no strict-transport-security
    • https://cateyheritage.com/flowers → no strict-transport-security
    • https://cateyheritage.com/events → no strict-transport-security
    • https://cateyheritage.com/about → no strict-transport-security
    • https://cateyheritage.com/food → no strict-transport-security
    • https://cateyheritage.com/csa-store → no strict-transport-security
    • https://cateyheritage.com/weddings → no strict-transport-security
    • https://cateyheritage.com/blog → no strict-transport-security
    • https://cateyheritage.com/?p=8 → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 16 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://cateyheritage.com/ → no content-security-policy
    • https://cateyheritage.com/our-farm → no content-security-policy
    • https://cateyheritage.com/contact → no content-security-policy
    • https://cateyheritage.com/shop → no content-security-policy
    • https://cateyheritage.com/flowers → no content-security-policy
    • https://cateyheritage.com/events → no content-security-policy
    • https://cateyheritage.com/about → no content-security-policy
    • https://cateyheritage.com/food → no content-security-policy
    • https://cateyheritage.com/csa-store → no content-security-policy
    • https://cateyheritage.com/weddings → no content-security-policy
    • https://cateyheritage.com/blog → no content-security-policy
    • https://cateyheritage.com/?p=8 → 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://cateyheritage.com/ → no x-frame-options
    • https://cateyheritage.com/our-farm → no x-frame-options
    • https://cateyheritage.com/contact → no x-frame-options
    • https://cateyheritage.com/shop → no x-frame-options
    • https://cateyheritage.com/flowers → no x-frame-options
    • https://cateyheritage.com/events → no x-frame-options
    • https://cateyheritage.com/about → no x-frame-options
    • https://cateyheritage.com/food → no x-frame-options
    • https://cateyheritage.com/csa-store → no x-frame-options
    • https://cateyheritage.com/weddings → no x-frame-options
    • https://cateyheritage.com/blog → no x-frame-options
    • https://cateyheritage.com/?p=8 → 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://cateyheritage.com/ → no x-content-type-options
    • https://cateyheritage.com/our-farm → no x-content-type-options
    • https://cateyheritage.com/contact → no x-content-type-options
    • https://cateyheritage.com/shop → no x-content-type-options
    • https://cateyheritage.com/flowers → no x-content-type-options
    • https://cateyheritage.com/events → no x-content-type-options
    • https://cateyheritage.com/about → no x-content-type-options
    • https://cateyheritage.com/food → no x-content-type-options
    • https://cateyheritage.com/csa-store → no x-content-type-options
    • https://cateyheritage.com/weddings → no x-content-type-options
    • https://cateyheritage.com/blog → no x-content-type-options
    • https://cateyheritage.com/?p=8 → 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://cateyheritage.com/ → no referrer-policy
    • https://cateyheritage.com/our-farm → no referrer-policy
    • https://cateyheritage.com/contact → no referrer-policy
    • https://cateyheritage.com/shop → no referrer-policy
    • https://cateyheritage.com/flowers → no referrer-policy
    • https://cateyheritage.com/events → no referrer-policy
    • https://cateyheritage.com/about → no referrer-policy
    • https://cateyheritage.com/food → no referrer-policy
    • https://cateyheritage.com/csa-store → no referrer-policy
    • https://cateyheritage.com/weddings → no referrer-policy
    • https://cateyheritage.com/blog → no referrer-policy
    • https://cateyheritage.com/?p=8 → 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://cateyheritage.com/ → no permissions-policy
    • https://cateyheritage.com/our-farm → no permissions-policy
    • https://cateyheritage.com/contact → no permissions-policy
    • https://cateyheritage.com/shop → no permissions-policy
    • https://cateyheritage.com/flowers → no permissions-policy
    • https://cateyheritage.com/events → no permissions-policy
    • https://cateyheritage.com/about → no permissions-policy
    • https://cateyheritage.com/food → no permissions-policy
    • https://cateyheritage.com/csa-store → no permissions-policy
    • https://cateyheritage.com/weddings → no permissions-policy
    • https://cateyheritage.com/blog → no permissions-policy
    • https://cateyheritage.com/?p=8 → no permissions-policy
  • NoteSoftware version disclosure

    Responses name the framework in an X-Powered-By header but hide the version.

    • server: nginx (93 responses)
    • x-powered-by: WP Engine (18 responses)
  • NoteThird-party scripts

    Scripts run from 4 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.)

    • ajax.googleapis.com (7 script tags)
    • lib.showit.co (33 script tags)
    • cdn.lightwidget.com (15 script tags)
    • www.paypal.com (2 script tags)
7 checks passed, 1 not applicable
  • OKHTTPS

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

    2 library versions recognised, none with known vulnerabilities.

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

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

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

No other scans of this site yet.

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

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