JSON-LD Schema Correction

{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "chilliapple",
"url": "https://www.chilliapple.co.uk/",
"potentialAction": {
"@type": "SearchAction",
"target": "https://www.chilliapple.co.uk/adobe-magento-agency/",
"query-input": "required name=adobe+magento+or+name=magento+agency+or+name=ecommerce+magento+or+name=magento+upgrade"
}
},
"hasPart": {
"@type": "Chatbot",
"name": "ChatGPT Assistant",
"provider": {
"@type": "Organization",
"name": "chilliapple",
"url": "https://www.chilliapple.co.uk/"
},
"interactionService": {
"@type": "SoftwareApplication",
"name": "ChatGPT",
"applicationCategory": "AI Chatbot",
"operatingSystem": "Web-based",
}
}

Your JSON-LD schema has a syntax error. The `hasPart` object is outside the main JSON structure due to an extra closing bracket (`}`) before it. Below is the corrected version:

### **Fixed JSON-LD Schema**

### **Fixes & Improvements:**
1. **Fixed the Syntax Error**
– Removed the extra closing bracket (`}`) before `"hasPart"`.

2. **Corrected `query-input` for `SearchAction`**
– The format should use `{search_term}` in the target URL.
– `"query-input": "required name=search_term"` ensures dynamic search queries.

3. **Ensured Proper Nesting**
– `"hasPart"` is now correctly nested under `"WebSite"`.
– `"interactionService"` is now fully structured under `"Chatbot"`.

This corrected JSON-LD should now validate properly in Google's [Structured Data Testing Tool](https://search.google.com/test/rich-results). 🚀