Semantec SEO learning
Repair schema findings by their consequences
Schema check findings can concern code syntax, a feature requirement, an optional enhancement or a false assertion. Identify which layer failed before setting repair priority. A warning colour cannot establish that the page tells the truth.
Read the diagnostic examples
Three findings, three different repairs
These fictional findings show why report severity and factual severity need separate judgments. Read the evidence and consequence, not colour alone.
Malformed JSON
Observable evidence: the parser rejects an unterminated string in the emitted graph.
Repair: correct the source that produces the markup, render it again and confirm the affected graph parses.
Consequence: hold the broken markup. A required feature condition may also remain unmet.
An optional entry is absent
Observable evidence: the relevant feature documentation identifies the entry as recommended rather than required for the intended use.
Repair: add it only when supported and useful; record it separately from blockers.
Consequence: the warning alone does not justify inventing an entry or blocking unrelated work.
Wrong author identity
Observable evidence: the byline and confirmed author record identify a different person from the referenced node.
Repair: resolve the identity and correct the emitter; check the byline and graph together.
Consequence: hold the false relationship even if a checker reports no errors.
Read the graph, the page and the source together
A parser can test an expression for syntactic readability. A vocabulary check can flag unsupported terms or entry formats. A test for a particular platform can assess some conditions for a search feature. None of these alone establishes that a node identifies the right person, that a price is current or that an assertion is visible and supported.
Keep four questions distinct: can the graph be read; does it use the intended vocabulary; does it meet the documented conditions for the intended feature; and does it accurately describe the page and its subjects? Record the tests performed and what remains unknown.
A material mismatch can require repair without a red report. A missing optional property can remain an enhancement. A required eligibility condition concerns that feature; it does not prove every other part of the website must be withdrawn.

Find the source of the defect before editing copies
Record the affected URL, node identifier, property path, emitted entry and expected entry with its controlling evidence. Trace the entry to its theme, plugin, template, product record or manual markup. A correction to one rendered copy will not repair a shared emitter that continues producing the defect.
- Identity or meaning failureResolve the subject or relationship with the factual owner. Repair references and visible statements that depend on it.
- Stale or unsupported entryCheck the effective period, market and version. Replace it with a supported current entry or remove the unsupported assertion; do not infer a missing entry merely to satisfy a test.
- Shared template defectRepair the source rule and inspect representative affected pages, including records with missing data or documented exceptions.
- Duplicate emittersCompare the emitted assertions and identities. Reconcile contradictions at their source; repeated syntax alone does not explain the factual consequence.
Assign one accountable repair owner for each finding, while identifying any editorial, product or technical evidence they need. State the release consequence and the condition that will permit reconsideration.

Retest the repaired output and its dependencies
In a fictional article family, a shared template points every author reference to one person. Repairing the visible byline on a single page leaves the graph and other articles wrong. Correct the author mapping, inspect the emitted reference on that page, and check other affected author combinations.
- Reproduce the original defect.Keep the failing entry and its location so the repair can be compared with the original finding.
- Verify the source correction.Confirm the identity, entry or output rule against the controlling record.
- Inspect the emitted result.Run the relevant syntax and feature checks, then compare the graph with the visible page. Check the served output after cache and output processing layers so an old or transformed graph does not hide the result.
- Test the affected family.Include an ordinary record, a case with a missing entry and any known exception. Retain a regression case for the original failure.
Record the change, its scope and the next review trigger. A later product release, source expiry or template change can reopen the decision. Passing a test does not guarantee indexing, rich results or a particular search presentation.

Questions and answers
Should every warning block a release?
No. Classify it as a required condition, an optional enhancement or a factual defect. Document the intended feature and evidence. Do not equate warning colour with business or factual severity.
Why can a valid graph still be wrong?
The tested rules may not establish identity, current facts, source support or consistency with visible content. A correctly formed reference can still identify the wrong person.
Who should repair the finding?
The accountable owner must control, or coordinate changes to, the source that produces the markup. A factual correction may need an editorial or product owner before a developer changes the emitter.
What should be checked after a repair?
The original failing assertion, the emitted graph, visible content, affected templates and relevant feature conditions. Check related assertions when the repair changes identity or a shared source.
Related reading and sources
Use these resources for the next question or the requirements relevant to your website work.
