pages-terms
Original:🇺🇸 English
Translated
When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," or "user agreement."
3installs
Added on
NPX Install
npx skill4agent add kostja94/marketing-skills pages-termsTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Pages: Terms of Service
Guides Terms of Service page content, structure, and compliance.
Initial Assessment
Identify:
- Product type: SaaS, e-commerce, content, marketplace
- Jurisdiction: Governing law, dispute resolution
- User types: B2B, B2C, both
- Indexing: Typically noindex for legal pages
Best Practices
Required Sections
| Section | Content |
|---|---|
| Acceptance | How agreement is formed (signup, use) |
| Service description | What you provide |
| User obligations | Acceptable use, account security |
| Intellectual property | Who owns what |
| Payment | If applicable; billing, refunds |
| Liability | Limitations, disclaimers |
| Termination | When and how accounts end |
| Governing law | Jurisdiction, dispute resolution |
| Changes | How you'll notify of updates |
| Contact | How to reach you about terms |
Content Principles
- Clear language: Plain English where possible
- Structure: Headings, table of contents
- Updates: Date; version if needed
- Legal review: Have lawyer review
Placement
- Footer: Link on every page
- Signup: Require acceptance (checkbox)
- Checkout: Link before purchase
SEO
- Noindex: Common for terms
- Canonical: If multiple versions
Output Format
- Outline (sections)
- Key points per section
- Acceptance flow (signup, checkout)
- Disclaimer: Recommend legal review
Related Skills
- pages-legal: Terms is a legal page type
- pages-privacy: Often linked together
- pages-contact: Contact for terms questions
- seo-technical-indexing: noindex for terms