Structured Data & Semantic Web on 247COMPASS

AggregateRating Schema

Thu, 01 Oct 2026 00:00:00 +0900

AggregateRating summarizes individual reviews with an average score and the total number of reviews or ratings. Eligible results can show this information visually as stars. Inflated review counts or fabricated scores can trigger structured-data enforcement and loss of rich-result eligibility. ratingValue must reflect the real system and remain within the declared bestRating, commonly 5. Populate the markup automatically from the review platform to reduce accidental discrepancies.

BreadcrumbList Schema

Thu, 01 Oct 2026 00:00:00 +0900

BreadcrumbList structures the same Home > Category > Current page path shown in the interface, helping search systems understand navigation and, where supported, present a readable path instead of a long URL. Assign position values in order. A mismatch between markup and the site’s real hierarchy creates confusing signals. Clear breadcrumbs are particularly useful on sites with several category levels, although their search display depends on the interface and search engine.

Course Schema

Thu, 01 Oct 2026 00:00:00 +0900

Course describes the educational offering, while hasCourseInstance can identify specific sessions, delivery modes and schedules. Use an array when several dates or levels, such as introductory and advanced cohorts, need separate representation. Genuine student ratings may add useful context where appropriate. Search support and rich-result requirements change over time, so neither CourseInstance nor ratings should be described as automatically securing a course card. Verify the current requirements of the intended discovery channel.

CreativeWork (isAccessibleForFree)

Thu, 01 Oct 2026 00:00:00 +0900

The isAccessibleForFree property declares that access to content requires payment. Identify the actual gated section with a cssSelector rather than describing an unrelated region. When crawlers can access full text but ordinary visitors see only a preview, correctly identifying the paywall helps explain that difference and avoid misleading signals. Publishers and research organizations can use this markup as part of a compliant approach to maintaining discovery while operating a subscription model.

Dataset Schema

Thu, 01 Oct 2026 00:00:00 +0900

Dataset can support discovery in Google’s Dataset Search and other systems that consume the vocabulary. Organizations publishing original research or statistics can use it to help researchers find, cite and reuse their work. temporalCoverage and spatialCoverage describe the time period and geographic area, improving the clarity of matching for specialized needs. Publishing trustworthy primary data can also be part of an AI-discovery strategy, but neither AI training use nor citations are guaranteed.

Event Schema

Thu, 01 Oct 2026 00:00:00 +0900

Event describes concerts, webinars or conferences for eligible event-search experiences. Keep eventAttendanceMode accurate for online, offline or mixed attendance and update eventStatus when an event is cancelled or postponed. When tickets sell out, reflect that in offers availability using the appropriate SoldOut value. An operational link between the ticketing system and markup helps avoid sending users outdated information.

FAQPage Schema

Thu, 01 Oct 2026 00:00:00 +0900

FAQPage markup must describe questions and answers actually visible in the page body. Adding hidden questions only to the schema violates structured-data policies and can lead to loss of rich-result eligibility. In 2023 Google restricted FAQ rich results largely to well-known, authoritative government and health websites. Other sites may still find the organization of clear question-and-answer content useful to readers and automated systems, but neither rich-result display nor AI citation is guaranteed. Avoid promotional copy or advertising links masquerading as answers.

Favicon

Thu, 01 Oct 2026 00:00:00 +0900

A favicon helps users distinguish a brand quickly among browser tabs and search results. The source recommends 48-pixel multiples, such as 48 by 48, 96 by 96 or 144 by 144; use an adequately sized square icon and check current search guidance rather than assuming those examples are universal requirements. Tiny or unclear artwork can look blurred. Site redesigns sometimes break favicon paths, so verify the deployed asset and eventual search appearance.

Featured Snippet

Thu, 01 Oct 2026 00:00:00 +0900

A featured snippet presents a concise answer in a prominent result box, historically above the first ordinary organic link. It can create exposure even without a click, although traffic outcomes vary. Practitioners often use concise paragraphs of around 40 to 50 words for definitions, numbered lists for processes and tables for comparisons. Place a clear answer directly below a relevant question heading. These formats improve extractability but cannot guarantee selection.

Google Discover

Thu, 01 Oct 2026 00:00:00 +0900

