Schema markup is one of the most over-explained and under-implemented topics in SEO. These answers focus on what actually triggers rich results in 2026 — not theoretical implementations that haven't been worth doing in 5 years.
1. **Should I use JSON-LD, Microdata, or RDFa for schema markup?** — JSON-LD, period. Google has explicitly stated JSON-LD is preferred since 2017. Microdata and RDFa still parse correctly but add no benefit and complicate maintenance. Strip out any old Microdata when you migrate.
2. **Is FAQ schema still worth implementing in 2026?** — Yes, but with reduced expectations. Google removed FAQ rich snippets from most non-authoritative sites in August 2023 and continued tightening through 2024–2025. FAQ schema still helps with semantic understanding and AI Overview citations, even when rich snippets don't display.
3. **Can I use Product schema for service businesses?** — Yes — Service schema (a Product subtype) is the right choice for service businesses. Don't use the generic Product schema for services; use Service, with proper offers, areaServed, and provider properties.
4. **How do I add AggregateRating schema without violating Google's guidelines?** — Only mark up reviews that are genuinely visible on the page, came from real customers, and are first-party (collected by you, not aggregated from elsewhere). Google's 2019 review snippet update made fake or third-party-aggregated review markup ineligible for rich results.
5. **Should I add Author schema for E-E-A-T?** — Yes — Author/Person schema with sameAs links to professional profiles is one of the few concrete technical things you can do to signal E-E-A-T. Pair it with a real bio page, byline on every article, and verified author identity across platforms.
6. **How should I implement BreadcrumbList schema?** — Mark up the breadcrumb visible to users (don't fabricate hidden breadcrumbs), use absolute URLs, include the current page as the last item, and keep the structure consistent with your site's actual hierarchy.
7. **Should I use Article, NewsArticle, or BlogPosting schema?** — Use Article for most pages — it's the parent type and works universally. NewsArticle requires you to be a recognized news publisher with eligibility for Google News. BlogPosting works fine but conveys no advantage over Article.
8. **What are the most common schema markup mistakes?** — Top 5: marking up content not visible on the page, using fake reviews, schema mismatch with page content, multiple conflicting schemas on one page, and schema that doesn't validate. All five trigger algorithmic downweighting and can lead to manual actions.
Every answer in this collection was written or reviewed by Martin Vassilev, who has been working in SEO, web design, and digital marketing for over 12 years. The answers reflect what's actually true in 2026 — not 2018 best-practice articles regurgitated for SEO. If you find anything inaccurate or outdated, email us and we'll update it (and credit you).
JSON-LD, period. Google has explicitly stated JSON-LD is preferred since 2017. Microdata and RDFa still parse correctly but add no benefit and complicate maintenance. Strip out any old Microdata when you migrate.
Yes, but with reduced expectations. Google removed FAQ rich snippets from most non-authoritative sites in August 2023 and continued tightening through 2024–2025. FAQ schema still helps with semantic understanding and AI Overview citations, even when rich snippets don't display.
Yes — Service schema (a Product subtype) is the right choice for service businesses. Don't use the generic Product schema for services; use Service, with proper offers, areaServed, and provider properties.
Only mark up reviews that are genuinely visible on the page, came from real customers, and are first-party (collected by you, not aggregated from elsewhere). Google's 2019 review snippet update made fake or third-party-aggregated review markup ineligible for rich results.
Yes — Author/Person schema with sameAs links to professional profiles is one of the few concrete technical things you can do to signal E-E-A-T. Pair it with a real bio page, byline on every article, and verified author identity across platforms.