Scanned sites / youtube.com / 2026-09-23-1939

youtube.com scan from 2026-09-23 19:39:54 UTC DR 99

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

Scan 2026-09-23-1939

Scanned 2026-09-23 19:39:54 UTC, finished 2026-09-23 22:30:19 UTC

Site: https://youtube.com/

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

69/ 100Needs work

On September 23, 2026 the Site Spider crawled 4154 pages and 890 assets of youtube.com, starting from https://youtube.com/. It scored 69 out of 100, a result that needs work. 14 of 27 checks found something to fix, led by title tags (1,983), heavy assets (86), meta descriptions (2,218); 3 checks passed. Most of the points went to title tags (−6.1), heavy assets (−6), meta descriptions (−5.4). 10 checks found something the score does not count, listed as noted. 10 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: Medium5 medium, 1 low and 1 info findings. See the security findings ↓

Pages crawled
4154
Assets fetched
890
Status
Completed
Checks with issues
14 of 27
CoverageComplete crawl

5,044 of 5,088 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 320 link destinations on other sites were checked, 1249 left unchecked.

  • Title tags1,983 issues
    1983 of 2490 pages have title issues. 787 noindex or canonicalized pages excluded.
    −6.1 points
  • Meta descriptions2,218 issues
    2218 of 2490 pages have meta description issues. 787 noindex or canonicalized pages excluded.
    −5.4 points
  • Headings751 issues
    751 of 2490 pages have heading issues. 787 noindex or canonicalized pages excluded.
    −1.4 points
  • Broken links18 issues
    232 internal links point at 18 broken URLs.
    −0.1 points
  • Links to other sites183 issues
    183 destinations answered with an error, 28 could not be determined (timeouts, rate limits or refusals), 1249 were left unchecked by the per-scan cap, of 300 destinations checked.
    −2.2 points
  • Redirects613 issues
    861 redirecting URLs, 44 of them chained.
    −0.7 points
  • Non-200 responses19 issues
    1452 URLs did not return a 2xx response. 877 of them are pages, 19 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability1,229 issues
    1229 of 3243 indexable pages have indexability warnings. 34 pages noindex by design.
    −3.8 points
  • Image alt text439 issues
    439 of 59158 image references have no alt attribute. 5049 use an empty alt (decorative), which is fine.
  • Heavy assets86 issues
    86 assets larger than 500 KB among 890 fetched assets.
    −6 points
  • Orphan pages927 issues
    927 pages have no internal links pointing at them.
    −1.1 points
  • Sitemap coverage1,670 issues
    19 sitemaps listing 2267 URLs: 510 crawled pages missing, 269 listed URLs broken or redirecting, 891 reachable only via the sitemap.
    −3.1 points
  • Internal link counts375 noted
    Internal link counts for 500 pages; 375 worth a look.
  • Thin content604 issues
    604 of 2490 pages have fewer than 200 words. 787 noindex or canonicalized pages excluded.
    −1.5 points
  • Duplicate content9 issues
    1 group of pages with identical HTML.
  • URL format3,190 noted
    3190 of 4154 page URLs are harder to read, share or cache than they need to be.
  • Canonicals803 noted
    803 of 3277 pages have a canonical worth checking.
  • Robots directives34 noted
    34 pages carry a robots directive; 3243 carry none.
  • Anchor text528 noted
    528 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure1,280 noted
    1280 of 2490 pages could use the title, heading and snippet space better. 787 noindex or canonicalized pages excluded.
  • Image weight and alt length16 noted
    3 images over 100 KB; 13 with alt text over 100 characters.
  • Response anomalies114 noted
    114 URLs answered in a way worth looking at.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 3277 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 positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookies2 noted
    8 cookies set by the site, 2 missing a protective flag; 15 response headers recorded across 5044 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 3277 pages; 3242 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 Insights5 noted
    Mobile performance 55 on average across 5 pages; 5 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this scan sits among all scanned sites

2909 sites, median 80%, average 79%

youtube.com scores 69%, higher than 14% of the 2909 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%: 16 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 55 sites70%: 48 sites71%: 79 sites72%: 77 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 134 sites79%: 112 sites80%: 129 sites81%: 123 sites82%: 136 sites83%: 121 sites84%: 131 sites85%: 106 sites86%: 97 sites87%: 95 sites88%: 82 sites89%: 77 sites90%: 57 sites91%: 61 sites92%: 44 sites93%: 32 sites94%: 25 sites95%: 17 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

Written from an earlier version of the analysis. The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

