Scanned sites / camosy.com
SEO report for camosy.com
The latest Site Spider scan of camosy.com, with 1 scan on record. Each scan is at its own address, for example /domain/camosy-com/2026-09-20-1000.
Latest scan
Scanned 9/20/2026, 10:00:01 AM, finished 9/20/2026, 11:21:36 AM. Found on page 1 of chatgpt for browser (api usage) results
Site: https://camosy.com/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 20, 2026 the Site Spider crawled 4999 pages and 1726 assets of camosy.com, starting from https://camosy.com/. It scored 82 out of 100, a good result. 9 of 14 checks found something to fix, led by orphan pages (1634), indexability (1244), redirects (500); 5 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, 2 low and 1 info findings. See the security findings ↓
- Pages crawled
- 4999
- Assets fetched
- 1726
- Status
- Completed
- Checks with issues
- 9 of 14
- Title tags62 issues62 of 168 pages have title issues. 1709 noindex or canonicalized pages excluded.
- Meta descriptions64 issues64 of 168 pages have meta description issues. 1709 noindex or canonicalized pages excluded.
- Headings8 issues8 of 168 pages have heading issues. 1709 noindex or canonicalized pages excluded.
- Broken linksOK0 internal links point at 0 broken URLs.
- Redirects500 issues3123 redirecting URLs, 0 of them chained.
- Non-200 responsesOK3123 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability1244 issues1244 of 1401 indexable pages have indexability warnings. 476 pages noindex by design.
- Image alt textOK0 of 11316 image references have no alt attribute. 3358 use an empty alt (decorative), which is fine.
- Heavy assets60 issues60 assets larger than 500 KB among the 100 heaviest.
- Orphan pages1634 issues1634 pages have no internal links pointing at them.
- Sitemap coverage152 issues1 sitemap listing 0 URLs: 152 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
- Thin content39 issues39 of 168 pages have fewer than 200 words. 1709 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this site sits among all scanned sites
1121 sites, median 82%, average 80%
camosy.com scores 82%, higher than 48% of the 1121 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsYour site has multiple issues primarily around redirects, non-200 responses, and content improvements. Prioritize addressing redirects and meta tags for better SEO performance and user experience.
- 1
Fix Redirects
Why: 3123 URLs redirecting can harm user experience and SEO.
How: Identify and remove unnecessary redirects to streamline the URL structure.
Checks: redirects, status-codes
- 2
Improve Title Tags
Why: 62 titles are too long, affecting SEO and click-through rates.
How: Shorten title tags to 60 characters or fewer for better SEO.
Checks: titles
- 3
Enhance Meta Descriptions
Why: 64 meta descriptions are too long or missing, which can lower click-through rates.
How: Revise or add meta descriptions to stay within 160 characters.
Checks: meta-descriptions
- 4
Resolve Non-200 Responses
Why: Addressing non-200 responses will enhance site reliability.
How: Fix URLs to return a 200 status code instead of redirects.
Checks: status-codes
- 5
Add Headings Structure
Why: 8 pages have multiple H1s, causing confusion for search engines.
How: Ensure each page has a single H1 tag with relevant content.
Checks: headings
- 6
Update Sitemap
Why: Sitemap is currently not listing important pages, affecting indexation.
How: Update the sitemap to include all crawled pages.
Checks: sitemap-coverage
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 crawlThe site has several security gaps, including missing security headers and outdated libraries. Key issues include a lack of HTTP Strict Transport Security and vulnerable JavaScript libraries that may expose users to attacks. Immediate actions are recommended to enhance security.
- 0 high
- 4 medium
- 2 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, visitors are susceptible to interception when accessing the site via HTTP.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains.
Evidence: HTTP Strict Transport Security
- 2
Missing X-Frame-Options HeaderMedium
Why it matters: Lack of this header makes the site vulnerable to clickjacking attacks.
Fix: Add the header: X-Frame-Options: DENY.
Evidence: Clickjacking protection
- 3
Vulnerable JavaScript Libraries DetectedMedium
Why it matters: Outdated jQuery versions have known vulnerabilities that could be exploited.
Fix: Update jQuery to at least version 3.5.0.
Evidence: Vulnerable JavaScript libraries
- 4
Leaked Google API KeyMedium
Why it matters: An exposed API key may allow unauthorized access to resources.
Fix: Restrict the key in Google Cloud console based on HTTP referrer.
Evidence: Keys and secrets in page code
- 5
Missing X-Content-Type-Options HeaderLow
Why it matters: Not sending this header can lead to MIME-type sniffing vulnerabilities.
Fix: Add the header: X-Content-Type-Options: nosniff.
Evidence: MIME sniffing protection
- 6
Missing Referrer-Policy HeaderLow
Why it matters: Not specifying this policy may result in exposing sensitive page information to third parties.
Fix: Add the header: Referrer-Policy: no-referrer.
Evidence: Referrer policy
- 7
Missing Permissions-Policy HeaderInfo
Why it matters: Absence of this reduces control over browser features that could be exploited.
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://camosy.com/ → no strict-transport-security
- https://camosy.com/about → no strict-transport-security
- https://camosy.com/careers → no strict-transport-security
- https://camosy.com/blog → no strict-transport-security
- https://camosy.com/services → no strict-transport-security
- https://camosy.com/projects → no strict-transport-security
- https://camosy.com/projects?_project_status=completed → no strict-transport-security
- https://camosy.com/projects?_project_status=underconstruction → no strict-transport-security
- https://camosy.com/gallery → no strict-transport-security
- https://camosy.com/events → no strict-transport-security
- https://camosy.com/contact → no strict-transport-security
- https://camosy.com/blog/sample-post-1 → no strict-transport-security
- 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://camosy.com/ → no x-frame-options
- https://camosy.com/about → no x-frame-options
- https://camosy.com/careers → no x-frame-options
- https://camosy.com/blog → no x-frame-options
- https://camosy.com/services → no x-frame-options
- https://camosy.com/projects → no x-frame-options
- https://camosy.com/projects?_project_status=completed → no x-frame-options
- https://camosy.com/projects?_project_status=underconstruction → no x-frame-options
- https://camosy.com/gallery → no x-frame-options
- https://camosy.com/events → no x-frame-options
- https://camosy.com/contact → no x-frame-options
- https://camosy.com/blog/sample-post-1 → 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://camosy.com/ → no x-content-type-options
- https://camosy.com/about → no x-content-type-options
- https://camosy.com/careers → no x-content-type-options
- https://camosy.com/blog → no x-content-type-options
- https://camosy.com/services → no x-content-type-options
- https://camosy.com/projects → no x-content-type-options
- https://camosy.com/projects?_project_status=completed → no x-content-type-options
- https://camosy.com/projects?_project_status=underconstruction → no x-content-type-options
- https://camosy.com/gallery → no x-content-type-options
- https://camosy.com/events → no x-content-type-options
- https://camosy.com/contact → no x-content-type-options
- https://camosy.com/blog/sample-post-1 → 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://camosy.com/ → no referrer-policy
- https://camosy.com/about → no referrer-policy
- https://camosy.com/careers → no referrer-policy
- https://camosy.com/blog → no referrer-policy
- https://camosy.com/services → no referrer-policy
- https://camosy.com/projects → no referrer-policy
- https://camosy.com/projects?_project_status=completed → no referrer-policy
- https://camosy.com/projects?_project_status=underconstruction → no referrer-policy
- https://camosy.com/gallery → no referrer-policy
- https://camosy.com/events → no referrer-policy
- https://camosy.com/contact → no referrer-policy
- https://camosy.com/blog/sample-post-1 → 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://camosy.com/ → no permissions-policy
- https://camosy.com/about → no permissions-policy
- https://camosy.com/careers → no permissions-policy
- https://camosy.com/blog → no permissions-policy
- https://camosy.com/services → no permissions-policy
- https://camosy.com/projects → no permissions-policy
- https://camosy.com/projects?_project_status=completed → no permissions-policy
- https://camosy.com/projects?_project_status=underconstruction → no permissions-policy
- https://camosy.com/gallery → no permissions-policy
- https://camosy.com/events → no permissions-policy
- https://camosy.com/contact → no permissions-policy
- https://camosy.com/blog/sample-post-1 → no permissions-policy
- FoundVulnerable JavaScript librariesMedium
2 libraries with published vulnerabilities: jQuery 1.9.1, jQuery 2.10.5. Whether they are exploitable depends on how the site uses them, but each has a fixed release.
- jQuery 1.9.1 in https://camosy.com/wp-content/themes/ninezeroseven/assets/js/scripts.js?ver=5.3…: 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 2.10.5 in https://camosy.com/wp-content/plugins/gravityforms/js/placeholders.jquery.min.j…: 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
- FoundKeys and secrets in page codeMedium
1 credential-like value found in code served to every visitor: Google API key.
- Google API key AIzaSy…OU (39 chars) in https://camosy.com/event/national-food-safety-education-month: 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 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.)
- html5shim.googlecode.com (40 script tags)
- connect.facebook.net (3 script tags)
- 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/
6 checks passed, 1 not applicable
- OKHTTPS
All 1877 crawled pages were served over HTTPS.
- OKContent Security Policy
A Content-Security-Policy is set.
- 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
10 forms found, all on HTTPS pages posting to HTTPS addresses.
- 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 camosy.com
No other scans of this site yet.
Sites scoring near camosy.com
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- www.brightondentalstudio.com82/100 · rank 527 · 110 pages
- www.germanautomotive.ca82/100 · rank 527 · 180 pages
- www.tsoralhealth.com82/100 · rank 527 · 44 pages
- www.tendingtoes.com82/100 · rank 527 · 23 pages
- seelyhomes.com82/100 · rank 527 · 116 pages
- www.lc-contracting.com82/100 · rank 527 · 228 pages
This report was produced by the DIY SEO Hub Site Spider crawling camosy.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.