Practical guide · Prepared with AI assistance
Match JSON-LD fields to visible information in blog articles. Verify titles, authors, images and dates to avoid invented promises of rich results.
Three takeaways from this article
- Match visible information.
- Do not invent authors or dates.
- Test JSON separately.
Markup should describe visible content
Structured data is not a place to add achievement or authorship information absent from the page. Google's Article documentation explains appropriate fields for understanding news and blog content. The markup and visible title, author and image should match. Adding this code alone does not guarantee a rich search appearance or ranking result.
Generate fields from the correct source
Generating the title, description and URL from the same content record reduces the risk of inconsistency. Do not put someone who is not actually responsible for the content in the author field. Use actual publication and modification dates if known. Do not present the preparation date of an unpublished draft as an actual publication date; do not invent unverified fields.
Example: an editor-reviewed guide
The hypothetical agency article visibly identifies the publishing unit responsible. Its JSON-LD contains the same title, address and cover image used on the page. If the article has not yet been scheduled for publication, date fields are not filled artificially. When the content goes live, actual publication information is added to the content record and all outputs are updated together.
Action card: Turn the plan into a concrete deliverable
The table below is a working example prepared for this guide. Fill the rows using your own resources and workflow; do not mark unverified information as completed deliverables.
| Decision / task | Requirements to be considered ready |
|---|---|
| Identity | Actual author or person responsible for publication |
| Content | Matching title, description and image |
| Date | Actual publication and meaningful update |
| Validation | JSON syntax and page consistency |
Testing and maintenance
Checking JSON syntax and eligibility for rich results are not the same test. First check that the data is valid JSON, then examine whether its fields match the content. Complete technical validation with suitable official testing tools. Adding schema does not solve a page being noindex or inaccessible. During design changes, check that visible author and date information has not disappeared.
AI support
The tool can draft field mappings, but must not add fictional expert titles, awards, ratings or dates. Do not place hidden marketing claims in schema. What the code describes and what users see must be the same. Final approval should pass through both the content editor and technical review.
Pre-publication checklist
- Match visible information.
- Do not invent authors or dates.
- Test JSON separately.
- Do not guarantee rich results.
Frequently asked questions
Will adding BlogPosting code make my article stand out?
There is no automatic result guarantee. Markup may help the page be understood; it does not remove the need for technical access and useful content.
Should we enter today's date if the publication date is unknown?
Do not use an inaccurate date. Distinguish preparation, upload and publication dates; update the content record appropriately when verified publication information becomes available.
Sources and further reading
The official documentation supports the explanations about the relevant platforms. The example tables and working methods are editorial suggestions prepared for this guide.
Google Search Central: Article and BlogPosting ↗This guide was prepared with AI assistance. Fictional examples are not customer results. No reach, sales, or search ranking is promised. The person responsible for the business should conduct a final review of accuracy and scope before publication.
Let's adapt this approach to your brand.
Let's define the scope of your needs together.
Explore the relevant service