What is Structured Data and Why It Matters

Structured data is a standardized format for organizing and presenting information on web pages in a way that search engines and other applications can easily understand and process ²⁴. Rather than relying solely on human-readable text, structured data uses coded markup to explicitly label and categorize content elements, enabling machines to comprehend not just what information exists, but what that information means ⁶⁸. The primary purpose of structured data is to enhance how search engines index, interpret, and display web content, resulting in richer search results and improved visibility ³. In the context of modern digital marketing and search engine optimization, structured data has become essential for businesses seeking to improve their online presence, increase click-through rates, and provide users with more relevant and visually engaging search results.

Overview

The emergence of structured data addresses a fundamental challenge in web communication: the gap between human-readable content and machine interpretation. While humans can easily understand context, relationships, and meaning within text, search engines historically struggled to extract semantic meaning from unstructured content ⁶. This limitation meant that search engines could match keywords but often failed to understand the true nature and context of information on web pages.

In 2011, major search engines including Google, Bing, and Yahoo collaborated to create Schema.org, establishing a standardized vocabulary for structured data implementation ². This collaborative project represented a pivotal moment in web development, providing a universal format that any website owner could adopt to create consistency across the web. The initiative transformed how websites communicate with search engines, moving from implicit pattern recognition to explicit, machine-readable declarations of content meaning.

Since its inception, structured data adoption has grown exponentially. As of 2024, over 45 million web domains utilize Schema.org markup, implementing more than 450 billion Schema.org objects ⁵. The practice has evolved from a technical novelty to a mainstream SEO necessity, with search engines increasingly relying on structured data to power rich results, knowledge panels, and enhanced search features. As artificial intelligence and voice search technologies advance, structured data has become even more critical, serving as a foundation for integration with emerging technologies that depend on machine-readable content ⁹.

Key Concepts

Schema.org Vocabulary

Schema.org provides the standardized vocabulary for structured data implementation, defining hundreds of entity types that can be marked up, including creative works, events, organizations, persons, places, and products ³. This vocabulary serves as a common language between websites and search engines, ensuring consistent interpretation of content across different platforms.

Example: A local bakery implementing structured data for their business would use the LocalBusiness schema type from Schema.org. Within this schema, they would specify properties such as name ("Sweet Treats Bakery"), address (123 Main Street, Springfield), telephone (555-0123), openingHours (Mo-Fr 07:00-19:00), and priceRange ($$). This structured approach allows search engines to display this information directly in search results and populate knowledge panels, making it easier for potential customers to find essential business details without clicking through to the website.

Types and Properties Hierarchy

Structured data operates on a hierarchical system where Types represent main objects or entities (such as Company, Product, or Event), while Properties describe attributes of those entities (such as name, homepage, or logo) ². This hierarchical approach enables precise, granular description of content that search engines can reliably interpret and utilize.

Example: An online bookstore marking up a specific book would use the Book type (a subtype of CreativeWork). The properties would include name ("The Great Gatsby"), author (F. Scott Fitzgerald), isbn (978-0-7432-7356-5), publisher (Scribner), datePublished (1925), numberOfPages (180), and bookFormat (Hardcover). If the bookstore also sells this book, they would nest a Product type within the Book markup, adding properties like price ($24.99), availability (InStock), and condition (New). This nested hierarchy allows search engines to understand both the creative work itself and its commercial availability.

JSON-LD Format

JSON-LD (JavaScript Object Notation for Linked Data) is the recommended encoding method for structured data because it is less prone to user errors, unaffected by layout changes, and easier to edit and maintain ¹⁷. Unlike Microdata and RDFa, which interweave markup with HTML elements, JSON-LD exists as a separate script block, making it simpler to implement and update.

Example: A restaurant implementing JSON-LD structured data would add a <script> tag in their page's <head> section containing code like this:

{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "The Garden Bistro",
  "servesCuisine": "Mediterranean",
  "priceRange": "$$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "456 Oak Avenue",
    "addressLocality": "Portland",
    "addressRegion": "OR",
    "postalCode": "97201"
  },
  "telephone": "+1-503-555-0199",
  "openingHoursSpecification": {
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"],
    "opens": "17:00",
    "closes": "22:00"
  }
}

This self-contained block can be added, edited, or removed without affecting the visible page layout or HTML structure.

