Scanned sites / keysearch.co / 2026-09-25-1415

keysearch.co scan from 9/25/2026, 2:15:28 PM

Scan 2026-09-25-1415

Scanned 9/25/2026, 2:15:28 PM, finished 9/25/2026, 3:55:14 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.

70/ 100Needs work

On September 25, 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 issues
    639 of 692 pages have title issues. 55 noindex or canonicalized pages excluded.
  • Meta descriptions500 issues
    661 of 692 pages have meta description issues. 55 noindex or canonicalized pages excluded.
  • Headings26 issues
    26 of 692 pages have heading issues. 55 noindex or canonicalized pages excluded.
  • Broken links3 issues
    4 internal links point at 3 broken URLs.
  • Redirects42 issues
    50 redirecting URLs, 6 of them chained.
  • Non-200 responses3 issues
    68 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability619 issues
    619 of 702 indexable pages have indexability warnings. 45 pages noindex by design.
  • Image alt text10 issues
    10 of 5113 image references have no alt attribute. 2051 use an empty alt (decorative), which is fine.
  • Heavy assets22 issues
    22 assets larger than 500 KB among the 100 heaviest.
  • Orphan pages12 issues
    12 pages have no internal links pointing at them.
  • Sitemap coverage383 issues
    1 sitemap listing 358 URLs: 357 crawled pages missing, 19 listed URLs broken or redirecting, 3 reachable only via the sitemap.
  • Thin content18 issues
    18 of 692 pages have fewer than 200 words. 55 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1265 sites, median 82%, average 80%

keysearch.co scores 70%, higher than 13% of the 1265 scanned sites. See the full ranking.

033660%: 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%: 1 site36%: 1 site37%: 0 sites38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 2 sites47%: 1 site48%: 1 site49%: 0 sites50%: 3 sites51%: 4 sites52%: 4 sites53%: 4 sites54%: 4 sites55%: 2 sites56%: 2 sites57%: 3 sites58%: 8 sites59%: 4 sites60%: 7 sites61%: 9 sites62%: 12 sites63%: 4 sites64%: 9 sites65%: 10 sites66%: 11 sites67%: 16 sites68%: 29 sites69%: 14 sites70%: 26 sites71%: 25 sites72%: 29 sites73%: 28 sites74%: 33 sites75%: 29 sites76%: 41 sites77%: 42 sites78%: 39 sites79%: 38 sites80%: 51 sites81%: 57 sites82%: 56 sites83%: 53 sites84%: 60 sites85%: 53 sites86%: 51 sites87%: 57 sites88%: 61 sites89%: 44 sites90%: 66 sites91%: 40 sites92%: 25 sites93%: 21 sites94%: 18 sites95%: 10 sites96%: 11 sites97%: 4 sites98%: 3 sites99%: 2 sites100%: 23 sites70% 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

Your website has several issues affecting performance and SEO. Prioritizing fixes will improve usability and search engine ranking significantly.

  1. 1

    Fix Broken Links

    Why: Broken links harm user experience and SEO rankings.

    How: Update or remove links to the broken URLs found.

    Checks: broken-links

  2. 2

    Consolidate Redirects

    Why: Chained and excessive redirects can slow down page load times and dilute link equity.

    How: Redirect chains should be reduced to a single redirect from the original URL.

    Checks: redirects

  3. 3

    Address Non-200 Responses

    Why: These issues prevent proper indexing and user access.

    How: Fix or remove URLs that return non-200 responses.

    Checks: status-codes

  4. 4

    Improve Title Tags and Meta Descriptions

    Why: Improving these will enhance click-through rates on search engine results pages.

    How: Craft unique and concise titles and descriptions for affected pages.

    Checks: titles, meta-descriptions

  5. 5

    Resolve Heading Issues

    Why: Proper heading structure improves accessibility and SEO.

    How: Ensure each page has one H1 tag, and improve other heading structures as needed.

    Checks: headings

  6. 6

    Enhance Sitemap Coverage

    Why: A comprehensive sitemap improves crawl efficiency and indexing.

    How: Update the sitemap to reflect accurate URLs and remove redirects.

    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 crawl

The site keysearch.co has several security gaps, including lack of HTTP Strict Transport Security and Content Security Policy headers. Cookies are missing protective flags, and there are vulnerable JavaScript libraries in use. Addressing these issues will enhance the site's security against potential attacks.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, attackers can intercept an initial request if the user types the address without HTTPS.

    Fix: Implement HSTS by adding the header: Strict-Transport-Security: max-age=31536000; includeSubDomains.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Without a CSP, there are no restrictions on where scripts and styles can load from, increasing XSS risk.

    Fix: Add a basic CSP header: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    Cookies Missing Protective FlagsMedium

    Why it matters: Cookies without proper flags can be compromised, allowing unauthorized access or attacks.

    Fix: Set the following cookie flags: PHPSESSID; Secure, HttpOnly, SameSite=None; csrftoken; Secure, HttpOnly; sessionid; Secure.

    Evidence: Cookie flags

  4. 4

    Vulnerable JavaScript LibrariesMedium

    Why it matters: The site uses outdated jQuery versions with known vulnerabilities that may be exploited.

    Fix: Upgrade jQuery to version 3.5.0 or later to mitigate these vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Server Version DisclosureLow

    Why it matters: Revealing server or framework versions may assist attackers in targeting known vulnerabilities.

    Fix: Disable the X-Powered-By header and manage server details to minimize disclosure.

    Evidence: Software version disclosure

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: Without a Permissions-Policy header, unnecessary browser features may be enabled, increasing risk.

    Fix: Implement a permissions policy 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://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.

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?

keysearch.co scan 2026-09-25-1415 | DIY SEO Hub