Structured data should describe your real page, not a better-sounding business: working record
Use this six-field worksheet to review schema truth, visibility and type fit before focusing on optional warning counts.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Page and schema type | Claim in markup | Visible supporting content | Required-field issue | Truth or scope correction | Validation and public retest |
|---|---|---|---|---|---|
| Illustrative: article schema | Unsupported five-star rating | No genuine supporting display | Not a missing-field problem | Remove unsupported claim | Developer retest pending |
- The starting row is fictional, not merchant evidence. Replace it with your own verified record. Blank fields remain unresolved.
- Create one row per decision or observation described in the article. Use the worked example to understand the method, not as proof about your business.
- Record exact public URLs and collection dates where relevant. Unknown, failed and not checked are different from a verified pass.
- Keep customer information, account credentials and private documents outside this worksheet. Use role names or internal references.
- A completed row does not prove publication, authorization, indexing, rankings or revenue. Record the actual acceptance check separately.
- Export the record to approved business storage if needed. Browser edits are cleared on reload.
A schema validator can confirm the markup reads fine and still miss a false business claim. Check the code and the page it describes. Structured data should make accurate information easier to understand, not add reviews, locations, or guarantees visitors can’t verify.
Use with this guide
website audit tool
Review the current scope and workflow for website audit tool.
business website tool
Review the current scope and workflow for business website tool.
Write wellness-class information without unsupported health claims
Describe the actual class and arrival process. A useful schedule page does not need unsupported promises about symptoms, outcomes or suitability for everyone.
Check the content before the warning count
Google says structured data must describe the page honestly. Misleading or irrelevant markup is out, and you can’t mark up content readers can’t see. First, figure out what the page is actually about and which schema type fits. A local service page, an article and a real dataset aren’t the same thing. Don’t pick a type just because it gets a pretty test result. The website audit tool can organize technical findings, but a person still needs to check that any rating, business identity or service claimed really exists and is accurately shown on the page.
Sources for this section: Google Search Central: structured-data guidelines
Separate syntax from eligibility and appearance
Valid JSON is one checkpoint. The supported feature also needs its required properties, and the content must follow policy and get the facts right. Google’s guidelines say automated tests can’t easily judge every quality requirement. So passing a tool doesn’t guarantee a rich result. Check the current official documentation for the schema feature you’re using. Don’t borrow a checklist for some unrelated type. The business website tool supports content publication where enabled, but structured-data implementation may require developer work. Check the live output after a shared template changes.
Sources for this section: Google Search Central: structured-data guidelines
Use a truthful-markup example
Imagine an illustrative repair-shop article that contains an Organization reference and Article markup. If the template adds a five-star rating that does not correspond to a genuine, supported review display, don’t invent visible reviews to make the markup look complete. Remove or correct the unsupported claim under the applicable guidance. An optional-field warning is different: resolve it only if the business has truthful information for that field. Don’t make up a license, address, or identifier just to silence a report. The audit needs to separate a technical omission from a real-world fact that’s missing.
Sources for this section: Google Search Central: structured-data guidelines
Verify the page and generated markup together
Ask the developer to check the public page, the generated structured data and the relevant validation result. Keep the business identity and URLs consistent across related pages where appropriate. Check that referenced images are relevant and accessible. Google’s image guidance recommends representative page imagery rather than unrelated generic visuals for article previews. A successful local preview is not enough if the deployed server serves different metadata. Retest after publication and record the date. Search Console notifications may reflect earlier crawls, so compare the live evidence with the reported issue. Don’t keep changing markup that’s already correct.
Sources for this section: Google Search Central: image best practices
Use the structured-data truth register
Create a row for each meaningful claim or issue, not just each page. Note the schema type, the claim, what visibly supports it, and any required-field problem. The business owner handles factual fixes. The developer handles implementation. Keep the validation result separate from the public retest. If information lacks support, leave it unresolved or remove it properly. Don’t guess to fill a field. BlueFinch’s audit doesn’t certify legal claims or guarantee enhanced search appearance. It gives you a repair record tied to actual page content and current official requirements.
For an optional field, record “not supplied because supporting fact unavailable” if that’s the honest answer. An advisory warning isn’t the same as an error for a required property. Make sure the reviewer gets that before asking the developer to add random values just to cut down the messages in an automated report.
Primary sources
BlueFinch last reviewed these sources on October 23, 2026. Check the linked sources for current requirements and product details.
Use this page for general business information. It is not legal, tax, or accounting advice.