Latest / Marketing Automation in 2026 / Schema.org for AI Surfacing: Which Markups Matter Now

Transcript

Schema.org for AI Surfacing: Which Markups Matter Now · Marketing Automation in 2026

• 0:00
  SPEAKER_00: Schema.org for Artificial Intelligence Surfacing.
• 0:03
  SPEAKER_00: Which markups matter now?
• 0:05
  SPEAKER_00: As of september fifth, twenty twenty six, structured data still helps search engines understand pages, authors, organizations, and facts.
• 0:14
  SPEAKER_00: However, it is not a direct ranking switch for artificial intelligence answers.
• 0:18
  SPEAKER_00: Google states that pages do not need special schema.org markup to appear in AI overviews or AI mode.
• 0:25
  SPEAKER_00: A page must mainly be crawlable, indexed, eligible for a search snippet, and supported by useful content.
• 0:31
  SPEAKER_00: Google also says structured data should match the visible page content.
• 0:35
  SPEAKER_00: The best current strategy is therefore use structured data to describe the page accurately.
• 0:40
  SPEAKER_00: Match the markup to the page's true purpose.
• 0:43
  SPEAKER_00: Build clear relationships between articles, authors, organizations, and topics.
• 0:48
  SPEAKER_00: Write direct, complete answers in visible HTML.
• 0:52
  SPEAKER_00: Measure artificial intelligence citations separately from traditional rich results.
• 0:56
  SPEAKER_00: Executive verdict.
• 0:58
  SPEAKER_00: For the full table, please open this article on autopod.co.
• 1:01
  SPEAKER_00: The broad research finding is important.
• 1:04
  SPEAKER_00: Adding generic structured data alone has not produced a consistent increase in artificial intelligence citations.
• 1:10
  SPEAKER_00: A controlled HREF study tracked 1,885 pages that added JavaScript object notation for linked data and compared them with 4,000 control pages.
• 1:20
  SPEAKER_00: It found no meaningful improvement in Google AI mode or ChatGPT citations.
• 1:25
  SPEAKER_00: Google AI overview citations declined slightly, but the researchers warned that the change was small and could not clearly be blamed on the markup.
• 1:33
  SPEAKER_00: A separate 2026 preprint found that generic types such as article, organization, breadcrumb list, and web page did not independently predict artificial intelligence citations after controlling for search rank and domain authority.
• 1:46
  SPEAKER_00: Its strongest finding was that pages with concrete, attribute-rich data, such as prices, ratings, and specifications, performed better than pages with only generic page labels.
• 1:57
  SPEAKER_00: That finding focused mainly on product and review pages, so it should not be treated as proof that any one of the types in this article creates a citation advantage.
• 2:06
  SPEAKER_00: What structured data can and cannot do?
• 2:08
  SPEAKER_00: Structured data is a machine readable description of a page.
• 2:12
  SPEAKER_00: It can tell a search engine what type of page it is, who wrote it, which organization published it, what question it answers, what date it was published or updated, which person, company, term, or dataset the page describes.
• 2:24
  SPEAKER_00: Google says structured data can help its systems understand page content and make pages eligible for richer search features.
• 2:31
  SPEAKER_00: It also says that Google search may use other schema.org properties for understanding, even when those properties do not trigger a visible search result.
• 2:39
  SPEAKER_00: Also, structured data does not guarantee a higher organic ranking, an artificial intelligence citation, a rich result, a knowledge panel, inclusion in an artificial intelligence answer, use of the exact text in the markup.
• 2:54
  SPEAKER_00: Bing gives similar guidance.
• 2:56
  SPEAKER_00: Its current webmaster guidance says structured data may support clearer grounding, but it does not guarantee visibility or citation traffic.
• 3:04
  SPEAKER_00: Bing also advises publishers to make facts and definitions explicit in the visible page content.
• 3:10
  SPEAKER_00: The main research limitation artificial intelligence answer panels usually show the source page, not the schema.org type that may have been present on that page.
• 3:20
  SPEAKER_00: Google does not publish a report saying, for example, that a page was cited because it used article instead of web page.
