Terms of service link
Whether the crawled pages link terms of service — the document that governs what visitors may do with the site and what the site owes them.
Terms of service — also called terms of use, terms and conditions or, for a shop, general terms of sale — set the rules between the site and its visitors: what they may do with the content and the service, what the operator is liable for, how disputes are settled and which law applies. For a shop or a paid service they are the contract itself; for a simple brochure site they are a good habit rather than a duty.
How SiteScan checks it
Every link on the crawled pages is checked, by address and by anchor text, for markers such as terms, /tos, conditions, agb, regulamin or «соглашение». A matching link on any crawled page counts for the whole site.
- Green — a terms page is linked.
- Amber — none was found. It is a warning, not a fault: plenty of sites have no use for terms of their own.
When you need them
If the site sells, takes bookings, runs accounts or lets users post content, publish terms and link them from the footer and from the checkout or sign-up form, where the visitor accepts them. Give the page a recognisable address such as /terms/ and a clear link text. The privacy policy is a separate document and should stay one.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “Privacy & consent”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data