Scanned sites / moz.com / 2026-10-18-1441

moz.com scan from 2026-10-18 14:41:11 UTC DR 91

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

Scan 2026-10-18-1441

Scanned 2026-10-18 14:41:11 UTC, finished 2026-10-18 18:54:57 UTC. Found with 42backlinks.com tool directory

Site: https://moz.com/

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

71/ 100Needs work

On October 18, 2026 the Site Spider crawled 4859 pages and 1093 assets of moz.com, starting from https://moz.com/. It scored 71 out of 100, a result that needs work. 14 of 33 checks found something to fix, led by heavy assets (120), meta descriptions (2,374), sitemap coverage (2,837); 3 checks passed. Most of the points went to heavy assets (−6), meta descriptions (−5.3), sitemap coverage (−4.7). 16 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
4859
Assets fetched
1093
Status
Completed
Checks with issues
14 of 33
CoverageJob finished, partial coverage

5,952 of 6,000 discovered URLs were fetched, 48 blocked by robots.txt, 38,667 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, 14628 left unchecked.

  • Title tags1,367 issues
    1367 of 2837 pages have title issues. 758 noindex or canonicalized pages excluded.
    −3.8 points
  • Meta descriptions2,374 issues
    2374 of 2837 pages have meta description issues. 758 noindex or canonicalized pages excluded.
    −5.3 points
  • Headings1,580 issues
    1580 of 2837 pages have heading issues. 758 noindex or canonicalized pages excluded.
    −2.6 points
  • Broken links518 issues
    11854 internal links point at 518 broken URLs.
    −2.9 points
  • Links to other sites37 issues
    37 destinations answered with an error, 96 could not be determined (timeouts, rate limits or refusals), 14628 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.4 points
  • Redirects749 issues
    761 redirecting URLs, 7 of them chained.
    −0.8 points
  • Non-200 responses520 issues
    1298 URLs did not return a 2xx response. 1264 of them are pages, 520 with an error status; the rest are assets or redirects.
    −1.4 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability187 issues
    187 of 3007 indexable pages have indexability warnings. 588 pages noindex by design.
    −0.5 points
  • Image alt text9,126 issues
    9126 of 58568 image references have no alt attribute. 3141 use an empty alt (decorative), which is fine.
    −0.9 points
  • Heavy assets120 issues
    120 assets larger than 500 KB among 1093 fetched assets.
    −6 points
  • Orphan pages49 issues
    49 pages have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage2,837 issues
    2 sitemaps listing 0 URLs: 2837 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −4.7 points
  • Internal link counts300 noted
    Internal link counts for 500 pages; 300 worth a look.
  • Thin content24 issues
    24 of 2837 pages have fewer than 200 words. 758 noindex or canonicalized pages excluded.
    −0.1 points
  • Duplicate content4 issues
    1 group of pages with identical HTML.
  • URL format500 noted
    500 of 4859 page URLs are harder to read, share or cache than they need to be.
  • Canonicals655 noted
    655 of 3595 pages have a canonical worth checking.
  • Robots directives3,097 noted
    3097 pages carry a robots directive; 498 carry none.
  • Anchor text1,597 noted
    1597 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure1,994 noted
    1994 of 2837 pages could use the title, heading and snippet space better. 758 noindex or canonicalized pages excluded.
  • Image weight and alt length1,169 noted
    245 images over 100 KB; 924 with alt text over 100 characters.
  • Response anomalies27 noted
    27 URLs answered in a way worth looking at.
  • HTML and head validation3,570 noted
    3570 of 3595 pages have HTML problems: 3570 with head tags outside <head>, 0 over 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured data68 noted
    3372 of 2837 indexable pages carry structured data: ListItem (3370), BreadcrumbList (3353), Organization (2950), Article (1635), WebPage (1256). 68 pages with errors a rich result would fail on.
  • Near duplicates18 noted
    18 pages in 8 groups read almost the same as another page (95% alike or more).
  • Soft 404s2 noted
    2 pages answer 200 but say they are not there.
  • 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 positions240 noted
    240 of 2001 linked pages are linked only from the template, never from another page's content.
  • Pagination124 noted
    206 pages in pagination sequences; 124 with problems.
  • Headers and cookies3 noted
    6 cookies set by the site, 3 missing a protective flag; 20 response headers recorded across 5952 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 3595 pages; 3521 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.
  • Spelling3,007 noted
    3007 words an English dictionary does not know, on 2485 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2284 sites, median 79%, average 78%

