Scanned sites / trends.google.com / 2026-10-04-0425

trends.google.com scan from 10/4/2026, 4:25:41 AM

Scan 2026-10-04-0425

Scanned 10/4/2026, 4:25:41 AM, finished 10/4/2026, 4:44:06 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.

79/ 100Good

On October 4, 2026 the Site Spider crawled 5 pages and 5 assets of trends.google.com, starting from https://trends.google.com/. It scored 79 out of 100, a good result. 7 of 16 checks found something to fix, led by title tags (3), meta descriptions (2), sitemap coverage (2); 6 checks passed. Most of the points went to title tags (−7.5), meta descriptions (−4), sitemap coverage (−3). 3 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: Medium4 medium and 1 low findings. See the security findings ↓

Pages crawled
5
Assets fetched
5
Status
Completed
Checks with issues
7 of 16
CoverageComplete crawl

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

  • Title tags3 issues
    3 of 3 pages have title issues. 1 noindex or canonicalized page excluded.
    −7.5 points
  • Meta descriptions2 issues
    2 of 3 pages have meta description issues. 1 noindex or canonicalized page excluded.
    −4 points
  • HeadingsOK
    0 of 3 pages have heading issues. 1 noindex or canonicalized page excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites1 issue
    1 destination answered with an error, 6 could not be determined (timeouts, rate limits or refusals), of 26 destinations checked.
    −0.4 points
  • Redirects2 noted
    2 redirecting URLs, 0 of them chained.
  • Non-200 responses3 noted
    3 URLs did not return a 2xx response. 1 of them is a page, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability1 issue
    1 of 4 indexable pages have indexability warnings.
    −2.5 points
  • Image alt text29 issues
    29 of 66 image references have no alt attribute. 34 use an empty alt (decorative), which is fine.
    −2.6 points
  • Heavy assetsOK
    0 assets larger than 500 KB among 5 fetched assets.
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
    −1 points
  • 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.
    −3 points
  • Internal link countsOK
    Internal link counts for 4 pages.
  • 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

2051 sites, median 80%, average 78%

trends.google.com scores 79%, higher than 45% of the 2051 scanned sites. See the full ranking.

0521040%: 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%: 3 sites42%: 0 sites43%: 1 site44%: 1 site45%: 4 sites46%: 4 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 3 sites52%: 9 sites53%: 6 sites54%: 8 sites55%: 6 sites56%: 6 sites57%: 7 sites58%: 14 sites59%: 6 sites60%: 10 sites61%: 14 sites62%: 16 sites63%: 19 sites64%: 16 sites65%: 28 sites66%: 24 sites67%: 39 sites68%: 34 sites69%: 24 sites70%: 46 sites71%: 48 sites72%: 64 sites73%: 57 sites74%: 57 sites75%: 73 sites76%: 83 sites77%: 76 sites78%: 96 sites79%: 78 sites80%: 104 sites81%: 102 sites82%: 99 sites83%: 91 sites84%: 87 sites85%: 73 sites86%: 76 sites87%: 65 sites88%: 68 sites89%: 53 sites90%: 39 sites91%: 39 sites92%: 33 sites93%: 17 sites94%: 14 sites95%: 10 sites96%: 7 sites97%: 8 sites98%: 1 site99%: 2 sites100%: 56 sites79% 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 some SEO issues to address, including duplicate title tags and meta descriptions, indexability warnings, and a missing sitemap. Fixing these will enhance visibility and indexing.

  1. 1

    Add a Sitemap

    Why: Improves search engine indexing.

    How: Create a sitemap and place it at /sitemap.xml. Update robots.txt to reference it if needed.

    Checks: sitemap-coverage

  2. 2

    Fix Title Tag Issues

    Why: Unique titles enhance click-through rates and SEO.

    How: Modify title tags for the affected pages to be unique and descriptive.

    Checks: titles

  3. 3

    Fix Meta Description Issues

    Why: Unique meta descriptions improve search result performance.

    How: Set unique meta descriptions for affected pages.

    Checks: meta-descriptions

  4. 4

    Resolve Indexability Warning

    Why: Ensures pages are indexed properly by search engines.

    How: Add a viewport meta tag to the identified page to address the warning.

    Checks: indexability

  5. 5

    Improve Image Alt Text

    Why: Enhances accessibility and SEO for images.

    How: Add descriptive alt text to the 29 images without attributes.

    Checks: images-alt

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 trends.google.com has several security concerns mainly related to response headers and cookie settings, increasing the risk of interception and clickjacking attacks. Immediate action is needed to enhance the site's security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users typing the site address without HTTPS can be intercepted.

    Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing X-Frame-OptionsMedium

    Why it matters: Pages can be embedded in frames, increasing the risk of clickjacking.

    Fix: Include the header: X-Frame-Options: DENY or SAMEORIGIN.

    Evidence: Clickjacking protection

  3. 3

    Insecure Cookie FlagsMedium

    Why it matters: Cookies can be accessed by scripts or sent over insecure channels.

    Fix: Set the following cookie flags: Secure; HttpOnly; SameSite=Strict.

    Evidence: Cookie flags

  4. 4

    Weak Content Security PolicyMedium

    Why it matters: The current policy permits unsafe inline scripts, reducing its effectiveness.

    Fix: Modify the CSP to remove 'unsafe-inline' and 'unsafe-eval' from script-src.

    Evidence: Content Security Policy

  5. 5

    Third-Party Scripts Lack Subresource IntegrityLow

    Why it matters: Scripts loaded from third-party domains risk altering site security if compromised.

    Fix: Implement Subresource Integrity (SRI) for external scripts or ensure a strong 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/ → require-trusted-types-for 'script';report-uri /_/TrendsUi/cspreport, script-src 'report-sample' 'nonce-h7hJwlDhoYc1ktOJjzElQQ' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /_/TrendsUi/cspreport;worker-src 'self'
    • https://trends.google.com/home → script-src 'report-sample' 'nonce-LWr_LFkEUjzzW0F6DZ4cog' '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-VAtqgzfeXYdtgzbs1EbXig' '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-v4d7JwFyVOCcuRe3m_-2yA' '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-10-04-0425 | DIY SEO Hub