100 Best Claude Online Review Response Prompts for SEO Agencies

Direct Answer

The best Claude prompts for online review response for SEO agencies are a curated set of precise, role-based prompts designed to craft thoughtful, compliant, and conversion-friendly replies to reviews. Each prompt specifies the role, task, context, output format, and constraints to ensure consistent messaging and SEO benefits while protecting brand voice.

Introduction

This page is a practical prompt library optimized for online review responses tailored to SEO agencies. It helps teams respond to reviews with strategies that enhance trust, reputation, and local search signals.

The prompts are built for agency teams, copywriters, and client managers who need ready-to-use responses that scale across multiple clients and locations without sacrificing quality or compliance.

How to Use These Claude Prompts

• Replace placeholders like [city], [region], and [ClientName] to fit your client. Add or adjust constraints to align with your brand voice and policy. Request outputs in your preferred formats such as bullet lists, short paragraphs, or Q&A style. Verify outputs for accuracy, tone, and compliance before posting. Use the prompts to standardize responses while allowing quick customization for individual reviews.

100 Best Claude Online Review Response Prompts for SEO Agencies

1. Standard positive response: You are an experienced client-review specialist. Task: draft a concise, warm response to a five-star review for a local SEO client. Context: the client helps small businesses improve organic visibility in [city]. Output format: bullet list with five elements: appreciation, client impact, quick clarifying question, offer of future support, sign-off. Constraints: maintain professional tone, include the client name [ClientName], and keep under 120 words.
2. Polite negative reply: Role: customer service and reputation manager. Task: compose a constructive reply to a three-star review that mentions slow response times. Context: the client is an SEO agency serving SMBs in [region]. Output format: paragraph with 8 sentences max. Constraints: acknowledge frustration, explain steps taken, offer direct contact, invite further feedback, end with an invitation to reconnect.
3. Negative review escalation: Role: escalation specialist for SEO agency. Task: transform a negative review into a learning point while preserving the brand. Context: reviewer claims unexpected charges. Output format: two-paragraph response plus a 3-bullet plan for improvement. Constraints: avoid legal language, propose a refund or credit if appropriate, reference policy link.
4. Success story pull: Role: marketing writer. Task: craft a reply highlighting measurable results from a satisfied client who saw a 40 percent traffic increase after a campaign. Context: audience includes local business owners in [city]. Output format: single-paragraph reply plus a brief statistic box in brackets. Constraints: keep non-promotional, emphasize partnership and next steps.
5. FAQ style reply: Role: customer support. Task: respond to a review asking about pricing tiers. Context: SEO service packages for small businesses. Output format: Q&A style in two short paragraphs. Constraints: clearly state tier names, price ranges, and a link to the pricing page. Include a friendly CTA.
6. Process transparency: Role: brand journalist. Task: reply to a review requesting more detail about delivery timelines. Context: ongoing SEO project for a local retailer. Output format: bullet list with steps and estimated times for each milestone. Constraints: avoid jargon, include a contact option for urgent questions.
7. Case study tease: Role: content strategist. Task: respond to a positive review by teasing a forthcoming case study. Context: client success in regional market. Output format: two sentences plus one teaser sentence. Constraints: no spoilers, invite to subscribe for updates.
8. Seasonal offer: Role: promotions manager. Task: reply to a seasonal review with a limited-time discount offer for ongoing SEO retainers. Context: business in [city]. Output format: short paragraph with a call-to-action and expiry date. Constraints: mention discount percentage, eligible services, and booking method.
9. General praise: Role: client liaison. Task: thank a reviewer who praises communication and transparency. Context: multiple ongoing projects. Output format: single-paragraph message with appreciation, brief project update, and invitation for further feedback. Constraints: keep under 90 words.
10. Service misalignment: Role: account manager. Task: respond to a review stating the scope didn’t meet expectations. Context: requested swift wins but strategy changed. Output format: two short paragraphs and a one-sentence commitment to align. Constraints: acknowledge misalignment, propose a revised plan within 48 hours.
11. On-site keyword note: Role: SEO specialist. Task: respond to review asking if on-site optimization was performed. Context: local business campaign. Output format: concise answer with a mini audit checklist. Constraints: provide specific on-page items checked and next steps.
12. Link-building concern: Role: outreach coordinator. Task: address a review criticizing link quality. Context: client focuses on sustainable, safe link-building. Output format: bullet list explaining approach, quality criteria, and monitoring plan. Constraints: avoid blaming, emphasize policy adherence.
13. Response timing: Role: operations lead. Task: respond to a review complaining about response time. Context: high-volume inquiries. Output format: two short paragraphs plus a 2-item plan to improve. Constraints: set realistic response SLA expectations.
14. Client appreciation: Role: client relationship manager. Task: craft a message thanking a long-term client for loyalty. Context: 2-year collaboration in SEO. Output format: warm note with a small update about latest results. Constraints: invite continued partnership.
15. Tiered service explain: Role: sales engineer. Task: explain differences between service tiers in a reply to a review. Context: new business owner reading reviews in [city]. Output format: bullet list with tier names, features, and typical results. Constraints: avoid jargon, include a CTA to compare plans.
16. Transparency about charges: Role: billing liaison. Task: address a review mentioning hidden fees. Context: monthly retainers for SEO. Output format: two paragraphs clarifying pricing structure and how to avoid surprises. Constraints: reference official pricing page.
17. Support escalation: Role: customer support lead. Task: provide a path for unresolved support issues mentioned in a review. Context: ongoing technical SEO audit. Output format: numbered steps 1-4 with timelines. Constraints: ensure escalation to senior team if needed.
18. Expanded services: Role: growth manager. Task: respond to a positive review that suggests adding local content services. Context: small business clients in [region]. Output format: brief acknowledgement, followed by a recommended next-step plan. Constraints: propose a pilot project.
19. Process proof: Role: case writer. Task: reply to a review asking for proof of results. Context: client visible metrics in report. Output format: short paragraph with reference to a shared attachment and offer to present live metrics. Constraints: avoid confidential data.
20. SLA reminder: Role: operations. Task: respond to a review mentioning SLA expectations. Context: fast-moving SEO projects. Output format: bullet list outlining SLAs and a contact point for breaches. Constraints: include business hours.
21. Accessibility tone: Role: accessibility advocate. Task: reply to a review using inclusive language. Context: diverse client base. Output format: two-paragraph response and a one-sentence commitment to accessibility. Constraints: avoid jargon and bias.
22. Crisis calm: Role: brand guardian. Task: respond to a negative review amid a local incident. Context: agency values community trust. Output format: empathetic two-paragraph reply plus a call-to-action for direct conversation. Constraints: avoid political references.
23. Feedback loop: Role: QA specialist. Task: request specific feedback from a client who left a vague review. Context: ongoing SEO audit. Output format: list of 5 targeted questions. Constraints: ask for metrics, timeline, and preferred communication channel.
24. Competition comparison: Role: market analyst. Task: respond to a review mentioning competitors. Context: owner evaluating multiple agencies. Output format: balanced paragraph with differentiators and an invitation to discuss in a call. Constraints: avoid calling out competitors directly.
25. Agency philosophy: Role: brand storyteller. Task: answer a review by describing the agency's approach to ethical SEO. Context: audience of risk-aware business owners. Output format: two short paragraphs. Constraints: include a short ethics statement.
26. Milestone update: Role: project manager. Task: update a reviewer on progress toward quarterly goals. Context: ongoing local SEO campaign. Output format: bullet list with 3 key milestones and dates. Constraints: keep concise.
27. Testimonials request: Role: client success. Task: encourage a happy reviewer to share a testimonial. Context: satisfied client in [city]. Output format: two-sentence prompt for them to copy-paste. Constraints: provide a link or form.
28. Referral incentive: Role: growth marketer. Task: announce a referral incentive in response to a positive review. Context: B2B SEO agency. Output format: short paragraph with terms and a CTA. Constraints: limit to one paragraph.
29. Seasonal content push: Role: content lead. Task: suggest adding seasonal local content in reply to a positive review. Context: restaurant clients in [city]. Output format: 3-bullet plan with ideas and a timing window. Constraints: propose quick wins.
30. Compliance check: Role: compliance officer. Task: ensure the response adheres to advertising rules. Context: claims about rankings. Output format: two short paragraphs and a compliance checklist. Constraints: avoid guarantees.
31. Localization note: Role: localization expert. Task: tailor the response for a neighborhood audience. Context: business hub in [neighborhood]. Output format: paragraph plus 2 neighborhood-specific phrases. Constraints: maintain brand voice.
32. Educational angle: Role: educator. Task: explain an SEO concept cited by a reviewer in simple terms. Context: owner with basic knowledge. Output format: concise definition and 2 example outcomes. Constraints: avoid technical jargon.
33. Visual prompt: Role: designer. Task: request permission to attach a small visual map of results in the reply. Context: local business SEO. Output format: two sentences requesting consent and describing the graphic. Constraints: avoid image hosting links.
34. Voice tuning: Role: copywriter. Task: adjust tone for a formal B2B client review. Context: enterprise-level projects in [region]. Output format: 1 paragraph with formal tone and a single CTA. Constraints: preserve authority.
35. CTA optimization: Role: conversion specialist. Task: add a call-to-action that invites scheduling a discovery call in a review response. Context: mid-funnel leads. Output format: one short paragraph with a link to calendar. Constraints: avoid hard sell.
36. Risk mitigation: Role: risk manager. Task: address a review raising concerns about data privacy. Context: SEO data handling. Output format: brief paragraph and a bulleted privacy practices list. Constraints: reference compliance standards.
37. Technical audit note: Role: technicalSEO lead. Task: reply to a review requesting a copy of the audit steps. Context: project in progress. Output format: numbered list of steps with approximate durations. Constraints: share non-sensitive methodology.
38. Reporting clarity: Role: data analyst. Task: respond to a reviewer asking for clearer reporting. Context: monthly SEO reporting. Output format: template-like response with 3 report sections. Constraints: include a brief glossary.
39. Client onboarding: Role: onboarding coordinator. Task: respond to a review praising the onboarding experience. Context: new client in [city]. Output format: two-paragraph welcome with next steps list. Constraints: include a welcome packet link.
40. Process role clarity: Role: project lead. Task: clarify who does what in the engagement. Context: small team. Output format: bullet list of roles and owners. Constraints: include escalation path.
41. Public notice: Role: communications manager. Task: reply to a review referencing public events. Context: community involvement. Output format: two short paragraphs with a note on corporate responsibility. Constraints: avoid political content.
42. Performance snapshot: Role: analytics lead. Task: share a mini performance snapshot in the reply. Context: client campaign in progress. Output format: one paragraph with key metric bullets in brackets. Constraints: no raw data beyond 3 metrics.
43. Learning prompt: Role: trainer. Task: present a learning takeaway from a positive review. Context: coaching junior staff. Output format: one-sentence takeaway and a 2-sentence example.
44. Apology plus remedy: Role: customer advocate. Task: apologize for a service hiccup and propose remedy. Context: weekly reporting delay. Output format: two short paragraphs and a remedy plan. Constraints: include a timeline.
45. Client history: Role: account historian. Task: reference past projects in a current reply to reinforce trust. Context: multiple clients. Output format: 3-sentence paragraph linking to past successes. Constraints: avoid private data.
46. Local market tone: Role: localization editor. Task: adjust reply to resonate with [city] business owners. Context: competitive market. Output format: paragraph with 2 local phrases. Constraints: maintain brand voice.
47. Content collaboration: Role: partnerships manager. Task: invite a reviewer to collaborate on a content piece. Context: industry topic. Output format: two-sentence invitation with collaboration details. Constraints: propose a mutual benefit.
48. Education offer: Role: education outreach. Task: offer a free SEO mini-guide in response to a reviewer. Context: improving client learning. Output format: short paragraph with download link. Constraints: ensure compliance.
49. Multichannel followup: Role: growth hacker. Task: outline a follow-up plan after a positive review across channels. Context: email, LinkedIn, and phone. Output format: bullet list of steps and timelines. Constraints: keep it concise.
50. Data-access request: Role: data privacy officer. Task: respond to a reviewer asking for data access. Context: ongoing audit. Output format: two paragraphs and a secure access instruction set. Constraints: verify identity before share.
51. Problem summary: Role: project navigator. Task: summarize a complex feedback into a simple problem statement. Context: SEO project constraints. Output format: single sentence problem statement plus 2 possible solutions. Constraints: avoid blaming.
52. Content calendar: Role: content planner. Task: propose a month-long local content calendar in reply to a review. Context: business in [city]. Output format: 7-item calendar with themes and dates. Constraints: ensure relevance.
53. Brand voice alignment: Role: voice custodian. Task: ensure the reply matches the agency's approved voice. Context: consistency across reviews. Output format: short paragraph and 2 voice-check questions. Constraints: maintain tone.
54. Bridge to case study: Role: strategist. Task: invite reviewer to view a relevant case study. Context: similar client success. Output format: two sentences with link reference. Constraints: avoid spoilers.
55. Live metrics offer: Role: data presenter. Task: offer to present live metrics in a call. Context: potential client reading reviews. Output format: one paragraph plus call-to-action for a demo. Constraints: respect privacy.
56. Process improvement: Role: process engineer. Task: acknowledge feedback about workflow and outline improvements. Context: QA audit. Output format: bullet list of 4 improvements with owners. Constraints: include expected impact.
57. Accessibility data: Role: accessibility consultant. Task: explain how reviews will be accessible to screen readers. Context: diverse user base. Output format: short explanation with 2 examples. Constraints: include compliance note.
58. Regional success: Role: regional manager. Task: share regional wins in response to a review. Context: multiple locales in [region]. Output format: 3-sentence update with a regional map link. Constraints: avoid confidential client data.
59. Template invitation: Role: template designer. Task: offer a reusable response template in reply to a review. Context: recurring feedback. Output format: 1 short paragraph and a link to template download. Constraints: ensure customization fields.
60. Policy reference: Role: policy advisor. Task: reference internal policy in a review reply where appropriate. Context: pricing or data usage. Output format: two short paragraphs and policy citation. Constraints: keep it accessible.
61. Industry expert: Role: industry commentator. Task: provide an expert-approved takeaway in response to a review. Context: SEO trends discussion. Output format: two paragraphs with 3 bullet insights. Constraints: cite sources if mentioned.
62. Security reassurance: Role: security officer. Task: reassure about data security in responses. Context: client data handling. Output format: brief paragraph plus 4 security practices. Constraints: no technical jargon.
63. Workshop offer: Role: events lead. Task: invite to a free workshop after a positive review. Context: local SMBs. Output format: 2-sentence invitation plus registration link. Constraints: limit to one paragraph.
64. Campaign alignment: Role: campaign manager. Task: align the reply with ongoing marketing campaigns. Context: cross-channel efforts in [city]. Output format: brief paragraph and a 2-point alignment note. Constraints: avoid overpromising.
65. Niche services: Role: service strategist. Task: mention a niche SEO service in response to a review. Context: specialized client needs. Output format: 2-sentence mention plus a CTA to learn more. Constraints: avoid hype.
66. Technical glossary: Role: trainer. Task: provide a glossary for technical terms used in the reply. Context: reviewer unfamiliar with jargon. Output format: list of 5 terms and simple definitions. Constraints: keep concise.
67. Problem-solution pairing: Role: consultant. Task: pair a reviewer problem with a concrete solution. Context: local e-commerce client. Output format: two-sentence problem-solution pair plus a next-step call.
68. Award mention: Role: PR lead. Task: mention a recent industry award in the reply. Context: trust-building. Output format: brief paragraph with award name and relevance. Constraints: no bragging.
69. Data-sharing opt-in: Role: compliance. Task: offer to share anonymized data highlights. Context: social proof in a review. Output format: two sentences and a link to data privacy page. Constraints: ensure anonymization.
70. Client success map: Role: strategist. Task: describe a simple client success map in reply to a review. Context: onboarding to outcomes. Output format: 4-step map with expected timing. Constraints: avoid overpromising.
71. Language tuning: Role: copywriter. Task: adapt language for non-native English readers. Context: international client base. Output format: 2-sentence version plus 3 simplified terms. Constraints: clarity first.
72. Local collaboration: Role: partnerships. Task: propose a joint local event in response to a positive review. Context: [city] business community. Output format: 3-bullet plan with roles and dates. Constraints: mutually beneficial.
73. Client advisory: Role: advisory board member. Task: invite reviewer to join a client advisory panel. Context: long-term client. Output format: two sentences with benefit outline. Constraints: exclusive access.
74. Quality claim: Role: quality lead. Task: address a review claiming inconsistent results. Context: multi-client project. Output format: brief explanation and a 2-item corrective plan. Constraints: provide measurable targets.
75. Content rights: Role: legal liaison. Task: reassure about rights to content used in campaigns. Context: asset usage. Output format: two short paragraphs and a rights note. Constraints: avoid legal boilerplate.
76. Onboarding timeline: Role: onboarding lead. Task: share a predictable timeline in reply to a review. Context: new client onboarding. Output format: 3 milestones with dates. Constraints: be realistic.
77. Stakeholder update: Role: project updater. Task: give a quick update for stakeholders who read reviews. Context: board audience. Output format: 2 short paragraphs with KPI bullets. Constraints: not client-specific.
78. Ethical prompt: Role: ethics officer. Task: confirm ethical guidelines followed in SEO work. Context: client case. Output format: two sentences with a brief ethics statement. Constraints: none.
79. Cross-sell pitch: Role: sales recruiter. Task: propose a cross-sell in a reply to a positive review. Context: existing client. Output format: one paragraph with 2 relevant services and CTA. Constraints: avoid pressure.
80. Time zone note: Role: client liaison. Task: acknowledge time-zone differences in communication. Context: remote teams serving [region]. Output format: short paragraph and tips for faster replies. Constraints: include preferred contact window.
81. Resource offer: Role: client success. Task: offer resources like templates in reply to a reviewer. Context: people learning SEO. Output format: two sentences and a download link. Constraints: ensure accessibility.
82. Technical debt remind: Role: engineering lead. Task: remind about reducing technical debt in response to a review. Context: ongoing optimization. Output format: 3 bullet points and a suggested plan. Constraints: focus on value.
83. Checklist style: Role: QA. Task: provide a small checklist of actions taken during the engagement. Context: client asks for transparency. Output format: numbered checklist 1-5. Constraints: include results where possible.
84. Risk-free offer: Role: marketing. Task: present a risk-free trial option in reply to a review. Context: potential client considering switching. Output format: 2 sentences with terms and conditions. Constraints: limit to 30 days.
85. Sustainability note: Role: brand guardian. Task: mention eco-friendly practices in the reply. Context: conscious business owners. Output format: two short paragraphs. Constraints: be authentic.
86. Portfolio tease: Role: outreach. Task: invite reviewer to view a portfolio of client wins. Context: new prospects in [city]. Output format: two sentences with link. Constraints: ensure accessibility.
87. Payment clarity: Role: billing. Task: clarify payment terms in response to a review. Context: retainer model. Output format: two short paragraphs with payment options. Constraints: avoid coercion.
88. Cite client benefit: Role: content writer. Task: explicitly name a client benefit noted by reviewer. Context: persuasive response. Output format: one paragraph with 2 benefit bullets. Constraints: keep factual.
89. Problem with scope: Role: project lead. Task: address confusion about scope in a review. Context: revised strategy. Output format: two short paragraphs and a revised scope outline. Constraints: timeline included.
90. Industry tip: Role: advisor. Task: share a practical SEO tip relevant to the reviewer’s industry. Context: local business. Output format: short tip and example outcome. Constraints: actionable.
91. Success metric request: Role: analyst. Task: ask for permission to share future metrics in a follow-up review. Context: ongoing campaign. Output format: two questions and a brief rationale. Constraints: privacy mindful.
92. Social proof: Role: marketing. Task: reference a publicly verifiable success metric in the reply. Context: case-like statement. Output format: one paragraph with metric and a CTA to learn more. Constraints: avoid confidential data.
93. Workflow visibility: Role: operations. Task: describe the workflow visible to clients in the reply. Context: transparency goals. Output format: 4-line summary. Constraints: non-technical.
94. Customer success story: Role: storyteller. Task: outline a micro-story of a client journey in the reply. Context: reader in [city]. Output format: 2 short paragraphs. Constraints: focus on outcome.
95. Audit-ready: Role: auditor liaison. Task: offer to generate an audit-ready summary in response to a review. Context: client project. Output format: 1 paragraph and a 1-page summary outline. Constraints: avoid exposing client data.
96. Mentorship offer: Role: community manager. Task: invite a reviewer to mentor junior team members. Context: industry peers. Output format: two sentences with signup details. Constraints: non-binding.
97. Guarantee note: Role: legal-friendly copywriter. Task: state a clear guarantee or policy in the reply. Context: service delivery. Output format: two short paragraphs. Constraints: be precise and compliant.
98. Multi-language: Role: localization. Task: offer translations of the reply in 2 common languages for the client base. Context: diverse city. Output format: one paragraph per language. Constraints: ensure accuracy.
99. Icon prompt: Role: design lead. Task: suggest an icon to accompany the response in the client portal. Context: visual branding. Output format: 1 sentence description of the icon and its meaning. Constraints: keep it simple.
100. Final call: Role: close-out specialist. Task: end with a final call to action for ongoing partnership. Context: continuous optimization. Output format: single paragraph with 2 bullet points for next steps. Constraints: invite conversation.

