How to Add Schema Markup Using JSON-LD: Complete SEO Guide

Search engines often struggle to understand the specific context of your website content. By implementing schema markup using JSON-LD, you provide clear signals that help crawlers identify your entities, purpose, and unique value. This technical foundation is essential for modern search optimization.

Adding structured data to your pages allows you to communicate directly with search algorithms. While this practice can lead to eye-catching rich results, remember that Google does not guarantee enhanced appearances for every implementation. Success depends on accuracy and relevance.

In this guide, we will walk through the entire process. You will learn how to select the right types, write valid code, deploy it effectively, and monitor your performance over time.

Key Takeaways

• Structured data helps search engines better interpret your website content.
• JSON-LD is the preferred format for adding these technical signals.
• Proper implementation can lead to enhanced search visibility and clicks.
• Google does not guarantee rich results even with perfect code.
• Testing your implementation is a critical step before going live.

Schema Markup using JSON-LD: What It Is and Why It Matters for SEO

Structured data acts as a bridge between your website content and the complex algorithms used by search engines. By using schema markup using JSON-LD, you provide clear, machine-readable signals that help crawlers understand the context of your pages. This process happens behind the scenes, meaning your site’s visual design remains exactly as you intended.

How structured data helps search engines interpret page content

Search engines are incredibly smart, but they still rely on hints to categorize information accurately. When you implement structured data, you are essentially labeling your content so that machines can easily identify entities like products, authors, or event dates. This clarity allows search engines to display your information more effectively in the results pages.

Why JSON-LD is the preferred schema implementation method

The JSON-LD schema format is the gold standard recommended by Google Search Central. Unlike older methods that required embedding code directly into HTML tags, JSON-LD uses a clean script block. This approach keeps your source code organized and prevents common errors that occur when mixing data with display elements.

Feature	JSON-LD	Microdata
Implementation	Script block	Inline HTML
Maintenance	Easy to update	Difficult to manage
Code Impact	Minimal	High

What rich results can and cannot do for organic visibility

Many site owners hope that adding code will automatically boost their rankings. However, it is important to understand that rich results are not a direct ranking factor. Instead, they are visual enhancements that make your listing more attractive to users, which can lead to higher click-through rates.

Schema eligibility versus guaranteed search enhancements

Implementing the correct code makes your page eligible for features like star ratings, recipe cards, or product prices. It does not guarantee that these features will appear. Google decides when to show these enhancements based on quality, relevance, and user intent.

Why accurate, visible page content is essential

Your JSON-LD schema must always reflect the information that a human visitor can see on the page. If you hide information or provide misleading data, you risk violating search guidelines. Always ensure that your structured data is a transparent representation of your actual content to maintain long-term trust with search engines.

Choose the Right Schema Type for Your Page

Choosing the right Schema.org vocabulary ensures that search engines understand your page’s true purpose. When you align your data with the correct schema types, you provide clear signals that help search engines categorize your content effectively.

Match schema types to search intent and page purpose

Every page on your site serves a specific goal, whether it is to inform, sell, or provide contact details. You must select a type that mirrors the actual content visible to the user. Misalignment can lead to poor performance or even manual actions from search engines.

Common schema types for United States websites

In the United States, specific formats dominate the search landscape. Using these standard definitions helps your site compete for rich results.

Article and BlogPosting for editorial content

If you publish news or opinion pieces, Article schema is essential. It helps search engines identify the headline, author, and publication date, which are critical for news carousels.

Product and Offer for ecommerce pages

For online stores, Product schema is the gold standard. It allows you to display price, availability, and review ratings directly in the search results, which often increases click-through rates.

LocalBusiness for businesses with physical locations

If you operate a brick-and-mortar store, LocalBusiness schema is vital. It communicates your address, phone number, and operating hours to local searchers.

Organization and WebSite for brand-level information

Every site should use Organization schema to define the entity behind the content. Additionally, WebSite schema helps search engines understand your site’s search box and sitelinks.

When to use multiple schema types on one URL

It is perfectly acceptable to nest or combine different types on a single page. For example, a product page might include both Product and Organization data to provide a complete picture. Consistency is key when linking these entities together to avoid confusion.

Schema types that require special eligibility or content standards

Keep in mind that simply adding code does not guarantee a rich result. Some features, like star ratings or event tickets, require specific content standards and strict eligibility rules. Always verify your implementation against the latest documentation to ensure your site meets these high-quality requirements.

