Scanned sites / fetchersfm.com

SEO report for fetchersfm.com

The latest Site Spider scan of fetchersfm.com, with 1 scan on record. Each scan is at its own address, for example /domain/fetchersfm-com/2026-10-01-2142.

Latest scan

Scanned 10/1/2026, 9:42:20 PM, finished 10/2/2026, 12:33:48 AM. Found on page 4 of brave web search results

Site: https://fetchersfm.com/

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

81/ 100Good

On October 1, 2026 the Site Spider crawled 124 pages and 664 assets of fetchersfm.com, starting from https://fetchersfm.com/. It scored 81 out of 100, a good result. 12 of 16 checks found something to fix, led by meta descriptions (89), heavy assets (48), title tags (33); 3 checks passed. Most of the points went to meta descriptions (−6), heavy assets (−6), title tags (−2.8). 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: Medium3 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
124
Assets fetched
664
Status
Completed
Checks with issues
12 of 16
CoverageComplete crawl

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

  • Title tags33 issues
    33 of 91 pages have title issues. 27 noindex or canonicalized pages excluded.
    −2.8 points
  • Meta descriptions89 issues
    89 of 91 pages have meta description issues. 27 noindex or canonicalized pages excluded.
    −6 points
  • Headings42 issues
    42 of 91 pages have heading issues. 27 noindex or canonicalized pages excluded.
    −2.1 points
  • Broken links1 issue
    1 internal link point at 1 broken URL.
    −0.2 points
  • Links to other sites2 issues
    2 destinations answered with an error, 13 could not be determined (timeouts, rate limits or refusals), of 39 destinations checked.
    −0.7 points
  • Redirects3 issues
    6 redirecting URLs, 1 of them chained.
    −0.1 points
  • Non-200 responses1 issue
    9 URLs did not return a 2xx response. 6 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.
  • IndexabilityOK
    0 of 91 indexable pages have indexability warnings. 27 pages noindex by design.
  • Image alt text13 issues
    13 of 876 image references have no alt attribute. 64 use an empty alt (decorative), which is fine.
    −0.1 points
  • Heavy assets48 issues
    48 assets larger than 500 KB among 664 fetched assets.
    −6 points
  • Orphan pages9 issues
    9 pages have no internal links pointing at them.
    −0.3 points
  • Sitemap coverage21 issues
    7 sitemaps listing 83 URLs: 10 crawled pages missing, 2 listed URLs broken or redirecting, 9 reachable only via the sitemap.
    −1.1 points
  • Internal link countsOK
    Internal link counts for 118 pages.
  • Thin content4 issues
    4 of 91 pages have fewer than 200 words. 27 noindex or canonicalized pages excluded.
    −0.3 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this site sits among all scanned sites

1645 sites, median 80%, average 79%

fetchersfm.com scores 81%, higher than 52% of the 1645 scanned sites. See the full ranking.

0511020%: 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%: 2 sites36%: 1 site37%: 2 sites38%: 2 sites39%: 0 sites40%: 2 sites41%: 0 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 5 sites50%: 3 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 6 sites55%: 3 sites56%: 5 sites57%: 6 sites58%: 11 sites59%: 6 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 16 sites64%: 10 sites65%: 18 sites66%: 18 sites67%: 31 sites68%: 25 sites69%: 24 sites70%: 34 sites71%: 37 sites72%: 47 sites73%: 41 sites74%: 46 sites75%: 53 sites76%: 61 sites77%: 59 sites78%: 76 sites79%: 58 sites80%: 80 sites81%: 102 sites82%: 80 sites83%: 77 sites84%: 71 sites85%: 56 sites86%: 58 sites87%: 53 sites88%: 56 sites89%: 49 sites90%: 31 sites91%: 34 sites92%: 22 sites93%: 11 sites94%: 13 sites95%: 7 sites96%: 6 sites97%: 7 sites98%: 2 sites99%: 2 sites100%: 54 sites81% 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