Google Discover surfaces content in a mobile feed without a user entering a query. Timely or visually appealing material can receive a large burst of visits compared with ordinary search. Large, high-quality images at least 1,200 pixels wide, compelling but accurate headlines and trustworthy content are important practices for Discover. They do not guarantee inclusion. Because traffic is highly volatile, treat it as supplementary acquisition rather than a dependable core KPI.

HowTo Schema

Thu, 01 Oct 2026 00:00:00 +0900

HowTo describes sequential guides such as assembly instructions, non-recipe DIY tasks and software installation. Each HowToStep can include text and supporting image or video information. This remains useful semantic markup for compatible systems. The source describes mobile Google HowTo results as still active after a desktop reduction in 2023; Google actually discontinued HowTo rich results in 2023, so this markup should not be presented as a current route to those cards.

ImageObject License Schema

Thu, 01 Oct 2026 00:00:00 +0900

The license property on ImageObject can link to usage terms, while acquireLicensePage points to a page where a license can be purchased or permission requested. This can support a licensable-image label in eligible Google Images results and clarify reuse conditions, although metadata alone does not prevent infringement or resolve legal issues. Both URLs must be real and accessible. The markup is particularly relevant to stock-image businesses and photographer portfolios where imagery is itself a commercial product.

ItemList Schema

Thu, 01 Oct 2026 00:00:00 +0900

ItemList organizes related items, such as recipes, courses or films, into a sequence. Only supported content types and feature requirements qualify for a search carousel; an arbitrary list, including jobs, does not automatically become one. Declare each item’s position and a valid accessible URL. Eligible horizontal displays can encourage exploration on mobile, but appearance is entirely at the search engine’s discretion.

JobPosting Schema

Thu, 01 Oct 2026 00:00:00 +0900

JobPosting can help vacancies appear in Google’s job-search experience, providing a channel beyond paid recruitment platforms such as JobKorea or Saramin. Specify validThrough when applicable and promptly retire expired postings or remove their markup. Leaving old jobs active or continually recycling misleading datePosted values can violate policies and impair future eligibility. Synchronize the structured data with the real recruitment lifecycle.

JSON-LD

Thu, 01 Oct 2026 00:00:00 +0900

JSON-LD combines JavaScript Object Notation with linked-data concepts that connect entities and their meaning. Its principal advantage is that it can be inserted independently in a script element without restructuring the surrounding HTML. Google recommends JSON-LD where possible because it is generally easier to maintain and generate through automated pipelines than embedded Microdata or RDFa. Multiple entities can be represented together in an array or graph, keeping complex pages manageable.

Knowledge Panel

Thu, 01 Oct 2026 00:00:00 +0900

Knowledge panels summarize entities in Google’s knowledge systems, commonly beside desktop results or within mobile layouts. Schema alone cannot guarantee a panel. Consistent names and facts across Organization or Person markup, Wikidata, Wikipedia and reliable reporting can help systems reconcile identity. Eligible representatives may claim a panel or submit suggested corrections; Wikipedia edits are a separate process and are not a management privilege automatically granted by a panel.

LocalBusiness Schema

Thu, 01 Oct 2026 00:00:00 +0900

LocalBusiness has many specific subtypes, including Restaurant, Store and Dentist. Choose the most appropriate subtype to describe the business precisely. Properties such as openingHoursSpecification, priceRange and paymentAccepted provide useful practical information for local discovery and inquiries. Keep the name, address and phone number consistent with Google Business Profile. Accurate data helps avoid conflicting location signals, but markup does not by itself guarantee local-pack placement.

MathSolver Schema

Thu, 01 Oct 2026 00:00:00 +0900

MathSolver was used in Google’s educational search integrations to describe mathematical solving tools and supporting workflows. Search-feature support changes over time and should be checked before implementation; markup alone does not secure an interactive result. LaTeX formulas can introduce rendering and accessibility issues, so provide appropriate MathML or meaningful alternative representations when needed. Keep solution explanations logically ordered and readable in addition to any machine-readable data.

MemberProgram Schema

Thu, 01 Oct 2026 00:00:00 +0900

MemberProgram describes benefits such as tier-based points or discounts so supported shopping systems can understand membership offerings. Use hasTiers to list levels such as Silver, Gold and VIP and suitable properties such as membershipPointsEarned to describe each benefit. Conditions in the markup must match the actual membership terms. Marketing and engineering teams should synchronize changes to avoid publishing inaccurate offers.