Plan the Information Your JSON-LD Markup Needs

Successful implementation of JSON-LD schema begins with careful preparation and inventory of your page content. Before you write any code, you must identify the core subject of your page and the specific details that define it. This planning phase ensures your markup is accurate, relevant, and helpful to search engines.

Identify the page entity and its primary properties

Every page on your website usually centers around a specific entity, such as a product, an article, or a local business. You should list the primary attributes that describe this entity, such as its name, unique identifier, and description. Clarity at this stage prevents errors later in the development process.

Separate required, recommended, and optional properties

Not all data points carry the same weight when it comes to search visibility. You must categorize your information to ensure you meet the baseline standards for your chosen schema type.

Use official Schema.org property definitions

The Schema.org vocabulary provides the standard definitions for all possible properties you might include. Reviewing these definitions helps you understand which fields are available to describe your content accurately. Using the correct vocabulary ensures that your structured data remains machine-readable and standardized.

Confirm Google Search Central requirements for rich results

While Schema.org defines the language, Google Search Central determines which properties are necessary to trigger specific rich results. You should verify the following requirements before finalizing your markup:

• Required properties: These are mandatory for the feature to appear.
• Recommended properties: These provide extra context and improve your chances of winning a rich result.
• Optional properties: These add depth but are not strictly necessary for basic eligibility.

Collect reliable business, product, author, and publisher details

Gathering accurate information is vital for building trust with search engines. Ensure you have verified details ready, such as:

• Official business addresses and contact information.
• Current product pricing and availability status.
• Author names and biographical links.
• Publisher branding and logo URLs.

Keep structured data consistent with visible page information

Your JSON-LD schema must always reflect the content that a human user sees on the page. If your markup claims a product costs $50, but the page displays $75, you risk violating quality guidelines. Consistency is the foundation of high-quality structured data that search engines can trust.

Build a Valid JSON-LD Schema Object

If you want to take full control over how your site appears in search, learning to build a custom JSON-LD schema object is essential. This process allows you to communicate directly with search engines, ensuring they understand the specific context of your content. By following a structured approach, you can create clean, error-free code that enhances your structured data strategy.

Step 1: Add the JSON-LD script container

Use the application/ld+json script type

Every implementation begins by defining the correct script tag within your HTML. You must specify the type as application/ld+json to ensure search engines recognize the block as valid JSON-LD script content. This tells the browser and crawlers to treat the enclosed text as machine-readable data rather than standard HTML.

Place valid JSON inside the script element

Once the container is ready, you will insert your data using standard JSON syntax. It is vital to remember that JSON is strict; every key and string value must be enclosed in double quotes. Missing a single comma or bracket will invalidate the entire object, rendering your efforts useless.

Step 2: Define the @context and @type properties

The foundation of any schema object relies on two specific properties: @context and @type. The context usually points to “https://schema.org,” which defines the vocabulary used for your markup. The type property then identifies the specific entity you are describing, such as a “Product,” “Article,” or “LocalBusiness.”

Step 3: Add core properties and accurate values

Format dates, URLs, images, ratings, and prices correctly

Accuracy is the most important factor when populating your properties. Search engines expect specific formats for different data types to process them correctly. For instance, images must be provided as absolute URLs, and ratings should be represented as numerical values within the defined scale.

Use ISO 8601 date formats and valid currency codes

When dealing with time-sensitive information, always use the ISO 8601 standard, such as YYYY-MM-DDThh:mm:ss. Similarly, ensure that all monetary values are paired with the correct three-letter currency code, like “USD.” Following these standards prevents parsing errors and ensures your structured data remains eligible for rich results.

“Good data is the bridge between your content and the user’s intent. When you provide clear, machine-readable information, you help search engines deliver the best possible experience.”

Step 4: Use @id to identify connected entities

To create a robust knowledge graph, you should use the @id property to provide a unique, stable identifier for your entities. This allows you to link different parts of your markup together, such as connecting an author to their specific article. By using a consistent @id, you help search engines understand that multiple pieces of information refer to the same real-world entity.

Step 5: Add nested objects and arrays without breaking JSON syntax

Complex pages often require nested information, such as a list of reviews or multiple authors. You can include these by nesting objects within your main JSON-LD schema or using arrays to group similar items. Always verify your syntax after adding these structures, as nested elements are common points for accidental punctuation errors.

