Scanned sites / trends.google.com / 2026-09-25-0354

trends.google.com scan from 9/25/2026, 3:54:44 AM

Scan 2026-09-25-0354

Scanned 9/25/2026, 3:54:44 AM, finished 9/25/2026, 3:56:28 AM. Found with 42backlinks.com tool directory

Site: https://trends.google.com/

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

80/ 100Good

On September 25, 2026 the Site Spider crawled 5 pages and 5 assets of trends.google.com, starting from https://trends.google.com/. It scored 80 out of 100, a good result. 6 of 14 checks found something to fix, led by image alt text (18), title tags (3), meta descriptions (2); 8 checks passed. 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 and 1 low findings. See the security findings ↓

Pages crawled
5
Assets fetched
5
Status
Completed
Checks with issues
6 of 14
  • Title tags3 issues
    3 of 3 pages have title issues. 1 noindex or canonicalized page excluded.
  • Meta descriptions2 issues
    2 of 3 pages have meta description issues. 1 noindex or canonicalized page excluded.
  • HeadingsOK
    0 of 3 pages have heading issues. 1 noindex or canonicalized page excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • RedirectsOK
    2 redirecting URLs, 0 of them chained.
  • Non-200 responsesOK
    3 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability1 issue
    1 of 4 indexable pages have indexability warnings.
  • Image alt text18 issues
    18 of 55 image references have no alt attribute. 34 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among the 5 heaviest.
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
  • Sitemap coverage2 issues
    No sitemap found. Tried: https://trends.google.com/sitemap.xml (301), https://trends.google.com/trends/sitemap.xml (404). Add one at /sitemap.xml or list it in robots.txt.
  • Thin contentOK
    0 of 3 pages have fewer than 200 words. 1 noindex or canonicalized page excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1245 sites, median 82%, average 80%

trends.google.com scores 80%, higher than 40% of the 1245 scanned sites. See the full ranking.

032640%: 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%: 1 site36%: 1 site37%: 0 sites38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 2 sites47%: 1 site48%: 1 site49%: 0 sites50%: 3 sites51%: 4 sites52%: 4 sites53%: 3 sites54%: 4 sites55%: 1 site56%: 2 sites57%: 3 sites58%: 8 sites59%: 4 sites60%: 7 sites61%: 9 sites62%: 12 sites63%: 4 sites64%: 9 sites65%: 10 sites66%: 10 sites67%: 16 sites68%: 28 sites69%: 15 sites70%: 26 sites71%: 25 sites72%: 29 sites73%: 28 sites74%: 33 sites75%: 28 sites76%: 42 sites77%: 42 sites78%: 40 sites79%: 36 sites80%: 51 sites81%: 58 sites82%: 54 sites83%: 54 sites84%: 60 sites85%: 53 sites86%: 49 sites87%: 55 sites88%: 58 sites89%: 41 sites90%: 64 sites91%: 40 sites92%: 24 sites93%: 20 sites94%: 16 sites95%: 10 sites96%: 11 sites97%: 4 sites98%: 3 sites99%: 2 sites100%: 23 sites80% 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

The site has several issues to address, notably the sitemap and title problems. Focusing on these key areas will improve SEO significantly.

  1. 1

    Create and Submit a Sitemap

    Why: A sitemap helps search engines index your pages efficiently.

    How: Generate a sitemap and add it at /sitemap.xml. Submit it in Google Search Console.

    Checks: sitemap-coverage

  2. 2

    Fix Title Tag Issues

    Why: Short or duplicate title tags can hurt page ranking and clarity in search results.

    How: Edit the title tags to be unique and longer than 30 characters each.

    Checks: titles

  3. 3

    Address Meta Description Problems

    Why: Duplicate meta descriptions can lead to lower click-through rates.

    How: Create unique meta descriptions for each page, ensuring they're under 160 characters.

    Checks: meta-descriptions

  4. 4

    Resolve Non-200 Responses

    Why: Fixing these URLs will enhance user experience and SEO.

    How: Redirect or fix the broken URLs to return a 200 status code.

    Checks: status-codes

  5. 5

    Optimize Image Alt Text

    Why: Adding alt text improves accessibility and SEO for images.

    How: Add descriptive alt attributes to the 18 images missing alt text.

    Checks: images-alt

  6. 6

    Link to Orphan Page

    Why: Internal linking ensures all pages are discoverable by search engines.

    How: Add at least one internal link to the orphan page.

    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

