Scanned sites / keysearch.co / 2026-11-01-0008

keysearch.co scan from 2026-11-01 00:08:25 UTC DR 71

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

Scan 2026-11-01-0008

Scanned 2026-11-01 00:08:25 UTC, finished 2026-11-01 00:13:59 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.

67/ 100Needs work

On November 1, 2026 the Site Spider crawled 811 pages and 573 assets of keysearch.co, starting from https://keysearch.co/. It scored 67 out of 100, a result that needs work. 13 of 33 checks found something to fix, led by title tags (643), indexability (593), meta descriptions (668); 6 checks passed. Most of the points went to title tags (−8.5), indexability (−7.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
811
Assets fetched
573
Status
Completed
Checks with issues
13 of 33
CoverageComplete crawl

1,384 of 1,386 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 tags643 issues
    643 of 697 pages have title issues. 61 noindex or canonicalized pages excluded.
    −8.5 points
  • Meta descriptions668 issues
    668 of 697 pages have meta description issues. 61 noindex or canonicalized pages excluded.
    −7.1 points
  • Headings24 issues
    24 of 697 pages have heading issues. 61 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.
  • Indexability593 issues
    593 of 713 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.
    −7.8 points
  • Image alt text8 issues
    8 of 5154 image references have no alt attribute. 2087 use an empty alt (decorative), which is fine.
  • Heavy assets22 issues
    22 assets larger than 500 KB among 573 fetched assets.
    −6 points
  • Orphan pages12 issues
    12 pages have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage388 issues
    1 sitemap listing 358 URLs: 362 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 content20 issues
    20 of 697 pages have fewer than 200 words. 61 noindex or canonicalized pages excluded.
    −0.2 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format15 noted
    15 of 811 page URLs are harder to read, share or cache than they need to be.
  • Canonicals640 noted
    640 of 758 pages have a canonical worth checking.
  • Robots directives138 noted
    138 pages carry a robots directive; 620 carry none.
  • Anchor text83 noted
    83 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure622 noted
    622 of 697 pages could use the title, heading and snippet space better. 61 noindex or canonicalized pages excluded.
  • Image weight and alt length93 noted
    93 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 758 pages have HTML problems: 0 with head tags outside <head>, 0 over 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    148 of 697 indexable pages carry structured data: WebSite (139), BreadcrumbList (137), ListItem (137), ImageObject (129), Person (81). 0 pages with errors a rich result would fail on.
  • Near duplicates602 noted
    602 pages in 299 groups read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 758 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 686 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 1384 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 758 pages; 722 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,063 noted
    1063 words an English dictionary does not know, on 585 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2358 sites, median 79%, average 78%

keysearch.co scores 67%, higher than 13% of the 2358 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%: 1 site10%: 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%: 7 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 18 sites59%: 8 sites60%: 16 sites61%: 12 sites62%: 20 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 35 sites67%: 36 sites68%: 34 sites69%: 47 sites70%: 44 sites71%: 69 sites72%: 71 sites73%: 71 sites74%: 68 sites75%: 72 sites76%: 86 sites77%: 93 sites78%: 106 sites79%: 88 sites80%: 109 sites81%: 106 sites82%: 114 sites83%: 102 sites84%: 109 sites85%: 89 sites86%: 72 sites87%: 74 sites88%: 58 sites89%: 66 sites90%: 37 sites91%: 47 sites92%: 38 sites93%: 24 sites94%: 17 sites95%: 12 sites96%: 12 sites97%: 12 sites98%: 5 sites99%: 2 sites100%: 68 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 several fixes to improve its SEO health score. Focus on resolving broken links, redirects, and providing meta descriptions for better visibility.

  1. 1

    Fix Broken Links

    Why: Broken links can hurt user experience and SEO rankings.

    How: Update or remove internal links that point to broken URLs.

    Checks: broken-links

  2. 2

    Reduce Redirects

    Why: Excessive redirects can slow down site speed and impact SEO.

    How: Minimize chained redirects to direct links and implement 301 redirects properly.

    Checks: redirects

  3. 3

    Address Non-200 Responses

    Why: Ensure all URLs return a 2xx response to improve accessibility and SEO.

    How: Fix or remove broken pages and ensure assets can be accessed directly.

    Checks: status-codes

  4. 4

    Implement Meta Descriptions

    Why: Meta descriptions enhance click-through rates from search results.

    How: Add unique meta descriptions for all identified pages.

    Checks: meta-descriptions

  5. 5

    Update Title Tags

    Why: Optimizing title tags improves search engine visibility.

    How: Revise title tags to ensure they are unique and within the optimal length.

    Checks: titles

  6. 6

    Improve Indexability

    Why: Correct indexability issues to ensure search engines can crawl and index your pages.

    How: Review and update the sitemap, especially for noindex pages.

    Checks: indexability, 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

Keysearch.co has several security vulnerabilities, notably missing HTTP Strict Transport Security and Content Security Policy headers, which could expose users to attacks. Additionally, cookies lack essential security flags, and two JavaScript libraries have known vulnerabilities. Immediate remediation is recommended.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without this header, initial requests can be intercepted.

    Fix: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to all HTTP responses.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows unrestricted script and resource loading, increasing XSS risk.

    Fix: Implement a CSP header: 'Content-Security-Policy: default-src 'self';'.

    Evidence: Content Security Policy

  3. 3

    Missing Secure Cookie FlagsMedium

    Why it matters: Cookies without proper flags can be vulnerable to unauthorized access.

    Fix: Set Secure, HttpOnly, and SameSite attributes for cookies: csrftoken, PHPSESSID, and sessionid.

    Evidence: Cookie flags

  4. 4

    Vulnerable JavaScript LibrariesMedium

    Why it matters: Using outdated libraries may expose the site to known vulnerabilities.

    Fix: Upgrade jQuery to version 3.5.0 or higher to mitigate vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Exposed Server and Framework VersionsLow

    Why it matters: Revealing server versions can assist attackers in exploiting known vulnerabilities.

    Fix: Remove 'x-powered-by' header and avoid disclosing server version in responses.

    Evidence: Software version disclosure

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: Without this header, browser features may be exploited by injected scripts.

    Fix: Add 'Permissions-Policy: geolocation=(self), microphone=()' to HTTP responses.

    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/changelog → 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
  • FoundContent Security PolicyMedium

    None of the 758 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/changelog → 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
  • 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/changelog → 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
  • 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 (1384 responses)
    • x-powered-by: PHP/7.4.33 (606 responses)
    • x-powered-by: PHP/8.2.35 (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.

    • csrftoken (set by https://keysearch.co/) lacks Secure, HttpOnly
    • PHPSESSID (set by https://keysearch.co/alternatives/ahrefs) lacks Secure, HttpOnly, SameSite
    • 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 (22 script tags)
    • cdn.jsdelivr.net (6 script tags)
    • www.google.com (4 script tags)
    • www.googletagmanager.com (32 script tags)
    • unpkg.com (16 script tags)
9 checks passed
  • OKHTTPS

    All 758 crawled pages were served over HTTPS.

  • OKClickjacking protection

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

  • OKMIME sniffing protection

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

  • OKReferrer policy

    referrer-policy is set on all 758 HTML pages.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    16 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?