Scanned sites / keysearch.co / 2026-09-22-1346
keysearch.co scan from 9/22/2026, 1:46:50 PM
Scan 2026-09-22-1346
Scanned 9/22/2026, 1:46:50 PM, finished 9/22/2026, 2:15:06 PM. Found with 42backlinks.com tool directory
Site: https://keysearch.co/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 22, 2026 the Site Spider crawled 800 pages and 834 assets of keysearch.co, starting from https://keysearch.co/. It scored 70 out of 100, a result that needs work. 12 of 14 checks found something to fix, led by indexability (619), title tags (500), meta descriptions (500); 2 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, 1 low and 1 info findings. See the security findings ↓
- Pages crawled
- 800
- Assets fetched
- 834
- Status
- Completed
- Checks with issues
- 12 of 14
- Title tags500 issues639 of 692 pages have title issues. 55 noindex or canonicalized pages excluded.
- Meta descriptions500 issues661 of 692 pages have meta description issues. 55 noindex or canonicalized pages excluded.
- Headings26 issues26 of 692 pages have heading issues. 55 noindex or canonicalized pages excluded.
- Broken links3 issues4 internal links point at 3 broken URLs.
- Redirects42 issues50 redirecting URLs, 6 of them chained.
- Non-200 responses3 issues68 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability619 issues619 of 702 indexable pages have indexability warnings. 45 pages noindex by design.
- Image alt text10 issues10 of 5113 image references have no alt attribute. 2051 use an empty alt (decorative), which is fine.
- Heavy assets22 issues22 assets larger than 500 KB among the 100 heaviest.
- Orphan pages12 issues12 pages have no internal links pointing at them.
- Sitemap coverage383 issues1 sitemap listing 358 URLs: 357 crawled pages missing, 19 listed URLs broken or redirecting, 3 reachable only via the sitemap.
- Thin content18 issues18 of 692 pages have fewer than 200 words. 55 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1176 sites, median 82%, average 80%
keysearch.co scores 70%, higher than 13% of the 1176 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 website needs improvements in broken links, redirects, non-200 responses, title tags, and meta descriptions. Prioritize fixing these to enhance SEO performance.
- 1
Fix Broken Links
Why: Eliminating broken links improves user experience and SEO.
How: Update or remove links pointing to https://www.keysearch.co/alternatives/semrush and others listed.
Checks: broken-links
- 2
Reduce Redirects
Why: Minimizing redirects can improve load times and user experience.
How: Consolidate chains by updating URLs to their final destination where possible.
Checks: redirects
- 3
Resolve Non-200 Responses
Why: Fixing these URLs enhances accessibility and improves SEO scores.
How: Check URLs returning non-200 and ensure they are live or correctly redirecting.
Checks: status-codes
- 4
Optimize Title Tags
Why: Improving title tags can elevate click-through rates and search rankings.
How: Rewrite titles for 639 pages with issues, sticking to recommended lengths.
Checks: titles
- 5
Enhance Meta Descriptions
Why: Optimized meta descriptions support better conversion rates from search results.
How: Create compelling meta descriptions for 661 affected pages.
Checks: meta-descriptions
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 keysearch.co has several critical security issues, including the absence of HTTP Strict Transport Security and Content Security Policy headers, which could expose users to attacks. Additionally, the site is using outdated JavaScript libraries and cookies lacking essential security flags. Immediate action is recommended to improve the site's security posture.
- 0 high
- 4 medium
- 1 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, visitors using HTTP are vulnerable to interception of their initial request.
Fix: Add the header: `Strict-Transport-Security: max-age=31536000; includeSubDomains` to all pages.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: A CSP prevents unauthorized sources from loading scripts, mitigating XSS attacks.
Fix: Add the header: `Content-Security-Policy: default-src 'self';` to all pages.
Evidence: Content Security Policy
- 3
Cookies Missing Security FlagsMedium
Why it matters: Without Secure, HttpOnly, and SameSite flags, cookies are more susceptible to theft and attacks.
Fix: Set cookies with: `Secure; HttpOnly; SameSite=Lax` for all relevant cookies.
Evidence: Cookie flags
- 4
Vulnerable JavaScript LibrariesMedium
Why it matters: Using outdated jQuery versions can expose the site to known vulnerabilities and attacks.
Fix: Upgrade jQuery to at least version 3.5.0 to mitigate these issues.
Evidence: Vulnerable JavaScript libraries
- 5
Server Version DisclosureLow
Why it matters: Exposing server version can help attackers identify vulnerabilities to exploit.
Fix: Disable the `X-Powered-By` header and configure Cloudflare to hide server info.
Evidence: Software version disclosure
- 6
Missing Permissions PolicyInfo
Why it matters: The lack of a Permissions-Policy can increase risk from injected scripts.
Fix: Add the header: `Permissions-Policy: none` to limit access to browser features.
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://keysearch.co/ → no strict-transport-security
- https://keysearch.co/user/login → no strict-transport-security
- https://keysearch.co/user/register → no strict-transport-security
- https://keysearch.co/alternatives/ahrefs → no strict-transport-security
- https://keysearch.co/alternatives/semrush → no strict-transport-security
- https://keysearch.co/alternatives/se-ranking → no strict-transport-security
- https://keysearch.co/tutorials/seo-crash-course → no strict-transport-security
- https://keysearch.co/tutorials → no strict-transport-security
- https://keysearch.co/affiliates → no strict-transport-security
- https://keysearch.co/contact → no strict-transport-security
- https://keysearch.co/terms → no strict-transport-security
- https://keysearch.co/privacy → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 747 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://keysearch.co/ → no content-security-policy
- https://keysearch.co/user/login → no content-security-policy
- https://keysearch.co/user/register → no content-security-policy
- https://keysearch.co/alternatives/ahrefs → no content-security-policy
- https://keysearch.co/alternatives/semrush → no content-security-policy
- https://keysearch.co/alternatives/se-ranking → no content-security-policy
- https://keysearch.co/tutorials/seo-crash-course → no content-security-policy
- https://keysearch.co/tutorials → no content-security-policy
- https://keysearch.co/affiliates → no content-security-policy
- https://keysearch.co/contact → no content-security-policy
- https://keysearch.co/terms → no content-security-policy
- https://keysearch.co/privacy → no content-security-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://keysearch.co/ → no permissions-policy
- https://keysearch.co/user/login → no permissions-policy
- https://keysearch.co/user/register → no permissions-policy
- https://keysearch.co/alternatives/ahrefs → no permissions-policy
- https://keysearch.co/alternatives/semrush → no permissions-policy
- https://keysearch.co/alternatives/se-ranking → no permissions-policy
- https://keysearch.co/tutorials/seo-crash-course → no permissions-policy
- https://keysearch.co/tutorials → no permissions-policy
- https://keysearch.co/affiliates → no permissions-policy
- https://keysearch.co/contact → no permissions-policy
- https://keysearch.co/terms → no permissions-policy
- https://keysearch.co/privacy → 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: cloudflare (1634 responses)
- x-powered-by: PHP/7.4.33 (608 responses)
- x-powered-by: PHP/8.2.31 (154 responses)
- FoundCookie flagsMedium
3 of 3 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.
- PHPSESSID (set by https://keysearch.co/) lacks Secure, HttpOnly, SameSite
- csrftoken (set by https://keysearch.co/user/login) lacks Secure, HttpOnly
- sessionid (set by https://keysearch.co/login/google-oauth2/) lacks Secure
- FoundVulnerable JavaScript librariesMedium
2 libraries with published vulnerabilities: jQuery 3.2.1, jQuery 1.9.1. Whether they are exploitable depends on how the site uses them, but each has a fixed release.
- jQuery 3.2.1 in https://www.keysearch.co/main/js/jquery-3.2.1.min.js: 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.9.1 in https://www.keysearch.co/main/plugin/bootstrap/js/bootstrap.js: 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
- NoteThird-party scripts
Scripts run from 5 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 (21 script tags)
- www.google.com (4 script tags)
- cdn.jsdelivr.net (4 script tags)
- www.googletagmanager.com (34 script tags)
- unpkg.com (17 script tags)
9 checks passed
- OKHTTPS
All 747 crawled pages were served over HTTPS.
- OKClickjacking protection
x-frame-options is set on all 747 HTML pages.
- OKMIME sniffing protection
x-content-type-options is set on all 747 HTML pages.
- OKReferrer policy
referrer-policy is set on all 747 HTML pages.
- OKMixed content
No HTTPS page loads a script, stylesheet, font or image over plain HTTP.
- OKForms over HTTPS
17 forms found, all on HTTPS pages posting to HTTPS addresses.
- 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.
Sites scoring near keysearch.co
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- hvacjs.ca71/100 · rank 972 · 11 pages
- thelemontree.ca71/100 · rank 972 · 35 pages
- www.woundscanada.ca70/100 · rank 996 · 2,416 pages
- www.helpfulhomeservices.com70/100 · rank 996 · 60 pages
- www.sahms.com70/100 · rank 996 · 25 pages
- www.carltonfarm.com70/100 · rank 996 · 590 pages
This report was produced by the DIY SEO Hub Site Spider crawling keysearch.co from its pages as published, the way a search engine does. It shows summary figures only.
Own keysearch.co?
- 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 keysearch.co. Removal needs no account and no proof of purchase.