Merchant Listing

Thu, 01 Oct 2026 00:00:00 +0900

Merchant listings can display products in supported Shopping and search experiences without paying for each listing. Keep Merchant Center product feeds and on-site Product data consistent. Accurate identifiers such as GTIN or MPN help systems recognize the same item across sellers and compare offers. Mismatches can cause disapprovals or other enforcement depending on the issue, so an automated synchronization process is safer than independent manual updates.

MerchantReturnPolicy Schema

Thu, 01 Oct 2026 00:00:00 +0900

MerchantReturnPolicy expresses return windows, methods and responsibility for return fees using standardized properties. Eligible shopping presentations may show information such as “free returns within 14 days.” Specify applicableCountry where needed and make the declared policy consistent with the rules and actual terms for that market. If policies vary by season or product category, attach the appropriate policy to each relevant product or offer rather than applying an inaccurate global rule.

Microdata

Thu, 01 Oct 2026 00:00:00 +0900

Microdata attaches semantic properties to HTML elements rather than placing data in a separate script block. Because content and structured data are interwoven, changes to markup require careful maintenance of the associated attributes. JSON-LD often simplifies this work and is Google’s preferred format where practical. For legacy CMS templates with extensive Microdata, migrate priority pages gradually instead of replacing all valid markup at once.

Movie Schema

Thu, 01 Oct 2026 00:00:00 +0900

Movie structures film information that can help systems connect release details, cast, trailers and reviews to the right work. It is often used by film databases and review publishers rather than only promotional film sites. Relevant sameAs links to reliable sources such as IMDb can clarify identity. Genuine aggregateRating information may support eligible review appearances. Neither markup nor external identity links guarantee a knowledge panel.

NewsArticle Schema

Thu, 01 Oct 2026 00:00:00 +0900

NewsArticle provides explicit news-publishing context for search systems. Include an accessible publisher logo that meets the applicable feature guidance; the source’s 60-by-60-pixel example should not be treated as a universal requirement. Keep datePublished accurate and update dateModified when reporting changes materially. Repeatedly refreshing a timestamp for trivial spelling corrections can create a misleading impression of freshness, so establish an editorial standard for substantive updates. Markup is useful but is not a prerequisite that guarantees Google News or Top Stories inclusion.

Offer Schema

Thu, 01 Oct 2026 00:00:00 +0900

Offer is usually nested within Product or another saleable item to describe actual commercial terms. For time-limited prices, priceValidUntil helps state when the advertised price expires. Omitting or failing to update offer data can leave obsolete information available to systems after a promotion ends. Sites with frequent stock or pricing changes should generate current Offer values from their commerce data at rendering or publishing time.

Open Graph (og tags)

Thu, 01 Oct 2026 00:00:00 +0900

Facebook introduced Open Graph in 2010, and many platforms, including KakaoTalk and Slack, now use its metadata for shared-link previews. Support on other platforms, including X, can involve additional platform-specific tags. A 1,200 by 630 pixel og:image is a common preview target, although cropping varies. Open Graph is not a direct search-ranking signal, but it shapes the first impression of a shared link and can affect social click-through.

Organization Schema

Thu, 01 Oct 2026 00:00:00 +0900

Organization provides foundational identity information that helps search systems distinguish a brand in a knowledge graph. Use an accessible official logo of suitable quality; the source recommends at least 112 by 112 pixels, while precise requirements vary by feature. contactPoint can describe support phone numbers or email addresses. Relevant sameAs links to official social or reference profiles clarify identity, although they do not guarantee a knowledge panel or direct contact display.

Person Schema

Thu, 01 Oct 2026 00:00:00 +0900

Person is an entity description that can be nested inside an article’s author property, whereas ProfilePage describes the page focused on that person. For coauthored work, list authors as an array so each contributor is identified transparently. As automated content production expands, accurately identifying the people who wrote or reviewed material remains valuable context. Markup should reflect genuine contributions and does not independently establish expertise.

PostalAddress Schema

Thu, 01 Oct 2026 00:00:00 +0900

