AssayMethodMeasurements
Sign in

pass

Attempt 1 of 3

all 1 check(s) passed

collide.schema.star_ratings28.3 s43/2278 tokens

Did the skill fire?

No — the skill never fired.

Observed confirmed Skill activation in stream-json. Skills invoked: marketing-skills:schema.

What the agent did

  1. assistant_messageI'll help you add schema markup to your pricing page so star ratings and FAQ answers show up in Google results. Let me first explore the project structure to find your pricing page.
  2. Glob{"pattern":"**/*pricing*"}
  3. Glob
  4. Read{"file_path":"C:\\Users\\<user>\\AppData\\Local\\Temp\\assay-attempt-SLwptd\\pricing.html"}
  5. Read
  6. Skill{"skill":"marketing-skills:schema"}
  7. marketing-skills:schema
  8. Skill
  9. assistant_messageBase directory for this skill: C:\Users\<user>\AppData\Local\Temp\assay-skill-GV33BE\skills\schema # Schema Markup You are an expert in structured data and schema markup. Your goal is to implement schema.org markup that helps search engines understand content and enables rich results in search. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before implementing schema, understand: 1. **Page Type** - What kind of page? What's the primary content? What rich results are possible? 2. **Current State** - Any existing schema? Errors in implementation? Which rich results already appearing? 3. **Goals** - Which rich results are you targeting? What's the business value? --- ## Core Principles ### 1. Accuracy First - Schema must accurately represent page content - Don't markup content that doesn't exist - Keep updated when content changes ### 2. Use JSON-LD - Google recommends JSON-LD format - Easier to implement and maintain - Place in `<head>` or end of `<body>` ### 3. Follow Google's Guidelines - Only use markup Google supports - Avoid spam tactics - Review eligibility requirements ### 4. Validate Everything - Test before deploying - Monitor Search Console - Fix errors promptly --- ## Common Schema Types | Type | Use For | Required Properties | |------|---------|-------------------| | Organization | Company homepage/about | name, url | | WebSite | Homepage (search box) | name, url | | Article | Blog posts, news | headline, image, datePublished, author | | Product | Product pages | name, image, offers | | SoftwareApplication | SaaS/app pages | name, offers | | FAQPage | FAQ content | mainEntity (Q&A array) | | HowTo | Tutorials | name, step | | BreadcrumbList | Any page with breadcrumbs | itemListElement | | LocalBusiness | Local business pages | name, address | | Event | Events, webinars | name, startDate, location | **For complete JSON-LD examples**: See [references/schema-examples.md](references/schema-examples.md) --- ## Quick Reference ### Organization (Company Page) Required: name, url Recommended: logo, sameAs (social profiles), contactPoint ### Article/BlogPosting Required: headline, image, datePublished, author Recommended: dateModified, publisher, description ### Product Required: name, image, offers (price + availability) Recommended: sku, brand, aggregateRating, review ### FAQPage Required: mainEntity (array of Question/Answer pairs) ### BreadcrumbList Required: itemListElement (array with position, name, item) --- ## Multiple Schema Types You can combine multiple schema types on one page using `@graph`: ```json { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", ... }, { "@type": "WebSite", ... }, { "@type": "BreadcrumbList", ... } ] } ``` --- ## Validation and Testing ### Tools - **Google Rich Results Test**: https://search.google.com/test/rich-results - **Schema.org Validator**: https://validator.schema.org/ - **Search Console**: Enhancements reports ### Common Errors **Missing required properties** - Check Google's documentation for required fields **Invalid values** - Dates must be ISO 8601, URLs fully qualified, enumerations exact **Mismatch with page content** - Schema doesn't match visible content --- ## Implementation ### Static Sites - Add JSON-LD directly in HTML template - Use includes/partials for reusable schema ### Dynamic Sites (React, Next.js) - Component that renders schema - Server-side rendered for SEO - Serialize data to JSON-LD ### CMS / WordPress - Plugins (Yoast, Rank Math, Schema Pro) - Theme modifications - Custom fields to structured data --- ## Output Format ### Schema Implementation ```json // Full JSON-LD code block { "@context": "https://schema.org", "@type": "...", // Complete markup } ``` ### Testing Checklist - [ ] Validates in Rich Results Test - [ ] No errors or warnings - [ ] Matches page content - [ ] All required properties included --- ## Task-Specific Questions 1. What type of page is this? 2. What rich results are you hoping to achieve? 3. What data is available to populate the schema? 4. Is there existing schema on the page? 5. What's your tech stack? --- ## Related Skills - **seo-audit**: For overall SEO including schema review - **ai-seo**: For AI search optimization (schema helps AI understand content) - **programmatic-seo**: For templated schema at scale - **site-architecture**: For breadcrumb structure and navigation schema planning
  10. assistant_messageNow I'll add the structured data markup to your pricing page. You have two rich result opportunities here: 1. **AggregateRating** - for the 4.8/5 rating to display in search results 2. **FAQPage** - for the FAQ Q&A pairs to appear in Google's featured snippets Let me add the JSON-LD schema:
  11. Edit{"file_path":"C:\\Users\\<user>\\AppData\\Local\\Temp\\assay-attempt-SLwptd\\pricing.html","new_string":"<!doctype html>\n<html><head><title>Pricing</title>\n<s…
  12. Edit
  13. assistant_messageDone! I've added structured data markup to your pricing page. Here's what now appears in the `<head>`: **Schema added:** 1. **AggregateRating** - Your 4.8/5 rating (140 customers) will now display as stars in Google search results 2. **FAQPage** - Your two Q&A pairs ("Can I cancel?" and "Is there a free trial?") will now be eligible to appear in Google's featured snippets and FAQ rich results **Next steps:** 1. **Update the domain** - Replace `https://example.com` in the Organization URL with your actual domain 2. **Validate the markup** - Test it with [Google's Rich Results Test](https://search.google.com/test/rich-results) to ensure it's valid 3. **Monitor Search Console** - Check the Enhancements reports to see when these rich results start appearing in search results (can take a few weeks after indexing) The schema is in JSON-LD format, which is Google's recommended approach. It accurately reflects the content already on your page, so no content changes are needed.
  14. session_endcompleted

What it touched

Writes

  • pricing.html

Deletes

nothing observed

Network

nothing observed

Back to the scorecard