MyIPScan

Website Security and SEO Tool

Structured Data / JSON-LD Validator

Check one public URL for JSON-LD blocks, schema.org types, malformed structured data, duplicate schema signals, and basic rich-results-oriented findings. This is a safe single-page diagnostic, not a crawler or Google Rich Results emulator.

Check structured data

Enter one public HTTP or HTTPS URL. The checker fetches only that URL, parses capped HTML for structured data, and does not execute JavaScript.
Technical response details (optional)

Trust note: this server-assisted check does not crawl links, render JavaScript, or store page content.

What this checks

MyIPScan safely fetches one public URL with DNS preflight, follows a limited redirect chain, reads a capped HTML response, parses JSON-LD script blocks, detects common schema.org types, and reports Microdata/RDFa as lightweight presence signals.

What the results mean

Valid JSON-LD and clear schema types can help parsers understand a page. Warnings point to issues worth reviewing, such as malformed JSON, missing @context or @type values, duplicate schema blocks, empty values, placeholder text, or schema URLs that differ from the canonical URL.

How to use this tool

  1. Enter the exact public page URL you want to inspect.
  2. Review the schema summary, JSON-LD blocks, validation findings, and Microdata/RDFa presence signals.
  3. Compare related page-level signals with the Meta Title / Description Checker, HTML Heading / Content Structure Checker, Open Graph / Social Preview Checker, Canonical / Noindex Checker, Sitemap Checker, and Robots.txt Checker.

FAQ

What is JSON-LD?

JSON-LD is a structured data format that places schema.org data inside script tags so search engines and other parsers can understand page entities and relationships.

What is structured data?

Structured data is machine-readable metadata that describes page content, such as an organization, article, FAQ, product, breadcrumb trail, or web application.

Does schema markup help SEO?

Schema markup can help search engines understand a page and may support eligible enhancements, but it is not a ranking or rich-result guarantee.

What causes invalid structured data?

Invalid structured data can come from malformed JSON, missing required-looking fields, duplicate templates, empty values, placeholder text, or schema that does not match the canonical page.

What is the difference between JSON-LD and Microdata?

JSON-LD keeps structured data in separate JSON script blocks, while Microdata embeds item attributes in the HTML markup. This tool parses JSON-LD and reports Microdata/RDFa as lightweight presence signals.

Limitations

This tool checks one public URL only. It does not execute JavaScript, crawl linked pages, emulate Google rendering, validate every schema.org property, or guarantee rich-result eligibility. See the methodology for how MyIPScan labels limited checks.

B2B diagnostic report model

Search and AI visibility diagnostics

Visibility checks connect access signals, robots.txt, bot-specific rules, noindex, canonical, sitemap, machine-readable metadata, llms.txt, structured data, headings, and Open Graph.

SummaryStart with a plain-language status for the public target.
Top issuesPrioritize the few findings that need attention first.
What passedShow expected public signals without turning them into a certification.
What needs reviewSeparate limited, unavailable, and review-worthy signals.
Why it mattersExplain the business, delivery, crawl, or implementation impact.
Recommended fixesPoint to the DNS, hosting, email, CMS, or SEO owner who can act.
What this tool cannot checkThis cannot guarantee ranking, indexing, search traffic, AI citations, crawler compliance, or how private AI/search systems will behave.
Client-safe copyClient-safe copy should keep crawlability findings and recommended fixes while removing raw headers, crawler-policy payloads, tokens, and oversized technical dumps.
Monitoring beta (optional)Optional monitoring beta can compare robots.txt, Googlebot access, noindex, canonical, sitemap inclusion, llms.txt, and AI crawler policy changes.

Client-safe report

Share findings without leaking raw technical material

Use Safe Copy or this page's summary when sending results to a client, vendor, developer, or support team. Raw headers, credentials, tokens, cookies, private addresses, email local-parts, and oversized payloads should stay out of client-facing copy.

Check Google/AI visibility

What this checks

Public crawl and metadata signals such as robots, sitemap, canonical, noindex, headings, structured data, and social preview tags.

Limits

What this cannot check

It cannot guarantee ranking, indexing, AI citation, or crawler behavior beyond visible public signals.

Read results

How to use the output

Treat results as review signals for this browser/session or public target. Re-test after one change, then use Safe Copy or notes that avoid raw identifiers.