PostalAddress is commonly nested in LocalBusiness, Organization and Event markup. Administrative divisions vary by country, so use addressRegion and addressLocality consistently with the actual address conventions. For a Korean address, KR is the ISO 3166-1 alpha-2 country code. Keep the address consistent with Google Business Profile and other official listings; focus on accurate identity and location rather than treating every punctuation difference as a ranking penalty.

Product Schema

Thu, 01 Oct 2026 00:00:00 +0900

Product markup provides information such as name, image and brand. Combine it with accurate Offer data for pricing and availability and genuine AggregateRating information where appropriate to support eligible product presentations. Reviews need to meet the applicable policies; no general claim that all first-party reviews require third-party verification should be assumed. Update availability to OutOfStock promptly when inventory is exhausted to avoid sending shoppers to a product they cannot buy.

Product Snippet

Thu, 01 Oct 2026 00:00:00 +0900

Product snippets can emphasize commerce information beneath a normal search title without requiring users to visit a separate Shopping tab. Their requirements depend on the supported product feature; not every snippet requires both an Offer and AggregateRating. Use accurate applicable properties and fix errors that affect eligibility. Review Search Console’s product enhancement reports and ensure price or stock changes update the associated markup.

ProductGroup Schema

Thu, 01 Oct 2026 00:00:00 +0900

ProductGroup associates variants with a shared product family, helping systems match a search such as “black earphones” to the relevant variant rather than a generic family page. Use variesBy to identify the varying attributes and hasVariant to list the individual Product entities. This parent-and-child structure is particularly useful for fashion or electronics catalogs with many options.

ProfilePage Schema

Thu, 01 Oct 2026 00:00:00 +0900

ProfilePage describes a page focused on an author or expert and can make evidence relevant to expertise and trust easier for systems to interpret. Person properties such as alumniOf, award and worksFor express education, awards and affiliation explicitly. For sensitive YMYL topics including medicine, finance and law, link articles to accurate author profiles through author references. The markup supplies identity and context rather than independently proving expertise or guaranteeing higher rankings.

QAPage Schema

Thu, 01 Oct 2026 00:00:00 +0900

QAPage applies to community question-and-answer pages such as Stack Overflow or Naver Knowledge iN, where users can submit different responses. It differs from an FAQ page whose publisher supplies the answers. Properties such as acceptedAnswer and upvoteCount can describe the chosen answer and its community support. Applying QAPage to a company FAQ where visitors cannot submit answers misrepresents the page, so the markup must match the actual interaction model.

RDFa (Resource Description Framework in Attributes)

Thu, 01 Oct 2026 00:00:00 +0900

RDFa adds attributes such as vocab, typeof and property directly to HTML elements to express semantic data. It helped establish semantic publishing, and Open Graph also uses conventions associated with RDFa. Embedded attributes can make templates verbose and harder to maintain, so JSON-LD is often favored for new structured-data implementations. Where a legacy site already uses valid RDFa, a gradual move beginning with new or priority pages is usually more practical than a rushed replacement.

Recipe Schema

Thu, 01 Oct 2026 00:00:00 +0900

Recipe schema structures prepTime, cookTime, ingredients, calories and step-by-step instructions so supported search and assistant systems can interpret cooking content. List recipeIngredient values as an array and express instructions with HowToStep entries. Clear photographs of the finished dish and genuine reviews can improve the usefulness of eligible recipe presentations. Incorrect ingredients or times mislead users and may violate structured-data policies; assistant support also depends on the particular service.

Restaurant Schema

Thu, 01 Oct 2026 00:00:00 +0900

Restaurant is a subtype of LocalBusiness and therefore also supports common properties such as address and telephone. Use openingHoursSpecification to express different hours by day, including shorter weekend service. hasMenu can link to the actual menu or describe menu information where appropriate. These details help search systems understand the restaurant and may support useful local presentations, but do not guarantee a particular map or result format.

Review Schema

Thu, 01 Oct 2026 00:00:00 +0900

Review markup describes one review, whereas AggregateRating summarizes multiple reviews. Use itemReviewed to identify the subject, reviewRating for the score and author for attribution. Self-authored or misleading promotional reviews can undermine credibility. Rich-result eligibility depends on the item type and Google’s review policies, including restrictions on self-serving business reviews; it should not be inferred merely from whether a review appears on a first-party or third-party site.

Rich Results

Thu, 01 Oct 2026 00:00:00 +0900