Rich Results

Rich results are enhanced search result displays that include additional information like ratings, prices, availability, cooking times, and ingredient lists ⁴. These elements make search results more visually appealing and informative to users, significantly improving click-through rates and user engagement.

Example: A food blogger publishing a recipe for chocolate chip cookies implements Recipe schema markup. When users search for "best chocolate chip cookies," the search results display not just the page title and description, but also a rich result showing a photo of the cookies, a 4.8-star rating based on 127 reviews, total time (45 minutes), calorie count (210 per serving), and a brief ingredient list. This rich result stands out visually from standard text listings, attracting more clicks and providing users with immediate value before they even visit the website.

Knowledge Panels

Knowledge panels are information boxes displayed alongside search results that consolidate essential business or entity information, improving brand identity and awareness ³. These panels are populated using structured data from the website and other authoritative sources, creating a comprehensive snapshot of an organization or entity.

Example: A technology startup implements Organization schema markup on their website, specifying properties including name, logo, url, sameAs (links to their LinkedIn, Twitter, and Facebook profiles), foundingDate, founders, and description. When users search for the company name, Google displays a knowledge panel on the right side of search results featuring the company logo, a brief description, founding information, social media links, and related searches. This consolidated presentation enhances brand visibility and provides users with authoritative information at a glance.

Semantic Meaning

Semantic meaning refers to the actual significance and context of information, rather than just the literal text ⁶. Structured data enables machines to understand semantic meaning by explicitly labeling the role and relationship of each content element.

Example: Consider the sentence "Marieke is the author of this post and she works at Yoast." To a human, the relationships are clear, but to a machine, this is simply a string of words. When converted to structured data using Article and Person schemas, the markup explicitly identifies "Marieke" as a Person entity with the role of author, establishes the relationship between this person and the article, and connects this person to the Organization entity "Yoast" through an employment relationship. This semantic clarity allows search engines to understand that Marieke is not just a word in the text, but a specific person with defined relationships to other entities ⁶.

Name-Value Pairing

Structured data operates on a name-value pairing system where each data element receives an explicit label (name) paired with its corresponding value ³. This pairing enables search engines to understand relationships between different data components and their relevance to search queries.

Example: An e-commerce site selling a laptop uses Product schema with name-value pairs such as "name": "Dell XPS 15 Laptop", "brand": "Dell", "price": "1299.99", "priceCurrency": "USD", "availability": "https://schema.org/InStock", and "aggregateRating": {"ratingValue": "4.6", "reviewCount": "89"}. Each property name (like "price" or "brand") is explicitly paired with its specific value, eliminating ambiguity. Search engines can then extract this information to display product details in rich results, compare prices across retailers, or filter search results by availability—all because the data is explicitly labeled rather than embedded in unstructured text.

Applications in Search Engine Optimization

E-commerce Product Visibility

Online retailers implement Product schema markup to display prices, availability, ratings, and reviews directly in search results, significantly improving conversion rates ⁶. This application is particularly valuable in competitive markets where visual differentiation in search results can determine which products receive clicks.

A sporting goods retailer selling running shoes implements comprehensive Product schema for each item in their catalog. For a specific Nike running shoe, they include properties for name, image, description, brand, sku, offers (containing price, currency, availability, and seller information), and aggregateRating (with rating value and review count). When potential customers search for "Nike running shoes size 10," the search results display rich snippets showing the shoe image, price ($129.99), availability (In Stock), and star rating (4.7 stars from 234 reviews). This detailed presentation allows shoppers to compare options directly in search results, and the retailer's products stand out visually from competitors who haven't implemented structured data.

Recipe and Food Content Discovery

Recipe websites implement Recipe schema to enable filtering by ingredients, cooking time, and calorie count, enhancing user search experience and making content more discoverable ⁴. This application addresses the specific needs of users searching for recipes with particular constraints or preferences.

A cooking blog specializing in quick weeknight dinners implements Recipe schema for all their content. For a "30-Minute Chicken Stir-Fry" recipe, they include properties such as name, image, author, datePublished, description, prepTime (PT10M), cookTime (PT20M), totalTime (PT30M), recipeYield (4 servings), recipeIngredient (listing all ingredients), recipeInstructions (step-by-step directions), nutrition (calories, protein, carbohydrates), and aggregateRating. When users search for "quick chicken dinner under 30 minutes," the recipe appears with a rich result showing the photo, total time, calorie count, and rating. Users can also filter recipe search results by cooking time or dietary restrictions, making the content more accessible to people with specific needs.

