Scanned sites / yoast.com / 2026-10-01-2201

yoast.com scan from 10/1/2026, 10:01:44 PM

Scan 2026-10-01-2201

Scanned 10/1/2026, 10:01:44 PM, finished 10/2/2026, 11:42:57 AM. Found with 42backlinks.com tool directory

Site: https://yoast.com/

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

83/ 100Good

On October 1, 2026 the Site Spider crawled 4174 pages and 1102 assets of yoast.com, starting from https://yoast.com/. It scored 83 out of 100, a good result. 12 of 16 checks found something to fix, led by heavy assets (26), sitemap coverage (2,555), title tags (1,012); 3 checks passed. Most of the points went to heavy assets (−6), sitemap coverage (−4.5), title tags (−3). 1 check found something the score does not count, listed as noted. 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, 1 low and 1 info findings. See the security findings ↓

Pages crawled
4174
Assets fetched
1102
Status
Completed
Checks with issues
12 of 16
CoverageJob finished, partial coverage

5,276 of 5,290 discovered URLs were fetched, 13 blocked by robots.txt, 72,113 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, 13674 left unchecked.

  • Title tags1,012 issues
    1012 of 2672 pages have title issues. 712 noindex or canonicalized pages excluded.
    −3 points
  • Meta descriptions873 issues
    873 of 2672 pages have meta description issues. 712 noindex or canonicalized pages excluded.
    −2.1 points
  • Headings18 issues
    18 of 2672 pages have heading issues. 712 noindex or canonicalized pages excluded.
  • Broken links29 issues
    139 internal links point at 29 broken URLs.
    −0.2 points
  • Links to other sites4 issues
    4 destinations answered with an error, 92 could not be determined (timeouts, rate limits or refusals), 13674 were left unchecked by the per-scan cap, of 300 destinations checked.
  • Redirects812 issues
    763 redirecting URLs, 65 of them chained.
    −1 points
  • Non-200 responses32 issues
    873 URLs did not return a 2xx response. 790 of them are pages, 32 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability152 issues
    152 of 2825 indexable pages have indexability warnings. 559 pages noindex by design.
    −0.4 points
  • Image alt text1 issue
    1 of 141639 image references have no alt attribute. 115610 use an empty alt (decorative), which is fine.
  • Heavy assets26 issues
    26 assets larger than 500 KB among 1102 fetched assets. 14 documents over that size are listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages49 issues
    49 pages have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage2,555 issues
    2 sitemaps listing 128 URLs: 2551 crawled pages missing, 1 listed URL broken or redirecting, 3 reachable only via the sitemap.
    −4.5 points
  • Internal link countsOK
    Internal link counts for 500 pages.
  • Thin contentOK
    0 of 2672 pages have fewer than 200 words. 712 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1763 sites, median 80%, average 79%

yoast.com scores 83%, higher than 63% of the 1763 scanned sites. See the full ranking.

