100 Best Claude Contract and Agreement Drafting Prompts for SEO Agencies

Direct Answer

The best Claude prompts for contract and agreement drafting for SEO agencies are ready-made, copyable templates that cover onboarding, retainers, NDAs, SOWs, change control, liability, data privacy, and compliance. Use them to draft enforceable contracts quickly, but review for jurisdiction-specific requirements.

Introduction

This page is a practical prompt library for contract and agreement drafting in the context of SEO agencies. It provides 100 copyable Claude prompts designed to produce ready-to-use contract language.

The prompts are suitable for agency owners, legal ops teams, and contract managers who need fast, compliant documents without inventing terms from scratch.

How to Use These Claude Prompts

• Replace placeholders like [client], [jurisdiction], [services], and [dates] with your specifics.
• Add constraints such as delivery timelines, data protection requirements, and SLA metrics to tailor prompts.
• Request outputs in a structured format like a contract-ready section plus an exhibit or schedule.
• Where helpful, specify the desired output format, jurisdiction, and applicable laws to improve accuracy.
• Verify outputs with a legal professional before finalizing and filing.

100 Best Claude Contract and Agreement Drafting Prompts for SEO Agencies

1. Client onboarding contract: Role: You are a contract attorney for an SEO agency. Task: Draft a client onboarding contract for a full-service SEO campaign. Context: The client is [client], located in [jurisdiction], with services [services], and a monthly retainer of [retainer]. Output format: a structured contract with defined sections and a signature page. Constraints: include data privacy clause, IP ownership, termination for convenience with 30 days’ notice, and a clear dispute resolution section. Ensure compliance with local laws and include a separate exhibit listing deliverables and reporting cadence.
2. SEO retainer agreement: Role: Legal counsel. Task: Create an SEO retainer agreement for ongoing monthly work. Context: Client [client], industry [industry], expected deliverables [deliverables], payment terms [terms], jurisdiction [jurisdiction]. Output format: full agreement plus schedule of services. Constraints: include milestones, change order process, and data processing addendum. Include a limitation of liability clause and a non-solicitation clause with a 12-month period.
3. NDA for collaborators: Role: Compliance officer. Task: Draft a mutual non-disclosure agreement for sharing confidential SEO techniques with a partner. Context: Parties [agencyName] and [partnerName], purpose [purpose], disclosure types [types], term [term]. Output format: NDAs with defined confidential information, exclusions, and return/destruction obligations. Constraints: include mutual carve-outs for information already public, and a governing law clause.
4. SOW for SEO project: Role: Project manager. Task: Prepare a detailed scope of work for an SEO project. Context: Project name [project], client [client], deliverables [deliverables], timeline [timeline], acceptance criteria [criteria]. Output format: SOW with milestones, responsibilities, acceptance tests, and change control. Constraint: tie payments to milestone completion and include a termination clause for convenience.
5. Managed services addendum: Role: Contracts lead. Task: Draft an addendum to convert a one-time project to managed SEO services. Context: Existing contract [existingContract], new terms [terms], price [price], term [term]. Output format: addendum with amendments, effective date, and integration clause. Constraints: preserve existing indemnities and add a service levels exhibit.
6. Data processing amendment: Role: Privacy officer. Task: Create a data processing amendment for client data handling. Context: Client [client], data types [dataTypes], processing locations [locations], security measures [measures]. Output format: amendment with DPA terms, breach notification timeline, and subprocessor list. Constraints: align with GDPR/CCPA where applicable.
7. Payment terms revision: Role: Finance liaison. Task: Rewrite payment terms for clarity and risk reduction. Context: Invoices issued monthly, late fee [fee], dispute process [process], currency [currency], jurisdiction [jurisdiction]. Output format: revised payment clause and exhibit for invoicing schedule. Constraints: add early payment discount and suspension rights for nonpayment.
8. Termination for convenience: Role: Contract owner. Task: Draft a termination for convenience clause with notice period. Context: Retainer [retainer], notice [noticePeriod], wind-down responsibilities [windDown]. Output format: clause plus transition plan. Constraints: include data transfer of deliverables and post-termination support options.
9. Intellectual property clause: Role: IP counsel. Task: Draft IP ownership and license terms for SEO deliverables. Context: Deliverables [deliverables], client ownership needs [ownership], agency license back [licenseBack]. Output format: clause set with exceptions and moral rights waiver note. Constraints: specify rights to use generic learnings but not client confidential data.
10. Confidential information scope: Role: Compliance analyst. Task: Define confidential information scope for SEO agency projects. Context: Parties [partyA] and [partyB], information types [types], disclosure channels [channels]. Output format: confidentiality clause with exceptions and time limits. Constraints: include trade secrets protection and survival period.
11. Service level exhibit: Role: Service manager. Task: Create a detailed service levels exhibit for SEO campaigns. Context: Services [services], KPIs [KPIs], reporting frequency [frequency], penalties [penalties]. Output format: exhibit attached to contract with measurement methods. Constraints: specify tolerance ranges and escalation steps.
12. Change order process: Role: Change manager. Task: Define a robust change order process for SEO work. Context: Change requests [requests], approval workflow [workflow], impact assessment [impact]. Output format: change control clause plus form template. Constraints: require written approval for any scope increase over 10 percent.
13. Deliverables schedule: Role: Project coordinator. Task: Draft a deliverables schedule for an SEO project. Context: Deliverables list [list], due dates [dates], reviewers [reviewers]. Output format: schedule with dependencies and acceptance milestones. Constraints: align with payment milestones.
14. Indemnity clause: Role: Risk advisor. Task: Draft mutual indemnities for third-party claims arising from SEO activities. Context: Covered claims [claims], exclusions [exclusions], defense costs [costs]. Output format: indemnity clause with carve-outs for gross negligence and willful misconduct. Constraints: cap liability to fees paid in the last twelve months.
15. Limitation of liability: Role: Risk manager. Task: Create liability cap and carve-outs for data breach and IP infringement. Context: Term [term], fees [fees], events [events]. Output format: liability clause with specific caps and exceptions. Constraints: include survival and coordination with DPA.
16. Privacy by design clause: Role: Privacy engineer. Task: Integrate privacy-by-design principles into contracts. Context: Data types [data], processing activities [activities], safeguards [safeguards]. Output format: privacy-by-design clause with audit rights. Constraints: tie to DPA and applicable laws.
17. Audit rights clause: Role: Compliance auditor. Task: Draft audit rights for client to review agency data handling. Context: Frequency [frequency], scope [scope], confidentiality [confidentiality]. Output format: audit clause with notice requirements and remediation period. Constraints: include third-party assessor rules.
18. Subprocessor disclosure: Role: Privacy officer. Task: Create a subprocessor disclosure clause. Context: Subprocessors [subprocessors], notice to client [notice]. Output format: disclosure clause with approval rights and list of subprocessors. Constraints: require annual update and security standards alignment.
19. Non-solicitation clause: Role: HR/legal. Task: Draft a non-solicitation clause for client contracts. Context: Parties [a], [b], duration [duration], geographic scope [scope]. Output format: non-solicitation clause with exceptions and remedies. Constraints: carve-out for general solicitations not targeted at individuals.
20. Data breach notification: Role: Security officer. Task: Draft a data breach notification protocol. Context: breach types [types], notification timeline [timeline], recipients [recipients]. Output format: notification clause with steps and client cooperation requirements. Constraints: comply with applicable breach laws.
21. GDPR addendum: Role: Privacy counsel. Task: Prepare GDPR alignment addendum for EU clients. Context: Data subjects [subjects], transfers [transfers], legal bases [bases]. Output format: GDPR-specific clauses with SCCs and transfer mechanisms. Constraints: ensure data subject rights handling is clear.
22. CCPA/CPRA alignment: Role: Compliance officer. Task: Draft CCPA/CPRA compliant terms for California clients. Context: Personal information [PI], rights requests [requests], verification steps [steps]. Output format: CCPA/addendum with service provider restrictions. Constraints: include opt-out mechanisms and sale restrictions.
23. Sales prospecting restrictions: Role: Compliance advisor. Task: Define permissible outreach in client contracts. Context: channels [channels], consent status [consent], blacklist lists [lists]. Output format: clause restricting or permitting certain outreach. Constraints: respect do-not-contact rules.
24. Return and archival policy: Role: Records manager. Task: Draft data return and archival obligations. Context: deliverables [deliverables], formats [formats], retention period [retention]. Output format: return of data clause plus archival obligations. Constraints: include secure deletion timelines.
25. Conflicts of interest: Role: Legal advisor. Task: Add a conflicts of interest disclosure clause. Context: potential conflicts [conflicts], disclosure method [method]. Output format: conflict disclosure clause with cure options. Constraints: require prompt updates for new conflicts.
26. Client responsibility section: Role: Contract drafter. Task: Define client responsibilities in SEO engagements. Context: tasks [tasks], approval cycles [cycles], access needs [needs]. Output format: client duties clause with consequences for non-performance. Constraints: align with service levels.
27. Intellectual property licenses: Role: IP strategist. Task: Create license terms for agency tools used in client work. Context: tools [tools], usage scope [scope], revocation terms [terms]. Output format: license clauses for tool usage with restrictions. Constraints: clarify ownership of tool outputs vs client data.
28. Warranties and disclaimers: Role: Legal counsel. Task: Prepare warranties and disclaimers for SEO deliverables. Context: deliverables [deliverables], performance expectations [expectations], disclaimers [disclaimers]. Output format: warranties clause with limitation language. Constraints: avoid over-promising results.
29. Compliance checklist: Role: Compliance analyst. Task: Produce a pre-signature contract compliance checklist. Context: jurisdiction [jurisdiction], required clauses [clauses], red flags [flags]. Output format: checklist with yes/no questions. Constraints: include data privacy, anti-bribery, and labor laws.
30. Indemnity caps by service: Role: Risk manager. Task: Tailor indemnity caps to SEO services. Context: service types [types], risk factors [factors], fee basis [fees]. Output format: service-specific indemnity cap language. Constraints: align with liability exclusions.
31. Escrow and transfer: Role: Operations lead. Task: Draft escrow and data transfer procedures. Context: assets [assets], transfer triggers [triggers], escrow terms [terms]. Output format: escrow clause with release conditions. Constraints: include data portability options.
32. SLA breach remedies: Role: Service manager. Task: Define remedies for SLA breaches. Context: breach events [events], notification [notification], cure period [period]. Output format: remedies clause with credit or termination options. Constraints: avoid penalties beyond agreed credits.
33. Open source compliance: Role: Tech lawyer. Task: Ensure open source compliance in contracts. Context: OSS used [OSS], licenses [licenses], attribution requirements [requirements]. Output format: OSS clause with disclosure and risk notes. Constraints: avoid license contamination.
34. Audit trail requirements: Role: Compliance officer. Task: Define audit trail for deliverables and changes. Context: systems [systems], data elements [elements], retention [retention]. Output format: clause requiring immutable logs and access controls. Constraints: specify format and exportability.
35. Export controls: Role: Legal advisor. Task: Add export control compliance to contracts. Context: destinations [destinations], controlled tech [tech], licenses [licenses]. Output format: export control clause with screening steps. Constraints: align with sanctions laws.
36. Non-waiver clause: Role: Contracts specialist. Task: Draft non-waiver clarifications. Context: prior actions [actions], ongoing obligations [obligations]. Output format: non-waiver clause with examples. Constraints: ensure no implied amendments.
37. Assignment and delegation: Role: Legal operations. Task: Create assignment clause for changes in client or agency. Context: parties [parties], notice obligations [notice], successorship [successor]. Output format: assignment language with consent not to be unreasonably withheld. Constraints: prohibit assignment to competitors.
38. Insurance requirements: Role: Risk manager. Task: Specify insurance coverage for SEO engagements. Context: coverage types [types], limits [limits], certificates [certificates]. Output format: insurance clause with proof requirements. Constraints: include cyber liability and professional liability.
39. Publicity rights: Role: Brand manager. Task: Define how contracts handle client testimonials and case studies. Context: media channels [channels], approval process [process], usage period [period]. Output format: publicity clause with consent and revocation options. Constraints: respect client branding guidelines.
40. Frustration and force majeure: Role: Risk counsel. Task: Add force majeure language. Context: events [events], notice [notice], mitigation [mitigation]. Output format: force majeure clause with reset options. Constraints: include pandemics and government actions.
41. Assignment to affiliates: Role: Contracts administrator. Task: Allow assignment to affiliate entities with controls. Context: affiliates [affiliates], consent standard [standard]. Output format: affiliate assignment clause with notice and compliance terms. Constraints: ensure equivalent protections.
42. Background checks: Role: Compliance advisor. Task: Integrate background checks for contractors. Context: contractors [contractors], scope [scope], data handling [dataHandling]. Output format: background check clause with retention of records. Constraints: comply with local employment laws.
43. Conflict resolution: Role: Legal mediator. Task: Define dispute resolution process. Context: forum [forum], escalation path [path], governing law [law]. Output format: dispute clause with tiers of resolution and mediation. Constraints: specify timelines.
44. Insurance certificates: Role: Risk manager. Task: Add certificate request workflow. Context: insured parties [parties], renewal dates [dates], verification steps [steps]. Output format: certificate clause with audit rights. Constraints: require up-to-date certificates before work begins.
45. Subcontractor clauses: Role: Procurement lead. Task: Draft subcontractor terms for SEO work. Context: subcontractors [subs], flow-down terms [flow], monitoring [monitor]. Output format: subcontractor clause with compliance and confidentiality. Constraints: require prime contractor oversight.
46. Work-for-hire clarity: Role: IP counsel. Task: Clarify work-for-hire status for deliverables. Context: deliverables [deliverables], ownership rights [rights], license back [licenseBack]. Output format: work-for-hire clause with exceptions. Constraints: ensure enforceability in jurisdiction.
47. Background data ownership: Role: Data lawyer. Task: Define ownership of pre-existing data used in projects. Context: data sets [datasets], licenses [licenses], attribution [attribution]. Output format: ownership clause with usage rights. Constraints: respect third-party rights.
48. Template library usage: Role: Knowledge manager. Task: Allow use of agency templates in client work. Context: templates [templates], customization limits [limits]. Output format: template usage clause with branding controls. Constraints: prohibit leakage of templates.
49. Acceptance criteria: Role: QA lead. Task: Define client acceptance criteria for deliverables. Context: criteria [criteria], tests [tests], sign-off process [signoff]. Output format: acceptance clause with rejection remedy. Constraints: include iteration limits.
50. Data localization: Role: Privacy officer. Task: Add data localization requirements when needed. Context: data residency [residency], transfers [transfers], client policy [policy]. Output format: localization clause with exceptions. Constraints: align with local laws.
51. Audit remediation plan: Role: Compliance manager. Task: Create remediation plan after audit finding. Context: findings [findings], timeline [timeline], responsible party [party]. Output format: remediation plan with milestones. Constraints: include evidence collection steps.
52. Confidentiality after termination: Role: Legal counsel. Task: Ensure confidentiality survives termination. Context: term [term], information types [types]. Output format: post-termination confidentiality clause with duration. Constraints: include return of materials.
53. Client data segregation: Role: Security architect. Task: Define data segregation in multi-client setups. Context: data sets [datasets], access controls [controls], environments [environments]. Output format: segregation clause with access restrictions. Constraints: require encryption at rest and in transit.
54. Export controls for services: Role: Compliance officer. Task: Ensure service terms respect export controls. Context: destinations [destinations], controlled tech [tech], licenses [licenses]. Output format: export control clause with screening steps. Constraints: update list regularly.
55. Open source disclosure: Role: Legal coder. Task: Include OSS disclosure requirements. Context: OSS used [oss], licenses [licenses], disclosure method [method]. Output format: OSS clause with attribution and risk notes. Constraints: avoid license contamination.
56. Data minimization: Role: Data protection officer. Task: Incorporate data minimization into processing agreements. Context: data types [types], processing purposes [purposes]. Output format: minimization clause with verification steps. Constraints: limit collection to necessary data.
57. Security incident response: Role: Security lead. Task: Draft incident response obligations. Context: incidents [incidents], notice times [times], cooperation [cooperation]. Output format: IR clause with roles and timelines. Constraints: include forensic cooperation and notifications.
58. Record retention schedule: Role: Records manager. Task: Create a data retention schedule. Context: data types [types], retention periods [periods], disposal method [method]. Output format: retention clause with deletion cycles. Constraints: align with legal holds.
59. Third-party risk: Role: Risk analyst. Task: Address third-party risk in contracts. Context: third parties [third], controls [controls], monitoring [monitor]. Output format: risk clause with vendor assessments. Constraints: require background checks for critical vendors.
60. Remedies for non-performance: Role: Project manager. Task: Define remedies for missed milestones. Context: milestones [milestones], impact [impact], cure period [period]. Output format: remedies clause with credits or termination options. Constraints: proportional remedies.
61. Venue and governing law: Role: Legal strategist. Task: Establish venue and governing law. Context: client location [location], agency location [location], dispute forum [forum]. Output format: governing law clause with venue. Constraints: harmonize with international clients.
62. Clarification language: Role: Editor. Task: Add clarifying language to ambiguous terms. Context: terms [terms], potential ambiguities [ambiguities]. Output format: clarification clause with examples. Constraints: avoid legalese overload.
63. Subcontracting flow-down: Role: Contracts administrator. Task: Ensure terms flow down to subcontractors. Context: subcontractors [subs], flow-down list [list]. Output format: flow-down clause with compliance requirements. Constraints: require parity of data protection.
64. Data subject rights: Role: DPO. Task: Define client rights data subjects can exercise. Context: rights [rights], response times [times]. Output format: data subject rights clause with process map. Constraints: align with GDPR/CCPA timelines.
65. Marketing approvals: Role: Compliance lead. Task: Add marketing approvals for client content. Context: channels [channels], approval roles [roles], turnaround [turnaround]. Output format: marketing approvals clause with escalation path. Constraints: avoid misrepresentation.
66. Payment dispute handling: Role: Accounts receivable. Task: Outline dispute handling for invoicing. Context: disputes [disputes], evidence [evidence], timelines [timelines]. Output format: dispute process with resolution steps. Constraints: require written notices.
67. Work restrictions: Role: Compliance officer. Task: Add work restriction clauses for client projects. Context: client locations [locations], prohibited activities [prohibitions]. Output format: work restriction clause with remedies. Constraints: ensure safety standards.
68. Analytics data handling: Role: Data engineer. Task: Define handling of analytics data. Context: data streams [streams], usage [usage], retention [retention]. Output format: analytics data clause with anonymization steps. Constraints: minimize personal data.
69. Template customization limits: Role: Knowledge manager. Task: Limit customization of templates. Context: templates [templates], customization scope [scope], branding [branding]. Output format: template usage limitations clause. Constraints: preserve core protections.
70. Client-side integrations: Role: IT security. Task: Address integrations with client systems. Context: integrations [integrations], access rights [rights], risk controls [controls]. Output format: integration clause with access management. Constraints: require security reviews.
71. Substantive edits policy: Role: Editorial lead. Task: Define policy for material contract edits. Context: edits [edits], approval workflow [workflow]. Output format: policy language with version control. Constraints: avoid retroactive changes.
72. Renewal terms: Role: Contract administrator. Task: Draft renewal terms for ongoing SEO services. Context: renewal notice [notice], price adjustment [adjustment], term length [term]. Output format: renewal clause with auto-renew provisions. Constraints: include opt-out option.
73. Data portability: Role: Data rights lawyer. Task: Ensure data portability rights after contract ends. Context: data formats [formats], transfer methods [methods], timelines [timelines]. Output format: portability clause with delivery method. Constraints: support common formats.
74. Audit readiness: Role: Compliance auditor. Task: Prepare contracts for upcoming audits. Context: audit scope [scope], evidence [evidence], witness [witness]. Output format: audit readiness clause with document list. Constraints: keep records organized.
75. Record customization: Role: Records manager. Task: Allow client-specific record customization. Context: record types [types], customization rules [rules]. Output format: customization clause with approval steps. Constraints: avoid over-sharing.
76. Data minimization during onboarding: Role: DPO. Task: Minimize data collection during client onboarding. Context: onboarding steps [steps], data fields [fields]. Output format: minimization clause with justification. Constraints: collect only necessary data.
77. Third-party cyber insurance: Role: Risk officer. Task: Require cyber insurance for vendors. Context: vendor risk [risk], coverage limits [limits]. Output format: cyber insurance clause with certificate requirements. Constraints: maintain current coverage.
78. Environmental and sustainability clauses: Role: CSR officer. Task: Include ESG considerations in contracts where relevant. Context: client values [values], reporting cadence [cadence]. Output format: ESG clause with alignment steps. Constraints: avoid greenwashing.
79. Remote work terms: Role: HR/legal. Task: Address remote work and data security. Context: locations [locations], devices [devices], access controls [controls]. Output format: remote work clause with security commitments. Constraints: require VPN and device encryption.
80. Intelligent data labeling: Role: Project lead. Task: Define data labeling terms for SEO analytics. Context: data types [types], labeling standards [standards]. Output format: labeling clause with quality controls. Constraints: ensure data privacy.
81. Disaster recovery integration: Role: IT lead. Task: Tie disaster recovery plans to contracts. Context: RPO/RTO [rpo], critical assets [assets]. Output format: DR clause with testing cadence. Constraints: include vendor recovery commitments.
82. Public cloud usage: Role: Cloud architect. Task: Regulate public cloud use in projects. Context: providers [providers], data location [location], security controls [controls]. Output format: cloud usage clause with compliance. Constraints: avoid vendor lock-in.
83. Code of conduct: Role: Compliance trainer. Task: Include a code of conduct for team members. Context: behaviors [behaviors], reporting channels [channels]. Output format: code of conduct clause with violation remedies. Constraints: require acknowledgement.
84. Conflict escalation: Role: Legal ops. Task: Define escalation steps for conflicts. Context: parties [parties], timelines [timelines], escalation paths [paths]. Output format: escalation clause with mediation options. Constraints: include deadline-driven steps.
85. Reminders and notices: Role: Contracts administrator. Task: Draft notice rules for contract communications. Context: delivery method [method], addresses [addresses], deemed receipt [receipt]. Output format: notices clause with timing rules. Constraints: require acknowledged receipt.
86. Joint marketing rights: Role: Partnerships lead. Task: Establish joint marketing terms with clients. Context: campaigns [campaigns], approval rights [rights], attribution [attribution]. Output format: joint marketing clause with branding guidelines. Constraints: respect client ownership of content.
87. Hold harmless clause: Role: Risk attorney. Task: Add hold harmless language in client contracts. Context: activities [activities], limits [limits]. Output format: hold harmless clause with carve-outs. Constraints: align with indemnity framework.
88. Background indemnities: Role: Risk manager. Task: Include background indemnities for agency pre-existing IP. Context: background IP [IP], licenses [licenses]. Output format: background indemnity clause with scope. Constraints: avoid broad leakage.
89. Export control screening: Role: Compliance officer. Task: Implement screening for export-control risks. Context: destinations [destinations], products [products], licenses [licenses]. Output format: screening clause with remediation steps. Constraints: update lists regularly.
90. Subscription termination: Role: Customer success. Task: Terminate subscriptions cleanly when contracts end. Context: user accounts [accounts], data export [export], access revocation [revocation]. Output format: termination clause with data handoff steps. Constraints: secure deletion timelines.
91. KPIs and reporting: Role: Analytics lead. Task: Define KPI reporting requirements for contracts. Context: metrics [metrics], cadence [cadence], format [format]. Output format: reporting clause with dashboards and samples. Constraints: ensure data accuracy.
92. Sustainability reporting: Role: Sustainability lead. Task: Include ESG reporting for marketing campaigns. Context: metrics [metrics], audit rights [rights]. Output format: ESG reporting clause with data sources. Constraints: align with client expectations.
93. Remote worker agreements: Role: HR/legal. Task: Draft agreements for remote SEO staff. Context: locations [locations], equipment [equipment], data access [access]. Output format: remote worker clause with security expectations. Constraints: include tax and payroll considerations.
94. Non-compete safeguards: Role: Legal strategist. Task: Add reasonable non-compete safeguards. Context: duration [duration], geography [geography], scope [scope]. Output format: non-compete clause with carve-outs. Constraints: comply with local laws.
95. Accessibility commitments: Role: Compliance officer. Task: Ensure accessibility standards in deliverables. Context: standards [standards], remediation steps [steps]. Output format: accessibility clause with monitoring. Constraints: include testing methods.
96. Client portal access: Role: IT admin. Task: Define client portal access terms. Context: roles [roles], data separation [dataSeparation], authentication [auth]. Output format: portal access clause with revocation steps. Constraints: multi-factor authentication required.
97. Subcontractor onboarding: Role: Vendor manager. Task: Create onboarding terms for subcontractors. Context: onboarding steps [steps], security training [training], acceptance [acceptance]. Output format: onboarding clause with timelines. Constraints: require NDA and background checks.
98. Intellectual property audits: Role: IP counsel. Task: Schedule IP audits for client deliverables. Context: audit frequency [frequency], scope [scope], remedies [remedies]. Output format: IP audit clause with report delivery. Constraints: protect agency pre-existing IP.
99. Data breach drills: Role: Security officer. Task: Plan data breach tabletop exercises. Context: scenarios [scenarios], participants [participants], evaluation [evaluation]. Output format: drill clause with outcomes. Constraints: publish de-identified results.
100. Final contract template: Role: Contracts leader. Task: Produce a final, reusable SEO contract template. Context: standard terms [terms], client customization options [options], governing law [law]. Output format: template with all core clauses and exhibits. Constraints: maintain modularity for future updates.