Local Business Information Management

Local businesses use Organization and LocalBusiness schema to consolidate contact information, hours, and location data into knowledge panels ³. This application is critical for businesses that depend on local customers finding accurate, up-to-date information about their services and availability.

A dental practice implements LocalBusiness schema (specifically, the Dentist subtype) on their website. The markup includes name ("Bright Smile Dental"), image (practice logo and office photos), address (complete postal address), telephone, email, url, priceRange, openingHoursSpecification (detailed hours for each day of the week), geo (latitude and longitude coordinates), paymentAccepted (insurance types and payment methods), and areaServed (neighborhoods and cities served). This comprehensive markup populates a knowledge panel in local search results, displays accurate hours in Google Maps, and ensures the practice appears in relevant local searches. When the practice updates their holiday hours, they modify the structured data, and the changes propagate across search platforms.

Event Promotion and Ticketing

Event organizers implement Event schema markup to enable rich result displays showing dates, locations, ticket availability, and performer information. This application helps events stand out in search results and provides potential attendees with essential information immediately.

A concert venue promoting an upcoming music festival implements Event schema for the event page. The markup includes name ("Summer Music Festival 2025"), startDate and endDate (with specific times), location (using Place schema with venue name and address), image (festival poster), description, performer (listing all bands and artists), offers (with ticket prices, availability, and purchase URL), and organizer (the promoting company). When music fans search for "concerts near me this summer," the festival appears with a rich result displaying the date, location, featured performers, ticket prices, and a direct link to purchase tickets. The structured data also enables the event to appear in specialized event search features and calendar integrations.

Best Practices

Prioritize JSON-LD Format

Use JSON-LD format for new structured data implementations due to its flexibility, ease of editing, and reduced error susceptibility ¹⁷. JSON-LD separates the structured data from the HTML markup, making it less likely that design changes will break the implementation and easier for non-technical team members to update.

Rationale: Unlike Microdata and RDFa, which require interweaving schema markup with HTML elements throughout the page, JSON-LD exists as a self-contained script block. This separation means that when a web designer restructures the page layout or a content manager updates the visible text, the structured data remains intact and functional. Additionally, JSON-LD is easier to validate, debug, and maintain because all the structured data exists in one location rather than scattered throughout the HTML.

Implementation Example: A news publisher implementing Article schema for their stories creates a standardized JSON-LD template that their content management system automatically populates with article metadata (headline, author, publication date, image, etc.). This template sits in the <head> section of every article page. When editors update article content or designers modify the page layout, the JSON-LD remains unchanged and continues to provide accurate structured data to search engines. The technical team can update the template once, and the changes apply across all articles, rather than requiring manual updates to individual HTML elements throughout thousands of pages.

Mark Only Visible Content

Never create structured data for information not visible to users, even if technically accurate ⁴. Structured data should describe content that actually appears on the page and is accessible to visitors, maintaining trust with search engines and avoiding penalties for deceptive practices.

Rationale: Search engines explicitly prohibit marking up content that users cannot see, as this practice can be used to manipulate search results. If structured data claims a page contains information that isn't actually visible to visitors, search engines may ignore the markup entirely or penalize the site. This principle ensures that structured data enhances the user experience rather than creating a disconnect between what search engines understand and what users actually find on the page.

Implementation Example: An online clothing retailer wants to implement Product schema for a dress. They include properties for name, price, color, size, and material—but only for information actually displayed on the product page. They do not add markup for sizes that are out of stock and not shown on the page, nor do they include detailed manufacturing information that exists in their internal database but isn't presented to customers. If they want to mark up additional product details, they first add that information to the visible page content, then create corresponding structured data. This approach ensures complete alignment between what users see and what search engines understand.

Implement Regular Validation and Monitoring

Use Google Search Console and other validation tools to verify correct implementation and monitor how search engines interpret structured data ⁴. Regular validation catches errors before they impact search visibility and ensures that markup remains accurate as content evolves.