• 3:27
  SPEAKER_00: This creates three different questions.
• 3:30
  SPEAKER_00: Was the page cited?
• 3:31
  SPEAKER_00: Did the page contain structured data?
• 3:33
  SPEAKER_00: Did the structured data cause the citation?
• 3:35
  SPEAKER_00: Most studies can answer only the first two.
• 3:38
  SPEAKER_00: They cannot prove the third.
• 3:40
  SPEAKER_00: That is why a page with FAQ page markup may appear frequently in artificial intelligence answers without the markup being the reason.
• 3:48
  SPEAKER_00: The page may have strong content, a high search ranking, many links, or a well-known brand.
• 3:54
  SPEAKER_00: Audit by schema type article.
• 3:56
  SPEAKER_00: What it does.
• 3:57
  SPEAKER_00: Article describes an article, news story, blog post, or similar editorial page.
• 4:03
  SPEAKER_00: Google supports article, news article, and blog posting as article types.
• 4:07
  SPEAKER_00: Google does not list required properties for article markup, but it recommends adding the properties that apply to the page.
• 4:14
  SPEAKER_00: Properties that matter most.
• 4:16
  SPEAKER_00: Use these when they are visible and accurate.
• 4:18
  SPEAKER_00: Headline, author, author.name, author.url, or author.same as date published, date modified, image, publisher, main entity of page, about in language.
• 4:30
  SPEAKER_00: Google recommends using a real person or organization for the author.
• 4:34
  SPEAKER_00: It also recommends keeping dates and structured data consistent with the visible publication and update dates.
• 4:40
  SPEAKER_00: Artificial Intelligence Effect, evidence level, indirect.
• 4:44
  SPEAKER_00: Article helps establish page type, authorship, and freshness.
• 4:48
  SPEAKER_00: These are useful signals for search systems, especially on fax pages and editorial content.
• 4:53
  SPEAKER_00: However, current evidence does not show that adding article alone increases artificial intelligence citations.
• 5:00
  SPEAKER_00: Article checklist.
• 5:02
  SPEAKER_00: The page is genuinely an article.
• 5:04
  SPEAKER_00: The headline matches the visible title.
• 5:06
  SPEAKER_00: Every visible author is included.
• 5:08
  SPEAKER_00: Each author has a separate person or organization object.
• 5:12
  SPEAKER_00: Author names contain names only, not job titles or publisher names.
• 5:17
  SPEAKER_00: The author links to a real profile or author page.
• 5:20
  SPEAKER_00: Publication and update dates are visible on the page.
• 5:23
  SPEAKER_00: Dates use the correct time zone when time is included.
• 5:26
  SPEAKER_00: The image represents the article.
• 5:28
  SPEAKER_00: The publisher is identified consistently across the site.
• 5:32
  SPEAKER_00: The article is not marked up as a different primary type, such as how to, unless the page truly serves both purposes.
• 5:39
  SPEAKER_00: Web page.
• 5:40
  SPEAKER_00: What it does.
• 5:44
  SPEAKER_00: Schema.org states that every web page is implicitly treated as a web page, but an explicit declaration can help when the page includes page level properties or relationships.
• 5:55
  SPEAKER_00: Useful properties include URL, name, description, in language, date modified, breadcrumb, main entity, about, is part of, primary image of page, artificial intelligence effect, evidence level, low and indirect.
• 6:10
  SPEAKER_00: Web page is best used as the outer page layer in a connected graph.
• 6:14
  SPEAKER_00: It can connect the page to its main article, definition, dataset, person, or organization.
• 6:20
  SPEAKER_00: It should not be treated as a special artificial intelligence optimization type.
• 6:24
  SPEAKER_00: A page that contains only a generic web page object usually provides less useful information than a page that clearly identifies its main entity.
• 6:33
  SPEAKER_00: Web page checklist.
• 6:34
  SPEAKER_00: One, use one stable add ID for the page.
• 6:38
  SPEAKER_00: Use the canonical URL as the page URL.