Rich results include visual or informational additions to ordinary text links, such as stars, prices, images or supported FAQ displays. They can make a result more prominent at the same ranking position. Not every Schema.org type corresponds to a Google rich-result feature: only supported types and eligible content qualify, while other markup mainly helps systems understand meaning. Review Search Console’s relevant enhancement reports to identify detected types and errors. Valid markup does not guarantee display.

Rich Results Test

Thu, 01 Oct 2026 00:00:00 +0900

The free Rich Results Test at search.google.com/test/rich-results accepts a URL or code and reports recognized rich-result types, syntax problems and missing required properties. A valid result does not guarantee that Google will display a rich result, because quality and policy assessments also apply. Include structured-data checks in pre-release validation and automate suitable local syntax and property checks in CI; do not assume the public tool provides an official general-purpose automation API.

sameAs Schema Property

Thu, 01 Oct 2026 00:00:00 +0900

sameAs links can connect official YouTube, Instagram, Wikipedia and LinkedIn pages to a single brand entity. They help systems reconcile identity across channels and interpret brand information for knowledge graphs and AI search. Incorrect links or abandoned accounts can introduce contradictory information, so review them regularly. Only include pages that genuinely identify the same entity.

Schema Markup

Thu, 01 Oct 2026 00:00:00 +0900

Schema markup uses a shared vocabulary containing hundreds of types, including Article, Product and FAQPage, and their associated properties. The vocabulary evolves through new releases, so monitor changes relevant to your content rather than assuming every new property is AI-specific or supported as a search enhancement. Reusable page-type templates mapped automatically to CMS fields provide an efficient maintenance model.

Schema Markup Validator

Thu, 01 Oct 2026 00:00:00 +0900

The Schema Markup Validator at validator.schema.org checks structured-data syntax and recognized vocabulary properties across Schema.org. It differs from Google’s Rich Results Test, which focuses on the types and requirements of supported Google features. The tools complement rather than replace one another. Use both where relevant before deployment to detect malformed data or vocabulary problems as well as feature-specific omissions.

Schema.org

Thu, 01 Oct 2026 00:00:00 +0900

Schema.org began in 2011 through collaboration among Google, Microsoft and Yahoo, with Yandex also participating. It aims to provide a shared vocabulary rather than a format controlled exclusively by one search engine. Developers and search systems use it to interpret content meaning, and other automated applications may also consume it. Monitor releases for relevant types and properties as the vocabulary evolves, without assuming every addition immediately creates a new search feature.

ShippingService Schema

Thu, 01 Oct 2026 00:00:00 +0900

ShippingService and OfferShippingDetails describe shipping charges, destinations and delivery expectations for supported shopping presentations, including free-shipping or arrival information. Distinguish handlingTime from transitTime so the expected delivery period is represented correctly. Large differences between declared and actual delivery times can lead to restricted display. Use DefinedRegion where appropriate to specify areas with different charges, such as remote islands, and declare multiple shipping options accurately.

Site Name (WebSite Schema)

Thu, 01 Oct 2026 00:00:00 +0900

The name and alternateName properties of WebSite can suggest a recognizable brand name, such as “MKTGLab,” in place of a bare domain like example.com. alternateName can include a common abbreviation or Korean brand spelling used by audiences. These properties do not guarantee the chosen search display: Google’s assessment and consistency across the site also matter.

Sitelinks

Thu, 01 Oct 2026 00:00:00 +0900

Sitelinks can provide shortcuts to pages such as Products, About and Support beneath a branded search result. No schema guarantees them; search systems select them using their interpretation of structure and relevance. Clear navigation and internal links help. The source refers to the former Sitelinks Searchbox integration using WebSite potentialAction, but Google retired that visible search feature in 2024. Ordinary sitelinks remain useful because they give users direct routes to key destinations and increase a brand’s presence in the results.

Snippet

Thu, 01 Oct 2026 00:00:00 +0900

Search snippets are generated primarily from page content, and a meta description may be used when it provides a useful summary. Google can select passages that better match the query, so a carefully written description may not appear verbatim. Review actual results for relevant queries to identify which passages are being selected and use those patterns to improve the clarity and structure of the page.

SoftwareApplication Schema

Thu, 01 Oct 2026 00:00:00 +0900