• Validate your code using the official Schema Markup Validator.
• Check for missing required fields before deployment.
• Test your final JSON-LD script in the Rich Results Test tool.

Write Practical JSON-LD Examples for Common Pages

Every page on your website serves a unique purpose, and your schema types should reflect that specific intent. By choosing the correct format, you help search engines categorize your content more effectively. This process ensures that your site appears correctly in search results, providing users with the most relevant information at a glance.

Article schema for a news or blog article

When you publish editorial content, using the Article schema is essential for establishing authority. This markup tells search engines that your page is a piece of journalism or a blog post rather than a generic web page.

Include headline, image, author, publisher, and date properties

To maximize the impact of your Article schema, you must include specific metadata. Always define the headline, the main image, and the author’s name. Additionally, providing the publisher details and the publication date helps search engines verify the freshness and credibility of your content.

Product schema for an ecommerce product page

If you run an online store, the Product schema is your most valuable tool for driving clicks. It allows you to display pricing, availability, and star ratings directly in the search results.

Connect Product, Offer, AggregateRating, and Review data accurately

You should only include Product schema data that is visible to the user on the page. Connect the product name with the current offer, including price and currency. If you have genuine customer feedback, use the AggregateRating and Review properties to showcase your reputation.

LocalBusiness schema for a location-based business

For brick-and-mortar stores, the LocalBusiness schema is vital for appearing in map packs and local search queries. This markup bridges the gap between your physical presence and your digital footprint.

Include name, address, telephone number, hours, and location details

Ensure your LocalBusiness schema contains your official business name, full street address, and a working telephone number. You should also include your operating hours to help potential customers know exactly when they can visit your store.

Organization and WebSite schema for brand identity

Finally, you should implement Organization schema and WebSite schema to define your brand’s identity. These types help search engines understand your site’s structure and your company’s official presence on the web. This is particularly useful for site-wide search boxes and brand knowledge panels.

Schema Type	Primary Purpose	Key Data Points
Article	Editorial Content	Headline, Author, Date
Product	Ecommerce Sales	Price, Rating, Availability
LocalBusiness	Physical Locations	Address, Phone, Hours
Organization	Brand Identity	Logo, Social Profiles, Name

Add JSON-LD to Your Website Without Affecting Page Design

You can easily integrate schema markup using JSON-LD without changing a single pixel of your website’s design. Because this data is contained within a script element, it remains invisible to your visitors while providing search engines with a clear map of your content.

Step 1: Add JSON-LD directly to the page HTML

Hard-coding your data provides the most control over your implementation. This method ensures that your JSON-LD script is always present, regardless of plugin updates or theme changes.

Place the script in the head or body section

You should place your code within the <head> or <body> tags of your HTML document. While both locations are technically acceptable, placing it in the <head> is often preferred for cleaner organization and faster parsing by search engine crawlers.

Step 2: Add schema through a content management system

If you prefer not to touch the raw code, many platforms offer automated ways to manage your structured data. These tools can save time, but they require careful configuration to ensure the output remains accurate.

Implement structured data in WordPress with a trusted SEO plugin

WordPress users often rely on reputable SEO plugins to handle technical tasks. These plugins can automatically generate the necessary JSON-LD script based on your post or page content, significantly reducing the risk of manual syntax errors.

Use Shopify settings, themes, or structured data apps carefully

Shopify store owners should be cautious when using third-party apps for schema. Always verify that the app does not inject conflicting code that might confuse search engines or slow down your page load times.

Step 3: Deploy schema through Google Tag Manager when appropriate

Google Tag Manager (GTM) is a powerful tool for deploying code without direct access to the site’s backend. It is particularly useful for large-scale sites where managing individual page files is impractical. However, ensure your GTM container is configured to fire the tags correctly on every relevant page load.

Step 4: Coordinate developer, SEO, and content changes

Successful implementation requires clear communication between your technical and content teams. Everyone must understand how the structured data is being applied to avoid accidental overwrites or deletions.

Prevent duplicate markup from themes, plugins, and custom code

One of the most common issues is having multiple sources of schema on a single page. You must audit your site to ensure that your theme, your SEO plugin, and your custom scripts are not all trying to define the same entity simultaneously.