• 6:40
  SPEAKER_00: Identify the page's true main entity.
• 6:43
  SPEAKER_00: Link the main entity back to the page with main entity of page.
• 6:47
  SPEAKER_00: Add in language when known.
• 6:49
  SPEAKER_00: Keep the page name and description aligned with visible content.
• 6:52
  SPEAKER_00: Do not use web page to hide the fact that the page is really an article, profile, dataset, or question page.
• 6:59
  SPEAKER_00: QA page.
• 7:00
  SPEAKER_00: What it does.
• 7:01
  SPEAKER_00: QA page is for a page focused on one question and its answers.
• 7:05
  SPEAKER_00: Google says it uses question structured data from pages marked as QA page, and there should be only one QA page and one main question on the page.
• 7:13
  SPEAKER_00: Required properties.
• 7:15
  SPEAKER_00: For current Google question and answer eligibility, QA page main entity, a nested question, question answer count, either accepted answer or suggested answer.
• 7:25
  SPEAKER_00: Answer text.
• 7:26
  SPEAKER_00: A question with no answers is not eligible for the rich result.
• 7:29
  SPEAKER_00: Important content rule Do not use QA page for a normal frequently asked questions page, a blog post that answers a question, a how-to article, a product page containing many questions, an editorial answer written only by the site owner.
• 7:44
  SPEAKER_00: Google says users must be able to submit answers for a normal QA page.
• 7:48
  SPEAKER_00: Valid examples include a forum question or a support page where users can provide answers.
• 7:53
  SPEAKER_00: Artificial intelligence effect.
• 7:55
  SPEAKER_00: Evidence level, medium semantic fit, no proven causal lift.
• 7:59
  SPEAKER_00: A real question and answer page is naturally easy for a retrieval system to understand.
• 8:04
  SPEAKER_00: However, no strong public study proves that QA page markup itself increases artificial intelligence citations.
• 8:10
  SPEAKER_00: QA page checklist.
• 8:12
  SPEAKER_00: 1.
• 8:13
  SPEAKER_00: The page focuses on one question.
• 8:15
  SPEAKER_00: Users can submit answers unless the page qualifies for a special education question and answer experience.
• 8:21
  SPEAKER_00: The full question is visible.
• 8:22
  SPEAKER_00: The full answer text is visible.
• 8:24
  SPEAKER_00: Accepted and suggested answers are labeled correctly.
• 8:29
  SPEAKER_00: Comments are marked as comments, not answers.
• 8:32
  SPEAKER_00: The page is not simply an editorial frequently asked questions page.
• 8:36
  SPEAKER_00: The page does not contain multiple unrelated questions.
• 8:39
  SPEAKER_00: QA page example.
• 8:41
  SPEAKER_00: Use this pattern only when the page truly supports a question and answer interaction.
• 8:45
  SPEAKER_00: How-to.
• 8:46
  SPEAKER_00: What it does.
• 8:47
  SPEAKER_00: How-to describes step-by-step instructions.
• 8:50
  SPEAKER_00: Google once supported how-to rich results, but it deprecated that search feature in September 2023.
• 8:56
  SPEAKER_00: Google said how-to results would no longer appear on desktop and had already been removed from mobile search.
• 9:03
  SPEAKER_00: Artificial intelligence effect.
• 9:05
  SPEAKER_00: Evidence level low for Google.
• 9:08
  SPEAKER_00: The visible steps may still help users and retrieval systems.
• 9:11
  SPEAKER_00: A clear tutorial with headings, numbered steps, tools, time, and warnings is easier to read and quote.
• 9:18
  SPEAKER_00: But current evidence does not show that how-to markup creates a special advantage in Google AI overviews, or AI mode.
• 9:25
  SPEAKER_00: Recommendation.
• 9:26
  SPEAKER_00: Use how-to only when the page genuinely teaches a task.
• 9:30
  SPEAKER_00: The steps are visible in the page content.
• 9:32
  SPEAKER_00: Another search engine, platform, or internal system benefits from the markup.