SoftwareApplication describes software details that can support eligible search presentations containing ratings, prices and compatibility information. Use suitable applicationCategory values, such as BusinessApplication or GameApplication, consistent with the relevant search documentation. For free software, declare an Offer price of 0 where required rather than omitting pricing. Eligibility depends on the supported feature and its actual requirements.

Speakable Schema

Thu, 01 Oct 2026 00:00:00 +0900

Speakable markup can identify a news summary or key passage with CSS selectors rather than asking a voice service to read the entire article. Support has historically been limited, particularly to eligible English-language US news experiences, and future expansion is not assured. Select passages of roughly two or three concise sentences that sound natural when read aloud. Verify the current eligibility and service requirements before relying on it for distribution.

Structured Data

Thu, 01 Oct 2026 00:00:00 +0900

Structured Data is a metadata layer that explicitly describes content using a standardized vocabulary, such as Schema.org, alongside the text that people read. Rather than inferring details from prose, a search engine can read explicit statements that a page describes a product priced at KRW 89,000 with a rating of 4.7. Its relevance also extends to generative AI services such as ChatGPT and Perplexity, where explicit information about entities can support the interpretation of web content; markup alone does not guarantee training use or citation.

Structured Data Manual Action

Thu, 01 Oct 2026 00:00:00 +0900

Google may impose a structured-data manual action when markup invents ratings or stock availability, describes information absent from the page, or uses hidden content to mislead systems. The action can remove rich-result eligibility for affected pages or wider portions of a site, weakening visual prominence in search. After correcting the problems, request reconsideration in Search Console where available. Review times vary and can extend for weeks, so preventing discrepancies between visible content and markup is preferable.

TVSeries Schema

Thu, 01 Oct 2026 00:00:00 +0900

TVSeries schema describes seasons, episode information, cast and broadcasters to help systems interpret television content and related media entities. Mark individual episodes separately as TVEpisode and make the series-to-episode hierarchy explicit. Use accurate official broadcaster names and episode numbers. Relevant sameAs links to recognized databases such as IMDb can help clarify entity identity, without guaranteeing a knowledge panel or card result.

VacationRental Schema

Thu, 01 Oct 2026 00:00:00 +0900

VacationRental describes properties such as apartment rentals, pensions and guesthouses. Supported integrations can help travel search systems understand these listings and direct users toward booking pages. Provide accurate check-in and check-out times, geographic coordinates and amenityFeature information so the listing can be matched to relevant needs. Keep prices and availability synchronized with the reservation system: discrepancies damage user trust and may affect eligibility.

VideoObject Schema

Thu, 01 Oct 2026 00:00:00 +0900

VideoObject specifies a video’s title, description, upload date, thumbnail URL and duration in ISO 8601 format, such as PT10M30S. Clip or hasPart information can identify Key Moments so users can navigate to relevant segments through supported search features. Thumbnail URLs must be publicly accessible and not blocked by robots.txt or authentication so Google can retrieve them.

Structured Data & Semantic Web on 247COMPASS

AggregateRating Schema

BreadcrumbList Schema

Course Schema

CreativeWork (isAccessibleForFree)

Dataset Schema

Event Schema

FAQPage Schema

Favicon

Featured Snippet

Google Discover

HowTo Schema

ImageObject License Schema

ItemList Schema

JobPosting Schema

JSON-LD

Knowledge Panel

LocalBusiness Schema

MathSolver Schema

MemberProgram Schema

Merchant Listing

MerchantReturnPolicy Schema

Microdata

Movie Schema

NewsArticle Schema

Offer Schema

Open Graph (og tags)

Organization Schema

People Also Ask (PAA)

Person Schema

PostalAddress Schema

Product Schema

Product Snippet

ProductGroup Schema

ProfilePage Schema

QAPage Schema

RDFa (Resource Description Framework in Attributes)

Recipe Schema

Restaurant Schema

Review Schema

Rich Results

Rich Results Test

sameAs Schema Property

Schema Markup

Schema Markup Validator

Schema.org

ShippingService Schema

Site Name (WebSite Schema)

Sitelinks

Snippet

SoftwareApplication Schema

Speakable Schema

Structured Data

Structured Data Manual Action

TVSeries Schema

VacationRental Schema

VideoObject Schema