Scanned sites / www.greasemonkey.com / 2026-11-02-0611

www.greasemonkey.com scan from 2026-11-02 06:11:51 UTC DR 47

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

Scan 2026-11-02-0611

Scanned 2026-11-02 06:11:51 UTC, finished 2026-11-02 11:00:13 UTC. Found on page 4 of brave web search results

Site: https://www.greasemonkey.com/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

85/ 100Good

On November 2, 2026 the Site Spider crawled 1523 pages and 1000 assets of www.greasemonkey.com, starting from https://www.greasemonkey.com/. It scored 85 out of 100, a good result. 12 of 33 checks found something to fix, led by sitemap coverage (1,476), title tags (542), heavy assets (5); 8 checks passed. Most of the points went to sitemap coverage (−5.9), title tags (−3.6), heavy assets (−3). 13 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: Medium3 medium and 2 low findings. See the security findings ↓

Pages crawled
1523
Assets fetched
1000
Status
Completed
Checks with issues
12 of 33
CoverageJob finished, partial coverage

2,523 of 2,523 discovered URLs were fetched, 43 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 1816 left unchecked.

  • Title tags542 issues
    542 of 1476 pages have title issues. 32 noindex or canonicalized pages excluded.
    −3.6 points
  • Meta descriptions412 issues
    412 of 1476 pages have meta description issues. 32 noindex or canonicalized pages excluded.
    −2.2 points
  • Headings5 issues
    5 of 1476 pages have heading issues. 32 noindex or canonicalized pages excluded.
  • Broken links3 issues
    4 internal links point at 3 broken URLs.
  • Links to other sites2 issues
    2 destinations answered with an error, 14 could not be determined (timeouts, rate limits or refusals), 1816 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.1 points
  • Redirects12 issues
    13 redirecting URLs, 3 of them chained.
  • Non-200 responses3 issues
    16 URLs did not return a 2xx response. 15 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.
  • Indexability32 issues
    32 of 1508 indexable pages have indexability warnings.
    −0.2 points
  • Image alt text6 issues
    6 of 25033 image references have no alt attribute. 29 use an empty alt (decorative), which is fine.
  • Heavy assets5 issues
    5 assets larger than 500 KB among 1000 fetched assets.
    −3 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage1,476 issues
    1 sitemap listing 0 URLs: 1476 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −5.9 points
  • Internal link counts341 noted
    Internal link counts for 500 pages; 341 worth a look.
  • Thin contentOK
    0 of 1476 pages have fewer than 200 words. 32 noindex or canonicalized pages excluded.
  • Duplicate content3 issues
    1 group of pages with identical HTML.
  • URL format123 noted
    123 of 1523 page URLs are harder to read, share or cache than they need to be.
  • Canonicals32 noted
    32 of 1508 pages have a canonical worth checking.
  • Robots directives1,508 noted
    1508 pages carry a robots directive; 0 carry none.
  • Anchor text12 noted
    12 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure547 noted
    547 of 1476 pages could use the title, heading and snippet space better. 32 noindex or canonicalized pages excluded.
  • Image weight and alt length718 noted
    108 images over 100 KB; 610 with alt text over 100 characters.
  • Response anomalies4 noted
    4 URLs answered in a way worth looking at.
  • HTML and head validationOK
    All 1508 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured data545 noted
    1508 of 1476 indexable pages carry structured data: BreadcrumbList (1508), ListItem (1508), WebSite (1508), Organization (1508), WebPage (1469). 545 pages with errors a rich result would fail on.
  • Near duplicates219 noted
    219 pages in 28 groups read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 1508 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 positions6 noted
    6 of 1476 linked pages are linked only from the template, never from another page's content.
  • Pagination32 noted
    39 pages in pagination sequences; 32 with problems.
  • Headers and cookiesOK
    2 cookies set by the site; 19 response headers recorded across 2523 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 1508 pages; 1471 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.
  • Spelling229 noted
    229 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

2591 sites, median 80%, average 78%

www.greasemonkey.com scores 85%, higher than 72% of the 2591 scanned sites. See the full ranking.

0601190%: 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%: 0 sites34%: 0 sites35%: 2 sites36%: 1 site37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 4 sites49%: 7 sites50%: 6 sites51%: 6 sites52%: 8 sites53%: 8 sites54%: 10 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 18 sites59%: 9 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 31 sites66%: 40 sites67%: 39 sites68%: 37 sites69%: 48 sites70%: 48 sites71%: 74 sites72%: 73 sites73%: 77 sites74%: 75 sites75%: 85 sites76%: 93 sites77%: 106 sites78%: 116 sites79%: 106 sites80%: 119 sites81%: 113 sites82%: 116 sites83%: 117 sites84%: 118 sites85%: 97 sites86%: 86 sites87%: 84 sites88%: 68 sites89%: 71 sites90%: 46 sites91%: 56 sites92%: 40 sites93%: 28 sites94%: 21 sites95%: 14 sites96%: 15 sites97%: 15 sites98%: 7 sites99%: 2 sites100%: 69 sites85% 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