Your site has a good health score but some issues need addressing, primarily broken links and redirects. Improving title tags, meta descriptions, and fixing orphan pages will enhance SEO performance.

  1. 1

    Fix Broken Links

    Why: 232 internal links point to broken URLs, harming user experience and SEO.

    How: Identify broken links and update or remove them from the site.

    Checks: broken-links

  2. 2

    Reduce Redirects

    Why: 861 URLs redirect, causing delays and poor user experience.

    How: Consolidate or remove unnecessary redirects, especially those in chains.

    Checks: redirects

  3. 3

    Address Non-200 Responses

    Why: 1452 URLs are not returning a valid response, affecting accessibility.

    How: Investigate and fix URLs generating non-200 responses.

    Checks: status-codes

  4. 4

    Enhance Title Tags

    Why: 1976 pages have title issues, impacting visibility in search results.

    How: Add or revise title tags to ensure uniqueness and relevance.

    Checks: titles

  5. 5

    Improve Meta Descriptions

    Why: 1714 pages have meta description issues, reducing click-through rates.

    How: Create unique and descriptive meta descriptions for affected pages.

    Checks: meta-descriptions

  6. 6

    Fix Orphan Pages

    Why: 927 pages lack internal links, making them hard to discover.

    How: Add internal links to orphan pages from related content.

    Checks: orphan-pages

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

This review highlights several security issues on your website, including missing critical HTTP headers and outdated libraries. Addressing these findings will improve your protection against various web security threats.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted on their first request when they miss the HTTPS prefix.

    Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to all responses.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Clickjacking Protection (X-Frame-Options)Medium

    Why it matters: Lack of this header allows embedding of your site in iframes, which can lead to clickjacking attacks.

    Fix: Include the header 'X-Frame-Options: DENY' on all pages.

    Evidence: Clickjacking protection

  3. 3

    Missing SameSite Cookie FlagsMedium

    Why it matters: Cookies without SameSite flag can be sent on cross-site requests, leading to potential CSRF attacks.

    Fix: Set the SameSite attribute on cookies (e.g., 'Set-Cookie: GPS=...; SameSite=Lax') for all relevant cookies.

    Evidence: Cookie flags

  4. 4

    Vulnerable JavaScript LibrariesMedium

    Why it matters: Using an outdated version of AngularJS exposes your site to known vulnerabilities.

    Fix: Upgrade AngularJS to a maintained version or replace it with a newer framework.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Leaked Google API KeysMedium

    Why it matters: Exposing API keys can lead to unauthorized access and misuse.

    Fix: Restrict these API keys in the Google Cloud console by specifying appropriate HTTP referrer restrictions.

    Evidence: Keys and secrets in page code

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Without a referrer policy, sensitive URL parameters can be shared with third-party sites.

    Fix: Implement 'Referrer-Policy: no-referrer' on all pages to limit referrer information.

    Evidence: Referrer policy

  7. 7

    Lack of Permissions PolicyInfo

    Why it matters: Not setting this policy exposes users to potential risks from unused browser features.

    Fix: Add 'Permissions-Policy: geolocation=(self), camera=()' to control feature access.

    Evidence: Permissions policy

