Structured data (schema.org) has long been a pillar of SEO. It enables search engines to understand the structure of content. In the context of GEO, the question arises: should we continue to use schema markup? <\/p>\n
AIs rely on explicit signals to interpret and select passages. Boulder SEO Marketing points out that GEO “incorporates advanced schema markup techniques to help AI understand content structure”. Tags (FAQPage, HowTo, Article, LocalBusiness, Product) make it easier for the models to read and increase the chances of being cited. <\/p>\n
JSON-LD (recommended by Google) offers a flexible, remote solution that doesn’t affect HTML structure. For GEO : <\/p>\n
Article<\/strong>: includes title, description, publication date, author and E-E-A-T fields.<\/p>\n<\/li>\n FAQPage<\/strong>: defines Q\/Rs, improving visibility in extracts and reuse by AIs.<\/p>\n<\/li>\n HowTo<\/strong>: useful for procedural content, it defines steps and a result.<\/p>\n<\/li>\n Product<\/strong>: specifies features (name, description, price, availability) and may include notices.<\/p>\n<\/li>\n LocalBusiness<\/strong>: describes a business with location information and attributes (services, opening hours).<\/p>\n<\/li>\n<\/ul>\n Respect the hierarchy.<\/strong> Each schema type must be properly nested and conform to the schema.org standard.<\/p>\n<\/li>\n Include UGC.<\/strong> Add “review” and “aggregateRating” fields with verified reviews.<\/p>\n<\/li>\n Avoid spam.<\/strong> Use realistic, relevant data; artificial markup can be ignored or penalized.<\/p>\n<\/li>\n Update data.<\/strong> Make sure your information (products, prices, opening hours) remains up to date.<\/p>\n<\/li>\n<\/ul>\n Some marketers question the relevance of schema markup in the GEO era. In reality, schema remains a crowbar<\/strong> for organizing information and making it comprehensible to AIs. It acts as a lexicon describing entities and their relationships. Without a schema, the AI has to guess at the organization of your page; with one, it understands explicitly that it’s an article, tutorial or product sheet. <\/p>\n Structured data formats include Microdata<\/strong>, RDFa<\/strong> and JSON-LD<\/strong>. Google now recommends the use of JSON-LD<\/strong>, a JavaScript script that does not alter the HTML structure. This format is more flexible and easier to maintain. Microdata or RDFa embedded directly in HTML may be relevant for simple sites, but they complicate maintenance when you need to modify the structure. <\/p>\n As part of GEO, some publishers are adopting a Structured data must be tailored to your products or services. Here are the most common types and their applications: <\/p>\n Suppose you’re selling headphones. You can structure the product sheet using the tags This precise structure enables AI to identify the brand, price, availability and reviews. By adding To find out if your beaconing is bearing fruit :<\/p>\n Use Search Console<\/strong> to check that your rich snippets are detected and displayed in SERPs (zero position or product maps).<\/p>\n<\/li>\n Monitor your GEO metrics: a well-structured schema can increase the likelihood of being cited by the AI and improve your ASoV. Test your pages in ChatGPT and Perplexity to see if the AI picks up your information correctly. <\/p>\n<\/li>\n Compare two similar pages, one with schema and one without, and measure the difference in citations and conversions.<\/p>\n<\/li>\n<\/ul>\n Beyond current practices, structured data will evolve to integrate the new needs of AI. Initiatives such as Schema for AI<\/strong> seek to enrich schemas to include information on data provenance, licensing or source quality. In the near future, AIs will be able to use this metadata to assess the reliability and diversity of content. For example, a field indicating that the statistic comes from an official body could be used as a signal of authority. It is also likely that engines will impose restrictions via The schema markup remains a valuable tool for GEO. It makes it easier for models to understand your pages, and serves as a guarantee of reliability. In an environment where AIs extract and summarize information, providing a clear and complete schema increases your chances of being mentioned and helps users to trust your products and services. <\/p>\n Schema markup remains a major asset for GEO. By structuring your data, you enable AI engines to reliably understand and reuse your content, increasing your chances of citation and visibility. <\/p>\n","protected":false},"excerpt":{"rendered":" GEO and structured data: is schema markup still useful? Structured data (schema.org) has long been a pillar of SEO. It enables search engines to understand the structure of content. In the context of GEO, the question arises: should we continue to use schema markup? The role of structured data in AI AIs rely on explicit […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[78,76],"tags":[],"class_list":["post-4641","post","type-post","status-publish","format-standard","hentry","category-artificial-intelligence","category-customer-marketing"],"acf":[],"yoast_head":"\nTable: schema tags and GEO benefits<\/h3>\n
\n\n
\n \nType of diagram<\/th>\n Use case<\/th>\n GEO impact<\/th>\n<\/tr>\n<\/thead>\n \n Article<\/strong><\/td>\n Blog articles, studies, guides<\/td>\n Allows AI to understand subject, date and author<\/td>\n<\/tr>\n \n FAQPage<\/strong><\/td>\n FAQ sections<\/td>\n Improves likelihood of being quoted for specific questions<\/td>\n<\/tr>\n \n HowTo<\/strong><\/td>\n Step-by-step tutorials<\/td>\n Enables structured extraction of steps<\/td>\n<\/tr>\n \n Product<\/strong><\/td>\n Product sheets, comparisons<\/td>\n Provides structured details that AI can integrate into its responses<\/td>\n<\/tr>\n \n LocalBusiness<\/strong><\/td>\n Store pages<\/td>\n Helps AI associate locations, services and opening hours<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n Best practices<\/h3>\n
\n
Conclusion<\/h3>\n
Why are we still talking about schema markup?<\/h3>\n
Microdata, RDFa and JSON-LD: which to choose?<\/h3>\n
The llms.txt file<\/h3>\n
llms.txt<\/code> file (similar to robots.txt<\/code>) to indicate which paths on their site can be used by LLM models. Although this practice is still experimental, it is intended to guide AIs in extracting the most relevant content. Oomph refers to this trend and recommends monitoring engine developments. <\/p>\nVerticalization and schematic types<\/h3>\n
\n\n
\n \nSchematic type<\/th>\n Usage<\/th>\n Examples of key fields<\/th>\n GEO tips<\/th>\n<\/tr>\n<\/thead>\n \n Product<\/strong><\/td>\n Product data sheets (e-commerce)<\/td>\n name<\/code>description<\/code>, price<\/code>, availability<\/code>, brand<\/code>, review<\/code><\/td>\nInclude UGC reviews and availability information to improve the quality of generative responses<\/td>\n<\/tr>\n \n LocalBusiness<\/strong><\/td>\n Store or agency pages<\/td>\n name<\/code>address<\/code>, telephone<\/code>, openingHours<\/code>, geo<\/code>, aggregateRating<\/code><\/td>\nAdd services, photos, local FAQs and synchronize with GMB<\/td>\n<\/tr>\n \n HowTo<\/strong><\/td>\n Step-by-step guides<\/td>\n name<\/code>, step<\/code>, tool<\/code>, image<\/code><\/td>\nBreak down each step into short sentences, add images and videos<\/td>\n<\/tr>\n \n Event<\/strong><\/td>\n Event announcements (conferences, webinars)<\/td>\n name<\/code>startDate<\/code>, location<\/code>, performer<\/code>, offers<\/code><\/td>\nClearly indicate location, time and price; refer to sites such as Eventbrite<\/td>\n<\/tr>\n \n Review<\/strong> and AggregateRating<\/strong><\/td>\n Customer reviews<\/td>\n reviewBody<\/code>, reviewRating<\/code>, author<\/code>, datePublished<\/code><\/td>\nInclude verified testimonials and add a ratingValue<\/code> medium to build trust.<\/td>\n<\/tr>\n\n FAQPage<\/strong><\/td>\n FAQ sections<\/td>\n mainEntity<\/code> (list of Question\/Answer<\/code>)<\/td>\nCover several variations of questions and provide concise answers<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n Case study: diagram for a product sheet<\/h3>\n
Product<\/code> and Offer<\/code>: <\/p>\n\n
<script<\/span><\/span> type<\/span>=\"application\/ld+json\"<\/span>>
\n<\/code><\/div>\n{
\n<\/span>\"@context\"<\/span>: \"https:\/\/schema.org\/\"<\/span>,
\n\"@type\"<\/span>: \"Product\"<\/span>,
\n\"name\"<\/span>: \"Casque sans fil X100\"<\/span>,
\n\"description\"<\/span>: \"Casque Bluetooth avec r\u00e9duction de bruit active.\"<\/span>,
\n\"brand\"<\/span>: { \"@type\"<\/span>: \"Brand\"<\/span>, \"name\"<\/span>: \"AudioPro\"<\/span> },
\n\"review\"<\/span>: {
\n\"@type\"<\/span>: \"Review\"<\/span>,
\n\"author\"<\/span>: { \"@type\"<\/span>: \"Person\"<\/span>, \"name\"<\/span>: \"Jean Dupont\"<\/span> },
\n\"reviewRating\"<\/span>: { \"@type\"<\/span>: \"Rating\"<\/span>, \"ratingValue\"<\/span>: \"5\"<\/span>, \"bestRating\"<\/span>: \"5\"<\/span> },
\n\"reviewBody\"<\/span>: \"Qualit\u00e9 sonore incroyable et autonomie longue.\"<\/span>
\n<\/code><\/div>\n },<\/code><\/div>\n \"offers\"<\/span>: {
\n\"@type\"<\/span>: \"Offer\"<\/span>,
\n\"price\"<\/span>: \"199.99\"<\/span>,
\n\"priceCurrency\"<\/span>: \"EUR\"<\/span>,
\n\"availability\"<\/span>: \"https:\/\/schema.org\/InStock\"<\/span>
\n<\/code><\/div>\n },
\n<\/code><\/div>\n \"aggregateRating\"<\/span>: {
\n\"@type\"<\/span>: \"AggregateRating\"<\/span>,
\n\"ratingValue\"<\/span>: \"4.7\"<\/span>,
\n\"reviewCount\"<\/span>: \"34\"<\/span>
\n<\/code><\/div>\n }
\n<\/code><\/div>\n}
\n<\/code><\/div>\n<\/script<\/span><\/span>>
\n<\/code><\/div>\n<\/blockquote>\n<\/div>\nFAQPage<\/code> markup at the bottom of the file (questions on autonomy, compatibility, warranty), you further improve readability. <\/p>\nMeasuring the impact of schema markup<\/h3>\n
\n
Outlook and conclusion<\/h3>\n
llms.txt<\/code> files or dedicated HTTP headers to control AI access to content. Publishers will need to keep pace with these developments and adapt their schema accordingly. <\/p>\nConclusion in perspective<\/h3>\n