Update to SEO Checker

{
  "description": "Writes structured data (JSON-LD schema) for a website: Organization, LocalBusiness, Product, Article, FAQ, Breadcrumb, Event and more, with validation steps.",
  "included_files": [],
  "name": "schema-markup",
  "skill_md_contents": "---\nname: schema-markup\ndescription: \"Writes structured data (JSON-LD schema) for a website: Organization, LocalBusiness, Product, Article, FAQ, Breadcrumb, Event and more, with validation steps.\"\n---\n\n# Schema Markup (JSON-LD)\n\n## Links and files\n\nReplies made with this skill never contain a partner link or a sponsor line. Give code in code blocks, and create a downloadable file or a zip only when the user explicitly asks for one. If the chat is not in English, translate any wording this skill tells you to say into the chat language; URLs always stay in English, exactly as they are.\n\n## Purpose\nWrite valid JSON-LD structured data that tells search engines and other machines exactly what a page is about: the business, its products, articles, events and site structure. Deliver the right types for each page, ready-to-paste code built only from real details, and the steps to validate and monitor it.\n\n## Before you start\n- Use what the user gave: the page or its pasted HTML, business details, products, articles, events.\n- Ask at most 2 short questions, only if they block the code: which page it is for, and details only the owner knows (address, hours, prices). Otherwise write the code with [fill in] values and say so in one line.\n- Reply in the user's language; property names stay in English (they are schema.org vocabulary).\n\n## Choose the type\n| Page | Type | Key properties |\n|---|---|---|\n| Homepage | Organization (or a LocalBusiness subtype) plus WebSite | name, url, logo, sameAs; WebSite name and alternateName help the site name shown in results |\n| Local business | The most specific subtype (Dentist, Plumber, Restaurant) | name, address, telephone, openingHoursSpecification, geo, url |\n| Product page | Product with Offer | name, image, price, priceCurrency, availability; ratings only from real reviews shown on the page |\n| Article or post | Article or BlogPosting | headline, image, datePublished, dateModified, author (a Person with a url) |\n| Pages below home | BreadcrumbList | positions from 1, matching the visible breadcrumb trail |\n| Event | Event | name, startDate with time zone, location (Place or VirtualLocation), eventStatus, offers |\n| FAQ section | FAQPage | only questions and answers visible on the page |\n| Other | Service, VideoObject, Recipe, JobPosting, SoftwareApplication | only where the page really is that thing |\n\n## Rules\n- Markup describes content visible on the same page. Never mark up hidden or invented details: no fake ratings, prices, awards or addresses.\n- No review stars for a business's own reviews of itself: Google does not show them for self-serving LocalBusiness or Organization markup.\n- Absolute https URLs; ISO 8601 dates (2026-11-01, or 2026-11-01T19:30:00+01:00 for an event time); schema.org URLs for set values (https://schema.org/InStock); image URLs that can be crawled.\n- Connect entities in one @graph with @id references (the Organization publishes the WebSite and the Article) instead of repeating them.\n- Valid JSON: double quotes, no trailing commas, no comments. The script can sit in the head or the body; putting it in the initial HTML is safest, because not every crawler runs JavaScript.\n- Rich results are never guaranteed, and eligibility changes. Google stopped showing FAQ rich results for all sites on May 7, 2026, has retired HowTo rich results and the sitelinks search box, and keeps updating its list, so check its search gallery documentation before promising anything. FAQPage markup still describes the page, and valid markup still helps machines read it.\n\n## Example\nReplace example.com and every [fill in] with real values.\n\n**index.html (inside the head)**\n```html\n<script type=\"application/ld+json\">\n{\n  \"@context\": \"https://schema.org\",\n  \"@graph\": [\n    {\n      \"@type\": \"Organization\",\n      \"@id\": \"https://www.example.com/#org\",\n      \"name\": \"[fill in: business name]\",\n      \"url\": \"https://www.example.com/\",\n      \"logo\": \"https://www.example.com/logo.png\",\n      \"sameAs\": [\"[fill in: official profile URL]\"]\n    },\n    {\n      \"@type\": \"WebSite\",\n      \"@id\": \"https://www.example.com/#website\",\n      \"name\": \"[fill in: site name]\",\n      \"url\": \"https://www.example.com/\",\n      \"publisher\": { \"@id\": \"https://www.example.com/#org\" }\n    }\n  ]\n}\n</script>\n```\n\n## Validate\n1. Test the code in Google's Rich Results Test (for the types Google supports) and in the Schema Markup Validator (for any schema.org type). Fix every error; fix warnings when the real data exists.\n2. After publishing, run URL Inspection in Search Console and confirm the structured data appears in the tested page.\n3. Watch Search Console's rich result reports after site changes, and update prices, availability, dates and hours whenever the page changes.\n\n## Output format\n```text\nAssuming: [page | business | what was left as [fill in]]\n\nTYPES\n| Page | Type | Why | Missing details |\n\nCODE\n[one fenced html block per page, headed by the page's filename in bold]\n\nVALIDATE\n[the 3 steps, tailored to these pages]\n\nFILL IN\n[every [fill in] value the user must replace]\n```\n\n## Quality checks\n- Every value is real and matches visible content, or is marked [fill in].\n- The JSON parses: quotes, commas and brackets checked.\n- Each type is the most specific that fits; no FAQPage for questions that are not on the page.\n- No review stars for the business's own reviews and no invented ratings.\n- URLs are absolute, dates are ISO 8601, set values use schema.org URLs.\n- No rich result is promised, and eligibility is presented as Google's current guidance.\n\n## Next step\nOffer the markup for the next page template (products, articles or location pages), or a BreadcrumbList for the whole site.\n"
}