moz.com scores 71%, higher than 20% of the 2284 scanned sites. See the full ranking.

0581150%: 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%: 45 sites70%: 41 sites71%: 68 sites72%: 70 sites73%: 65 sites74%: 70 sites75%: 71 sites76%: 87 sites77%: 92 sites78%: 106 sites79%: 86 sites80%: 106 sites81%: 106 sites82%: 115 sites83%: 95 sites84%: 106 sites85%: 85 sites86%: 66 sites87%: 71 sites88%: 62 sites89%: 61 sites90%: 33 sites91%: 44 sites92%: 33 sites93%: 21 sites94%: 14 sites95%: 10 sites96%: 9 sites97%: 9 sites98%: 4 sites99%: 0 sites100%: 70 sites71% 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 has significant technical issues that need addressing, particularly broken links, redirects, and missing titles/meta descriptions. These should be prioritized for better SEO performance.

  1. 1

    Fix Broken Links

    Why: Broken links harm user experience and SEO.

    How: Identify and update/remove links pointing to non-functional URLs.

    Checks: broken-links

  2. 2

    Reduce Redirects

    Why: Excessive redirects can slow down site speed.

    How: Minimize the number of hops and consider straightening redirect chains.

    Checks: redirects

  3. 3

    Resolve Non-200 Responses

    Why: Fixing these ensures that search engines can index your content.

    How: Review URLs returning errors and address the underlying issues.

    Checks: status-codes

  4. 4

    Optimize Title Tags

    Why: Proper titles improve click-through rates in search results.

    How: Create unique and descriptive title tags for affected pages.

    Checks: titles

  5. 5

    Add Meta Descriptions

    Why: Meta descriptions boost relevancy and attractiveness in SERPs.

    How: Write unique meta descriptions for pages that are missing them.

    Checks: meta-descriptions

  6. 6

    Correct Heading Issues

    Why: Proper heading structure aids in SEO and user readability.

    How: Ensure each page has only one H1 and meaningful subheadings.

    Checks: headings

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 has several security vulnerabilities, including missing protections for data handling and cookie transmission. Critical issues like potential content sniffing and mixed content resources could be exploited. Additionally, there's a need to address outdated libraries and leaked API keys to enhance overall security.

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

    Insecure Cookie FlagsMedium

    Why it matters: Cookies without HttpOnly, Secure, and SameSite flags are vulnerable to theft and misuse.

    Fix: Set cookies with the flags: HttpOnly, Secure, SameSite=Strict or Lax.

    Evidence: Cookie flags

  2. 2

    Mixed Content ResourcesMedium

    Why it matters: Loading resources over HTTP on HTTPS pages can be intercepted or altered by attackers.

    Fix: Ensure all resources are loaded over HTTPS.

    Evidence: Mixed content

  3. 3

    Vulnerable JavaScript LibraryMedium

    Why it matters: jQuery 1.9.1 has known vulnerabilities that could be exploited.

    Fix: Upgrade jQuery to at least version 3.5.0.

    Evidence: Vulnerable JavaScript libraries

  4. 4

    Leaked API KeysMedium

    Why it matters: Exposed API keys can be misused, leading to potential data breaches.

    Fix: Restrict the API keys by HTTP referrer and usage in the Google Cloud console.

    Evidence: Keys and secrets in page code

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers might misinterpret files as scripts, leading to potential XSS attacks.

    Fix: Implement the header 'X-Content-Type-Options: nosniff' in server responses.

    Evidence: MIME sniffing protection

  6. 6

    Missing Permissions-Policy HeaderInfo

    Why it matters: This header can limit browser feature access and reduce risks from injected scripts.

    Fix: Add 'Permissions-Policy: <policy>' header as appropriate to your site's features.

    Evidence: Permissions policy

