Scanned sites / trends.google.com / 2026-09-16-0344

trends.google.com scan from 9/16/2026, 3:44:42 AM

Scan 2026-09-16-0344

Scanned 9/16/2026, 3:44:42 AM, finished 9/16/2026, 3:45:53 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 September 16, 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. 6 of 14 checks found something to fix, led by image alt text (33), 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 text33 issues
    33 of 68 image references have no alt attribute. 32 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

1059 sites, median 82%, average 80%

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

027540%: 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%: 1 site46%: 1 site47%: 0 sites48%: 1 site49%: 0 sites50%: 3 sites51%: 3 sites52%: 1 site53%: 1 site54%: 2 sites55%: 1 site56%: 2 sites57%: 3 sites58%: 6 sites59%: 3 sites60%: 5 sites61%: 8 sites62%: 12 sites63%: 4 sites64%: 8 sites65%: 9 sites66%: 7 sites67%: 15 sites68%: 27 sites69%: 12 sites70%: 20 sites71%: 20 sites72%: 23 sites73%: 24 sites74%: 30 sites75%: 27 sites76%: 38 sites77%: 35 sites78%: 31 sites79%: 30 sites80%: 41 sites81%: 52 sites82%: 46 sites83%: 44 sites84%: 50 sites85%: 46 sites86%: 46 sites87%: 46 sites88%: 54 sites89%: 38 sites90%: 51 sites91%: 36 sites92%: 24 sites93%: 17 sites94%: 15 sites95%: 8 sites96%: 9 sites97%: 5 sites98%: 2 sites99%: 1 site100%: 11 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

Your site has several issues that need attention, primarily focusing on redirects, title tags, meta descriptions, and sitemap coverage. Addressing these will enhance your site's SEO performance.

  1. 1

    Fix Redirects

    Why: Two URLs redirect unnecessarily, potentially causing confusion for search engines.

    How: Redirect the URL 'https://trends.google.com/' to the final URL directly. Update or remove the sitemap URL redirect.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Three URLs do not return a 200 status, impacting accessibility and SEO.

    How: Ensure 'https://trends.google.com/sitemap.xml' redirects to an active page or create a proper sitemap at the main URL.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: Three pages have short or duplicate title tags, which can limit search visibility and click-through rate.

    How: Update title tags to be unique and more descriptive, ensuring they exceed 30 characters for better SEO.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: Two pages have duplicate meta descriptions.

    How: Create unique meta descriptions for each page, focusing on differentiating content and relevant keywords.

    Checks: meta-descriptions

  5. 5

    Create Sitemap

    Why: No sitemap found, which hinders search engines' ability to discover pages effectively.

    How: Generate a sitemap and upload it to 'https://trends.google.com/sitemap.xml'. Link it in the robots.txt file as well.

    Checks: sitemap-coverage

  6. 6

    Add Image Alt Text

    Why: 33 out of 68 images lack alt text, which is important for accessibility and SEO.

    How: Add descriptive alt attributes to images that currently have none, ensuring they reflect the image content.

    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 has several security gaps that need addressing to protect users. Key issues include missing HSTS, lacking protection against clickjacking, insecure cookie flags, and a weak Content Security Policy. These issues expose users to potential attacks and data theft.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: No HSTS headers mean users can be intercepted on their first request without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Clickjacking ProtectionMedium

    Why it matters: Some pages lack X-Frame-Options, allowing potentially malicious framing.

    Fix: Include 'X-Frame-Options: DENY' in HTTP response headers for all pages.

    Evidence: Clickjacking protection

  3. 3

    Insecure Cookie FlagsMedium

    Why it matters: Cookies without Secure, HttpOnly, and SameSite attributes are vulnerable to interception and cross-site attacks.

    Fix: Set cookie attributes: 'Set-Cookie: NID=<value>; HttpOnly; Secure; SameSite=Lax'.

    Evidence: Cookie flags

  4. 4

    Weak Content Security PolicyMedium

    Why it matters: Allowing 'unsafe-inline' and 'unsafe-eval' undermines the effectiveness of the CSP against injected scripts.

    Fix: Update CSP to remove 'unsafe-inline' and 'unsafe-eval' and only use scripts from trusted sources.

    Evidence: Content Security Policy

  5. 5

    Third-Party Scripts Without Integrity ChecksLow

    Why it matters: Scripts from external domains without SRI are vulnerable to compromise and can be altered.

    Fix: Implement Subresource Integrity (SRI) for all external scripts or restrict them via Content Security Policy.

    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-nRldiiKHM11OZudDpJIm4Q' '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 → require-trusted-types-for 'script';report-uri /_/TrendsUi/cspreport, script-src 'report-sample' 'nonce-oIRA__UyS_mEh5FP6F4D_g' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /_/TrendsUi/cspreport;worker-src 'self'
    • https://trends.google.com/tv/?rows=3&cols=4 → script-src 'report-sample' 'nonce-Q98G8OTMhfdWJnJ4KLQb6w' '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 → require-trusted-types-for 'script';report-uri /_/TrendsUi/cspreport, script-src 'report-sample' 'nonce-ZvasCAyDDI52INIMqou6tQ' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /_/TrendsUi/cspreport;worker-src 'self'
  • 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.

This report was produced by the DIY SEO Hub Site Spider crawling trends.google.com from its public pages. Anyone can run a scan of any site they own or are authorised to check. Is this your site? Claim it to manage the listing, or ask for removal through the support form.

trends.google.com scan 2026-09-16-0344 | DIY SEO Hub