What the checks found

  • FoundHTTP Strict Transport SecurityMedium

    756 of 3277 HTML pages send strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://www.youtube.com/creators/ → no strict-transport-security
    • https://www.youtube.com/ads/ → no strict-transport-security
    • https://www.youtube.com/howyoutubeworks/?utm_campaign=ytgen&utm_source=ythp&utm_medium=LeftNav&utm_content=txt&u=https%… → no strict-transport-security
    • https://www.youtube.com/howyoutubeworks/our-policies/ → no strict-transport-security
    • https://www.youtube.com/creators/get-started/ → no strict-transport-security
    • https://www.youtube.com/creators/create/overview/ → no strict-transport-security
    • https://www.youtube.com/creators/create/youtube-create-app/ → no strict-transport-security
    • https://www.youtube.com/creators/create/shorts/ → no strict-transport-security
    • https://www.youtube.com/creators/create/longform/ → no strict-transport-security
    • https://www.youtube.com/creators/create/live/ → no strict-transport-security
    • https://www.youtube.com/creators/create/podcasts/ → no strict-transport-security
    • https://www.youtube.com/creators/create/ai-for-creators/ → no strict-transport-security
  • FoundClickjacking protectionMedium

    719 of 3277 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://www.youtube.com/t/contact_us/ → no x-frame-options
    • https://www.youtube.com/creators/ → no x-frame-options
    • https://www.youtube.com/ads/ → no x-frame-options
    • https://www.youtube.com/t/terms → no x-frame-options
    • https://www.youtube.com/howyoutubeworks/?utm_campaign=ytgen&utm_source=ythp&utm_medium=LeftNav&utm_content=txt&u=https%… → no x-frame-options
    • https://www.youtube.com/howyoutubeworks/our-policies/ → no x-frame-options
    • https://www.youtube.com/creators/get-started/ → no x-frame-options
    • https://www.youtube.com/creators/create/overview/ → no x-frame-options
    • https://www.youtube.com/creators/create/youtube-create-app/ → no x-frame-options
    • https://www.youtube.com/creators/create/shorts/ → no x-frame-options
    • https://www.youtube.com/creators/create/longform/ → no x-frame-options
    • https://www.youtube.com/creators/create/live/ → 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://www.youtube.com/ → no referrer-policy
    • https://www.youtube.com/t/contact_us/ → no referrer-policy
    • https://www.youtube.com/creators/ → no referrer-policy
    • https://www.youtube.com/ads/ → no referrer-policy
    • https://www.youtube.com/t/terms → no referrer-policy
    • https://www.youtube.com/new → no referrer-policy
    • https://www.youtube.com/howyoutubeworks/?utm_campaign=ytgen&utm_source=ythp&utm_medium=LeftNav&utm_content=txt&u=https%… → no referrer-policy
    • https://www.youtube.com/howyoutubeworks/our-policies/ → no referrer-policy
    • https://www.youtube.com/creators/get-started/ → no referrer-policy
    • https://www.youtube.com/creators/create/overview/ → no referrer-policy
    • https://www.youtube.com/creators/create/youtube-create-app/ → no referrer-policy
    • https://www.youtube.com/creators/create/shorts/ → no referrer-policy
  • FoundPermissions policyInfo

    756 of 3277 HTML pages send 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://www.youtube.com/creators/ → no permissions-policy
    • https://www.youtube.com/ads/ → no permissions-policy
    • https://www.youtube.com/howyoutubeworks/?utm_campaign=ytgen&utm_source=ythp&utm_medium=LeftNav&utm_content=txt&u=https%… → no permissions-policy
    • https://www.youtube.com/howyoutubeworks/our-policies/ → no permissions-policy
    • https://www.youtube.com/creators/get-started/ → no permissions-policy
    • https://www.youtube.com/creators/create/overview/ → no permissions-policy
    • https://www.youtube.com/creators/create/youtube-create-app/ → no permissions-policy
    • https://www.youtube.com/creators/create/shorts/ → no permissions-policy
    • https://www.youtube.com/creators/create/longform/ → no permissions-policy
    • https://www.youtube.com/creators/create/live/ → no permissions-policy
    • https://www.youtube.com/creators/create/podcasts/ → no permissions-policy
    • https://www.youtube.com/creators/create/ai-for-creators/ → no permissions-policy
  • FoundCookie flagsMedium

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

    • GPS (set by https://www.youtube.com/) lacks SameSite
    • NID (set by https://www.youtube.com/ads/) lacks SameSite
  • FoundVulnerable JavaScript librariesMedium

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

    • AngularJS 1.6.4 in https://ajax.googleapis.com/ajax/libs/angularjs/1.6.4/angular.min.js: end of life since January 2022; CVE-2022-25844, CVE-2022-25869, CVE-2023-26116, CVE-2023-26117, CVE-2023-26118 and later advisories will never be fixed; fixed in a maintained framework (AngularJS has no fixed release)
  • FoundKeys and secrets in page codeMedium

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

    • Google API key AIzaSy…W8 (39 chars) in https://www.youtube.com/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
    • Google API key AIzaSy…p0 (39 chars) in https://www.youtube.com/howyoutubeworks/static/compiled/shared.index.min.js?cac…: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • NoteContent Security Policy

    A Content-Security-Policy is set, but it allows inline or eval scripts ('unsafe-inline' / 'unsafe-eval'), which removes most of its protection against injected scripts.

    • https://www.youtube.com/ → require-trusted-types-for 'script', base-uri 'self';object-src 'none';script-src 'report-sample' 'nonce-MrrH2XTSdTTgECmlDB8BIQ' 'unsafe-inline' 'strict-dynamic' https: http: 'unsafe-eval';report-uri https://csp.withgoogle.com/csp/youtube_main/strict
    • https://www.youtube.com/t/contact_us/ → require-trusted-types-for 'script', base-uri 'self';object-src 'none';script-src 'report-sample' 'nonce-EAi9Hft0zF3FlXF48Omjlw' 'unsafe-inline' 'strict-dynamic' https: http: 'unsafe-eval';report-uri https://csp.withgoogle.com/csp/youtube_main/strict
    • https://www.youtube.com/ads/ → script-src 'nonce-Hd588gfqbSw4GOoDqPkXNQ' 'report-sample' 'strict-dynamic' 'unsafe-eval' 'unsafe-inline' http: https:; object-src 'none'; report-uri https://csp.withgoogle.com/csp/yt-ce-dev; base-uri 'none'
    • https://www.youtube.com/t/terms → base-uri 'self';object-src 'none';script-src 'report-sample' 'nonce-KLor8rzeRbM6QUuqrVi2_g' 'unsafe-inline' 'strict-dynamic' https: http: 'unsafe-eval';report-uri https://csp.withgoogle.com/csp/youtube_main/strict, require-trusted-types-for 'script'
    • https://www.youtube.com/new → require-trusted-types-for 'script', base-uri 'self';object-src 'none';script-src 'report-sample' 'nonce-0vrWytKdbyuP7V_QfoaqDA' 'unsafe-inline' 'strict-dynamic' https: http: 'unsafe-eval';report-uri https://csp.withgoogle.com/csp/youtube_main/strict
    • https://www.youtube.com/howyoutubeworks/?utm_campaign=ytgen&utm_source=ythp&utm_medium=LeftNav&utm_content=txt&u=https%… → script-src 'nonce-J90umPE49rcNiQTPV0gNug' 'report-sample' 'strict-dynamic' 'unsafe-eval' 'unsafe-hashes' 'unsafe-inline' http: https:; object-src 'none'; report-uri https://csp.withgoogle.com/csp/youtube-marketing; base-uri 'self'
    • https://www.youtube.com/howyoutubeworks/our-policies/ → script-src 'nonce-t0kgG7E68h8GHjp3xaT_6Q' 'report-sample' 'strict-dynamic' 'unsafe-eval' 'unsafe-hashes' 'unsafe-inline' http: https:; object-src 'none'; report-uri https://csp.withgoogle.com/csp/youtube-marketing; base-uri 'self'
    • https://www.youtube.com/creators/get-started/ → script-src 'nonce-SwU3w2GDzNDotoKb3n6K1g' 'report-sample' 'strict-dynamic' 'unsafe-eval' 'unsafe-hashes' 'unsafe-inline' http: https:; object-src 'none'; report-uri https://csp.withgoogle.com/csp/youtube-marketing; base-uri 'self'
    • https://www.youtube.com/creators/create/overview/ → script-src 'nonce-fTXL38Z5Y2zbUbzFdyIXFg' 'report-sample' 'strict-dynamic' 'unsafe-eval' 'unsafe-hashes' 'unsafe-inline' http: https:; object-src 'none'; report-uri https://csp.withgoogle.com/csp/youtube-marketing; base-uri 'self'
    • https://www.youtube.com/creators/create/longform/ → script-src 'nonce-I6oAalmhsU_710kfFaqhgg' 'report-sample' 'strict-dynamic' 'unsafe-eval' 'unsafe-hashes' 'unsafe-inline' http: https:; object-src 'none'; report-uri https://csp.withgoogle.com/csp/youtube-marketing; base-uri 'self'
    • https://www.youtube.com/creators/create/ai-for-creators/ → script-src 'nonce-a3lvkUMIcNffRFVEoBkuqQ' 'report-sample' 'strict-dynamic' 'unsafe-eval' 'unsafe-hashes' 'unsafe-inline' http: https:; object-src 'none'; report-uri https://csp.withgoogle.com/csp/youtube-marketing; base-uri 'self'
    • https://www.youtube.com/creators/grow/overview/ → script-src 'nonce-lmU4a4b68BUC69y0PRWsnw' 'report-sample' 'strict-dynamic' 'unsafe-eval' 'unsafe-hashes' 'unsafe-inline' http: https:; object-src 'none'; report-uri https://csp.withgoogle.com/csp/youtube-marketing; base-uri 'self'
  • NoteThird-party scripts

    Scripts run from 1 other domain 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.gstatic.com (28 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: /login
6 checks passed
  • OKHTTPS

    All 3277 crawled pages were served over HTTPS.

  • OKMIME sniffing protection

    x-content-type-options is set on all 3277 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

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

Own youtube.com?