“Clean, well-structured data is the foundation of modern search visibility. When you avoid redundancy, you allow search engines to process your information with maximum efficiency.”

Method	Ease of Use	Control Level	Best For
Direct HTML	Low	High	Custom Websites
SEO Plugins	High	Medium	WordPress Sites
Tag Manager	Medium	Medium	Large Enterprises

Validate JSON-LD Before and After Publishing

Validation acts as a safety net for your SEO efforts, catching mistakes before they impact your rankings. Even a small typo can prevent search engines from reading your structured data correctly. By following a rigorous testing process, you ensure that your hard work translates into tangible search benefits.

Step 1: Check syntax with the Schema Markup Validator

The Schema Markup Validator is your primary tool for checking the structural integrity of your code. It focuses on whether your JSON-LD follows the correct vocabulary and syntax rules required by the schema.org standards.

Find missing commas, quotation marks, braces, and brackets

JSON-LD is highly sensitive to formatting errors. A single missing comma or an unclosed brace will cause the entire script to fail. Use the validator to scan for these syntax-level issues before you deploy your code to the live environment.

Step 2: Test eligible features with Google’s Rich Results Test

While the validator checks for general syntax, the Rich Results Test is specifically designed to see if your content qualifies for special search features. This tool simulates how Google interprets your markup for specific search experiences.

Review detected items, errors, warnings, and preview eligibility

The tool will highlight any missing required properties that prevent your page from appearing as a rich result. Pay close attention to warnings, as these often suggest optional fields that could further enhance your visibility in the search engine results pages.

“Testing is not just a final step; it is a continuous process of ensuring that your data remains accurate and useful for both users and search engines.”

— SEO Best Practices Guide

Step 3: Inspect the live URL after deployment

Once your code is live, you must verify that the search engine can actually see it. Sometimes, server-side caching or security plugins can block crawlers from accessing your structured data.

Confirm that search engines can crawl the page and rendered markup

Use the URL Inspection tool in Google Search Console to confirm that the page is indexed correctly. This ensures that the rendered HTML contains the JSON-LD script exactly as you intended.

Step 4: Resolve errors based on impact and feature requirements

Not all errors carry the same weight. Prioritize fixing errors that prevent rich results from appearing, such as missing price or availability fields on product pages. Once these are resolved, you can address minor warnings to optimize your implementation further.

Tool Name	Primary Focus	Best Used For
Schema Markup Validator	Syntax & Vocabulary	Initial code development
Rich Results Test	Google Eligibility	Feature-specific testing
Search Console	Live Performance	Post-deployment monitoring

Connect Related Entities with @id and Schema Graphs

Building a cohesive web of information helps search engines understand the relationships between your content pieces. By using unique identifiers, you create a robust and interconnected knowledge graph for your website. This approach ensures that your structured data is not just a collection of isolated facts, but a meaningful map of your brand’s digital presence.

Use @id to connect the webpage, organization, author, and main entity

The @id property acts as a unique fingerprint for every entity on your page. By assigning a consistent URI to your Organization schema, author profiles, and the webpage itself, you allow search engines to link these items together accurately. This prevents ambiguity and helps crawlers recognize that the “Author” mentioned in your article is the same person linked to your WebSite schema.

Build an @graph for pages with multiple related entities

When a single page contains several distinct items, a schema graph is the most effective way to organize them. Instead of scattering your code, you can group all related entities within one JSON-LD block. This structure clarifies how different parts of your content interact, making it easier for search engines to parse complex relationships.

Connect WebPage and Article entities on editorial URLs

For blog posts or news articles, you should link the WebPage entity to the Article entity using the same @id. This connection tells Google that the specific page is the container for the editorial content. It reinforces the authority of the author and the publisher by tying them directly to the content they produced.

Connect Product, Offer, Brand, and Review entities on product URLs

Ecommerce pages benefit greatly from linking multiple entities like Product, Offer, and Brand. By using the @id property to reference the specific product, you can attach reviews and pricing offers to that item without confusion. This creates a clear hierarchy that helps search engines display rich results with confidence.

Prevent conflicting names, URLs, authors, and publisher information

Consistency is the foundation of effective structured data. If your organization name or author profile URL changes across different pages, search engines may struggle to group your content correctly. Always ensure that the information in your code matches the visible text on your page to avoid triggering quality flags.