0521030%: 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%: 0 sites15%: 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%: 2 sites38%: 2 sites39%: 1 site40%: 2 sites41%: 1 site42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 6 sites57%: 6 sites58%: 11 sites59%: 6 sites60%: 10 sites61%: 11 sites62%: 15 sites63%: 16 sites64%: 12 sites65%: 20 sites66%: 19 sites67%: 34 sites68%: 27 sites69%: 25 sites70%: 39 sites71%: 38 sites72%: 49 sites73%: 50 sites74%: 48 sites75%: 57 sites76%: 71 sites77%: 63 sites78%: 84 sites79%: 60 sites80%: 86 sites81%: 103 sites82%: 82 sites83%: 82 sites84%: 79 sites85%: 59 sites86%: 65 sites87%: 55 sites88%: 60 sites89%: 52 sites90%: 32 sites91%: 34 sites92%: 24 sites93%: 14 sites94%: 12 sites95%: 11 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 54 sites83% 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 has several low-impact issues that can be quickly addressed. Prioritize fixing broken links and optimizing non-200 responses, followed by updating titles, meta descriptions, and enhancing sitemap coverage.

  1. 1

    Fix Broken Links

    Why: Broken links negatively impact user experience and SEO.

    How: Update or remove links that lead to broken URLs identified during the crawl.

    Checks: broken-links

  2. 2

    Resolve Redirects

    Why: Too many redirects can slow down site performance and confuse users.

    How: Reduce the number of chained redirects by ensuring links point directly to the final destination.

    Checks: redirects

  3. 3

    Address Non-200 Responses

    Why: Pages returning errors can hurt your rankings and site usability.

    How: Identify and fix all URLs returning non-200 statuses as listed in the crawl.

    Checks: status-codes

  4. 4

    Update Title Tags

    Why: Optimizing title tags can improve click-through rates and rankings.

    How: Revise titles to meet best practices; ensure they are concise and accurately reflect page content.

    Checks: titles

  5. 5

    Improve Meta Descriptions

    Why: Well-crafted meta descriptions can enhance visibility and click rates.

    How: Rewrite meta descriptions to stay within pixel limits while effectively describing the content.

    Checks: meta-descriptions

  6. 6

    Enhance Sitemap Coverage

    Why: A comprehensive sitemap is crucial for search engine indexing.

    How: Add missing pages to your sitemap and resolve any sitemaps that redirect.

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

The website yoast.com has several security issues, including missing clickjacking protection and cookie security flags. Additionally, a Google API key is exposed in page code, which could lead to unauthorized usage if not properly restricted.

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

    Missing Clickjacking ProtectionMedium

    Why it matters: Without X-Frame-Options or CSP frame-ancestors, pages can be embedded by attackers, potentially leading to phishing attacks.

    Fix: Add the header 'X-Frame-Options: DENY' or 'Content-Security-Policy: frame-ancestors 'none'' to all pages.

    Evidence: Clickjacking protection

  2. 2

    Cookies Lacking Secure FlagsMedium

    Why it matters: Cookies without Secure, HttpOnly, or SameSite flags can be exploited, allowing attackers to steal session data or conduct cross-site request forgery.

    Fix: Set cookies with 'Secure', 'HttpOnly', and 'SameSite=Lax' or 'SameSite=Strict' attributes.

    Evidence: Cookie flags

  3. 3

    Exposed Google API KeyMedium

    Why it matters: An exposed API key can be misused, especially if it lacks referrer restrictions.

    Fix: Remove the key from the page code and restrict its usage in the Google Cloud console to specific HTTP referrers.

    Evidence: Keys and secrets in page code

  4. 4

    Missing Referrer PolicyLow

    Why it matters: Without a Referrer-Policy, sensitive URL parameters could be leaked to external sites.

    Fix: Add the header 'Referrer-Policy: no-referrer' or another appropriate policy to all pages.

    Evidence: Referrer policy

  5. 5

    Missing Permissions PolicyInfo

    Why it matters: Without a Permissions-Policy, browser features like camera or microphone access might be misused by third-party scripts.

    Fix: Add the header 'Permissions-Policy: geolocation=(), microphone=(), camera=()' to all pages.

    Evidence: Permissions policy

