100 Best Claude Schema Markup Prompts for SEO Agencies

Direct Answer

The best Claude prompts for schema markup for SEO agencies are a curated set of practical, role driven tasks that guide Claude to generate correct JSON-LD structures, audit and expand markup, and validate outputs for agency pages. Use placeholders to customize agency details and pages, and always constrain to pure JSON-LD when required.

Introduction

This page provides a practical prompt library focused on schema markup for SEO agencies. It helps teams quickly generate, validate, and refine structured data across service pages, blog posts, and events.

Designed for SEO agencies, marketers, and developers who implement and maintain schema markup using Claude prompts, this collection emphasizes accuracy, completeness, and adaptability across pages and templates.

How to Use These Claude Prompts

• Replace placeholders like [agencyName], [agencyUrl], and [pageUrl] with your real data before running the prompt.
• Add constraints such as required properties and formats to ensure consistent JSON-LD output.
• Request a specific output format, like pure JSON or JSON-LD script blocks, to simplify integration.
• Verify the generated markup against schema.org guidelines and Google’s structured data testing tool after generation.
• If outputs are too verbose, ask Claude to return only the JSON object, excluding comments or explanations.
• For recurring pages, reuse and modify prompts by swapping placeholders for new pages or sections.

100 Best Claude Schema Markup Prompts for SEO Agencies