• 9:36
  SPEAKER_00: Your team can maintain it without creating conflicting data.
• 9:40
  SPEAKER_00: For Google search, prioritize strong HTML headings, numbered lists, clear instructions, and useful images or video.
• 9:48
  SPEAKER_00: Tutorial checklist.
• 9:49
  SPEAKER_00: The page teaches a real task.
• 9:51
  SPEAKER_00: The result of the task is clear.
• 9:53
  SPEAKER_00: Each step is visible and complete.
• 9:55
  SPEAKER_00: Step names match the visible headings.
• 9:57
  SPEAKER_00: Tools and supplies are real and visible.
• 10:00
  SPEAKER_00: Time estimates are accurate.
• 10:02
  SPEAKER_00: Safety warnings are included where needed.
• 10:04
  SPEAKER_00: The first section gives a short answer or outcome.
• 10:07
  SPEAKER_00: The page does not rely on markup to provide the instructions.
• 10:10
  SPEAKER_00: Claim review.
• 10:11
  SPEAKER_00: What it does, claim review was designed for fact-checking content.
• 10:14
  SPEAKER_00: Google phased out claim review support in search as part of its 2025 effort to simplify search results.
• 10:21
  SPEAKER_00: The type was removed from Search Console reporting and the rich results test.
• 10:25
  SPEAKER_00: Artificial Intelligence Effect.
• 10:27
  SPEAKER_00: Evidence level, no current Google Advantage.
• 10:30
  SPEAKER_00: A high quality fact check can still be cited because it clearly states the claim, the rating, the evidence, the date, the fact-checking organization, the reasoning behind the conclusion.
• 10:40
  SPEAKER_00: Those benefits come mainly from the content itself, not from the retired Google search feature.
• 10:45
  SPEAKER_00: Recommendation for a fax page.
• 10:47
  SPEAKER_00: Use article or news article when the page is editorial.
• 10:50
  SPEAKER_00: Clearly state the claim in visible text.
• 10:52
  SPEAKER_00: Cite primary evidence.
• 10:54
  SPEAKER_00: Identify the author and reviewing organization.
• 10:56
  SPEAKER_00: Add publication and review dates.
• 10:58
  SPEAKER_00: Use claim review only if another platform or data system specifically requires it.
• 11:03
  SPEAKER_00: Do not add claim review only because you expect Google Artificial Intelligence Answers to prefer it.
• 11:08
  SPEAKER_00: FAQ page.
• 11:10
  SPEAKER_00: What it does.
• 11:11
  SPEAKER_00: FAQ page describes a page containing questions and official answers.
• 11:16
  SPEAKER_00: Google stopped showing the FAQ rich result in search starting May 7, 2026, and removed the related documentation in June 2026.
• 11:26
  SPEAKER_00: Artificial Intelligence Effect.
• 11:28
  SPEAKER_00: Evidence level, weak and mixed.
• 11:30
  SPEAKER_00: A 90-day vendor study added FAQ page markup to 120 pages.
• 11:36
  SPEAKER_00: It found no reliable improvement in ChatGPT, Gemini, or Google AI overview citations.
• 11:42
  SPEAKER_00: Perplexity showed a small increase, but the study itself said the result was platform specific and did not prove causation.
• 11:50
  SPEAKER_00: Another study of 615 already cited pages found that FAQ markup appeared more often on heavily cited pages.
• 11:58
  SPEAKER_00: That relationship disappeared after controlling for repeated pages from the same publishers.
• 12:03
  SPEAKER_00: The researchers concluded that the evidence did not establish an effect from the markup itself.
• 12:09
  SPEAKER_00: Recommendation.
• 12:10
  SPEAKER_00: Use frequently asked questions when they improve the page for readers.
• 12:14
  SPEAKER_00: Do not add large blocks of generic questions just to target artificial intelligence answers.
• 12:19
  SPEAKER_00: If you keep FAQ page markup for another search engine or content system, make every question visible, make every answer complete.
• 12:27
  SPEAKER_00: Keep the markup identical to the page.
