Scanned sites / trends.google.com / 2026-09-19-0347
trends.google.com scan from 9/19/2026, 3:47:38 AM
Scan 2026-09-19-0347
Scanned 9/19/2026, 3:47:38 AM, finished 9/19/2026, 3:50:52 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.
On September 19, 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 (35), 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 issues3 of 3 pages have title issues. 1 noindex or canonicalized page excluded.
- Meta descriptions2 issues2 of 3 pages have meta description issues. 1 noindex or canonicalized page excluded.
- HeadingsOK0 of 3 pages have heading issues. 1 noindex or canonicalized page excluded.
- Broken linksOK0 internal links point at 0 broken URLs.
- RedirectsOK2 redirecting URLs, 0 of them chained.
- Non-200 responsesOK3 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability1 issue1 of 4 indexable pages have indexability warnings.
- Image alt text35 issues35 of 70 image references have no alt attribute. 32 use an empty alt (decorative), which is fine.
- Heavy assetsOK0 assets larger than 500 KB among the 5 heaviest.
- Orphan pages1 issue1 page have no internal links pointing at them.
- Sitemap coverage2 issuesNo 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 contentOK0 of 3 pages have fewer than 200 words. 1 noindex or canonicalized page excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1099 sites, median 82%, average 80%
trends.google.com scores 79%, higher than 36% of the 1099 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 good health score, but there are key issues to address including redirects, non-200 responses, title/meta description problems, and no sitemap. Prioritize these fixes for better SEO performance.
- 1
Fix Redirects
Why: Redirections can cause crawling issues.
How: Update the URL for /sitemap.xml directly to point to the correct sitemap path.
Checks: redirects
- 2
Resolve Non-200 Responses
Why: These errors prevent users from accessing important pages.
How: Directly update the requests leading to 301 and 404 errors to ensure they return a valid 200 status.
Checks: status-codes
- 3
Improve Title Tags
Why: Short and duplicate title tags can confuse search engines.
How: Rewrite titles to be unique and over 30 characters, e.g., 'Google Trends - Discover What's Trending'.
Checks: titles
- 4
Enhance Meta Descriptions
Why: Duplicate and short descriptions affect CTR.
How: Create unique meta descriptions for each page with a length of 50-160 characters.
Checks: meta-descriptions
- 5
Create a Sitemap
Why: A sitemap helps search engines discover and index your pages.
How: Generate a sitemap and add it to https://trends.google.com/sitemap.xml.
Checks: sitemap-coverage
- 6
Add Alt Text to Images
Why: Alt text improves accessibility and SEO.
How: Add descriptive alt attributes to the 35 images lacking them, e.g., 'Google logo'.
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 crawlThe website has several important security issues that need to be addressed. Most notably, it lacks strict transport security, clickjacking protection, and secure cookie flags. Additionally, its Content Security Policy allows unsafe script execution, increasing the risk of script injection attacks.
- 0 high
- 4 medium
- 1 low
- 0 info
- 1
Missing HTTP Strict Transport SecurityMedium
Why it matters: Without HSTS, visitors may be intercepted on the first request when accessing the site without HTTPS.
Fix: Implement the HSTS header: 'Strict-Transport-Security: max-age=31536000; includeSubDomains'.
Evidence: HTTP Strict Transport Security
- 2
No Clickjacking ProtectionMedium
Why it matters: The absence of X-Frame-Options allows the page to be embedded in frames, posing clickjacking risks.
Fix: Add the X-Frame-Options header: 'X-Frame-Options: DENY'.
Evidence: Clickjacking protection
- 3
Cookie Flags MissingMedium
Why it matters: The cookie lacks Secure, HttpOnly, and SameSite flags, risking cookie theft and Cross-Site Request Forgery.
Fix: Set cookie flags: 'Set-Cookie: NID=<value>; Secure; HttpOnly; SameSite=Strict'.
Evidence: Cookie flags
- 4
Insecure Content Security PolicyMedium
Why it matters: Allowing 'unsafe-inline' and 'unsafe-eval' in CSP significantly reduces its effectiveness against attacks.
Fix: Revise the CSP to remove 'unsafe-inline' and 'unsafe-eval'.
Evidence: Content Security Policy
- 5
Third-party Scripts Without Subresource IntegrityLow
Why it matters: Running scripts from external domains without Subresource Integrity can lead to content manipulation if those domains are compromised.
Fix: Consider adding Subresource Integrity or adjusting the CSP to specify trusted domains.
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-CQkdmxKShBDEGp60CYqMxg' '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-FZBkbxMuRYzDWDyum2uqLg' '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-V1p8oxQNlrCmoJUzFSguEQ' '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-nqyfnZo6P-yl85Es6i1mMQ' '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.