Structured Data Visible-content Comparator
Compare supplied markup facts with page excerpts; flag unsupported claims.
Compare selected scalar JSON-LD facts with supplied page excerpts using normalized literal matching. Formatting and meaning still need review; pages are not fetched.
Using Structured Data Visible-content Comparator
Compare supplied markup facts with page excerpts; flag unsupported claims.
- Try the tailored worked example, or open supported local sources. Configuration-only builders start from editable settings. Input schema: One JSON object: {graph: JSON-LD, excerpts: [{url,text}] }.
- Select a Review card for source evidence and supported manual fields. Details & settings controls the thresholds, patterns, URL policy or observation windows; originals stay unchanged.
- Use Preview to inspect the result and method notes. Interactive accessibility prototypes support real keyboard controls; search tools work only with supplied evidence.
- Use Export for the complete workflow ZIP or individual artifacts. Open an exported file before publishing it. Save review retains settings/decisions and source fingerprints; file-based projects need the exact originals to reopen.
Example
The worked example is specific to Structured Data Visible-content Comparator. It uses One JSON object: {graph: JSON-LD, excerpts: [{url,text}] }. Compare selected scalar JSON-LD facts with supplied page excerpts using normalized literal matching. Formatting and meaning still need review; pages are not fetched.Questions & answers
What does Structured Data Visible-content Comparator support?
Compare selected scalar JSON-LD facts with supplied page excerpts using normalized literal matching. Formatting and meaning still need review; pages are not fetched.
What should my input contain?
One JSON object: {graph: JSON-LD, excerpts: [{url,text}] }.
What can I export, and does this change my live website?
Exports include the result data, source fingerprints, decisions and task-specific artifacts such as printable HTML, SVG review evidence, timed VTT notes, JSON-LD, sitemap XML, rule cases or checklists. These pages do not deploy rules, submit URLs, crawl a server or publish content. Public pages retain approved ads and optional consent-based analytics.
What should I verify before relying on the result?
Use the method notes and full evidence. Files are normally limited to eight sources, 25 MiB each and 80 MiB total, with smaller format/graph/image bounds. Worker analyses stop after 30 seconds. Accessibility helpers require real user/assistive-technology review; search evidence cannot guarantee indexing, eligibility, ranking changes or causal effects.
Related tools
A useful next step for your task.
Developer & DataRobots.txt Generator & TesterRecommendedFull workspaceBuild and edit robots.txt with multiple crawler groups, Allow and Disallow rules, sitemap declarations and ready presets. Test URL lists, explain…
Developer & DataHreflang Generator & CheckerBuild multilingual page groups, generate hreflang HTML tags, HTTP Link headers and XML sitemaps, and check supplied markup for missing alternates,…
Developer & DataCanonical Conflict AnalyzerCompare canonical, redirect and sitemap signals from imported crawls; export contradictions.
Developer & DataIndexability Decision TraceCombine supplied robots, meta and status evidence; explain likely indexability barriers.
Help improve this tool
Report a problem or suggest an improvement
Describe the issue without pasting private tool input. Feedback goes to our admin inbox.