Use canonical URLs and stable identifiers across the website

Your @id values should always point to the canonical URL of the page or entity. Using stable, permanent identifiers prevents broken links in your knowledge graph when you update your site structure. By maintaining this consistency, you ensure that your site remains a reliable source of information for both users and search engines.

Follow Google Guidelines and Avoid Structured Data Spam

Navigating the world of structured data requires a firm grasp of Google’s core expectations. When you implement code to enhance your search presence, you must align your technical efforts with the official structured data guidelines provided by Google Search Central. Following these rules ensures that your site remains a trusted source for both users and search engines.

Represent only content that appears on the page

The most fundamental rule is that your markup must reflect the actual content visible to a user on the page. If a user visits your URL, they should see the same information that you have defined in your JSON-LD script. Transparency is key to maintaining a healthy relationship with search algorithms.

Use accurate ratings, reviews, prices, availability, and business details

Accuracy is non-negotiable when it comes to e-commerce and local business information. If your product is out of stock, your schema must reflect that status immediately. Providing outdated prices or incorrect business hours can lead to a poor user experience and potential penalties.

“The goal of structured data is to help search engines understand the content of your page, not to manipulate how that content is presented in search results.”

Google Search Central

Avoid marking up hidden, misleading, outdated, or irrelevant content

You should never attempt to hide information from users while showing it to search engines. This practice is considered spammy and can severely damage your site’s reputation. Always ensure that your markup is relevant to the specific page being indexed.

Do not create fake reviews or self-serving rating data

Authenticity is vital for building trust. Never generate fake reviews or use self-serving ratings to artificially boost your visibility. Search engines are increasingly sophisticated at detecting patterns that indicate manipulated feedback.

Do not use schema solely to target unrelated rich results

Some site owners try to force specific rich results by adding schema that does not match the page’s intent. This strategy is counterproductive and often leads to the removal of your eligibility for those features. Focus on providing value rather than chasing visual enhancements.

Understand manual actions, rich result removals, and algorithmic changes

Violating these policies can result in a manual action against your site. This might mean your pages lose their rich results entirely, which often leads to a drop in organic traffic. Staying updated with the latest documentation from Google Search Central is the best way to protect your long-term search performance.

Practice Type	Compliant Action	Non-Compliant Action
Product Pricing	Reflects current live price	Shows outdated or fake price
User Reviews	Displays genuine customer feedback	Uses fabricated or self-serving data
Content Visibility	Markup matches visible text	Markup hides text from users
Schema Intent	Matches page purpose	Targets unrelated rich results

Monitor, Maintain, and Troubleshoot Your Schema Markup

Once you have implemented your JSON-LD schema, the real work of monitoring and optimization begins. Maintaining a healthy search presence requires a proactive approach to ensure your data remains accurate and effective over time.

Track enhancements and errors in Google Search Console

Google Search Console serves as your primary dashboard for monitoring the health of your site. By navigating to the “Enhancements” section, you can quickly identify any warnings or errors that might prevent your pages from appearing as rich results.

Regularly reviewing these reports helps you stay aligned with structured data guidelines. If Google detects an issue, it will often provide specific details on which properties are missing or invalid, allowing you to fix them before they impact your visibility.

Use URL Inspection to verify indexing and detected structured data

When you make changes to your code, use the URL Inspection tool to see how Google currently views your page. This tool allows you to test the live version of your site to confirm that your JSON-LD schema is being correctly parsed.

It is a great way to verify that your markup is indexed and associated with the correct page content. If you do not see your data appearing here, it is a clear sign that your implementation needs further review.

Diagnose common JSON-LD implementation problems

Even experienced developers encounter issues when managing complex data structures. Use the following table to identify and resolve the most frequent technical hurdles you might face.

Issue Type	Common Cause	Recommended Fix
Missing Markup	Script not in HTML	Check source code for script tags
Property Errors	Incorrect formatting	Validate against schema.org types
Plugin Conflicts	Multiple active tools	Disable redundant SEO plugins
Canonical Mismatch	Wrong URL referenced	Update @id to match canonical URL

Markup does not appear in the HTML source or rendered DOM

If your code is missing, ensure your CMS or tag manager is firing correctly. Sometimes, dynamic content loading can hide your structured data from crawlers.

Required properties are missing or incorrectly formatted

Every schema type has specific requirements. Double-check that you have included all mandatory fields, such as prices for products or author names for articles.

