Scanned sites / keysearch.co / 2026-10-19-2334

keysearch.co scan from 2026-10-19 23:34:26 UTC DR 71

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-10-19-2334

Scanned 2026-10-19 23:34:26 UTC, finished 2026-10-19 23:42:30 UTC. 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 19, 2026 the Site Spider crawled 801 pages and 565 assets of keysearch.co, starting from https://keysearch.co/. It scored 66 out of 100, a result that needs work. 13 of 33 checks found something to fix, led by title tags (639), indexability (595), meta descriptions (664); 6 checks passed. Most of the points went to title tags (−8.5), indexability (−8), meta descriptions (−7.1). 14 checks found something the score does not count, listed as noted. 4 checks were not run because the crawl fetched nothing for them. 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
13 of 33
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 were 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 sites3 issues
    3 destinations answered with an error, 11 could not be determined (timeouts, rate limits or refusals), of 35 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.
  • 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.
  • HTML and head validation2 noted
    2 of 748 pages have HTML problems: 0 with head tags outside <head>, 0 over 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    138 of 693 indexable pages carry structured data: BreadcrumbList (137), ListItem (137), WebSite (137), ImageObject (129), Person (81). 0 pages with errors a rich result would fail on.
  • Near duplicates600 noted
    600 pages in 298 groups read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 748 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positions23 noted
    23 of 682 linked pages are linked only from the template, never from another page's content.
  • Pagination1 noted
    18 pages in pagination sequences; 1 with problems.
  • Headers and cookies3 noted
    3 cookies set by the site, 3 missing a protective flag; 15 response headers recorded across 1366 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 748 pages; 713 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling1,062 noted
    1062 words an English dictionary does not know, on 583 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2291 sites, median 79%, average 78%

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

0571140%: 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%: 1 site15%: 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%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 16 sites59%: 7 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 21 sites65%: 32 sites66%: 36 sites67%: 34 sites68%: 35 sites69%: 46 sites70%: 41 sites71%: 68 sites72%: 70 sites73%: 67 sites74%: 70 sites75%: 70 sites76%: 88 sites77%: 92 sites78%: 105 sites79%: 87 sites80%: 106 sites81%: 107 sites82%: 114 sites83%: 95 sites84%: 107 sites85%: 83 sites86%: 68 sites87%: 73 sites88%: 60 sites89%: 61 sites90%: 33 sites91%: 44 sites92%: 35 sites93%: 21 sites94%: 14 sites95%: 10 sites96%: 9 sites97%: 10 sites98%: 4 sites99%: 0 sites100%: 70 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

KeySearch has critical issues with broken links, redirects, and meta descriptions. The site requires attention to improve SEO and user experience. Below are prioritized fixes for optimal impact.

  1. 1

    Fix Broken Links

    Why: 4 internal links are broken, which can hurt UX and SEO rankings.

    How: Update or remove links pointing to broken URLs identified in the crawl.

    Checks: broken-links

  2. 2

    Resolve Redirects

    Why: 50 URLs are redirecting, with 6 chained, causing potential SEO issues.

    How: Review and consolidate redirects to ensure they point directly to the final destination.

    Checks: redirects

  3. 3

    Address Non-200 Responses

    Why: 68 URLs did not return a 2xx response, impacting usability and indexing.

    How: Identify source of errors and fix or remove faulty pages.

    Checks: status-codes

  4. 4

    Implement Meta Descriptions

    Why: 664 pages have meta description issues, leading to poor search visibility.

    How: Write unique meta descriptions for all affected pages as indicated in task.

    Checks: meta-descriptions

  5. 5

    Fix Sitemap Coverage

    Why: 358 URLs are missing from the sitemap, which can affect crawlability.

    How: Ensure all relevant pages are included in the sitemap and fix broken or redirecting entries.

    Checks: sitemap-coverage

  6. 6

    Add Canonical Tags

    Why: 580 pages lack canonical tags, which can lead to indexing issues.

    How: Review and implement canonical tags on the affected pages as a quick fix to improve indexing.

    Evidence: 580 pages flagged: No canonical.

    580 pages affected

    Depends on: Confirm the pages really share a cause before changing them together.

    Checks: indexability

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 security issues that need attention, primarily lacking critical headers like HSTS and Content Security Policy, which can expose it to attacks. Additionally, cookie protection lacks essential flags. Upgrading vulnerable libraries is crucial to enhance overall security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users may be vulnerable to man-in-the-middle attacks when accessing the site 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: The absence of a CSP allows loading resources from any source, making the site vulnerable to cross-site scripting (XSS) attacks.

    Fix: Implement CSP by adding the header: 'Content-Security-Policy: default-src 'self'; script-src 'self' https://trustedsource.com;'. Please adjust the sources based on your needs.

    Evidence: Content Security Policy

  3. 3

    Cookies Lack Protective FlagsMedium

    Why it matters: Missing flags on cookies expose them to theft and misuse through cross-site scripting.

    Fix: Set the following attributes: 'PHPSESSID: HttpOnly; Secure; SameSite=Lax', 'csrftoken: HttpOnly; Secure', 'sessionid: Secure'.

    Evidence: Cookie flags

  4. 4

    Outdated JavaScript LibrariesMedium

    Why it matters: Using vulnerable library versions may expose the site to security risks that can be exploited.

    Fix: Upgrade jQuery to at least version 3.5.0 to fix the listed vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Software Version DisclosureLow

    Why it matters: Revealing server and framework versions aids attackers in identifying vulnerabilities.

    Fix: Remove or obscure the 'x-powered-by' header and configure your server to minimize information exposure.

    Evidence: Software version disclosure

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: Not setting a Permissions-Policy can leave unused features active, increasing the risk if a malicious script runs.

    Fix: Implement Permissions-Policy by adding the header: 'Permissions-Policy: geolocation=(self), 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.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

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?