1. Create LocalBusiness schema: You are a structured data engineer. Task: generate a complete JSON-LD LocalBusiness schema for a hypothetical SEO agency page. Context: use the organization name, address, contact, openingHours, and url placeholders. Output format: JSON-LD script block but provide only the JSON object. Constraints: include at least name, url, logo, telephone, address, openingHours, and@type. Do not include extraneous data. Ensure type is LocalBusiness and matches schema.org.
2. Generate Organization schema: Role: schema expert. Task: produce a JSON-LD Organization schema for an SEO agency with correct properties including name, url, logo, contactPoint, and address. Context: placeholders: [agencyName], [agencyUrl], [agencyLogo], [agencyPhone], [agencyAddress]. Output: pure JSON object, with @context and @type Organization. Constraint: include sameAs if available as an array of URLs.
3. Audit Article schema: Role: SEO auditor. Task: craft an Article schema snippet for a blog post on schema markup best practices. Context: placeholders for headline, author, datePublished, image, and publisher. Output: JSON-LD with @type Article, include mainEntityOfPage, image, and publisher. Constraint: ensure the date is in ISO 8601 format and the articleBody is not included, only structured data.
4. Review FAQPage structure: Instruction: build an FAQPage schema for a frequently asked questions list about schema markup. Context: placeholders for questions and acceptedAnswers. Output: JSON-LD with @type FAQPage and mainEntity as an array of Question objects. Constraint: keep questions concise and answers brief.
5. WebSite and WebPage combo: Role: data engineer. Task: provide a WebSite schema with potentialAction entry for a site search. Context: placeholders for url and potentialQuery. Output: JSON-LD containing WebSite and a nested WebPage for searchAction. Constraint: avoid including any items beyond WebSite, WebPage, and potentialAction where required.
6. Product schema for services: You are a schema coder. Task: create a Product schema for an SEO services package. Context: placeholders: productName, sku, price, currency, availability, url. Output: JSON-LD with @type Product, offers object, and aggregateRating if available. Constraint: keep to JSON only.
7. Service schema for offerings: Role: semantic coder. Task: construct a Service schema for an SEO audit package. Context: placeholders: serviceName, serviceId, provider, areaServed, priceRange. Output: a JSON-LD Service snippet with provider as Organization or Person. Constraint: include serviceType and areaServed arrays.
8. BreadcrumbList construction: Role: content architect. Task: generate a BreadcrumbList for a services site with three levels: Home, Services, SEO Audit. Context: placeholders for item names and URL patterns. Output: JSON-LD BreadcrumbList with itemListElement as an array of ListItem objects.
9. Event schema basics: You are a data model expert. Task: create an Event schema for a webinar about schema markup for SEO agencies. Context: placeholders: eventName, startDate, location, offers. Output: JSON-LD with @type Event, location as Place, and offers as Offer object. Constraint: date should be in ISO format.
10. Person schema for authors: Role: author data mapper. Task: produce a Person schema for a contributing author. Context: placeholders: authorName, authorUrl, sameAs. Output: JSON-LD with possibleRole and affiliation. Constraint: keep to essential properties only.
11. Review schema for testimonials: You are a review schema specialist. Task: craft a Review schema for a client testimonial. Context: placeholders: reviewer, rating, reviewBody, itemReviewed. Output: JSON-LD with reviewRating as Rating, bestRating as '5', ratingValue placeholder.
12. ImageObject for logos: Role: media data engineer. Task: create an ImageObject schema for a logo image. Context: placeholders: imageUrl, caption, height, width. Output: JSON-LD with uploadDate if available. Constraint: keep it minimal.
13. WebPage for service page: You are a page data architect. Task: generate a WebPage schema for an SEO services page. Context: placeholders: pageName, description, inLanguage. Output: JSON-LD with mainEntity as a Service and isPartOf site. Constraint: include about and copyrightYear where applicable.
14. NewsArticle schema usage: Role: news writer. Task: craft a NewsArticle schema for a press release about schema markup wins. Context: placeholders: headline, datePublished, dateline, authors. Output: JSON-LD with publication date and sourceOrganization.
15. Code block not allowed: Role: policy checker. Task: ensure the prompt does not include code blocks. Context: none. Output: plain JSON-LD only. Constraint: avoid fenced code blocks.
16. LocalBusiness hours: Role: data collector. Task: create a LocalBusiness hours snippet. Context: placeholders: openingHours, closingHours, timeZone. Output: JSON-LD with openingHours as per days.
17. AggregateRating for services: You are a ratings specialist. Task: add an AggregateRating to a Service. Context: placeholders: ratingValue, reviewCount. Output: JSON-LD with aggregateRating object.
18. HowTo schema for tutorials: Role: instructional designer. Task: build a HowTo schema for a tutorial about schema markup. Context: placeholders: steps, totalTime, supply, tool. Output: JSON-LD with step array and potentialAction.
19. CreativeWork for case studies: Role: content strategist. Task: create a CreativeWork schema for a case study on improved click through rate. Context: placeholders: author, datePublished, keywords. Output: JSON-LD with keywords and about.
20. FAQ for agencies: Role: FAQ generator. Task: form a set of 5FAQ items about schema markup for agencies. Context: placeholders: question, acceptedAnswer. Output: JSON-LD with mainEntity as array of Question objects.
21. Poorly formed vs valid: Role: validator. Task: compare two schema snippets one invalid and one valid for a page. Context: placeholders: invalidSnippet, validSnippet. Output: JSON-LD showing corrections and rationale.
22. Structured data testing: Role: QA engineer. Task: describe steps to test schema markup with a test tool. Context: placeholders: toolName, testCase. Output: JSON-LD style checklist.
23. Language mapping for locales: Role: localization engineer. Task: generate LocalBusiness with multiple languages, set inLanguage and inLanguageAlt. Output: JSON-LD array supporting multiple locales.
24. Validation error notes: Role: error analyst. Task: outline typical schema validation errors and fixes for an SEO agency site. Context: placeholders: errorType, fixIdea. Output: JSON-LD style notes.
25. Sitelinks SearchBox: Role: site architect. Task: implement SitelinksSearchBox for an agency site. Context: placeholders: potentialQuery, targetPage. Output: JSON-LD with potentialAction object.
26. Medical schemas avoidance: Role: policy advisor. Task: ensure no medical or health claims in schema for an SEO agency site. Output: JSON-LD clearly non medical.
27. Event with webinar details: Role: events coordinator. Task: build Event schema for a recurring monthly webinar. Context: placeholders: startDate, duration, eventAttendanceMode. Output: JSON-LD with repeatedEvent if applicable.
28. ServicePricing schema: Role: pricing analyst. Task: add Offers with price and priceCurrency to a Service. Context: placeholders: price, currency. Output: JSON-LD with priceSpecification.
29. Person with Affiliate: Role: partner manager. Task: build Person schema for an author with sameAs and affiliation. Output: JSON-LD.
30. Quality assurance notes: Role: QA lead. Task: produce a checklist of schema QA checks for a page. Context: placeholders: checks. Output: JSON-LD style or plain list.
31. Service taxonomy: Role: taxonomy engineer. Task: generate an itemListElement list for a Service taxonomy page. Output: JSON-LD with itemListElement array.
32. ProductReview for services: Role: reviewer. Task: write a ProductReview for an SEO package. Context: placeholders: product, author, reviewBody, ratingValue. Output: JSON-LD with reviewRating.
33. VideoObject schema: Role: video producer. Task: create a VideoObject schema for a service explainer video. Context: placeholders: name, thumbnailUrl, uploadDate, contentUrl. Output: JSON-LD.
34. Organization with sameAs: Role: schema maintainer. Task: add sameAs array to an Organization schema. Context: placeholders: socialLinks. Output: JSON-LD with sameAs.
35. SiteNavigationElement: Role: UX data steward. Task: add SiteNavigationElement entries for main sections. Output: JSON-LD with navElement list.
36. NewsMediaOrganization: Role: media schema engineer. Task: create a NewsMediaOrganization schema for a marketing news page. Output: JSON-LD with publishDate and accessibleVersion.
37. GeoCoordinates: Role: geodata engineer. Task: add geo coordinates to LocalBusiness. Context: placeholders: latitude, longitude. Output: JSON-LD with geo object.
38. SoftwareApplication: Role: product architect. Task: craft SoftwareApplication schema for a marketing tool used by agencies. Context: placeholders: operatingSystem, applicationCategory. Output: JSON-LD.
39. AggregateOffer for bundles: Role: commerce strategist. Task: create an AggregateOffer for bundled services. Context: placeholders: highPrice, lowPrice, offerCount. Output: JSON-LD.
40. DeliveryMethod details: Role: logistics coder. Task: specify deliveryMethod for a service. Output: JSON-LD with deliveryDetails.
41. Audience targeting hints: Role: market analyst. Task: include audience segment in a Service schema using audience property. Output: JSON-LD.
42. Brand schema for agencies: Role: branding specialist. Task: create Brand schema for the agency. Context: placeholders: brandName, brandLogo. Output: JSON-LD.
43. CivicStructure: Role: municipal data. Task: add CivicStructure only if relevant to page. Output: JSON-LD with proper type and properties.
44. EducationalCredential: Role: educator. Task: add EducationalCredential only if relevant to readers. Output: JSON-LD.
45. CreativeWorkSeason: Role: content planner. Task: create a CreativeWorkSeason if using seasonal campaigns. Output: JSON-LD.
46. Quantitative property: Role: data validator. Task: include quantitativeProperty for numeric values in a Service. Output: JSON-LD.
47. SoftwareApplicationStatus: Role: product manager. Task: set applicationStatus for a software tool. Output: JSON-LD.
48. Plan andPricing: Role: pricing strategist. Task: represent pricing plan with offers and priceCurrency. Output: JSON-LD.
49. ActionableHowTo: Role: educator. Task: convert a how to into an actionable HowTo with steps and time. Output: JSON-LD.
50. MedicalSciImage: Role: data policy. Task: ensure no medical claims in content; omit MedicalSeries.
51. Event attendance guidance: Role: events planner. Task: include attendanceMode in Event schema. Output: JSON-LD.
52. Audience as Organization: Role: audience mapping. Task: model audience as Organization or Person in Service context. Output: JSON-LD.
53. PriceSpecification details: Role: pricing specialist. Task: add priceSpecification with minPrice and maxPrice. Output: JSON-LD.
54. Language and accessibility: Role: accessibility engineer. Task: set inLanguage and accessibilityControl details. Output: JSON-LD.
55. VideoObject for channel: Role: video strategist. Task: create VideoObject with embedUrl and contentUrl. Output: JSON-LD.
56. CollectionPage: Role: cataloger. Task: add CollectionPage to group multiple items. Output: JSON-LD.
57. ImageGallery: Role: media curator. Task: build ImageGallery schema for a portfolio page. Output: JSON-LD.
58. DataFeed for products: Role: data engineer. Task: generate DataFeed for product-like services. Output: JSON-LD.
59. WebPage Distractor test: Role: QA. Task: compare two similar WebPage schemas to ensure only one is correct for a given page. Output: JSON-LD with notes.
60. Organization with contactPoint: Role: contact optimization. Task: add contactPoint to Organization schema. Output: JSON-LD.
61. SeoAuditservice: Role: naming architect. Task: create a Service named SeoAuditService with areaServed. Output: JSON-LD.
62. Breadcrumb with news: Role: content planner. Task: BreadcrumbList for a section containing news and services. Output: JSON-LD.
63. Review snippet for page: Role: copywriter. Task: add a Review snippet for a page with reviewer and rating. Output: JSON-LD.
64. Speaker schema: Role: event manager. Task: create Person who is a speaker for an event and link to event. Output: JSON-LD.
65. Dataset schema usage: Role: data steward. Task: attach Dataset schema for marketing benchmarks. Output: JSON-LD.
66. MediaObject for podcast: Role: podcast producer. Task: build MediaObject for a podcast episode. Context: placeholders: title, duration, contentUrl. Output: JSON-LD.
67. HowToSection usage: Role: instructional designer. Task: create HowToSection containing steps for a process. Output: JSON-LD.
68. QAPage structure: Role: QA engineer. Task: build QAPage for an agency knowledge base. Output: JSON-LD.
69. ContactPoint for agency: Role: CRM manager. Task: add ContactPoint with contactType and areaServed. Output: JSON-LD.
70. Rating on Services: Role: ratings analyst. Task: attach Rating to a Service with ratingValue and ratingCount. Output: JSON-LD.
71. Volume and duration: Role: content planner. Task: include duration in HowTo or CreativeWork. Output: JSON-LD.
72. Place schema for office: Role: geodata. Task: add Place with geo coordinates for the agency office. Output: JSON-LD.
73. PersonAffiliation: Role: HR data. Task: attach affiliation to a Person schema. Output: JSON-LD.
74. LegalEntity compliance: Role: compliance officer. Task: ensure legalEntity array usage where required. Output: JSON-LD.
75. Audience targeting depth: Role: marketing strategist. Task: add audience as an array to a Service or Product. Output: JSON-LD.
76. ImageObject alt text: Role: accessibility advocate. Task: add alt text to an ImageObject for logos and banners. Output: JSON-LD.
77. Social profiles: Role: brand steward. Task: populate sameAs with social profile URLs in Organization schema. Output: JSON-LD.
78. FAQ theme expansion: Role: content strategist. Task: expand a 5 item FAQ to 7 items with distinct questions. Output: JSON-LD.
79. Product with review: Role: product manager. Task: attach a Product with a Review object. Output: JSON-LD.
80. WebSite with search: Role: site architect. Task: add WebSite with potentialAction for search on agency site. Output: JSON-LD.
81. Event with location: Role: events coordinator. Task: Event schema with Place as location. Output: JSON-LD.
82. Meta tags hint: Role: SEO copywriter. Task: describe relevance of meta fields in JSON-LD. Output: JSON-LD style notes.
83. Legal schema snippets: Role: compliance editor. Task: include LegalService or LegalPerson if applicable. Output: JSON-LD.
84. Portfolio structuring: Role: portfolio manager. Task: create CreativeWorkSeries or CollectionPage for portfolio items. Output: JSON-LD.
85. Speakable specification: Role: accessibility engineer. Task: add Speakable annotation for audio content. Output: JSON-LD.
86. Dataset for benchmarks: Role: data scientist. Task: attach Dataset to a page with keywords. Output: JSON-LD.
87. SoftwareApplicationInstall: Role: product owner. Task: provide SoftwareApplicationInstall if needed. Output: JSON-LD.
88. WebPage with audience: Role: market researcher. Task: add audience as a property to a WebPage. Output: JSON-LD.
89. Offer for packages: Role: sales engineer. Task: include Offer with url and availability on a Service. Output: JSON-LD.
90. Connection to CreativeWork: Role: content strategist. Task: link a CreativeWork to an Organization. Output: JSON-LD.
91. LegalStatus schema: Role: compliance lead. Task: include LegalStatus where applicable in Organization. Output: JSON-LD.
92. PaymentMethod details: Role: finance manager. Task: attach paymentAccepted to an Offer. Output: JSON-LD.
93. Contact form schema: Role: web developer. Task: describe an embedded contact form using WebComponent or ScholarlyAction. Output: JSON-LD.
94. QAPage FAQ merge: Role: QA strategist. Task: merge a QAPage with an FAQPage when both apply. Output: JSON-LD.
95. Series schema usage: Role: content architect. Task: create CreativeWorkSeries for a series of schema lessons. Output: JSON-LD.
96. MobileFriendly schema: Role: accessibility engineer. Task: ensure inLanguage and mobileFriendly property where relevant. Output: JSON-LD.
97. Organization with dept: Role: org designer. Task: add Department to Organization instance. Output: JSON-LD.
98. Logo verification: Role: brand verifier. Task: verify Logo object aligns with Organization. Output: JSON-LD.
99. ImageObject nonempty: Role: data quality. Task: ensure ImageObject has at least url and dataContentType when used. Output: JSON-LD.
100. Schema map summary: Role: navigator. Task: summarize all added schemas for a page into a single Schema map JSON-LD. Output: JSON-LD.