What the checks found

  • FoundMIME sniffing protectionLow

    3373 of 3595 HTML pages send x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.

    • https://moz.com/login → no x-content-type-options
    • https://moz.com/mozcast → no x-content-type-options
    • https://moz.com/api/docs → no x-content-type-options
    • https://moz.com/api/dashboard/usage → no x-content-type-options
    • https://moz.com/freemium/keyword-explorer → no x-content-type-options
    • https://moz.com/freemium/competitive-research → no x-content-type-options
    • https://moz.com/freemium/local/presence-checker → no x-content-type-options
    • https://moz.com/subscriptions → no x-content-type-options
    • https://moz.com/freemium/brand-authority-freemium-form → no x-content-type-options
    • https://moz.com/api/docs/welcome → no x-content-type-options
    • https://moz.com/api/dashboard → no x-content-type-options
    • https://moz.com/api/docs/guides/getting-started → no x-content-type-options
  • 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://moz.com/ → no permissions-policy
    • https://moz.com/products/pro → no permissions-policy
    • https://moz.com/products/local → no permissions-policy
    • https://moz.com/products/stat → no permissions-policy
    • https://moz.com/products/api → no permissions-policy
    • https://moz.com/products/ai-explorer → no permissions-policy
    • https://moz.com/moz-data → no permissions-policy
    • https://moz.com/explorer → no permissions-policy
    • https://moz.com/link-explorer → no permissions-policy
    • https://moz.com/competitive-research → no permissions-policy
    • https://moz.com/products/pro/seo-toolbar → no permissions-policy
    • https://moz.com/free-seo-tools → no permissions-policy
  • FoundCookie flagsMedium

    118 of 121 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.

    • SERVD_LOGGED_IN_STATUS (set by https://moz.com/sitemap.xml) lacks Secure
    • 18 Oct 2026 15:12:59 GMT (set by https://moz.com/community/users/4633600) lacks Secure, HttpOnly, SameSite
    • 18 Oct 2026 19:22:08 GMT (set by https://moz.com/images/assets/features/identify-keywords-within-striking-distan…) lacks Secure, HttpOnly, SameSite
    • 18 Oct 2026 19:22:17 GMT (set by https://moz.com/images/products/MozCertificationTechnicalSEO.png?auto=compress%…) lacks Secure, HttpOnly, SameSite
    • 18 Oct 2026 19:22:42 GMT (set by https://moz.com/images/about/gold-roger-1.jpg?auto=compress%2Cformat&fit=crop&d…) lacks Secure, HttpOnly, SameSite
    • 18 Oct 2026 19:22:52 GMT (set by https://moz.com/images/blog/insets/Custom-Inset-Images/AI-Research-GTM-Blog-Hea…) lacks Secure, HttpOnly, SameSite
    • 18 Oct 2026 19:22:54 GMT (set by https://moz.com/images/assets/backgrounds/moz-local-hero-gradient.jpeg?auto=com…) lacks Secure, HttpOnly, SameSite
    • 18 Oct 2026 15:26:01 GMT (set by https://moz.com/google-api-leaks) lacks Secure, HttpOnly, SameSite
    • 18 Oct 2026 19:23:12 GMT (set by https://moz.com/images/user/photo/1681526501869.jpeg?w=160&h=160&auto=compress%…) lacks Secure, HttpOnly, SameSite
    • 18 Oct 2026 19:23:19 GMT (set by https://moz.com/images/assets/features/slide-24-ai-share-of-voice-result.jpg?au…) lacks Secure, HttpOnly, SameSite
    • 18 Oct 2026 19:23:22 GMT (set by https://moz.com/images/blog/Blog-OG-images/WTF-is-NL-Web-Social_Card.png?w=1200…) lacks Secure, HttpOnly, SameSite
    • 18 Oct 2026 15:32:18 GMT (set by https://moz.com/community/users/22308147) lacks Secure, HttpOnly, SameSite
  • FoundMixed contentMedium

    87 resources on HTTPS pages are loaded over plain HTTP, 4 of them scripts or stylesheets that browsers block or that can be tampered with in transit.

    • https://moz.com/about/team/funnylookinhat loads image http://i.imgur.com/ctECATe.gif
    • https://moz.com/about/team/funnylookinhat loads image http://i.imgur.com/8knHvsl.gif
    • https://moz.com/blog/google-instant-fewer-changes-to-seo-than-the-ave… loads image http://blog.conductor.com/wp-content/uploads/2010/09/Research-visits-search-term-length-5…
    • https://moz.com/blog/how-to-build-a-facebook-group loads image http://www.searchenginejournal.com/wp-content/uploads/2015/10/facebook-traffic-380x239.png
    • https://moz.com/blog/how-to-build-a-facebook-group loads image http://www.searchenginejournal.com/wp-content/uploads/2015/10/Screen-Shot-2015-10-15-at-8…
    • https://moz.com/blog/how-to-build-a-facebook-group loads image http://www.searchenginejournal.com/wp-content/uploads/2015/10/IMG_1055-380x310.png
    • https://moz.com/blog/how-to-build-a-facebook-group loads image http://www.searchenginejournal.com/wp-content/uploads/2015/10/facebook-group-reach-760x27…
    • https://moz.com/blog/how-to-build-a-facebook-group loads image http://www.searchenginejournal.com/wp-content/uploads/2015/10/Screen-Shot-2015-10-15-at-9…
    • https://moz.com/blog/how-to-build-a-facebook-group loads image http://www.searchenginejournal.com/wp-content/uploads/2015/10/Screen-Shot-2015-10-16-at-9…
    • https://moz.com/blog/how-to-build-a-facebook-group loads image http://www.searchenginejournal.com/wp-content/uploads/2015/10/Screen-Shot-2015-10-15-at-8…
    • https://moz.com/blog/how-to-build-a-facebook-group loads image http://www.searchenginejournal.com/wp-content/uploads/2015/10/Screen-Shot-2015-10-16-at-9…
    • https://moz.com/blog/how-to-build-a-facebook-group loads image http://www.searchenginejournal.com/wp-content/uploads/2015/10/Screen-Shot-2015-10-16-at-1…
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 1.9.1 in https://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.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
  • FoundKeys and secrets in page codeMedium

    2 credential-like values found in code served to every visitor: Google API key.

    • Google API key AIzaSy…gM (39 chars) in https://moz.com/_next/static/chunks/6735-2f61ee0698accc13.js: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
    • Google API key AIzaSy…tU (39 chars) in https://moz.com/_next/static/chunks/6735-2f61ee0698accc13.js: 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 (5952 responses)
    • x-powered-by: NodeBB (801 responses)
  • NoteThird-party scripts

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

    • cloud.wordlift.io (39 script tags)
    • cdn.ziffstatic.com (39 script tags)
    • moz-static.moz.com (156 script tags)
    • static.cloudflareinsights.com (39 script tags)
    • fast.wistia.com (12 script tags)
    • js.hsforms.net (8 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 1 path that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.

    • Disallow: /admin-preview/*
7 checks passed
  • OKHTTPS

    All 3595 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

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

  • OKContent Security Policy

    A Content-Security-Policy is set on 615 of 3595 pages.

  • OKClickjacking protection

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

  • OKReferrer policy

    A referrer policy is set through a <meta name="referrer"> tag.

  • OKForms over HTTPS

    42 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.

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

Own moz.com?