Most schema markup templates are a few JSON-LD snippets to copy. This free schema markup template is a working kit instead: an Excel JSON-LD Builder that writes clean, copy and paste markup for 9 types from plain form fields, and a Schema Lab that audits every structured data block on your site against Google's required and recommended properties, its quality rules and 11 weighted checks.
It is built for 2026. Google has retired several rich results, including FAQ rich results in May 2026, and it says there is no special schema needed for AI Overviews or AI Mode, only markup that matches the visible page. So the kit tells you which types still earn a Google result, which markup is missing required properties, which values no longer match the page, which pages are blocked, where the type is wrong for the page and where review markup is self serving, and it plans the rollout per template.
What is in the free schema markup kit
Download the full kit (ZIP, 385 KB)
Preview: the Schema Lab tab
A live look at the first rows of the demo data inside the workbook. Grey columns with a green label calculate by themselves in Excel and Google Sheets.
| URL | Schema type | Missing required (list)auto formula | Recommended presentauto formula | Score (0 to 100)auto formula | Gradeauto formula | Rich result eligibilityauto formula | Priorityauto formula |
|---|---|---|---|---|---|---|---|
| https://brewnest.example/ | Organization | 6 | 89 | A | Details only: no review stars for self serving reviews | Fix now: self serving review markup | |
| https://brewnest.example/ | WebSite | 1 | 100 | A | Test it in the Rich Results Test | Healthy: monitor | |
| https://brewnest.example/blog/pour-over-coffee-guide/ | BlogPosting | 4 | 96 | A | Eligible (Google does not guarantee it) | Improve: add recommended properties | |
| https://brewnest.example/blog/pour-over-coffee-guide/ | BreadcrumbList | 0 | 100 | A | Eligible (Google does not guarantee it) | Healthy: monitor | |
| https://brewnest.example/blog/best-coffee-beans-india/ | BlogPosting | 6 | 84 | B | Eligible (Google does not guarantee it) | Improve when you can | |
| https://brewnest.example/shop/monsoon-malabar-250g/ | Product | 4 | 100 | A | Eligible (Google does not guarantee it) | Healthy: monitor | |
| https://brewnest.example/shop/kalimpong-light-roast/ | Product | 2 | 72 | B | No: does not match the page | Fix now: markup does not match the page | |
| https://brewnest.example/shop/coorg-dark-roast/ | Product | one of offers, review, aggregateRating | 0 | 56 | C | No: required properties missing | Fix now: required properties missing |
| https://brewnest.example/shop/ | Product | 2 | 79 | B | No: wrong type for this page | Fix: wrong type for this page | |
| https://brewnest.example/cafe/koregaon-park/ | LocalBusiness | 7 | 100 | A | Eligible (Google does not guarantee it) | Healthy: monitor | |
| https://brewnest.example/events/home-brewing-workshop/ | Event | location.address | 5 | 60 | C | No: required properties missing | Fix now: required properties missing |
| https://brewnest.example/videos/aeropress-recipe/ | VideoObject | uploadDate | 3 | 56 | C | No: required properties missing | Fix now: required properties missing |
Demo data for a fictional company, with illustrative numbers. The workbook has more columns, 500 ready rows, a dashboard, a page map and settings.
How to use this schema markup template
- Check the type rules. On Settings, set the analysis date and look at the Type Rules for the types you use. Google's required and recommended properties for 17 types are ready, with retired rich results marked.
- List your templates. On the Rollout Plan, add one row per page template and schema type (blog post plus BlogPosting, product page plus Product). Markup is added per template, so this is your plan.
- Test one live URL per template. Run a sample URL through the Rich Results Test and note the result and the properties it finds.
- Add a Schema Lab row per block. Paste the schema type, the format and the property names, comma separated, with a dot for nested ones like
author.nameoroffers.price. - Compare with the visible page. Check every marked up value against what visitors see: prices, dates, names, hours, ratings. Choose Yes, Partly or No, and add the Search Console report status and whether the page is blocked.
- Fix by priority. Sort by Priority. Fix blocked pages, mismatches and missing required properties first. Build new or corrected markup on the JSON-LD Builder.
- Release, validate and recheck. After release, test again, watch the Search Console enhancement reports, mark the template Validated and recheck values every time the template or prices change.
Schema markup in the AI search era
Schema markup, or structured data, is code that describes a page in a standard vocabulary from schema.org: this is a product with this price, this is an article by this author, this is an event on this date at this place. Google uses it to understand pages and to show some results with extra features, called rich results.
Google's general structured data guidelines set the rules for this kit:
- JSON-LD is recommended. Google supports JSON-LD, Microdata and RDFa, and marks JSON-LD as recommended.
- Markup must match the page. Google says structured data must be a true representation of the page content, and not to mark up content that is not visible to readers or that is misleading.
- Required properties decide eligibility. Google says items missing required properties are not eligible for rich results, and that the more recommended properties you provide, the higher quality the result is to users.
- Do not block the page. Google says not to block structured data pages with robots.txt, noindex or other access controls.
- Nothing is guaranteed. Google does not guarantee that structured data will show up in results, even when it is correct. A structured data manual action removes rich result eligibility but, Google says, does not affect how the page ranks.
What changes with AI search:
- No special schema for AI. Google's AI features page says there is no special schema.org structured data you need to add to appear in AI Overviews or AI Mode, and no new machine readable files are needed.
- Matching the visible text is now a stated best practice. The same page lists "making sure your structured data matches the visible text on the page" among the practices that still apply. That is why Matches the visible page carries the highest weight in this kit, together with required properties.
- Fewer rich result types. Google keeps simplifying results. FAQ rich results stopped appearing on 7 May 2026, How to rich results ended in 2023, and several features were phased out in 2025. Time spent on retired types is time not spent on Product, Article, Event or LocalBusiness markup that still earns a result.
Which schema types still earn a Google result
This is the Type Rules table on Settings, built from Google's documentation for each feature (read November 2026). Check the doc for a type before a big rollout, because Google updates them.
| Schema type | What Google can show | Status | Required |
|---|---|---|---|
| Article, BlogPosting, NewsArticle | A better title, image and date | Supported | None; headline, image, dates and author are recommended |
| Product | Product snippet: price, availability, ratings | Supported | name, plus one of offers, review or aggregateRating; offers.price inside an offer |
| Organization | Name, logo and company facts | Supported | None; name, url, logo, sameAs and more are recommended |
| LocalBusiness | Address, hours and phone | Supported | name, address |
| BreadcrumbList | Breadcrumb trail | Supported | itemListElement, with item, name and position per crumb (item optional on the last) |
| VideoObject | Thumbnail, date and key moments | Supported | name, thumbnailUrl, uploadDate |
| Event | Date, place and tickets | Supported | name, startDate, location with address |
| ProfilePage | The person or organization behind content | Supported | mainEntity with a name |
| DiscussionForumPosting | Forum threads | Supported | author, author.name, datePublished, and one of text, image or video |
| Review | Star rating | Supported | author, itemReviewed with name, reviewRating with ratingValue |
| WebSite | Site name in results | Supported | name, url |
| Person | No result of its own; used inside Article, ProfilePage and others | Supports other types | None |
| FAQPage | FAQ rich result | Retired 2026 | Not shown in Google Search from 7 May 2026 |
| HowTo | How to rich result | Retired 2023 | Ended on mobile in August 2023 and on desktop in September 2023 |
| ClaimReview | Fact check rich result | Retired 2025 | Phased out of Google Search in 2025 |
Google's search gallery lists every feature it supports today, including types not in this table such as Recipe, Job posting and Course list. Add any of them to the empty Type Rules rows.
What is inside the schema markup workbook
| Tab | What it does | What you type |
|---|---|---|
| Schema Lab | One row per markup block. Looks up what Google can show and the type's status, checks the page type, counts required and recommended properties and lists the missing ones, flags self serving reviews and stale values. Runs 11 weighted checks and gives a score, grade, fixes, rich result eligibility and a priority. | URL, page type, schema type, format, property names, matches page, Rich Results Test, Search Console report, blocked, last checked, impressions |
| JSON-LD Builder | Writes one line, copy and paste JSON-LD for Article or BlogPosting, Product, Organization, LocalBusiness, BreadcrumbList, VideoObject, Event, ProfilePage and WebSite. Leaves empty optional fields out and checks for missing required ones. | Plain values: names, URLs, dates, prices |
| Rollout Plan | One row per template and type, with what Google can show, required and recommended properties, days to target and the next step. | Template, example URL, pages, type, owner, status, target date |
| Dashboard | 15 key numbers, results by schema type, blocks by priority and blocks failing each check, with two charts. | Nothing |
| Settings | Analysis date, coverage and freshness rules, grades, the 11 checks with weights, rules and fixes, the Type Rules table for 17 types and lists. | Optional tuning and new types |
| AI Prompts, Checklist, Sources | All 22 prompts, the checklist with automatic progress, and where every fact and assumption comes from. | Yes or No per step |
Yellow cells are inputs. Grey cells under green headers are formulas. All 500 Schema Lab rows and 100 Rollout Plan rows are ready with formulas and dropdowns.
The 11 schema checks and why each one matters
Each check scores 1 (pass), 0.5 (partly) or 0 (fix). A check is left blank, and not scored, when it does not apply or you have no data. The weights and thresholds are starter assumptions for this kit and are editable on Settings.
| Check | Weight | Rule | Why it matters |
|---|---|---|---|
| All required properties | 12 | Every required property, each either or group and conditional ones like offers.price with offers. | Google says items missing required properties are not eligible for rich results. |
| Matches the visible page | 12 | Your check: Yes, Partly or No. | Markup must be a true representation of the page. The Rich Results Test cannot see a wrong price. |
| Not blocked for Googlebot | 8 | No robots.txt block, noindex or login. | Google cannot use markup on a page it cannot crawl or index. |
| Passes Rich Results Test | 8 | Valid pass, warnings partly, invalid or not tested fix. | The quickest way to catch technical errors. |
| Type earns a Google result | 6 | Supported pass, retired partly. | Retired rich results no longer show, whatever the markup. |
| Enough recommended properties | 6 | 70 percent or more pass, 40 percent or more partly. | Google says more recommended properties give a higher quality result. |
| Type fits the page | 6 | The page type is in the type's Best on list. | For example, product snippets are for pages about one product, not categories. |
| Search Console status | 5 | Report valid pass, warnings partly, errors fix. | Shows problems across every page of a template, not just one URL. |
| No self serving reviews | 5 | No review or aggregateRating in Organization or LocalBusiness markup about your own business. | Google supports these reviews only on sites that capture reviews about other businesses. |
| Values up to date | 4 | Checked within 180 days pass, 365 partly. | Google asks for up to date information. Prices, hours and dates go stale fast. |
| JSON-LD format | 3 | JSON-LD pass, Microdata or RDFa partly. | All three work; JSON-LD is Google's recommended format and the easiest to maintain. |
How the score and eligibility work (with a worked example)
The score is the weighted share of checks a markup block passes: the sum of weight x result for every check with data, divided by the total weight of those checks, times 100. A is 85 or more, B is 70 or more, C is 55 or more, anything lower is D. Rich result eligibility is a separate verdict: a block is Eligible only when the type is supported, nothing required is missing, the page is not blocked, the values match the page, the type fits and the Rich Results Test passes. Even then Google does not guarantee a rich result.
Worked example. In the demo, BrewNest checks the Product markup on its Kalimpong light roast page. The markup has name, image, description, brand, offers, offers.price, offers.priceCurrency. The Rich Results Test says Valid, Search Console shows Warnings, and the values were last checked on 10 March 2026. But the markup still says Rs 499 while the page now says Rs 549.
- Required: 3 of 3 present: name, one of the offers, review or aggregateRating group (offers), and offers.price because offers is used.
- Recommended: 2 of 5 present (offers and offers.priceCurrency), so 40 percent. Missing: aggregateRating, review, offers.availability.
- Passes (43 points): type earns a result (6), all required properties (12), not blocked (8), Rich Results Test (8), type fits the page (6) and JSON-LD (3).
- Partly (7.5 points): recommended properties (half of 6), Search Console warnings (half of 5) and values last checked 257 days ago (half of 4).
- Fails (0 points): matches the visible page.
Self serving reviews do not apply to Product, so the total weight is 70. 50.5 of 70 is a score of 72, grade B, with 4 fixes. A B looks fine, but the priority is Fix now: markup does not match the page and eligibility says No: does not match the page. This is the lesson of the example: the Rich Results Test checks syntax, not truth. Only you can see that the price changed.
The fix is to output the price from the same field the page uses, add offers.availability, and recheck the values. Build the corrected block on the JSON-LD Builder to see the shape.
Other demo rows show the range. The home page Organization markup includes aggregateRating and review from a review widget, so it shows Fix now: self serving review markup. The Coorg dark roast is missing its price block, so the list says one of offers, review, aggregateRating. The shop category page carries Product markup and shows Fix: wrong type for this page. The workshop Event is missing location.address and the AeroPress video is missing uploadDate. The FAQ and How to blocks show Low priority: rich result retired. The author profile is perfect markup on a page set to noindex by mistake, so it shows Fix now: blocked for Googlebot. The pour over guide scores 96 but covers only 57 percent of recommended Article properties, so it shows Improve: add recommended properties (dateModified, author.name and author.url).
Priority rules
| Priority | Rule | What to do |
|---|---|---|
| Fix now: blocked for Googlebot | robots.txt, noindex or a login blocks the page. | Unblock it, unless the page should really stay out of Google. |
| Fix now: markup does not match the page | Matches = No. | Generate markup from the same data the page shows. |
| Fix now: required properties missing | Any required property missing on a supported type. | Add it in the template. |
| Fix now: invalid markup | Rich Results Test says Invalid. | Fix the syntax errors the test lists. |
| Fix now: self serving review markup | Reviews in Organization or LocalBusiness markup about your own business. | Remove review and aggregateRating from that markup. |
| Fix: wrong type for this page | Page type not in the type's Best on list. | Use a type that describes the main content, or remove the markup. |
| Low priority: rich result retired | FAQPage, HowTo or ClaimReview. | Accurate markup can stay; do not invest more time. |
| Improve: add recommended properties | Recommended coverage below 70 percent. | Add the recommended properties you can fill with true facts. |
| Healthy: monitor | Score 85 or more. | Recheck after template or price changes. |
| Improve when you can | Everything else. | Work through the fixes in order. |
Using the JSON-LD Builder
Each of the 9 blocks has plain fields (name, URL, date, price), a note saying whether Google requires or recommends the property, a grey output cell and a check. Empty optional fields are left out by themselves, so the output stays valid.
- Fill the yellow fields with facts that appear on the page. Use ISO 8601 dates with a time zone, such as
2026-12-13T10:00:00+05:30. - Wait for the check to say Ready to paste. If it says Missing, add what it lists.
- Copy the grey output cell. It is one line, so it pastes cleanly into a page, a CMS field or a tag manager.
- Paste it into the page head or body, publish, and test the live URL in the Rich Results Test.
For example, the demo Product block outputs "offers": {"@type": "Offer", "price": 549, "priceCurrency": "INR", "availability": "https://schema.org/InStock"} and a rating with 38 reviews. The BreadcrumbList block leaves item off the last crumb, as Google allows. Every demo output is checked as valid JSON when the kit is built.
For templates with hundreds of pages, use the builder output as the pattern and have your CMS fill the values from page data. Our guide on how to add schema markup to any website shows where to place it on common platforms.
Column by column guide to the Schema Lab
| Column | What goes in it | Tip |
|---|---|---|
| URL, Page type | The page and one of 16 page types. | A page with two blocks (Article and BreadcrumbList) gets two rows. |
| Schema type, Format | A type from Type Rules, and JSON-LD, Microdata or RDFa. | Spelling must match the Type Rules row. A LocalBusiness subtype can use the LocalBusiness row. |
| Properties in the markup | Property names, comma separated. Nested names with a dot: author.name, offers.price, location.address. | A nested name also counts its parent, so author.name covers author. |
| Matches the visible page? | Yes, Partly or No, after comparing every value with the page. | The most important judgement in the sheet. Be strict. |
| Rich Results Test, Search Console report | The result of each. | Use Not supported by the test for types the test does not cover. |
| Blocked for Googlebot?, Values last checked | Yes or No, and a date. | Check robots.txt, the robots meta tag and logins. |
| Impressions | Search Console, last 28 days. | Fix markup on pages people actually see first. |
| Measures, checks, Score, Grade, Fixes, Eligibility, Priority | Automatic. | Row 3 above the checks shows each weight from Settings. |
Your first 30 days with this kit
- Week 1: inventory. List every template on the Rollout Plan and test one URL each. Fill the Schema Lab for your top 20 pages by impressions.
- Week 2: fix the blockers. Unblock pages, fix mismatched values and add missing required properties in the templates.
- Week 3: clean up. Remove self serving review markup and wrong types, and stop new work on retired types like FAQ and How to.
- Week 4: add value. Add recommended properties and roll out supported types you are missing, such as Product offers, Event or BreadcrumbList, using the builder.
Then watch the Search Console reports and mark templates Validated. Structured data helps Google understand who you are; the entity research template kit helps you decide which entities and facts each page should make clear.
The chained prompt workflow (from page to validated markup)
Prompts 18 to 22 below are built to run in order in one AI chat:
- Brief the assistant on your site and the rules: only visible facts, JSON-LD, Google's required properties.
- Paste the page text and the facts it shows.
- Get the JSON-LD for the right type with every required and useful recommended property.
- Pressure test it line by line against the page and Google's rules.
- Get a row for Excel, ready to paste into the Schema Lab.
AI assistants often invent ratings, prices or dates to fill a schema. Give them only the facts on your page, and always run the result through the Rich Results Test.
Schema markup mistakes to avoid
- Markup that does not match the page. Old prices, old dates and hidden content break Google's rules and its AI best practice.
- Missing required properties. No rich result is possible without them.
- Reviews about yourself. Star ratings from your own widget in Organization or LocalBusiness markup will not show.
- Product markup on category pages. Product snippets are for pages about one product.
- Investing in retired types. FAQ and How to rich results are gone; spend the time on supported types.
- Blocking the page. noindex or robots.txt makes the best markup useless.
- Trusting the Rich Results Test alone. It checks syntax and required fields, not whether the values are true.
- Expecting schema to rank the page. Structured data helps Google understand and present a page; it does not replace helpful content. Our guide what is schema markup explains what it can and cannot do.
AI prompts for schema markup
Copy a prompt, replace the green parts in square brackets, and paste it into ChatGPT, Claude or Gemini. Always check the output against real data before you act on it.
Here is a summary of my page: [URL, page type, main content]. Which schema.org type best describes the main content, and does Google show a rich result for it today? List any secondary types worth adding, like BreadcrumbList. Only suggest types that describe content visible on the page.
Here is the visible text of my [page type] page: [paste]. Write JSON-LD for the [type] type using only facts that appear in this text. Include Google's required properties and the recommended ones the text supports. Do not invent prices, ratings, dates or names.
Here is the JSON-LD on my page: [paste]. And here is the visible page text: [paste]. List every value in the markup that is not on the page or differs from it, every required property Google needs for this type that is missing, and any property that looks invented.
The Rich Results Test shows these errors and warnings for my page: [paste]. Here is my markup: [paste]. Explain each issue in plain words and give me the corrected JSON-LD.
Here is one row of my product data with these columns: [paste]. Write Product JSON-LD with name, image, description, brand, sku and an Offer with price, priceCurrency and availability. Then turn it into a template with placeholders I can fill from each row.
Write BlogPosting JSON-LD for my article "[title]" by [author] ([author profile URL]), published [date], updated [date], with this main image: [URL]. Use ISO 8601 dates with my time zone ([zone]). Add only properties I gave you.
Write JSON-LD for my [business type] using the most specific schema.org subtype. Name: [name]. Address: [address]. Phone: [phone]. Hours: [hours]. Website: [URL]. Coordinates: [lat, long]. Use openingHoursSpecification for the hours. No reviews or ratings.
Write Event JSON-LD for "[event]" on [date and time] at [venue and full address], tickets [price and currency] at [URL], organised by [organiser]. Add eventStatus and eventAttendanceMode. Flag anything Google requires that I did not give you.
My page [URL] sits under this trail: [Home > Section > Page, with URLs]. Write BreadcrumbList JSON-LD that matches the breadcrumb shown on the page. Leave item off the last crumb if it is the current page.
Write VideoObject JSON-LD for my video "[title]": description [text], thumbnail [URL], upload date [date], duration [minutes and seconds], file URL [URL], embed URL [URL]. Convert the duration to ISO 8601.
Write Organization JSON-LD for my home page and a separate WebSite block for the site name. Name: [name]. Other name: [short name]. URL: [URL]. Logo: [URL]. Official profiles: [URLs]. Contact: [email, phone]. Address: [address]. No reviews or ratings.
Write ProfilePage JSON-LD for the author page of [name] at [URL]: [short bio], photo [URL], profiles [URLs], page created [date], updated [date]. The person should be the mainEntity.
I want to add review stars with this markup: [paste]. The reviews are about [my own business or another product or business] and they come from [source]. Based on Google's review snippet guidelines, is this eligible? If not, what should I do instead?
My site uses these schema types: [list]. Which of them no longer produce a rich result in Google Search, and which still do? For the retired ones, should I keep, change or remove the markup? Base your answer on Google's current documentation and say what to verify.
Here is the Microdata on my page: [paste HTML]. Convert it to an equivalent JSON-LD block with the same values, and list the HTML attributes I can remove once the JSON-LD is live.
My site has these templates: [list with page counts]. Suggest the schema types for each template, the data fields each needs from my CMS, and the order to roll them out based on which still earn a Google result.
Here are the key numbers and top issues from my schema audit: [paste Dashboard numbers and Schema Lab priorities]. Explain in plain words what to fix first, what can wait and what I can ignore.
You are my structured data editor. My site: [site], about [topic]. Rules: JSON-LD only, the most specific schema.org type, every Google required property, recommended properties only when the page shows the fact, never invent values, no reviews about my own business. Confirm, then wait for my page.
Here is the page: URL [URL], page type [type], visible text [paste], and these facts that appear on it: [prices, dates, names, address, hours]. Tell me which schema types fit this page and which Google rich results they can earn.
Write the JSON-LD for the main type you chose, plus BreadcrumbList if the page shows a breadcrumb. Use only the facts I gave you. After the code, list each Google required property and where its value comes from on the page.
Check your JSON-LD line by line: is every value visible on the page, are all required properties present, is the type right for the page, are dates in ISO 8601 with a time zone, and is anything invented or self serving? Return the corrected code.
Turn the final markup into a row with tabs between columns for my Schema Lab: URL, Page type, Schema type, Format (JSON-LD), Properties in the markup (comma separated property names, nested ones with a dot), Matches the visible page (Yes), Rich Results Test (Not tested), Search Console report (blank), Blocked for Googlebot (No), Values last checked ([today]), Notes.
Schema Markup checklist
- Each template has a planned schema type that describes its main content
- The type still earns a Google result; no new work on retired FAQ or How to rich results
- All Google required properties are present for each type
- Recommended properties are added where the page shows the fact
- Every marked up value is visible on the page and matches it exactly
- Nothing in the markup is hidden, invented or misleading
- No review or rating markup about your own business
- Product markup only on pages about one product
- Markup is in JSON-LD and generated from the same data the page shows
- Dates use ISO 8601 with a time zone
- Marked up pages are not blocked by robots.txt, noindex or a login
- A sample URL per template passes the Rich Results Test before release
- Search Console enhancement reports are checked after release
- Values are rechecked after every template, price or schedule change
0 of 14 done
Related free assets
Read next on Brandella Journal
- What is schema markup? A complete guide for SEO and AI search
- How to add schema markup to any website (JSON-LD examples)
- LocalBusiness schema markup: 7 essential properties to add
Free tools that pair with this asset
Sources
- Google Search Central: General structured data guidelines
- Google Search Central: Structured data markup that Google Search supports
- Google Search Central: AI features and your website
- Google Search Central: Product snippet structured data
- Google Search Central: Latest documentation updates (FAQ rich result retirement)
- Google Search Central Blog: Changes to HowTo and FAQ rich results
FAQ about schema markup
1Is this schema markup template free?
Yes. The Excel workbook, JSON-LD Builder, PDF guide, prompts and checklist are free to download and use for your own sites and for clients, with no sign up.
2Which format should I use for structured data?
Google supports JSON-LD, Microdata and RDFa and recommends JSON-LD. The kit's builder writes JSON-LD and the Schema Lab scores Microdata and RDFa as partly, because they work but are harder to maintain.
3Does schema markup help with AI Overviews and AI Mode?
Google says there is no special schema.org structured data needed to appear in its AI features, and lists making sure structured data matches the visible text as a best practice. So accurate markup on a good page helps; extra markup just for AI does not.
4Should I remove FAQ schema now that FAQ rich results are gone?
Google stopped showing FAQ rich results on 7 May 2026. Accurate FAQ markup can stay, but it will not produce a rich result, so the kit marks it as low priority. Spend new effort on supported types such as Product, Article, Event or LocalBusiness.
5Why does the Rich Results Test pass but I get no rich result?
The test checks syntax and required properties. Google also needs the values to match the page, the page to be indexable and the content to meet its guidelines, and even then it does not guarantee a rich result. The kit checks those other conditions too.
6Can I add star ratings for my own business?
Not in Organization or LocalBusiness markup about your own business. Google supports review markup for these types only on sites that capture reviews about other businesses. The kit flags this as self serving review markup.