The site has several important security configurations missing or improperly set. Key issues include lack of HTTP Strict Transport Security (HSTS) and Clickjacking protections. Additionally, cookie settings need to be improved for better security. Recommended changes can help protect your users from potential attacks.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors using HTTP could be intercepted on their first request.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Clickjacking ProtectionMedium

    Why it matters: Pages can be embedded in frames, which may allow clickjacking attacks.

    Fix: Set the header: X-Frame-Options: DENY on all relevant HTML pages.

    Evidence: Clickjacking protection

  3. 3

    Cookies Lack Protective FlagsMedium

    Why it matters: Missing flags can allow scripts to read cookies, increasing risk of attacks.

    Fix: Update cookies to set Secure, HttpOnly, and SameSite attributes.

    Evidence: Cookie flags

  4. 4

    Content Security Policy Allows Inline ScriptsMedium

    Why it matters: Enabling 'unsafe-inline' scripts reduces protection against injected scripts.

    Fix: Revise the Content-Security-Policy to disallow 'unsafe-inline' scripts.

    Evidence: Content Security Policy

  5. 5

    Third-party Scripts Without Subresource IntegrityLow

    Why it matters: Scripts from external domains can be compromised, affecting site security.

    Fix: Implement Subresource Integrity (SRI) for third-party scripts, or specify these hosts in a more restrictive CSP.

    Evidence: Third-party scripts

What the checks found

  • FoundHTTP Strict Transport SecurityMedium

    No HTML page sends strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://trends.google.com/trends/ → no strict-transport-security
    • https://trends.google.com/home → no strict-transport-security
    • https://trends.google.com/tv/?rows=3&cols=4 → no strict-transport-security
    • https://trends.google.com/trending → no strict-transport-security
  • FoundClickjacking protectionMedium

    3 of 4 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://trends.google.com/tv/?rows=3&cols=4 → no x-frame-options
  • FoundCookie flagsMedium

    1 of 1 cookie 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.

    • NID (set by https://trends.google.com/trends/) lacks Secure, SameSite
  • 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://trends.google.com/trends/ → script-src 'report-sample' 'nonce-TvEtFO2Z1t7RxQlrRO1l7g' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /_/TrendsUi/cspreport;worker-src 'self', require-trusted-types-for 'script';report-uri /_/TrendsUi/cspreport
    • https://trends.google.com/home → script-src 'report-sample' 'nonce-CxaALJfhr3To6bBt3DcVIQ' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /_/TrendsUi/cspreport;worker-src 'self', require-trusted-types-for 'script';report-uri /_/TrendsUi/cspreport
    • https://trends.google.com/tv/?rows=3&cols=4 → script-src 'report-sample' 'nonce-ncFXGIUiK4huKvWfuPXo4Q' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /tv/_/TrendsTvUi/cspreport;worker-src 'self', require-trusted-types-for 'script';report-uri /tv/_/TrendsTvUi/cspreport
    • https://trends.google.com/trending → script-src 'report-sample' 'nonce-mVsirUo_e6-mpoPUllxBTw' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /_/TrendsUi/cspreport;worker-src 'self', require-trusted-types-for 'script';report-uri /_/TrendsUi/cspreport
  • NoteThird-party scripts

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

    • www.gstatic.com (1 script tag)
    • www.googletagmanager.com (1 script tag)
9 checks passed, 2 not applicable
  • OKHTTPS

    All 4 crawled pages were served over HTTPS.

  • OKMIME sniffing protection

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

  • OKReferrer policy

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

  • OKPermissions policy

    permissions-policy is set on all 4 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.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

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

  • Not applicableForms over HTTPS

    No forms were found on the sampled pages.

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

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

Own trends.google.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 trends.google.com. Removal needs no account and no proof of purchase.
trends.google.com scan 2026-09-25-0354 | DIY SEO Hub