Best Practices

• Keep responses concise and client-specific to avoid generic language. Use a consistent tone across all replies to strengthen brand identity. Include a clear call to action where appropriate, such as inviting further discussion or providing a link for more information. Regularly review and update prompts to reflect policy changes and evolving SEO best practices.
• Store prompts in a centralized library and train staff to adapt them for different clients while preserving safety and compliance.

Common Mistakes to Avoid

• Using overly promotional language that can appear insincere. Ignoring reviewer concerns or failing to acknowledge issues. Providing unsafe or disclosive information that breaches privacy. Failing to include a clear call to action or next steps. Using a rigid template that ignores context of the review.

FAQ

What makes a good review response for an SEO agency?

A good response acknowledges the reviewer, addresses concerns clearly, reinforces brand values, and provides a path for further engagement, all while maintaining concise, professional language.

How can I ensure replies are SEO-friendly?

Include relevant keywords naturally, reference local signals when applicable, and keep responses informative and helpful to encourage engagement and local relevance.

Should I respond to all reviews?

Yes, respond to both positive and negative reviews to show reliability and care. Tailor each reply to the specific feedback.

How do I avoid making promises I can't keep?

Be transparent about what you will do, offer a concrete next step, and avoid guarantees or exaggerated claims.

What tone should I use in replies?

Use a professional yet approachable tone, adapted to the client’s audience, with empathy for negative feedback and appreciation for positive feedback.

Can I use these prompts for multiple clients?

Yes, these prompts are designed to be adaptable across clients with placeholders for client names, cities, and specifics.