Scanned sites / yoast.com / 2026-09-28-2126
yoast.com scan from 9/28/2026, 9:26:41 PM
Scan 2026-09-28-2126
Scanned 9/28/2026, 9:26:41 PM, finished 9/28/2026, 10:00:34 PM. Found with 42backlinks.com tool directory
Not a full crawl. The site rate-limited the crawler (25 requests answered 429), so the scan finished early with 2069 URLs left unfetched. Results cover what was crawled.
Site: https://yoast.com/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 28, 2026 the Site Spider crawled 324 pages and 2 assets of yoast.com, starting from https://yoast.com/. It scored 91 out of 100, an excellent result. 8 of 16 checks found something to fix, led by sitemap coverage (130), title tags (78), meta descriptions (72); 6 checks passed. Most of the points went to title tags (−3), sitemap coverage (−3), meta descriptions (−2.2). 2 checks 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
- 324
- Assets fetched
- 2
- Status
- Completed
- Checks with issues
- 8 of 16
326 of 2,404 discovered URLs were fetched, 9 blocked by robots.txt, 5,753 left out by the 5,000-page and 1,000-asset budget, 2,069 skipped when the crawl was cut short. 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, 597 left unchecked.
- Title tags78 issues78 of 250 pages have title issues. 10 noindex or canonicalized pages excluded.−3 points
- Meta descriptions72 issues72 of 250 pages have meta description issues. 10 noindex or canonicalized pages excluded.−2.2 points
- Headings4 issues4 of 250 pages have heading issues. 10 noindex or canonicalized pages excluded.−0.1 points
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sites5 issues5 destinations answered with an error, 97 could not be determined (timeouts, rate limits or refusals), 597 were left unchecked by the per-scan cap, of 300 destinations checked.−0.8 points
- Redirects40 issues41 redirecting URLs, 0 of them chained.−0.6 points
- Non-200 responses41 noted41 URLs did not return a 2xx response. 40 of them are pages, 0 with an error status; the rest are assets or redirects.
- Rate limited24 issues24 URLs (24 pages) answered HTTP 429 on every try, so the crawler backed off and moved on without analysing them. A site that throttles crawlers this hard can throttle search engines too.−0.4 points
- IndexabilityOK0 of 250 indexable pages have indexability warnings. 10 pages noindex by design.
- Image alt text1 issue1 of 10709 image references have no alt attribute. 9531 use an empty alt (decorative), which is fine.
- Heavy assetsOK0 assets larger than 500 KB among 2 fetched assets.
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverage130 issuesNo sitemap found. Tried: https://yoast.com/sitemap.xml (301), https://yoast.com/sitemap_index.xml (skipped). Add one at /sitemap.xml or list it in robots.txt.−3 points
- Internal link countsOKInternal link counts for 260 pages.
- Thin contentOK0 of 250 pages have fewer than 200 words. 10 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1341 sites, median 80%, average 79%
yoast.com scores 91%, higher than 90% of the 1341 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsYour site has a strong health score of 91/100. However, we need to address redirect issues, non-200 responses, optimized metadata, and heading structures to improve SEO performance.
- 1
Fix Redirect and Non-200 Responses
Why: 41 URLs are redirecting or not returning 2xx responses, which can harm crawl efficiency.
How: Identify and update or remove the 41 problematic URLs to return 200 status.
Checks: redirects, status-codes
- 2
Resolve Rate Limiting
Why: 24 pages returned HTTP 429, limiting crawler access can hinder indexing.
How: Adjust server settings to allow crawlers more access, or reduce throttling on the identified pages.
Checks: rate-limited
- 3
Add Missing Sitemap
Why: No sitemap found can lead to inefficient crawling of your pages.
How: Create a sitemap and make it accessible at /sitemap.xml.
Checks: sitemap-coverage
- 4
Update Title Tags
Why: 78 pages have title issues affecting click-through rates.
How: Create unique, relevant title tags for all affected pages exceeding 30 characters.
Checks: titles
- 5
Optimize Meta Descriptions
Why: 72 pages have meta description issues which can lead to lower engagement.
How: Write unique meta descriptions for affected pages, ensuring they are under 160 characters.
Checks: meta-descriptions
- 6
Fix Heading Structure
Why: 4 pages have heading issues which can confuse search engines.
How: Ensure only one H1 per page and adjust remaining headings appropriately.
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 crawlYour website has several security concerns that need immediate attention, specifically around headers and cookie protection. Implementing the recommended changes will strengthen your defenses against attacks like clickjacking and session hijacking, and better protect your users' privacy.
- 0 high
- 3 medium
- 1 low
- 1 info
- 1
Missing Clickjacking ProtectionMedium
Why it matters: Lack of X-Frame-Options allows your pages to be embedded in iframes, risking clickjacking attacks.
Fix: Add 'X-Frame-Options: DENY' to your HTTP response headers.
Evidence: Clickjacking protection
- 2
Unprotected CookiesMedium
Why it matters: Several cookies lack Secure, HttpOnly, and SameSite flags, making them vulnerable to theft and cross-site request forgery.
Fix: Set cookies with 'Secure; HttpOnly; SameSite=Strict' attributes wherever applicable.
Evidence: Cookie flags
- 3
Leaked API KeyMedium
Why it matters: A visible Google API key can be misused, especially if not properly restricted in the Google Cloud console.
Fix: Restrict the API key to specific HTTP referrers in your Google Cloud settings.
Evidence: Keys and secrets in page code
- 4
Missing Referrer PolicyLow
Why it matters: Without a referrer-policy, you expose users' full page addresses to third parties.
Fix: Add 'Referrer-Policy: no-referrer' to your HTTP response headers.
Evidence: Referrer policy
- 5
No Permissions Policy SetInfo
Why it matters: Lack of a permissions-policy allows unnecessary browser features, increasing risk if an attacker injects malicious scripts.
Fix: Add 'Permissions-Policy: no-camera, no-microphone, no-geolocation' to your HTTP headers.
Evidence: Permissions policy
What the checks found
- FoundClickjacking protectionMedium
1 of 260 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 260 crawled pages were served over HTTPS.
- OKHTTP Strict Transport Security
strict-transport-security is set on all 260 HTML pages.
- OKContent Security Policy
A Content-Security-Policy is set on 1 of 260 pages.
- OKMIME sniffing protection
x-content-type-options is set on all 260 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
1 library version 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.
- sgvet.com92/100 · rank 87 · 33 pages
- outlookoptometry.com92/100 · rank 87 · 13 pages
- www.perfectionplumbing.ca91/100 · rank 105 · 409 pages
- www.physiomira.com91/100 · rank 105 · 31 pages
- freestenohub.com91/100 · rank 105 · 4,991 pages
- yogapassage.ca91/100 · rank 105 · 60 pages
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?
- 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 yoast.com. Removal needs no account and no proof of purchase.