Rationale: Structured data syntax is precise, and small errors can cause search engines to ignore the markup entirely. Properties must use exact names from the Schema.org vocabulary, values must follow specified formats (such as ISO 8601 for dates), and required properties must be present. Additionally, search engine requirements may change over time, and content updates may inadvertently break previously functional markup. Regular validation ensures ongoing compliance and effectiveness.

Implementation Example: A travel website with thousands of hotel listings implements a monthly validation routine. Their technical team uses Google's Rich Results Test to check a sample of pages across different hotel types and locations, verifying that the markup produces the expected rich results. They monitor Google Search Console's Enhancement reports to identify any structured data errors or warnings across the site. When they discover that 50 hotel pages show errors for missing priceRange properties, they update their template to include this information. They also set up automated alerts that notify the team when Search Console detects new structured data errors, allowing them to respond quickly to issues before they impact search visibility.

Start Simple and Expand Gradually

Begin with basic schema types and expand gradually as expertise develops ². This approach reduces the risk of errors, allows teams to learn from initial implementations, and ensures that foundational markup is solid before adding complexity.

Rationale: Structured data can become complex quickly, especially when nesting multiple schema types or implementing advanced properties. Starting with simple, high-impact implementations allows teams to gain confidence, understand validation processes, and see results before investing in more sophisticated markup. This incremental approach also makes it easier to identify and fix problems, as issues can be isolated to recent changes rather than buried in complex, comprehensive implementations.

Implementation Example: A professional services firm begins their structured data journey by implementing basic Organization schema on their homepage, including only essential properties: name, url, logo, telephone, and address. After validating this implementation and confirming it appears correctly in search results, they add sameAs properties linking to their social media profiles. Once comfortable with Organization schema, they expand to Person schema for their leadership team, then Article schema for their blog posts, and eventually Service schema for their offerings. Each expansion builds on previous knowledge, and the team develops internal documentation and processes based on lessons learned from earlier implementations.

Implementation Considerations

Tool and Format Selection

Organizations must choose between manual coding, automated tools, and content management system plugins based on their technical capabilities and specific needs ². Each approach offers different balances of flexibility, ease of use, and maintenance requirements.

For organizations with in-house development teams and unique content structures, manual coding provides maximum flexibility and control. A large media company with custom content types and complex relationships between articles, authors, and topics might manually code JSON-LD templates that precisely capture their content model. This approach requires significant technical expertise but allows for sophisticated implementations that automated tools cannot achieve.

Mid-sized businesses without dedicated development resources often benefit from online schema generators and tools that require no coding skills ². A boutique hotel could use a schema generator to create LocalBusiness and Hotel markup by filling out web forms with their business information, then copying the generated code into their website. This approach balances ease of use with reasonable customization, though it may not support highly specialized schema types or complex nested structures.

Organizations using popular content management systems like WordPress, Shopify, or WooCommerce can leverage plugins that automatically generate appropriate structured data ⁶. An e-commerce store running on WooCommerce might install a schema plugin that automatically creates Product markup for all items in their catalog, pulling information from existing product fields. This approach requires minimal technical knowledge and ensures consistency across large numbers of pages, though customization options may be limited to what the plugin supports.

Audience-Specific Customization

Structured data implementation should align with the specific needs and search behaviors of target audiences. Different industries and content types require different schema types and properties to maximize relevance and visibility.

A medical practice targeting local patients would prioritize LocalBusiness and MedicalBusiness schema types, emphasizing properties like address, telephone, openingHours, acceptedPaymentMethod, and medicalSpecialty. They might also implement FAQPage schema for common patient questions about insurance, procedures, and appointments. This focus addresses the specific information needs of people searching for local healthcare providers.

In contrast, a software-as-a-service company targeting business customers would prioritize Organization, Product, and SoftwareApplication schema types, emphasizing properties like applicationCategory, offers (with subscription pricing), aggregateRating, and featureList. They might implement HowTo schema for tutorial content and VideoObject schema for product demonstrations. This approach aligns with the research and evaluation behaviors of B2B buyers.

Organizational Maturity and Resource Allocation

The scope and sophistication of structured data implementation should match an organization's digital maturity, technical resources, and strategic priorities. Attempting overly ambitious implementations without adequate resources often leads to incomplete or error-prone markup that provides little value.