• 12:30
  SPEAKER_00: Do not repeat the same question in several schema blocks.
• 12:33
  SPEAKER_00: Do not expect a Google FAQ rich result.
• 12:36
  SPEAKER_00: FAQ page example for non-Google consumers.
• 12:39
  SPEAKER_00: This is a semantic description, not a promise of a Google search feature.
• 12:44
  SPEAKER_00: Organization.
• 12:45
  SPEAKER_00: What it does.
• 12:46
  SPEAKER_00: Organization helps Google understand and disambiguate a company, nonprofit, publisher, school, or other organization.
• 12:54
  SPEAKER_00: Google says organization markup can influence visual elements such as the logo shown in search and some knowledge panel information.
• 13:01
  SPEAKER_00: There are no required properties in Google's current organization guide.
• 13:06
  SPEAKER_00: Recommended properties.
• 13:07
  SPEAKER_00: Use the properties that are true and visible.
• 13:09
  SPEAKER_00: Name, alternate name, URL, logo, same as description, telephone, email address identifier, founding date, parent organization.
• 13:18
  SPEAKER_00: Artificial intelligence effect.
• 13:20
  SPEAKER_00: Evidence level indirect but useful.
• 13:22
  SPEAKER_00: Organization can connect the publisher to an article, the company to its products or services, the brand to its official profiles, the organization to a known web identity.
• 13:32
  SPEAKER_00: This is useful for entity disambiguation.
• 13:34
  SPEAKER_00: It does not prove that an artificial intelligence system will cite the page.
• 13:40
  SPEAKER_00: Place the full organization object on the homepage or organization page.
• 13:44
  SPEAKER_00: Use a stable at ID such as use the exact public organization name.
• 13:49
  SPEAKER_00: Link to real official profiles with same as.author, QA page, question or answer author, profile page, main entity organization.employee, review.author.
• 14:24
  SPEAKER_00: Google's Profile Guidance says a profile page must focus on one person or organization.
• 14:30
  SPEAKER_00: The profile page object requires a main entity and that entity must be a person or organization.
• 14:35
  SPEAKER_00: The person or organization must have a name or an alternate name when no name is available.
• 14:40
  SPEAKER_00: Recommended properties, name URL, same as, image, description, job title, works for, knows about, affiliation identifier, artificial intelligence effect, evidence level, indirect.
• 14:52
  SPEAKER_00: Person markup can help connect an author's name to a biography, a job or role, an organization, published articles, external profiles, areas of expertise.
• 15:01
  SPEAKER_00: Use it to make identity clear, not to claim expertise that the page does not support.
• 15:06
  SPEAKER_00: Person checklist.
• 15:07
  SPEAKER_00: Use person only for a real person.
• 15:10
  SPEAKER_00: Use organization for a company or publication.
• 15:12
  SPEAKER_00: Link the person to a visible author page.
• 15:15
  SPEAKER_00: Use same as only for accurate official profiles.
• 15:19
  SPEAKER_00: Keep job titles and credentials current.
• 15:21
  SPEAKER_00: Add all visible authors, not just the lead author.
• 15:24
  SPEAKER_00: Use the same person ad ID across articles and profile pages.
• 15:28
  SPEAKER_00: Required property matrix.
• 15:30
  SPEAKER_00: For the full table, please open this article on autopod.co.
• 15:34
  SPEAKER_00: Google's general guidance favors complete and accurate data over large amounts of incomplete markup.
• 15:40
  SPEAKER_00: It also warns that structured data must represent visible content, and that correct markup still does not guarantee a rich result.
• 15:47
  SPEAKER_00: Use case implementation checklists.
• 15:49
  SPEAKER_00: Facts pages.
• 15:50
  SPEAKER_00: Best combination.
• 15:51
  SPEAKER_00: Web page, article, or news article, person, organization, optional.
• 15:55
  SPEAKER_00: Claim review only for another supported consumer.
• 15:58
  SPEAKER_00: Checklist.
• 15:59
  SPEAKER_00: State the main fact near the top of the page.
• 16:01
  SPEAKER_00: Name the source of the fact.
