Scanned sites / keysearch.co / 2026-09-28-1555
keysearch.co scan from 9/28/2026, 3:55:43 PM
Scan 2026-09-28-1555
Scanned 9/28/2026, 3:55:43 PM, finished 9/28/2026, 4:23:45 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 28, 2026 the Site Spider crawled 800 pages and 834 assets of keysearch.co, starting from https://keysearch.co/. It scored 66 out of 100, a result that needs work. 13 of 16 checks found something to fix, led by title tags (639), indexability (623), meta descriptions (664); 2 checks passed. Most of the points went to title tags (−8.6), indexability (−8.3), meta descriptions (−7.1). 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: Medium4 medium, 1 low and 1 info findings. See the security findings ↓
- Pages crawled
- 800
- Assets fetched
- 834
- Status
- Completed
- Checks with issues
- 13 of 16
1,634 of 1,636 discovered URLs were fetched, 2 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 49 link destinations on other sites were checked.
- Title tags639 issues639 of 692 pages have title issues. 55 noindex or canonicalized pages excluded.−8.6 points
- Meta descriptions664 issues664 of 692 pages have meta description issues. 55 noindex or canonicalized pages excluded.−7.1 points
- Headings26 issues26 of 692 pages have heading issues. 55 noindex or canonicalized pages excluded.−0.2 points
- Broken links3 issues4 internal links point at 3 broken URLs.−0.1 points
- Links to other sites3 issues3 destinations answered with an error, 11 could not be determined (timeouts, rate limits or refusals), of 49 destinations checked.−0.2 points
- Redirects42 issues50 redirecting URLs, 6 of them chained.−0.2 points
- Non-200 responses3 issues68 URLs did not return a 2xx response. 53 of them are pages, 3 with an error status; the rest are assets or redirects.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability623 issues623 of 702 indexable pages have indexability warnings. 45 pages noindex by design. 4 noindex pages are listed in the sitemap, which asks search engines both to visit and to ignore them.−8.3 points
- 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 834 fetched assets.−6 points
- Orphan pages12 issues12 pages have no internal links pointing at them.−0.1 points
- Sitemap coverage383 issues1 sitemap listing 358 URLs: 357 crawled pages missing, 19 listed URLs broken or redirecting, 3 reachable only via the sitemap.−3.1 points
- Internal link countsOKInternal link counts for 500 pages.
- Thin content18 issues18 of 692 pages have fewer than 200 words. 55 noindex or canonicalized pages excluded.−0.2 points
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1334 sites, median 80%, average 79%
keysearch.co scores 66%, higher than 10% of the 1334 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 several key fixes to improve its SEO health score. Prioritizing meta descriptions and resolving redirects will yield significant impact.
- 1
Fix Broken Links
Why: Broken links harm user experience and SEO rankings.
How: Update or remove links pointing to broken URLs.
Checks: broken-links
- 2
Resolve Redirects
Why: Chained redirects can slow down site speed and affect crawl efficiency.
How: Aim to reduce the number of redirects, especially those that are chained.
Checks: redirects
- 3
Address Title Tag Issues
Why: Improper titles can confuse search engines and users.
How: Revise titles for 639 pages for uniqueness and adherence to best practices.
Checks: titles
- 4
Enhance Meta Descriptions
Why: Missing meta descriptions result in lost click potential from search results.
How: Create unique meta descriptions for all pages lacking them.
Checks: meta-descriptions
- 5
Fix Indexability Warnings
Why: Pages without canonicals can lead to duplicate content issues.
How: Add canonical tags to 608 affected pages to clarify original content.
Checks: indexability
- 6
Update Sitemap Coverage
Why: An incomplete sitemap negatively impacts indexation by search engines.
How: Ensure all pages are properly listed and accessible in the sitemap.
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 crawlKeysearch.co has several security issues that need addressing, particularly missing headers and outdated libraries. Critical findings include the lack of HSTS and Content Security Policy headers, which could expose users to risks during initial connections. Additionally, outdated JavaScript libraries present vulnerabilities that may be exploitable based on the site's usage.
- 0 high
- 4 medium
- 1 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: The absence of HSTS allows potential interception of unencrypted requests.
Fix: Implement `Strict-Transport-Security: max-age=63072000; includeSubDomains; preload` header.
Evidence: HTTP Strict Transport Security
- 2
No Content Security Policy (CSP)Medium
Why it matters: Lacking CSP opens the site to attacks via malicious scripts and content injection.
Fix: Add `Content-Security-Policy: default-src 'self';` header to restrict resources.
Evidence: Content Security Policy
- 3
Missing Secure Cookie FlagsMedium
Why it matters: Cookies lacking Secure and HttpOnly flags are vulnerable to interception and XSS.
Fix: Set `Secure`, `HttpOnly`, and `SameSite` flags for cookies: PHPSESSID, csrftoken, sessionid.
Evidence: Cookie flags
- 4
Outdated jQuery LibrariesMedium
Why it matters: Using outdated jQuery versions can lead to vulnerabilities like XSS and prototype pollution.
Fix: Upgrade jQuery to at least version 3.5.0 to address known vulnerabilities.
Evidence: Vulnerable JavaScript libraries
- 5
Revealing Server VersionLow
Why it matters: Server and framework version exposure can aid attackers in targeting vulnerabilities.
Fix: Remove or obscure the `Server` and `X-Powered-By` headers.
Evidence: Software version disclosure
- 6
Lack of Permissions PolicyInfo
Why it matters: Absence of permissions policy could allow broad feature access to potential attackers.
Fix: Add `Permissions-Policy: geolocation=(self), microphone=()`, etc., to restrict 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.
- physicaltherapyspokane.com67/100 · rank 1164 · 32 pages
- beyondvision.ca67/100 · rank 1164 · 1,173 pages
- peacevalleydrygoods.com67/100 · rank 1164 · 12 pages
- ag-power.com66/100 · rank 1190 · 1,774 pages
- www.triplesco.com66/100 · rank 1190 · 17 pages
- www.kulamanufarm.com66/100 · rank 1190 · 16 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.