A startup with limited technical resources might begin with basic Organization schema on their homepage and Product schema for their core offerings, using automated tools or plugins to minimize maintenance burden. As the organization grows and develops more technical capability, they can expand to more sophisticated implementations.

An enterprise organization with dedicated SEO and development teams can pursue comprehensive structured data strategies across all content types, implementing custom solutions for complex content relationships and maintaining detailed markup across thousands of pages. They might develop automated testing and validation processes, create internal training programs, and assign specific team members to monitor and optimize structured data performance.

Integration with Broader SEO Strategy

Structured data should complement and enhance other SEO efforts rather than existing as an isolated tactic ³. The most effective implementations align structured data with content strategy, technical SEO, and user experience optimization.

A content publisher implementing Article schema ensures that the structured data reflects their editorial standards and content quality signals. They include author properties that link to detailed author profiles, datePublished and dateModified properties that demonstrate content freshness, and image properties that showcase high-quality visuals. This structured data reinforces their broader content strategy focused on expertise, authority, and trustworthiness. They coordinate structured data implementation with their technical SEO team to ensure proper canonicalization, mobile optimization, and page speed—all factors that influence how search engines utilize structured data.

Common Challenges and Solutions

Challenge: Complexity and Learning Curve

Understanding Schema.org vocabulary and selecting appropriate schema types requires significant investment in learning ². The Schema.org vocabulary includes hundreds of types and thousands of properties, making it difficult for newcomers to identify which schemas apply to their content and which properties are essential versus optional. This complexity can lead to analysis paralysis, where organizations delay implementation because they feel overwhelmed by options, or to poor implementations that use inappropriate schema types or miss critical properties.

Solution:

Begin with high-impact, straightforward schema types that directly address business priorities, using official documentation and examples as guides. Organizations should identify their three to five most important content types or business objectives, then research which schema types best support those priorities. Google Search Central documentation provides specific guidance on which schema types enable rich results and which properties are required, recommended, or optional for each type ⁴.

For example, a local restaurant should start with Restaurant schema (a subtype of LocalBusiness) rather than attempting to implement every possible schema type. They would consult Google's documentation to identify required properties (name, address), recommended properties (servesCuisine, priceRange, telephone), and optional properties that might provide additional value (menu, acceptsReservations). They would implement the required and recommended properties first, validate the implementation, and only add optional properties after confirming the basic markup works correctly. This focused approach builds competence and confidence before expanding to more complex implementations.

Challenge: Maintenance and Content Synchronization

Structured data must be kept synchronized with actual content; outdated markup can damage credibility with search engines and users ⁴. When visible page content changes but structured data remains static, the disconnect can cause search engines to display incorrect information in rich results, leading to poor user experiences and potential penalties. This challenge is particularly acute for organizations with large numbers of pages, frequently updated content, or multiple team members making changes.

Solution:

Implement automated structured data generation through content management systems or develop templated approaches that pull data from the same sources as visible content. Rather than manually coding structured data for each page, organizations should create systems where structured data automatically updates when content changes.

A news organization publishing dozens of articles daily would integrate structured data generation into their content management system workflow. When journalists create a new article and fill in fields for headline, author, publication date, and featured image, the CMS automatically generates corresponding JSON-LD markup using Article schema. When editors update the article or change the headline, the structured data updates automatically. This systematic approach eliminates the risk of content and markup falling out of sync and ensures consistency across thousands of articles without requiring manual intervention for each update.

For organizations without sophisticated CMS capabilities, creating standardized templates with clear documentation about which fields correspond to which schema properties can help maintain synchronization. A small business might create a simple checklist that reminds them to update both visible content and structured data whenever they change business hours, add new products, or modify pricing.

Challenge: Format Selection and Technical Implementation

Choosing between JSON-LD, Microdata, and RDFa can be confusing, and incorrect technical implementation can result in search engines ignoring the markup entirely ¹⁷. Each format has different syntax requirements and implementation methods, and mixing formats or using incorrect syntax creates validation errors that prevent structured data from functioning.

Solution:

Adopt JSON-LD as the standard format for all new implementations unless specific technical constraints require alternatives, and use validation tools throughout the development process ¹⁷. JSON-LD's separation from HTML markup makes it less error-prone and easier to maintain, and it is Google's recommended format.