• 16:03
  SPEAKER_00: Link to primary evidence.
• 16:05
  SPEAKER_00: Include the date of publication and last review.
• 16:08
  SPEAKER_00: Identify the author and reviewer.
• 16:10
  SPEAKER_00: Separate facts from opinion.
• 16:12
  SPEAKER_00: Use article when the page is editorial.
• 16:14
  SPEAKER_00: Do not use claim review as a current Google search tactic.
• 16:18
  SPEAKER_00: Definition pages.
• 16:19
  SPEAKER_00: Best combination.
• 16:20
  SPEAKER_00: Web page defined term.
• 16:22
  SPEAKER_00: Optional article if the page is a long editorial explanation.
• 16:25
  SPEAKER_00: Organization or person when an expert or publisher is responsible.
• 16:29
  SPEAKER_00: Define term is intended for a word, phrase, code, or concept with a formal definition.
• 16:34
  SPEAKER_00: Its main properties include name, description, term code, indefined term set, and same as.
• 16:40
  SPEAKER_00: Checklist.
• 16:40
  SPEAKER_00: Give the definition in the first paragraph.
• 16:43
  SPEAKER_00: Use one clear term as the main entity.
• 16:45
  SPEAKER_00: Add alternate names only when they are real.
• 16:48
  SPEAKER_00: Link to a reliable external definition when appropriate.
• 16:51
  SPEAKER_00: Explain the term in plain language.
• 16:53
  SPEAKER_00: Avoid marking the list of unrelated terms as one defined term.
• 16:58
  SPEAKER_00: Tutorial's best combination.
• 17:00
  SPEAKER_00: Web page how to only when another consumer needs it.
• 17:04
  SPEAKER_00: Article when the tutorial is also an editorial article.
• 17:08
  SPEAKER_00: Person and organization for authorship.
• 17:10
  SPEAKER_00: Checklist.
• 17:11
  SPEAKER_00: State the result before the steps.
• 17:13
  SPEAKER_00: Use numbered visible headings.
• 17:15
  SPEAKER_00: Keep each step focused on one action.
• 17:18
  SPEAKER_00: Include tools, supplies, time, and warnings where needed.
• 17:22
  SPEAKER_00: Add images or video when they help.
• 17:25
  SPEAKER_00: Do not hide the steps only in JSON LD.
• 17:28
  SPEAKER_00: Do not expect how-to rich results in Google search.
• 17:32
  SPEAKER_00: Data catalogs best combination.
• 17:38
  SPEAKER_00: Organization schema.org defines dataset as a body of structured information and supports relationships such as included in data catalog and distribution.
• 17:47
  SPEAKER_00: Google clarified in late 2025 that dataset structured data is used by dataset search and is not a general Google search result feature.
• 17:56
  SPEAKER_00: It should therefore be treated as a data discovery and interoperability layer, not an artificial intelligence citation shortcut.
• 18:03
  SPEAKER_00: Checklist.
• 18:04
  SPEAKER_00: Give each dataset a stable identifier.
• 18:07
  SPEAKER_00: State the subject and scope.
• 18:09
  SPEAKER_00: Include the publisher or creator.
• 18:11
  SPEAKER_00: Add the date range covered by the data.
• 18:13
  SPEAKER_00: State geographic coverage when relevant.
• 18:16
  SPEAKER_00: Describe licenses and access conditions.
• 18:18
  SPEAKER_00: Add each downloadable file as a data download.
• 18:21
  SPEAKER_00: Include file format and download URL.
• 18:24
  SPEAKER_00: Keep catalog metadata synchronized with the actual files.
• 18:28
  SPEAKER_00: Document update frequency and last update date.
• 18:31
  SPEAKER_00: JSON LD example, fax page.
• 18:34
  SPEAKER_00: This example connects the page, article, author, publisher, and topic.
• 18:38
  SPEAKER_00: Replace every value with information that appears on the real page.
• 18:42
  SPEAKER_00: JSON LD example, definition page.
• 18:45
  SPEAKER_00: The definition mud also appears as normal page text.