Best Practices

• Test every generated JSON-LD with a structured data validator before deploying.
• Keep prompts modular so you can reuse individual components across pages and services.
• Document any deviations or custom properties to maintain consistency across the site.
• Avoid duplicating identical scripts on multiple pages to reduce crawl weight and potential conflicts.
• Regularly update prompts to reflect evolving schema.org types and search engine guidelines.

Common Mistakes to Avoid

• Using generic prompts that omit essential properties like datePublished or @type for important pages.
• Omitting the required @context or mislabeling types such as using LocalBusiness for a non local page.
• Including raw HTML or code blocks in the output when JSON-LD is required.
• Assuming one schema fits all pages without tailoring it to the page’s purpose.
• Forgetting to validate the generated JSON-LD with a real validator before deployment.

FAQ

What is schema markup and why do agencies use it?

Schema markup is structured data that helps search engines understand page content. Agencies use it to improve visibility and eligibility for rich results.

How do I start creating schema markup for a service page?

Identify the service type, add an appropriate Service or Organization schema, and then attach offers, areaServed, and provider details as needed.

Can I reuse prompts for multiple pages?

Yes, modular prompts can be adapted by swapping placeholders like [pageUrl] and [serviceName] to fit new pages.

What tools should I use to validate JSON-LD?

Use Google's Rich Results Test, the Structured Data Testing Tool, or the JSON-LD Playground to verify syntax and structure.

How do I handle multilingual schema markup?

Add inLanguage and inLanguage alternatives where relevant and maintain separate JSON-LD blocks per language if necessary.

What common errors should I avoid in schema markup?

Incorrect @type, missing required properties, invalid date formats, or conflicting properties across related schemas.