Best Practices

• Keep prompts modular by reusing core clauses across contracts.
• Combine prompts to generate comprehensive documents rather than single-section outputs.
• Test prompts with sample client scenarios to ensure practical coverage.
• Refine prompts to reflect local laws and industry standards.
• Include review steps in the outputs to catch ambiguities and ensure compliance.

Common Mistakes to Avoid

• Assuming one contract template fits all clients and jurisdictions.
• Omitting data privacy and security clauses early in the drafting process.
• Not aligning termination, liability, and IP provisions with actual services.
• Using generic terms that do not reflect specific SEO services and deliverables.
• Failing to validate outputs with a qualified attorney before use.

FAQ

What makes these Claude prompts suitable for SEO agency contracts?

They are tailored to typical SEO service agreements, NDAs, SOWs, and compliance needs, with role-based prompts, clear tasks, and ready-to-use outputs.

Can I customize prompts for my jurisdiction?

Yes, replace placeholders like [jurisdiction], [dates], and [terms] to reflect local laws and client needs.

How do I verify the generated contracts are enforceable?

Have a licensed attorney review the outputs, check for jurisdictional requirements, and ensure alignment with client policies.

Do prompts cover data privacy and security?

Yes, multiple prompts include data processing, breach notification, and privacy-by-design clauses.

Are these prompts suitable for large agencies and freelancers?

They scale from small teams to larger agencies by combining prompts and editing exhibits for complexity.

Can I reuse prompts for ongoing engagements?

Yes, many prompts generate boilerplate sections that can be saved as templates for future clients.