• 18:48
  SPEAKER_00: Do not place the definition only in the structured data.
• 18:51
  SPEAKER_00: JSON LD example, tutorial.
• 18:54
  SPEAKER_00: Because Google's how-to-rich result is deprecated, treat this as optional markup for other systems.
• 18:59
  SPEAKER_00: The visible page should still contain the full instructions.
• 19:03
  SPEAKER_00: JSON LD example, data catalog, common implementation pitfalls, mismatch schema.
• 19:09
  SPEAKER_00: The most serious mistake is marking up content that users cannot see.
• 19:13
  SPEAKER_00: Google says structured data must be a true representation of the page, and misleading or hidden content can make a page ineligible for rich results.
• 19:21
  SPEAKER_00: Common examples.
• 19:22
  SPEAKER_00: Marking an article as a how-to when it contains no real steps.
• 19:26
  SPEAKER_00: Marking a company as an author when the article was written by a person, adding FAQ answers that do not appear on the page.
• 19:32
  SPEAKER_00: Using a future publication date.
• 19:34
  SPEAKER_00: Marking a general blog post as QA page.
• 19:37
  SPEAKER_00: Adding claim review to an opinion article.
• 19:39
  SPEAKER_00: Thin answers, structured data cannot fill an empty page, a short vague answer inside answer.txt or accepted answer does not create a strong source.
• 19:49
  SPEAKER_00: The visible content should answer the question directly, explain important limits and exceptions, name sources, include dates, examples, or measurements where useful, stand on its own when copied out of context.
• 20:03
  SPEAKER_00: Google's artificial intelligence guidance says there is no ideal page length and no need to break content into tiny pieces for artificial intelligence systems.
• 20:12
  SPEAKER_00: The better goal is useful, complete, people first content.
• 20:16
  SPEAKER_00: Duplicate entities.
• 20:18
  SPEAKER_00: Avoid publishing several conflicting versions of the same organization, author, or page.
• 20:24
  SPEAKER_00: Weak implementation.
• 20:25
  SPEAKER_00: One organization object with one name on the home page.
• 20:29
  SPEAKER_00: A second object with a different name on every article.
• 20:32
  SPEAKER_00: A third object with no add ID on the author page.
• 20:35
  SPEAKER_00: Better implementation.
• 20:36
  SPEAKER_00: Give the organization one stable add ID.
• 20:39
  SPEAKER_00: Give each author one stable add ID.
• 20:42
  SPEAKER_00: Reference those objects from articles, profiles, and question pages.
• 20:45
  SPEAKER_00: Keep the name, logo, URL, and external identity links consistent.
• 20:50
  SPEAKER_00: Duplicate questions.
• 20:51
  SPEAKER_00: Do not repeat the same question in FAQ page, QA page, article markup, several visible page sections, multiple JSON LD blocks.
• 21:00
  SPEAKER_00: Use the schema type that matches the page's main purpose.
• 21:04
  SPEAKER_00: A single clear answer is better than several overlapping markup blocks.
• 21:08
  SPEAKER_00: Incorrect dates.
• 21:09
  SPEAKER_00: Google uses several sources to estimate publication and update dates.
• 21:13
  SPEAKER_00: It recommends that visible dates and structured dates agree, and it warns against using future dates or dates related to events discussed in the article, rather than dates related to the page itself.
• 21:24
  SPEAKER_00: Overusing Same As.
• 21:26
  SPEAKER_00: A SAME as link should identify the same real world person or organization.
• 21:30
  SPEAKER_00: Do not link to an unrelated social profile, a search results page, a generic directory listing, a page with a different spelling or identity, a profile that the organization does not control.
• 21:42
  SPEAKER_00: JavaScript only markup.
• 21:44
  SPEAKER_00: Google can process structured data added to the rendered page, but a JavaScript only implementation can be harder for other crawlers and auditing tools to detect.
• 21:52
  SPEAKER_00: A server-rendered JSON LD block is usually easier to test and maintain.
