Begin with the page and its purpose
Choose a real page and identify what it contains. A business contact page, product page and article serve different purposes and can require different information. Do not invent reviews, prices, opening hours or credentials to complete a markup template. Information should be supported by the page and business. Some pages do not need structured data for a particular search feature, so absence alone is not an automatic technical failure.
Check whether the JSON-LD can be read
JSON-LD is a common format for embedding structured data. A missing comma, broken quotation mark or malformed object can stop a parser from reading it. ColbySEO's public report can assess JSON-LD syntax in collected source pages and use conclusive syntax evidence in the Technical score. A syntax pass establishes readability of that markup sample, not the truth of every value or eligibility for a search feature.
- Find the affected source page and script.
- Repair malformed syntax at its template or source.
- Check other pages that use the same component.
Review values against visible content
Compare the business name, address, contact information and other relevant fields with the actual page and current operation. A copied template can leave another company's details behind even while the JSON parses correctly. Conflicting plugins can also emit overlapping or inconsistent objects. Keep the markup accurate and maintainable; correcting the shared source is safer than layering another script over information you no longer trust.
Validate the intended supported feature
If your goal is a specific Google search feature, read that feature's current documentation and test with the appropriate validation tool. Required and recommended properties differ by feature. Google's Rich Results Test can assess supported markup, but an eligible result still does not guarantee display. A general parser and a feature-specific validator answer different questions, so do not describe a JSON-LD syntax pass as complete rich-result validation.
Keep deployment and outcomes separate
Publish a focused correction and inspect the live page. Confirm the source now contains the expected markup, then rerun the relevant syntax and feature checks. Use a free ColbySEO report and its saved PDF to document the public evidence. Search appearance requires separate observation over time. When requesting help, provide the page URL and the type of information it should represent, rather than asking for markup solely to raise a score.
Common questions
Does valid JSON-LD guarantee a rich result?
No. Valid syntax is one layer. Relevant feature requirements, content policies and Google's presentation decisions are separate considerations, and eligibility does not guarantee a particular display.
Is a page without structured data automatically unhealthy?
No. Review the page's purpose and whether a supported feature is useful. Do not add irrelevant or unsupported information simply to make a checker show more passes.
Does the free report validate every schema property?
No. Its conclusive score check concerns collected JSON-LD syntax. Accuracy, completeness and feature-specific eligibility require additional review and appropriate validation.