The site has some technical SEO issues to address, particularly broken links, redirects, and meta descriptions. Correcting these will improve site health and user experience.

  1. 1

    Fix Broken Links

    Why: Broken links lead to a poor user experience and can affect your SEO ranking.

    How: Replace or remove the 4 internal links pointing to broken URLs.

    Checks: broken-links

  2. 2

    Reduce Redirects

    Why: Excessive or chained redirects negatively impact page loading speed and SEO.

    How: Resolve the 13 redirects, particularly the 3 chained redirects.

    Checks: redirects

  3. 3

    Resolve Non-200 Responses

    Why: Pages returning non-200 responses can harm crawling and indexing.

    How: Fix the 16 URLs not returning a valid response.

    Checks: status-codes

  4. 4

    Improve Meta Descriptions

    Why: Meta descriptions are crucial for click-through rates and search visibility.

    How: Provide unique meta descriptions for the 412 pages with issues.

    Checks: meta-descriptions

  5. 5

    Ensure Sitemap Coverage

    Why: A complete sitemap enhances indexation and SEO efficiency.

    How: Update the sitemap to include the 1476 crawled pages not currently listed.

    Checks: sitemap-coverage

  6. 6

    Address Duplicate Content

    Why: Duplicate content can confuse search engines and dilute page authority.

    How: Review the identified duplicates and canonicalize as needed.

    Checks: duplicate-content

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 has several security issues that need urgent attention, especially regarding cookie settings, vulnerable libraries, and exposed API keys. Implementing recommended fixes will enhance the site's security posture significantly.

  • 0 high
  • 3 medium
  • 2 low
  • 0 info
  1. 1

    Insecure Cookie SettingsMedium

    Why it matters: 2 of 4 cookies lack Secure, HttpOnly, and SameSite flags, allowing potential access from client-side scripts.

    Fix: Set the following flags for cookies: Secure, HttpOnly, SameSite=Strict.

    Evidence: Cookie flags

  2. 2

    Vulnerable JavaScript LibraryMedium

    Why it matters: Using jQuery 3.0.1 exposes the site to known vulnerabilities. Exploits may depend on actual usage.

    Fix: Upgrade jQuery to version 3.5.0 or later to eliminate vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  3. 3

    Exposed API KeyMedium

    Why it matters: A Google API key is publicly accessible, increasing the risk of misuse.

    Fix: Restrict the API key by referrer and API settings in the Google Cloud console.

    Evidence: Keys and secrets in page code

  4. 4

    Version Disclosure in Server BannerLow

    Why it matters: The server reveals the framework but not the version, which still gives attackers some information.

    Fix: Consider hiding the X-Powered-By header completely by configuring your server.

    Evidence: Software version disclosure

  5. 5

    Third-Party Scripts Lack Integrity ChecksLow

    Why it matters: Scripts from other domains run on your site without Subresource Integrity, posing a risk if those domains are compromised.

    Fix: Implement Subresource Integrity or apply a Content-Security-Policy restricting these scripts.

    Evidence: Third-party scripts

What the checks found

  • FoundCookie flagsMedium

    2 of 4 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.

    • 02 Nov 2026 07:18:35 GMT (set by https://www.greasemonkey.com/car-tips/category/car-maintenance/page/3/) lacks Secure, HttpOnly, SameSite
    • 02 Nov 2026 07:18:36 GMT (set by https://www.greasemonkey.com/car-tips/category/engine/page/2/) lacks Secure, HttpOnly, SameSite
  • FoundVulnerable JavaScript librariesMedium

    1 library with published vulnerabilities: jQuery 3.0.1. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 3.0.1 in https://www.greasemonkey.com/wp-content/plugins/gravityforms/js/placeholders.jq…: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…zQ (39 chars) in https://www.greasemonkey.com/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • NoteSoftware version disclosure

    Responses name the framework in an X-Powered-By header but hide the version.

    • server: cloudflare (2523 responses)
    • x-powered-by: WP Engine (1526 responses)
  • NoteThird-party scripts

    Scripts run from 3 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.)

    • www.google.com (3 script tags)
    • portal.autoops.com (2 script tags)
    • booking.cinch.io (2 script tags)
11 checks passed
  • OKHTTPS

    All 1508 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 1508 HTML pages.

  • OKContent Security Policy

    A Content-Security-Policy is set.

  • OKClickjacking protection

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

  • OKMIME sniffing protection

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

  • OKReferrer policy

    referrer-policy is set on all 1508 HTML pages.

  • OKPermissions policy

    permissions-policy is set on all 1508 HTML pages.

  • OKMixed content

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

  • OKForms over HTTPS

    274 forms found, all on HTTPS pages posting to HTTPS addresses.

  • 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 www.greasemonkey.com

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 www.greasemonkey.com from its pages as published, the way a search engine does. It shows summary figures only.

Own www.greasemonkey.com?

  • Claim this site to manage the listing, hide it from the public lists, or keep it.
  • Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming www.greasemonkey.com. Removal needs no account and no proof of purchase.