What the checks found

  • FoundClickjacking protectionMedium

    2 of 3384 HTML pages send 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://yoast.com/ → no x-frame-options
    • https://yoast.com/shop/ → no x-frame-options
    • https://yoast.com/product/yoast-seo-wordpress/ → no x-frame-options
    • https://yoast.com/product/yoast-woocommerce-seo/ → no x-frame-options
    • https://yoast.com/product/yoast-seo-ai-plus/ → no x-frame-options
    • https://yoast.com/product/yoast-seo-shopify/ → no x-frame-options
    • https://yoast.com/product/google-docs-addon/ → no x-frame-options
    • https://yoast.com/yoast-partners/resellers/ → no x-frame-options
    • https://yoast.com/product/yoast-seo-premium-wordpress/ → no x-frame-options
    • https://yoast.com/academy/ → no x-frame-options
    • https://yoast.com/academy/free-seo-training-seo-for-beginners/ → no x-frame-options
    • https://yoast.com/tag/seo-basics/ → 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://yoast.com/ → no referrer-policy
    • https://yoast.com/shop/ → no referrer-policy
    • https://yoast.com/product/yoast-seo-wordpress/ → no referrer-policy
    • https://yoast.com/product/yoast-woocommerce-seo/ → no referrer-policy
    • https://yoast.com/product/yoast-seo-ai-plus/ → no referrer-policy
    • https://yoast.com/product/yoast-seo-shopify/ → no referrer-policy
    • https://yoast.com/product/google-docs-addon/ → no referrer-policy
    • https://yoast.com/yoast-partners/resellers/ → no referrer-policy
    • https://yoast.com/product/yoast-seo-premium-wordpress/ → no referrer-policy
    • https://yoast.com/academy/ → no referrer-policy
    • https://yoast.com/academy/free-seo-training-seo-for-beginners/ → no referrer-policy
    • https://yoast.com/tag/seo-basics/ → 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://yoast.com/ → no permissions-policy
    • https://yoast.com/shop/ → no permissions-policy
    • https://yoast.com/product/yoast-seo-wordpress/ → no permissions-policy
    • https://yoast.com/product/yoast-woocommerce-seo/ → no permissions-policy
    • https://yoast.com/product/yoast-seo-ai-plus/ → no permissions-policy
    • https://yoast.com/product/yoast-seo-shopify/ → no permissions-policy
    • https://yoast.com/product/google-docs-addon/ → no permissions-policy
    • https://yoast.com/yoast-partners/resellers/ → no permissions-policy
    • https://yoast.com/product/yoast-seo-premium-wordpress/ → no permissions-policy
    • https://yoast.com/academy/ → no permissions-policy
    • https://yoast.com/academy/free-seo-training-seo-for-beginners/ → no permissions-policy
    • https://yoast.com/tag/seo-basics/ → no permissions-policy
  • FoundCookie flagsMedium

    5 of 6 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.

    • yith_wcmcs_currency (set by https://yoast.com/checkout/) lacks Secure, HttpOnly, SameSite
    • wp_woocommerce_session_4b6b2654624af0555bb41be2bef184bb (set by https://yoast.com/checkout/) lacks SameSite
    • shop_cart_count (set by https://yoast.com/cart/?add-to-cart=4113952) lacks Secure, HttpOnly, SameSite
    • woocommerce_items_in_cart (set by https://yoast.com/cart/?add-to-cart=4113952) lacks Secure, HttpOnly, SameSite
    • woocommerce_cart_hash (set by https://yoast.com/cart/?add-to-cart=4113952) lacks Secure, HttpOnly, SameSite
  • FoundKeys and secrets in page codeMedium

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

    • Google API key AIzaSy…vQ (39 chars) in https://yoast.com/checkout/: 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 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.)

    • cdn-4.convertexperiments.com (40 script tags)
    • widget.trustpilot.com (6 script tags)
    • mbyoastbv.activehosted.com (17 script tags)
    • fast.wistia.net (1 script tag)
    • maps.googleapis.com (1 script tag)
10 checks passed
  • OKHTTPS

    All 3384 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

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

  • OKContent Security Policy

    A Content-Security-Policy is set on 2 of 3384 pages.

  • OKMIME sniffing protection

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

  • OKSoftware version disclosure

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

  • OKMixed content

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

  • OKForms over HTTPS

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

  • OKVulnerable JavaScript libraries

    2 library versions recognised, none with known vulnerabilities.

  • 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 yoast.com

Their neighbours in the SEO rank table, which orders every scanned site by health score.

This report was produced by the DIY SEO Hub Site Spider crawling yoast.com from its pages as published, the way a search engine does. It shows summary figures only.

Own yoast.com?

yoast.com scan 2026-10-01-2201 | DIY SEO Hub