Model facts before markup
Structured data describes what a page is about. It should match the visible content and the real business. Before adding properties, confirm the business name, actual address, service areas, author, contact details, and relevant external profiles.
Use stable identifiers
Give the business and author stable identifiers, then reference them from service and article records. Separate script blocks can reference the same identifiers; nesting everything into one graph is not a prerequisite for correctness.
| Relationship | Meaning |
|---|---|
| Service → provider | Who delivers the work |
| Service → areaServed | Where the service is available |
| Article → author | Who wrote the material |
| Person → sameAs | Another profile for the same person |
Geographic example
A consultant based in Faisalabad who works remotely with a Houston business can describe Houston as a service area. That does not create a Houston office. Use the actual provider address; do not assign a city-center coordinate as a substitute business location.
Keep article records aligned
Use the same resolved record for the visible title, publication date, modification date, author, and JSON-LD. A later editorial change should update the modification date, not silently rewrite the original publication date. Optional word counts should be computed or omitted rather than maintained as guesses.
Validate meaning and syntax
Parse the JSON and review the relationships. Use the appropriate validation tools for eligible search features, then check the output in the real page. Correct markup does not guarantee a Knowledge Panel, a rich result, a ranking, or an AI citation.