Scanned sites / maof.org / 2026-11-11-1509

maof.org scan from 2026-11-11 15:09:01 UTC DR 48

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

Scan 2026-11-11-1509

Scanned 2026-11-11 15:09:01 UTC, finished 2026-11-11 15:10:28 UTC

Site: https://maof.org/

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

69/ 100Needs work

On November 11, 2026 the Site Spider crawled 127 pages and 3 assets of maof.org, starting from https://maof.org/. It scored 69 out of 100, a result that needs work. 10 of 33 checks found something to fix, led by indexability (125), meta descriptions (105), headings (125); 13 checks passed. Most of the points went to indexability (−10), meta descriptions (−6.7), headings (−6). 10 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
127
Assets fetched
3
Status
Completed
Checks with issues
10 of 33
CoverageComplete crawl

130 of 130 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 117 link destinations on other sites were checked.

  • Title tags69 issues
    69 of 125 pages have title issues.
    −5.5 points
  • Meta descriptions105 issues
    105 of 125 pages have meta description issues.
    −6.7 points
  • Headings125 issues
    125 of 125 pages have heading issues.
    −6 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites4 issues
    4 destinations answered with an error, 18 could not be determined (timeouts, rate limits or refusals), of 117 destinations checked.
    −1.2 points
  • Redirects2 issues
    2 redirecting URLs, 1 of them chained.
    −0.1 points
  • Non-200 responses2 noted
    2 URLs did not return a 2xx response. 2 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability125 issues
    125 of 125 indexable pages have indexability warnings.
    −10 points
  • Image alt textOK
    0 of 1263 image references have no alt attribute. 327 use an empty alt (decorative), which is fine.
  • Heavy assets1 issue
    1 asset larger than 500 KB among 3 fetched assets.
    −0.6 points
  • Orphan pages4 issues
    4 pages have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage6 issues
    1 sitemap listing 123 URLs: 2 crawled pages missing, 0 listed URLs broken or redirecting, 4 reachable only via the sitemap.
    −0.3 points
  • Internal link counts3 noted
    Internal link counts for 125 pages; 3 worth a look.
  • Thin contentOK
    0 of 125 pages have fewer than 200 words.
  • Duplicate content2 issues
    1 group of pages with identical HTML.
    −0.1 points
  • URL format4 noted
    4 of 127 page URLs are harder to read, share or cache than they need to be.
  • Canonicals125 noted
    125 of 125 pages have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 125 pages are open to search engines.
  • Anchor text4 noted
    4 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure125 noted
    125 of 125 pages could use the title, heading and snippet space better.
  • Image weight and alt length1 noted
    0 images over 100 KB; 1 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 125 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    No page carries structured data (125 indexable pages checked).
  • Near duplicates46 noted
    46 pages in 9 groups read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 125 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 positions20 noted
    20 of 121 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    1 cookie set by the site; 13 response headers recorded across 130 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 125 pages; 0 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.
  • Spelling99 noted
    99 words an English dictionary does not know, on 54 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2892 sites, median 80%, average 79%

maof.org scores 69%, higher than 14% of the 2892 scanned sites. See the full ranking.

0761520%: 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%: 2 sites37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 10 sites55%: 10 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 54 sites70%: 47 sites71%: 79 sites72%: 77 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 113 sites80%: 129 sites81%: 123 sites82%: 135 sites83%: 120 sites84%: 130 sites85%: 106 sites86%: 96 sites87%: 94 sites88%: 82 sites89%: 73 sites90%: 56 sites91%: 60 sites92%: 44 sites93%: 30 sites94%: 26 sites95%: 16 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 152 sites69% 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 site needs fixes for redirects, title tags, meta descriptions, headings, and indexability issues. Improving these can enhance performance and user experience significantly.

  1. 1

    Fix Redirects

    Why: Chained and multiple redirects can confuse users and search engines.

    How: Update links to point directly to the final destination URL.

    Checks: redirects

  2. 2

    Update Title Tags

    Why: 69 pages have title issues, affecting SEO and clarity.

    How: Ensure each page has a unique, descriptive title under 60 characters.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: 105 pages lack optimized meta descriptions, hindering click-through rates.

    How: Write unique, engaging meta descriptions for all affected pages, ideally under 160 characters.

    Checks: meta-descriptions

  4. 4

    Address Heading Problems

    Why: 125 pages have heading issues, which affects content structure and SEO.

    How: Ensure each page has one H1 tag and uses H2s and H3s appropriately.

    Checks: headings

  5. 5

    Resolve Indexability Warnings

    Why: All pages have indexability issues, which can prevent them from being indexed.

    How: Add canonical and language attributes to each page to avoid confusion.

    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

