Shops and catalogs
If JSON-LD says $12 and the button says $40, you published a lie for machines. Visible wins, then markup.
LocalBusiness hours schema is a sibling idea: markup equals page. Offer and availability must match sold-out. We will not invent rich-result guarantees. Search Central documents the types. Someone who pasted a Product JSON-LD generator with last year's price and five stars. If it is not on the card, it is not in the graph.
Use Product structured data only when it matches the visible title, price, currency, and availability on the Bizzit shop. Do not stuff reviews. Do not markup a SKU you cannot sell. Free is you.bizzit.io with 50 Cipher turns and no daily cap. Pro is $12 a month with checkout on your account and no sales cut. Processor fees are theirs.
Who this is for
Someone who pasted a Product JSON-LD generator with last year's price and five stars. If that is not you, a different Bizzit guide will fit better, do not force this URL.
The actual answer
LocalBusiness hours schema is a sibling idea: markup equals page. Offer and availability must match sold-out. We will not invent rich-result guarantees. Search Central documents the types. If it is not on the card, it is not in the graph. The short version is still the one in the box at the top of this page. The rest of the article exists so you do not have to guess the limits.
Do this in order
Finish the card. Then markup. Then compare. Rebuild if Cipher's graph drifted.
- Lock visible price and availability
- Add Product markup that copies those fields
- Skip review schema you did not earn
- Remove markup from sold-out if the offer is gone
- Do not doorway product graphs per city
What not to do
Do not invent SKU availability in JSON-LD. Do not copy another shop's offers. Do not mix Service schema on a mug. That is the usual way a useful page turns into a doorway, a fake comparison, or a brief Cipher cannot honor.
How this shows up on Bizzit
FAQ schema is separate and must also match visible FAQs.
Currency in the graph
The schema currency must be the checkout currency you mean. Do not mark EUR on a USD button.
Limits
Do not invent SKU availability in JSON-LD. Do not copy another shop's offers. Do not mix Service schema on a mug.
Limits and caveats
Do not invent SKU availability in JSON-LD. Do not copy another shop's offers. Do not mix Service schema on a mug.
If a sentence would require a competitor SKU we have not verified, or a statistic we did not measure, it does not belong here.
What to do after you read this
If this page answered the query, open Create with the nouns from your own business, not a slogan. If it did not, you are probably in the wrong cluster: go back to the blog hub or Shops and catalogs. Do not spin a second URL for a synonym. One intent per page is the whole point of this library.
Tools that actually do this job
These are public pages. Use them when the job is this job. They are not a second product you have to buy.
Primary sources
Questions people actually ask
Does schema rank the product?
It can affect eligibility. We do not sell rankings.
Multiple offers?
Only true variants you ship. Empty cells for fake colors.
Merchant Center?
Google's product. We will not paste their grid onto Pro.
GBP products vs schema?
Both must agree with the site. Two catalogs is two lies if they drift.