Scanned sites / keysearch.co / 2026-09-16-0414
keysearch.co scan from 9/16/2026, 4:14:00 AM
Scan 2026-09-16-0414
Scanned 9/16/2026, 4:14:00 AM, finished 9/16/2026, 1:28:26 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 16, 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
1053 sites, median 82%, average 80%
keysearch.co scores 70%, higher than 13% of the 1053 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 findingsThe website has multiple SEO issues affecting performance. Prioritize fixing broken links and redirect chains, followed by addressing title and meta description issues for improved visibility.
- 1
Fix Broken Links
Why: Broken links hurt user experience and SEO.
How: Update or remove broken links found in the crawl.
Checks: broken-links
- 2
Streamline Redirects
Why: Reducing chained redirects improves loading speed and SEO.
How: Minimize redirect chains by connecting users directly to the final URL.
Checks: redirects
- 3
Optimize Title Tags
Why: Proper titles boost search rankings and click-through rates.
How: Revise titles to be unique, under 60 characters, and reflective of page content.
Checks: titles
- 4
Enhance Meta Descriptions
Why: Meta descriptions impact click-through rates from search results.
How: Create unique meta descriptions for each page, under 160 characters.
Checks: meta-descriptions
- 5
Address Heading Issues
Why: Improving heading structure aids in content clarity and SEO.
How: Ensure each page has one H1 tag and proper H2 usage.
Checks: headings
- 6
Fix Sitemap Coverage
Why: Correct sitemaps help search engines index your site efficiently.
How: Update the sitemap to reflect accurate URLs, removing any that redirect or are broken.
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 multiple security vulnerabilities including missing strict transport security, content security policy, and cookie flags. These may allow attackers to intercept connections, execute malicious scripts, and exploit cookie data. Address these issues promptly to improve your website's security.
- 0 high
- 4 medium
- 1 low
- 1 info
- 1
Missing HTTP Strict Transport SecurityMedium
Why it matters: Without HSTS, connections can be intercepted when users type the address without HTTPS.
Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains'.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security PolicyMedium
Why it matters: No CSP header means a browser can load resources from any source, increasing XSS risk.
Fix: Implement a CSP header like 'Content-Security-Policy: default-src 'self';'.
Evidence: Content Security Policy
- 3
Missing Secure Cookie FlagsMedium
Why it matters: Missing flags expose cookies to theft and misuse via scripts and non-secure connections.
Fix: Set flags: 'Set-Cookie: PHPSESSID=yourvalue; Secure; HttpOnly; SameSite=Lax'.
Evidence: Cookie flags
- 4
Vulnerable JavaScript LibrariesMedium
Why it matters: Outdated jQuery versions have known vulnerabilities that can be exploited.
Fix: Upgrade jQuery to at least version 3.5.0.
Evidence: Vulnerable JavaScript libraries
- 5
Server Version DisclosureLow
Why it matters: Revealing server version may help attackers identify vulnerabilities.
Fix: Remove or modify the 'X-Powered-By' header. Use 'X-Powered-By: ' to hide the version.
Evidence: Software version disclosure
- 6
Missing Permissions PolicyInfo
Why it matters: Without this policy, features such as camera and geolocation can be used by scripts.
Fix: Add a header like 'Permissions-Policy: geolocation=(self), 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://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.
This report was produced by the DIY SEO Hub Site Spider crawling keysearch.co 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.