Scanned sites / keysearch.co / 2026-10-01-1631

keysearch.co scan from 10/1/2026, 4:31:58 PM

Scan 2026-10-01-1631

Scanned 10/1/2026, 4:31:58 PM, finished 10/1/2026, 9:42:33 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.

66/ 100Needs work

On October 1, 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
CoverageComplete crawl

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 issues
    639 of 692 pages have title issues. 55 noindex or canonicalized pages excluded.
    −8.6 points
  • Meta descriptions664 issues
    664 of 692 pages have meta description issues. 55 noindex or canonicalized pages excluded.
    −7.1 points
  • Headings26 issues
    26 of 692 pages have heading issues. 55 noindex or canonicalized pages excluded.
    −0.2 points
  • Broken links3 issues
    4 internal links point at 3 broken URLs.
    −0.1 points
  • Links to other sites3 issues
    3 destinations answered with an error, 11 could not be determined (timeouts, rate limits or refusals), of 49 destinations checked.
    −0.2 points
  • Redirects42 issues
    50 redirecting URLs, 6 of them chained.
    −0.2 points
  • Non-200 responses3 issues
    68 URLs did not return a 2xx response. 53 of them are pages, 3 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability623 issues
    623 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 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 834 fetched assets.
    −6 points
  • Orphan pages12 issues
    12 pages have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage383 issues
    1 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 countsOK
    Internal link counts for 500 pages.
  • Thin content18 issues
    18 of 692 pages have fewer than 200 words. 55 noindex or canonicalized pages excluded.
    −0.2 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1629 sites, median 80%, average 79%

keysearch.co scores 66%, higher than 10% of the 1629 scanned sites. See the full ranking.

0511010%: 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%: 2 sites36%: 1 site37%: 2 sites38%: 2 sites39%: 0 sites40%: 2 sites41%: 0 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 5 sites50%: 3 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 6 sites55%: 3 sites56%: 5 sites57%: 5 sites58%: 10 sites59%: 5 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 15 sites64%: 10 sites65%: 18 sites66%: 18 sites67%: 31 sites68%: 25 sites69%: 22 sites70%: 35 sites71%: 37 sites72%: 47 sites73%: 39 sites74%: 46 sites75%: 53 sites76%: 60 sites77%: 59 sites78%: 75 sites79%: 57 sites80%: 80 sites81%: 101 sites82%: 80 sites83%: 78 sites84%: 71 sites85%: 55 sites86%: 57 sites87%: 52 sites88%: 56 sites89%: 47 sites90%: 31 sites91%: 34 sites92%: 22 sites93%: 11 sites94%: 13 sites95%: 7 sites96%: 6 sites97%: 7 sites98%: 2 sites99%: 2 sites100%: 53 sites66% 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

Several technical issues need addressing to improve SEO health, especially focusing on broken links, redirects, and optimizing titles and meta descriptions.

  1. 1

    Fix Broken Links

    Why: Broken links harm user experience and can lead to lower SEO rankings.

    How: Update or remove links pointing to broken URLs across the site.

    Checks: broken-links

  2. 2

    Eliminate Redirects

    Why: Redirects can slow down your site and affect crawl efficiency.

    How: Remove unnecessary redirects and consolidate chains to direct links.

    Checks: redirects

  3. 3

    Enhance Title Tags

    Why: Optimized title tags improve click-through rates and search visibility.

    How: Create unique, relevant titles for at least 639 pages with issues.

    Checks: titles

  4. 4

    Improve Meta Descriptions

    Why: Meta descriptions attract clicks from search results and improve CTR.

    How: Write compelling meta descriptions for the 622 pages missing them.

    Checks: meta-descriptions

  5. 5

    Resolve Indexability Issues

    Why: Indexability warnings prevent search engines from properly crawling pages.

    How: Address the canonical issues on 608 pages to ensure clarity for crawlers.

    Checks: indexability

  6. 6

    Update Sitemap Coverage

    Why: An accurate sitemap helps search engines discover your content more effectively.

    How: Adjust the sitemap to reflect all 357 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 website keysearch.co has multiple security issues, including missing important HTTP headers like HTTP Strict Transport Security and Content Security Policy. Additionally, cookies lack protective flags, and outdated JavaScript libraries with known vulnerabilities are in use. It's crucial to address these issues to enhance your website's security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted on their first HTTP request.

    Fix: Set `Strict-Transport-Security: max-age=31536000; includeSubDomains; preload` in response headers.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows unrestricted sources for scripts, styles, and frames, increasing XSS risks.

    Fix: Add `Content-Security-Policy: default-src 'self';` in response headers.

    Evidence: Content Security Policy

  3. 3

    Cookies Missing Protective FlagsMedium

    Why it matters: Cookies being sent without Secure, HttpOnly, or SameSite flags can be stolen or misused.

    Fix: Set the flags: `Secure; HttpOnly; SameSite=Lax` for all cookies.

    Evidence: Cookie flags

  4. 4

    Outdated and Vulnerable JavaScript LibrariesMedium

    Why it matters: Using old versions of jQuery exposes the site to known vulnerabilities.

    Fix: Update jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Server Version DisclosureLow

    Why it matters: Revealing server software and version can aid attackers in exploiting vulnerabilities.

    Fix: Remove or obscure `Server` and `X-Powered-By` headers from responses.

    Evidence: Software version disclosure

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: Without this policy, the site may be vulnerable to rogue scripts accessing sensitive features.

    Fix: Add `Permissions-Policy: geolocation=(), microphone=(), camera=()` in response headers.

    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-10-01-1631 | DIY SEO Hub