Several issues were identified, including broken links, redirects, and missing meta descriptions across many pages. Prioritizing these fixes will enhance your SEO performance and user experience.

  1. 1

    Fix Broken Link

    Why: A broken internal link negatively impacts user experience and SEO.

    How: Update or remove the link from https://fetchersfm.com/grooming-spa/ pointing to a 404 URL.

    Checks: broken-links

  2. 2

    Reduce Redirect Chains

    Why: Redirect chains can slow page speed and dilute link equity.

    How: Simplify or eliminate the chain for the 6 redirecting URLs.

    Checks: redirects

  3. 3

    Resolve Non-200 Responses

    Why: These can lead to poor SEO and user frustration.

    How: Fix the 9 URLs returning non-200 responses, focus on the status errors.

    Checks: status-codes

  4. 4

    Update Title Tags

    Why: Inaccurate title tags can hinder rankings and click-through rates.

    How: Revise the 33 problematic titles to meet standard lengths and provide unique content.

    Checks: titles

  5. 5

    Complete Missing Meta Descriptions

    Why: Missing meta descriptions can hurt click-through rates from search results.

    How: Craft and add descriptions to the 70 pages lacking them.

    Checks: meta-descriptions

  6. 6

    Enhance Thin Content

    Why: Thin content may be less valuable for SEO.

    How: Add more relevant content to the 4 pages with less than 200 words.

    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 fetchersfm.com lacks essential security headers, which exposes it to various risks such as cookie hijacking and clickjacking. Implementing strict transport security and content type options is critical to enhance security and protect visitor data.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted if they enter the URL without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Clickjacking ProtectionMedium

    Why it matters: Absence of X-Frame-Options allows the site to be embedded in frames, risking clickjacking.

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

    Evidence: Clickjacking protection

  3. 3

    Missing Cookie Security FlagsMedium

    Why it matters: Cookies are vulnerable to theft and cross-site request forgery without proper flags.

    Fix: Set cookies with flags: HttpOnly; Secure; SameSite=Strict

    Evidence: Cookie flags

  4. 4

    Missing MIME Sniffing ProtectionLow

    Why it matters: Lack of X-Content-Type-Options can cause browsers to incorrectly interpret file types.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Without a Referrer-Policy, sensitive page information can be leaked to external sites.

    Fix: Add the header: Referrer-Policy: no-referrer-when-downgrade

    Evidence: Referrer policy

  6. 6

    Third-party Scripts without SRILow

    Why it matters: Running scripts from other domains without Subresource Integrity poses a risk if they are compromised.

    Fix: Consider using a Content Security Policy to restrict loaded scripts.

    Evidence: Third-party scripts

  7. 7

    Missing Permissions Policy on Login PagesInfo

    Why it matters: Without Permissions-Policy, the site cannot restrict unused browser features, which increases risk.

    Fix: Add the header: Permissions-Policy: geolocation=(), microphone=(), camera=()

    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://fetchersfm.com/ → no strict-transport-security
    • https://fetchersfm.com/social-daycare-boarding/ → no strict-transport-security
    • https://fetchersfm.com/enrichment-daycare/ → no strict-transport-security
    • https://fetchersfm.com/fetchers-training/ → no strict-transport-security
    • https://fetchersfm.com/grooming-day-spa/ → no strict-transport-security
    • https://fetchersfm.com/in-ground-dog-fences/ → no strict-transport-security
    • https://fetchersfm.com/nutrition/ → no strict-transport-security
    • https://fetchersfm.com/cattery/ → no strict-transport-security
    • https://fetchersfm.com/requirements/ → no strict-transport-security
    • https://fetchersfm.com/careers/ → no strict-transport-security
    • https://fetchersfm.com/meet-our-team/ → no strict-transport-security
    • https://fetchersfm.com/blog/ → no strict-transport-security
  • FoundClickjacking protectionMedium

    2 of 118 HTML pages send 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://fetchersfm.com/ → no x-frame-options
    • https://fetchersfm.com/social-daycare-boarding/ → no x-frame-options
    • https://fetchersfm.com/enrichment-daycare/ → no x-frame-options
    • https://fetchersfm.com/fetchers-training/ → no x-frame-options
    • https://fetchersfm.com/grooming-day-spa/ → no x-frame-options
    • https://fetchersfm.com/in-ground-dog-fences/ → no x-frame-options
    • https://fetchersfm.com/nutrition/ → no x-frame-options
    • https://fetchersfm.com/cattery/ → no x-frame-options
    • https://fetchersfm.com/requirements/ → no x-frame-options
    • https://fetchersfm.com/careers/ → no x-frame-options
    • https://fetchersfm.com/meet-our-team/ → no x-frame-options
    • https://fetchersfm.com/blog/ → 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://fetchersfm.com/ → no x-content-type-options
    • https://fetchersfm.com/social-daycare-boarding/ → no x-content-type-options
    • https://fetchersfm.com/enrichment-daycare/ → no x-content-type-options
    • https://fetchersfm.com/fetchers-training/ → no x-content-type-options
    • https://fetchersfm.com/grooming-day-spa/ → no x-content-type-options
    • https://fetchersfm.com/in-ground-dog-fences/ → no x-content-type-options
    • https://fetchersfm.com/nutrition/ → no x-content-type-options
    • https://fetchersfm.com/cattery/ → no x-content-type-options
    • https://fetchersfm.com/requirements/ → no x-content-type-options
    • https://fetchersfm.com/careers/ → no x-content-type-options
    • https://fetchersfm.com/meet-our-team/ → no x-content-type-options
    • https://fetchersfm.com/blog/ → no x-content-type-options
  • FoundReferrer policyLow

    2 of 118 HTML pages send 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://fetchersfm.com/ → no referrer-policy
    • https://fetchersfm.com/social-daycare-boarding/ → no referrer-policy
    • https://fetchersfm.com/enrichment-daycare/ → no referrer-policy
    • https://fetchersfm.com/fetchers-training/ → no referrer-policy
    • https://fetchersfm.com/grooming-day-spa/ → no referrer-policy
    • https://fetchersfm.com/in-ground-dog-fences/ → no referrer-policy
    • https://fetchersfm.com/nutrition/ → no referrer-policy
    • https://fetchersfm.com/cattery/ → no referrer-policy
    • https://fetchersfm.com/requirements/ → no referrer-policy
    • https://fetchersfm.com/careers/ → no referrer-policy
    • https://fetchersfm.com/meet-our-team/ → no referrer-policy
    • https://fetchersfm.com/blog/ → no referrer-policy
  • FoundPermissions policyInfo

    116 of 118 HTML pages send 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://fetchersfm.com/wp-login.php?itsec-hb-token=sprout → no permissions-policy
    • https://fetchersfm.com/wp-login.php?itsec-hb-token=sprout&action=lostpassword → no permissions-policy
  • FoundCookie flagsMedium

    2 of 2 cookies are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • itsec-hb-login-25d82f9709a516e5d5364cc36332f51f (set by https://fetchersfm.com/wp-login.php?itsec-hb-token=sprout) lacks SameSite
    • wordpress_test_cookie (set by https://fetchersfm.com/wp-login.php?itsec-hb-token=sprout) lacks SameSite
  • 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 (80 script tags)
    • cdn.callrail.com (40 script tags)
9 checks passed
  • OKHTTPS

    All 118 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set on 2 of 118 pages.

  • 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

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

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 fetchersfm.com

No other scans of this site yet.

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

Own fetchersfm.com?

fetchersfm.com SEO report | DIY SEO Hub