Scanned sites / keysearch.co / 2026-10-04-2127

keysearch.co scan from 10/4/2026, 9:27:34 PM

Scan 2026-10-04-2127

Scanned 10/4/2026, 9:27:34 PM, finished 10/4/2026, 9:51:03 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.

67/ 100Needs work

On October 4, 2026 the Site Spider crawled 801 pages and 565 assets of keysearch.co, starting from https://keysearch.co/. It scored 67 out of 100, a result that needs work. 12 of 22 checks found something to fix, led by title tags (639), indexability (595), meta descriptions (664); 2 checks passed. Most of the points went to title tags (−8.5), indexability (−8), meta descriptions (−7.1). 8 checks found something the score does not count, listed as noted. 1 check was not run because the crawl fetched nothing for it. 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
801
Assets fetched
565
Status
Completed
Checks with issues
12 of 22
CoverageComplete crawl

1,366 of 1,368 discovered URLs were fetched, 2 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 35 link destinations on other sites have not been checked.

  • Title tags639 issues
    639 of 693 pages have title issues. 55 noindex or canonicalized pages excluded.
    −8.5 points
  • Meta descriptions664 issues
    664 of 693 pages have meta description issues. 55 noindex or canonicalized pages excluded.
    −7.1 points
  • Headings26 issues
    26 of 693 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 sitesNot checked
    Not checked: the crawl fetched nothing this check can look at.
  • 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.
  • Indexability595 issues
    595 of 703 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 points
  • Image alt text10 issues
    10 of 5116 image references have no alt attribute. 2051 use an empty alt (decorative), which is fine.
  • Heavy assets20 issues
    20 assets larger than 500 KB among 565 fetched assets.
    −6 points
  • Orphan pages12 issues
    12 pages have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage384 issues
    1 sitemap listing 358 URLs: 358 crawled pages missing, 19 listed URLs broken or redirecting, 3 reachable only via the sitemap.
    −3.1 points
  • Internal link counts45 noted
    Internal link counts for 500 pages; 45 worth a look.
  • Thin content18 issues
    18 of 693 pages have fewer than 200 words. 55 noindex or canonicalized pages excluded.
    −0.2 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format9 noted
    9 of 801 page URLs are harder to read, share or cache than they need to be.
  • Canonicals636 noted
    636 of 748 pages have a canonical worth checking.
  • Robots directives138 noted
    138 pages carry a robots directive; 610 carry none.
  • Anchor text83 noted
    83 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure618 noted
    618 of 693 pages could use the title, heading and snippet space better. 55 noindex or canonicalized pages excluded.
  • Image weight and alt length89 noted
    89 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies3 noted
    3 URLs answered in a way worth looking at.

Where this scan sits among all scanned sites

2071 sites, median 79%, average 78%

keysearch.co scores 67%, higher than 12% of the 2071 scanned sites. See the full ranking.

0521030%: 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%: 1 site28%: 0 sites29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 1 site36%: 2 sites37%: 2 sites38%: 3 sites39%: 2 sites40%: 2 sites41%: 1 site42%: 0 sites43%: 0 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 4 sites48%: 4 sites49%: 3 sites50%: 5 sites51%: 6 sites52%: 9 sites53%: 6 sites54%: 7 sites55%: 7 sites56%: 5 sites57%: 11 sites58%: 15 sites59%: 7 sites60%: 12 sites61%: 9 sites62%: 18 sites63%: 20 sites64%: 17 sites65%: 36 sites66%: 24 sites67%: 39 sites68%: 34 sites69%: 31 sites70%: 36 sites71%: 62 sites72%: 67 sites73%: 58 sites74%: 58 sites75%: 76 sites76%: 78 sites77%: 86 sites78%: 95 sites79%: 83 sites80%: 97 sites81%: 103 sites82%: 100 sites83%: 93 sites84%: 90 sites85%: 70 sites86%: 69 sites87%: 62 sites88%: 68 sites89%: 47 sites90%: 37 sites91%: 43 sites92%: 24 sites93%: 19 sites94%: 14 sites95%: 7 sites96%: 5 sites97%: 9 sites98%: 2 sites99%: 1 site100%: 57 sites67% 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 requires fixes, particularly related to broken links and meta descriptions. Key improvements can significantly enhance your SEO and user experience.

  1. 1

    Fix Broken Links

    Why: Resolve 4 internal links pointing to broken URLs, enhancing user experience.

    How: Identify and redirect or update the broken links found on the specified URLs.

    Checks: broken-links

  2. 2

    Address Redirects

    Why: Minimize 50 redirects including 6 chained ones to improve site speed and SEO.

    How: Consolidate URLs to reduce hops and set up 301 redirects where necessary.

    Checks: redirects

  3. 3

    Enhance Meta Descriptions

    Why: Write meta descriptions for 622 pages to boost click-through rates and SEO.

    How: Create unique, keyword-rich meta descriptions using the suggested task.

    Checks: meta-descriptions

  4. 4

    Fix Indexability Issues

    Why: 580 pages need canonical tags to avoid content duplication and improve rankings.

    How: Review each flagged page for appropriate canonicalization to consolidate link equity.

    Checks: indexability

  5. 5

    Improve Sitemap Coverage

    Why: 358 URLs are missing from the sitemap which can hinder indexing.

    How: Update the sitemap to include all relevant pages and ensure it adheres to structure standards.

    Checks: sitemap-coverage

  6. 6

    Resolve Title Tag Issues

    Why: 639 pages have title issues, which can affect search visibility.

    How: Review and create unique title tags for affected pages, ensuring proper length and relevance.

    Checks: titles

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 several critical security issues that need to be addressed. No HTTP Strict Transport Security or Content Security Policy is in place, raising the risk of data interception and malicious script execution. Additionally, cookies are not appropriately protected, and outdated JavaScript libraries with known vulnerabilities are being used. It's vital to take corrective actions promptly.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, an attacker can intercept traffic from users who enter the site without HTTPS.

    Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of a CSP allows potentially harmful scripts from any source to execute, increasing XSS risks.

    Fix: Add the header: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    Insecure Cookie FlagsMedium

    Why it matters: Cookies can be accessed by scripts or transmitted over insecure connections without protective flags.

    Fix: Set flags: HttpOnly, Secure, SameSite=None on cookies PHPSESSID, csrftoken, and sessionid.

    Evidence: Cookie flags

  4. 4

    Outdated JavaScript Libraries with VulnerabilitiesMedium

    Why it matters: Using vulnerable libraries exposes the site to potential attacks such as XSS and prototype pollution.

    Fix: Upgrade jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Exposing Server Version InformationLow

    Why it matters: Disclosing server version can help attackers exploit known vulnerabilities.

    Fix: Remove or modify headers: Change X-Powered-By to a less informative value or remove it.

    Evidence: Software version disclosure

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: Without a permissions policy, certain features remain available for misuse by malicious scripts.

    Fix: Add the 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 748 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 (1366 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 748 crawled pages were served over HTTPS.

  • OKClickjacking protection

    x-frame-options is set on all 748 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 748 HTML pages.

  • OKReferrer policy

    referrer-policy is set on all 748 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-04-2127 | DIY SEO Hub