A web development team creating structured data for a client would establish JSON-LD as their standard approach, developing reusable templates for common schema types. Before deploying any structured data to production, they would validate the markup using Google's Rich Results Test and Schema.org's validator, checking for syntax errors, missing required properties, and proper nesting of schema types. They would test the markup on staging environments first, verifying that it produces the expected rich results before implementing on live pages.

For organizations that have existing Microdata or RDFa implementations, a gradual migration to JSON-LD can reduce risk while improving maintainability. They might begin by implementing JSON-LD for new content types while leaving existing markup in place, then systematically converting older implementations during regular content updates or site redesigns.

Challenge: Validation Errors and Debugging

Even carefully implemented structured data can contain errors that prevent it from functioning correctly, and identifying the source of errors in complex markup can be time-consuming and frustrating ⁴. Common errors include misspelled property names, incorrect value formats, missing required properties, and improper nesting of schema types. These errors may not be immediately obvious, especially when markup appears to be correctly formatted but uses property names or values that don't match Schema.org specifications.

Solution:

Establish a systematic validation and testing process using multiple tools, and maintain detailed documentation of schema implementations to facilitate troubleshooting. Organizations should validate structured data at multiple stages: during development, before deployment, and regularly after implementation.

A development team would use Google's Rich Results Test during initial development to verify that markup produces the intended rich results. They would use Schema.org's validator to check for technical compliance with the vocabulary. They would review Google Search Console's Enhancement reports after deployment to identify any errors or warnings that appear when Google crawls the live pages. When errors occur, they would systematically check each property against official documentation, verify that values match required formats (such as using ISO 8601 format for dates), and confirm that all required properties are present.

Creating internal documentation that maps each schema implementation to specific business content helps teams quickly identify where errors originate. For example, documenting that Product schema for electronics includes specific properties for brand, model, sku, and gtin13 allows teams to quickly verify that all required product data is available and correctly formatted when validation errors occur.

Challenge: Measuring Impact and ROI

Determining the specific impact of structured data on search visibility, click-through rates, and business outcomes can be difficult because structured data works in conjunction with many other SEO and content factors ³. Organizations may implement structured data but struggle to isolate its effects from other optimization efforts, making it challenging to justify continued investment or prioritize structured data projects.

Solution:

Establish baseline metrics before implementation, monitor specific rich result performance through Google Search Console, and track changes in click-through rates for pages with structured data compared to similar pages without markup. While perfect attribution is impossible, organizations can gather meaningful evidence of structured data's impact through careful measurement.

An e-commerce company implementing Product schema would first document baseline metrics for product pages: average search impressions, click-through rates, and conversion rates. After implementing structured data, they would use Google Search Console's Performance report filtered by "Rich results" to track how often their products appear with enhanced displays. They would compare click-through rates for product pages with rich results to similar products without rich results, controlling for factors like price, brand, and category. They would also monitor whether products with structured data appear for more diverse search queries, indicating improved search engine understanding of product attributes.

For local businesses implementing LocalBusiness schema, tracking changes in knowledge panel impressions, map pack appearances, and "near me" search visibility provides evidence of structured data's impact. Comparing phone calls, direction requests, and website visits before and after implementation helps quantify business value, even if perfect attribution to structured data alone is not possible.

See Also

• Rich Results and Enhanced Search Features
• Google Search Console for Structured Data

References

1. Best Version Media. (2024). Schema Markup Explained: A Local SEO Strategy Every Business Needs. https://www.bestversionmedia.com/schema-markup-explained-a-local-seo-strategy-every-business-needs/
2. Mangools. (2024). Structured Data. https://mangools.com/blog/structured-data/
3. Moz. (2024). Schema Structured Data. https://moz.com/learn/seo/schema-structured-data
4. Google. (2025). Introduction to Structured Data. https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data
5. Schema.org. (2025). Schema.org. https://schema.org
6. Yoast. (2024). What is Structured Data? https://yoast.com/what-is-structured-data/
7. seoClarity. (2024). POV: Schema. https://www.seoclarity.net/blog/pov-schema-17554/
8. Neil Patel. (2024). Get Started Using Schema. https://neilpatel.com/blog/get-started-using-schema/
9. Digital Marketing Institute. (2024). What is Schema Markup. https://digitalmarketinginstitute.com/blog/what-is-schema-markup