Your website has several security vulnerabilities, including lack of content security policy and vulnerable JavaScript libraries. Implementing a content security policy and updating libraries are crucial for protecting against attacks. Additionally, sensitive information like API keys should be restricted.

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

    Missing Content Security PolicyMedium

    Why it matters: Without a Content Security Policy, your site is vulnerable to cross-site scripting (XSS) and data injection attacks.

    Fix: Add a Content-Security-Policy header, e.g., `Content-Security-Policy: default-src 'self';`.

    Evidence: Content Security Policy

  2. 2

    Missing X-Frame-Options HeaderMedium

    Why it matters: Lack of this header allows clickjacking attacks where malicious sites can overlay your pages in a frame.

    Fix: Add an X-Frame-Options header with value `DENY` or `SAMEORIGIN`.

    Evidence: Clickjacking protection

  3. 3

    Vulnerable JavaScript LibraryMedium

    Why it matters: Using jQuery 2.2.0 exposes your site to known vulnerabilities that could be exploited.

    Fix: Upgrade jQuery to at least version 3.5.0 to mitigate risks.

    Evidence: Vulnerable JavaScript libraries

  4. 4

    Leaked API KeysMedium

    Why it matters: Exposing Google API keys can lead to unauthorized usage of your APIs, potentially incurring costs.

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

    Evidence: Keys and secrets in page code

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Not implementing a referrer policy may expose sensitive information from URLs when users navigate away from your site.

    Fix: Add a Referrer-Policy header, e.g., `Referrer-Policy: no-referrer`.

    Evidence: Referrer policy

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: No permissions policy could allow unauthorized access to browser features.

    Fix: Add a Permissions-Policy header, e.g., `Permissions-Policy: geolocation=(self)`.

    Evidence: Permissions policy

What the checks found

  • FoundContent Security PolicyMedium

    None of the 125 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://maof.org/ → no content-security-policy
    • https://maof.org/volunteer → no content-security-policy
    • https://maof.org/donate → no content-security-policy
    • https://maof.org/about-us/mission-vision-values → no content-security-policy
    • https://maof.org/about-us/services → no content-security-policy
    • https://maof.org/about-us/team → no content-security-policy
    • https://maof.org/about-us/board-of-directors → no content-security-policy
    • https://maof.org/about-us/locations → no content-security-policy
    • https://maof.org/about-us/careers → no content-security-policy
    • https://maof.org/education/child-care → no content-security-policy
    • https://maof.org/education/head-start → no content-security-policy
    • https://maof.org/education/preschool → no content-security-policy
  • FoundClickjacking protectionMedium

    No HTML page sends x-frame-options. Without X-Frame-Options (or a CSP frame-ancestors directive) the pages can be embedded in a frame on another site and overlaid with invisible controls.

    • https://maof.org/ → no x-frame-options
    • https://maof.org/volunteer → no x-frame-options
    • https://maof.org/donate → no x-frame-options
    • https://maof.org/about-us/mission-vision-values → no x-frame-options
    • https://maof.org/about-us/services → no x-frame-options
    • https://maof.org/about-us/team → no x-frame-options
    • https://maof.org/about-us/board-of-directors → no x-frame-options
    • https://maof.org/about-us/locations → no x-frame-options
    • https://maof.org/about-us/careers → no x-frame-options
    • https://maof.org/education/child-care → no x-frame-options
    • https://maof.org/education/head-start → no x-frame-options
    • https://maof.org/education/preschool → no x-frame-options
  • FoundReferrer policyLow

    No HTML page sends referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.

    • https://maof.org/ → no referrer-policy
    • https://maof.org/volunteer → no referrer-policy
    • https://maof.org/donate → no referrer-policy
    • https://maof.org/about-us/mission-vision-values → no referrer-policy
    • https://maof.org/about-us/services → no referrer-policy
    • https://maof.org/about-us/team → no referrer-policy
    • https://maof.org/about-us/board-of-directors → no referrer-policy
    • https://maof.org/about-us/locations → no referrer-policy
    • https://maof.org/about-us/careers → no referrer-policy
    • https://maof.org/education/child-care → no referrer-policy
    • https://maof.org/education/head-start → no referrer-policy
    • https://maof.org/education/preschool → no referrer-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://maof.org/ → no permissions-policy
    • https://maof.org/volunteer → no permissions-policy
    • https://maof.org/donate → no permissions-policy
    • https://maof.org/about-us/mission-vision-values → no permissions-policy
    • https://maof.org/about-us/services → no permissions-policy
    • https://maof.org/about-us/team → no permissions-policy
    • https://maof.org/about-us/board-of-directors → no permissions-policy
    • https://maof.org/about-us/locations → no permissions-policy
    • https://maof.org/about-us/careers → no permissions-policy
    • https://maof.org/education/child-care → no permissions-policy
    • https://maof.org/education/head-start → no permissions-policy
    • https://maof.org/education/preschool → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 2.2.0 in https://code.jquery.com/jquery-2.2.0.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…bY (39 chars) in https://maof.org/about-us/locations: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
    • Google API key AIzaSy…9o (39 chars) in https://maof.org/education/preschool: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • NoteThird-party scripts

    Scripts run from 11 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 (40 script tags)
    • use.typekit.net (40 script tags)
    • www.google.com (40 script tags)
    • kit.fontawesome.com (40 script tags)
    • static.ctctcdn.com (40 script tags)
    • 7yssx7.csb.app (40 script tags)
    • js.hs-scripts.com (40 script tags)
    • translate.google.com (40 script tags)
    • files.sunnysidecollective.com (4 script tags)
    • maps.google.com (2 script tags)
    • cdn.jsdelivr.net (1 script tag)
9 checks passed
  • OKHTTPS

    All 125 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

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

  • OKMIME sniffing protection

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

  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKCookie flags

    All 1 cookie carry Secure, HttpOnly and SameSite flags.

  • OKMixed content

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

  • OKForms over HTTPS

    44 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 maof.org

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

Own maof.org?