Multiple plugins generate conflicting schema entities

Using too many SEO plugins often leads to duplicate or contradictory data. Stick to one reliable method for generating your markup to avoid confusing search engines.

Markup describes a different page than the canonical URL

Always ensure your @id identifier matches the canonical URL of the page. This prevents search engines from associating your data with the wrong content.

Update schema when content, products, authors, or business details change

Your website is a living entity, and your data should reflect that. Whenever you update product prices, change business hours, or publish new author bios, remember to refresh your JSON-LD schema accordingly.

Stale information can lead to a poor user experience and may cause Google to stop displaying your rich results. Keeping your data current is essential for maintaining trust with both users and search engines.

Measure clicks and impressions without assuming schema alone caused growth

Finally, analyze your performance data to see how rich results influence your traffic. While schema can improve your click-through rate, remember that it is only one part of your overall SEO strategy.

Look for trends in Google Search Console to see if specific rich results correlate with higher engagement. Avoid assuming that schema alone caused growth, as content quality and site speed remain critical factors for success.

Conclusion

Implementing schema markup using JSON-LD transforms how search engines perceive your website. You now possess the tools to plan, build, and maintain a robust data strategy that highlights your unique content.

Effective structured data provides clear signals to Google about your page entities. This clarity helps search engines categorize your information accurately. While these efforts support your eligibility for rich results, remember that search rankings depend on many factors beyond code alone.

Consistency remains vital for long-term success. Keep your markup aligned with the visible text on your pages to maintain trust with users and search platforms. Regularly audit your implementation to ensure your data reflects current business details, product availability, and author information.

Start small by applying these practices to your most important pages. Monitor your performance in Google Search Console to see how your site appears in search results. Share your experiences or ask questions about specific schema types to keep the conversation going with your peers in the SEO community.

FAQ

What exactly is JSON-LD and how does it help my SEO?

JSON-LD is a machine-readable format that describes the entities and purpose of your webpage without changing its visible layout. By using this format, you provide Google and other search engines with clear, structured information, making your site eligible for rich results that can improve your organic visibility.

Does implementing schema markup guarantee that I will get rich results in Google Search?

No, Google Search Central explicitly states that correctly implemented structured data makes a page eligible for enhanced displays, but it is not a guarantee. Google determines search appearances based on many factors, including the relevance and quality of the visible page content.

Which schema types are best for my United States-based business?

It depends on your content! Most sites use Organization or WebSite for brand identity. Editorial sites should use Article or BlogPosting, while ecommerce stores rely on Product, Offer, and AggregateRating. If you have a physical storefront, LocalBusiness is essential for providing your address and phone number to search engines.

How do I ensure my JSON-LD code is formatted correctly?

You must follow specific syntax rules, such as using ISO 8601 date formats and valid currency codes. It is also important to use @context to identify the vocabulary and @type to define the entity. To keep your code clean, use the application/ld+json script type and ensure all braces and brackets are balanced.

Can I use a plugin like Yoast SEO or Rank Math to add schema?

Absolutely! For WordPress users, a trusted SEO plugin like Yoast SEO or Rank Math is a great way to deploy schema without writing code. Shopify users can also find dedicated apps or theme settings to manage their structured data. Just be careful to avoid duplicate markup if you are using multiple tools at once.

What tools should I use to validate my structured data?

Start with the Schema Markup Validator to check for general syntax errors like missing commas. Once your code is clean, use Google’s Rich Results Test to see if your page is eligible for specific search enhancements. Finally, use the URL Inspection tool in Google Search Console to verify that the live version of your page is being rendered correctly.

Is it okay to mark up information that isn’t visible on the page?

No, that is considered structured data spam. Google guidelines require that your markup accurately represents the content users can actually see. Marking up hidden or misleading information can lead to a manual action or the loss of your rich result eligibility.

What is an @graph and when should I use it?

An @graph allows you to connect multiple related entities within a single JSON-LD block. For example, you can use it to show the relationship between a WebPage, its Article content, the author, and the publisher. This helps search engines understand the full context of your page more efficiently.

How do I monitor my schema performance over time?

You can track your “Enhancements” and any detected errors directly in Google Search Console. This tool will show you which pages are generating rich result impressions and clicks, and will alert you if any required properties become missing or outdated as you update your site.