• 21:57
  SPEAKER_00: A practical testing plan.
• 21:59
  SPEAKER_00: To measure whether markup has an incremental effect, use a controlled test instead of relying on a few manual searches.
• 22:06
  SPEAKER_00: Before the change, record target queries, current organic ranking, whether an artificial intelligence answer appears, which pages are cited, citation position when available, search traffic, conversions, current structured data, content changes made during the test period.
• 22:21
  SPEAKER_00: During the test, add one major markup change at a time.
• 22:25
  SPEAKER_00: Keep content internal links, titles, and backlinks stable.
• 22:28
  SPEAKER_00: Use similar control pages that do not receive the change.
• 22:31
  SPEAKER_00: Record the exact publication date of the change.
• 22:34
  SPEAKER_00: Wait long enough for crawling and reprocessing.
• 22:37
  SPEAKER_00: HREFs used matched controls and a before and after difference and differences method.
• 22:42
  SPEAKER_00: Its approach is a useful model for organizations that want to test structured data instead of assuming that a correlation proves causation.
• 22:50
  SPEAKER_00: After the change track.
• 22:51
  SPEAKER_00: Google Search Console Artificial Intelligence Performance Data, Google AI Overview Citations, Google AI Mode Citations, Bing Webmaster Tools Artificial Intelligence Citations, Chat GPT, Gemini, or Perplexity Citations when relevant, organic rankings, search clicks, assisted conversions.
• 23:11
  SPEAKER_00: Google Reports Artificial Intelligence Search Traffic through Search Console Performance Reporting.
• 23:16
  SPEAKER_00: Bing's Artificial Intelligence Performance Reporting shows cited pages and grounding queries, but it does not show why a page was selected or how important it was within an answer.
• 23:26
  SPEAKER_00: Recommended implementation order.
• 23:28
  SPEAKER_00: For most publishers, the best order is fix visible content first.
• 23:32
  SPEAKER_00: Make crawling and indexing reliable.
• 23:34
  SPEAKER_00: Implement article for real editorial pages.
• 23:37
  SPEAKER_00: Connect authors with person and profile pages.
• 23:40
  SPEAKER_00: Connect publishers with organization.
• 23:42
  SPEAKER_00: Use web page as a clean page level graph layer.
• 23:45
  SPEAKER_00: Use QA page only for genuine community questions.
• 23:49
  SPEAKER_00: Use Define Term for glossary and definition pages.
• 23:52
  SPEAKER_00: Use dataset and data catalog for data resources.
• 23:55
  SPEAKER_00: Treat FAQ page, how-to, and claim review as secondary or non-Google markup because their Google search features have been removed or deprecated.
• 24:04
  SPEAKER_00: Conclusion.
• 24:05
  SPEAKER_00: The strongest current lesson is simple.
• 24:08
  SPEAKER_00: Schema.org markup helps machines understand content, but it is not a guaranteed path into artificial intelligence answers.
• 24:15
  SPEAKER_00: The most durable implementation is not a large collection of schema types.
• 24:19
  SPEAKER_00: It is a small, accurate entity graph.
• 24:21
  SPEAKER_00: Article describes the editorial page.
• 24:24
  SPEAKER_00: Person identifies the author.
• 24:28
  SPEAKER_00: Web page connects the page to its main entity.
• 24:30
  SPEAKER_00: QA page describes a genuine user question in its answers.
• 24:34
  SPEAKER_00: Define term clarifies a definition.
• 24:36
  SPEAKER_00: Data set and data catalog describe structured data resources.
• 24:40
  SPEAKER_00: Use structured data where it adds clear meaning.
• 24:42
  SPEAKER_00: Do not use it to disguise thin content, duplicate visible text, or imitate a search feature that Google no longer supports.
• 24:49
  SPEAKER_00: For artificial intelligence surfacing, the highest value work remains clear answers, strong evidence, accurate entities, current information, and content that can stand on its own.
• 24:59
  SPEAKER_00: All links to sources are available in the text version of this article.
• 25:03
  SPEAKER_00: You can find the full article at autopod.co.