@qobi/seocode 0.1.0

package/rules/seo-rules.json

@@ -0,0 +1,3414 @@
+{
+  "version": "1.4.5",
+  "updatedAt": "2026-09-04",
+  "changeLog": [
+    {
+      "date": "2026-09-04",
+      "version": "1.4.5",
+      "source": "Google AI Optimization Guide — https://developers.google.com/search/docs/fundamentals/ai-optimization-guide (scraped 2026-09-04) and Google AI Features in Search — https://developers.google.com/search/docs/appearance/ai-features (scraped 2026-09-04) and Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-09-04) and Google Structured Data Search Gallery — https://developers.google.com/search/docs/appearance/structured-data/search-gallery (scraped 2026-09-04)",
+      "changes": [
+        "Added rule: european-search-dataset-licensing — Google has refreshed the European Search Dataset Licensing Program page with updated eligibility criteria and application details; relevant for publishers in the EU seeking to license their content to Google Search",
+        "Confirmed rule: favicon-aspect-ratio — changelog confirms favicon documentation updated to explicitly list supported file formats; no change to requirements; already reflected in existing rule (lastUpdated 2026-08-29)",
+        "Confirmed rule: site-reputation-policy-eea — changelog confirms site reputation policy adjusted for EEA; already reflected in existing rule (lastUpdated 2026-08-29)",
+        "Confirmed rule: preferred-sources-feature — changelog confirms new custom interactive button for preferred sources; already reflected in existing rule (lastUpdated 2026-08-29)",
+        "Confirmed rule: social-video-platform-search-console — already reflected",
+        "Confirmed rule: fake-incentivized-reviews-policy — already reflected",
+        "Confirmed rule: package-tracking-early-adopters-closed — already reflected",
+        "Confirmed rule: canonicalization-reevaluation-time — already reflected",
+        "Confirmed rule: product-category-schema — already reflected",
+        "Confirmed rule: sale-price-effective-date-schema — already reflected",
+        "Confirmed rule: amp-direct-publisher-hosting — already reflected",
+        "Confirmed rule: site-move-domain-variants — already reflected",
+        "Confirmed rule: llms-txt-not-required — confirmed again in current AI optimization guide scrape; already reflected",
+        "Confirmed rule: faq-rich-result-documentation-removed — already reflected",
+        "Confirmed rule: tennessee-small-business-search-notifications — already reflected",
+        "Confirmed rule: third-party-seo-tools-guidance — already reflected",
+        "Confirmed rule: preferred-sources-ai-mode — already reflected",
+        "Confirmed rule: has-adult-consideration-schema — already reflected",
+        "Confirmed rule: generative-ai-optimization — confirmed again in current AI optimization guide scrape; content matches existing rule description; no new actionable guidance beyond what is already reflected",
+        "Confirmed rule: spam-policies-apply-to-ai-responses — confirmed again; already reflected",
+        "Confirmed rule: faq-schema-deprecated — Search Gallery does not list FAQPage; already reflected",
+        "Confirmed rule: speakable-schema-deprecated — Search Gallery lists Speakable under legacy entry; Google no longer supports it as a rich result type; already reflected",
+        "Confirmed rule: ai-features-snippet-eligibility — confirmed again in current AI features guide scrape; already reflected",
+        "Confirmed rule: agent-friendly-website — confirmed again in current AI optimization guide scrape; already reflected",
+        "Confirmed rule: back-button-hijacking — already reflected",
+        "Confirmed rule: robots-meta-outside-head — already reflected",
+        "Confirmed rule: noindex-javascript-accessibility-outdated — already reflected",
+        "Confirmed rule: crawling-docs-migrated — already reflected",
+        "Confirmed rule: spam-reports-manual-action — already reflected",
+        "Confirmed rule: read-more-deeplink — already reflected",
+        "Confirmed rule: image-preferred-source-metadata — already reflected",
+        "Confirmed rule: breadcrumbs-desktop-only — Search Gallery confirms breadcrumbs; already reflected",
+        "Confirmed rule: video-transparency — already reflected",
+        "Confirmed rule: structured-data-javascript-initial-html — already reflected",
+        "Confirmed rule: mobile-version-links — already reflected",
+        "Confirmed rule: review-snippet-requires-comment — already reflected",
+        "Confirmed rule: practice-problem-schema-deprecated — Search Gallery does not list PracticeProblem; already reflected",
+        "Confirmed rule: special-announcement-schema-deprecated — Search Gallery does not list SpecialAnnouncement; already reflected",
+        "Confirmed rule: missing-hreflang — already reflected",
+        "Confirmed rule: hreflang-no-combined-attributes — already reflected",
+        "Confirmed rule: robots-txt-unsupported-fields — already reflected",
+        "Confirmed rule: merchant-shipping-policy-schema — already reflected",
+        "Confirmed rule: video-indexing-criteria — Search Gallery confirms Video; already reflected",
+        "Confirmed rule: explicit-content-video-crawlable — already reflected",
+        "Confirmed rule: indexing-api-spam-detection — already reflected",
+        "Confirmed rule: avif-image-format-supported — already reflected",
+        "Confirmed rule: c2pa-metadata — already reflected",
+        "Confirmed rule: ai-mode-search-console — already reflected",
+        "Confirmed rule: loyalty-program-schema — Search Gallery confirms merchant listings; already reflected",
+        "Confirmed rule: merchant-return-policy-schema — Search Gallery confirms merchant listings; already reflected",
+        "Confirmed rule: product-structured-data-single-product — Search Gallery confirms Product; already reflected",
+        "Confirmed rule: url-parameters-best-practice — already reflected",
+        "Confirmed rule: safe-search-explicit-tagging — already reflected",
+        "Confirmed rule: organization-markup — Search Gallery confirms Organization; already reflected",
+        "Confirmed rule: site-name-schema — already reflected",
+        "Confirmed rule: event-structured-data-requirements — Search Gallery confirms Event; already reflected",
+        "Confirmed rule: dataset-schema-phased-out — Search Gallery lists Dataset under Google Dataset Search only; already reflected",
+        "Confirmed rule: sitelinks-searchbox-removed — Search Gallery does not list SearchAction/sitelinks searchbox; already reflected",
+        "Confirmed rule: core-updates-continuous — already reflected",
+        "Confirmed rule: googlebot-file-size-limits — already reflected",
+        "Confirmed rule: recipe-thumbnail-property — Search Gallery confirms Recipe; already reflected",
+        "Confirmed rule: south-africa-carousel-structured-data — already reflected",
+        "Confirmed rule: turkey-carousel-structured-data — already reflected",
+        "Confirmed rule: noindex-in-javascript — already reflected",
+        "Confirmed rule: canonical-javascript-best-practice — already reflected",
+        "Confirmed rule: javascript-non-200-rendering — already reflected",
+        "Confirmed rule: javascript-paywall-detection — already reflected",
+        "Confirmed rule: follow-feature-removed — already reflected",
+        "Confirmed rule: schema-org-shipping-vocabulary-updated — already reflected",
+        "Confirmed rule: schema-org-iptc-digital-source-type — already reflected",
+        "Confirmed rule: schema-org-v30-equivalence-annotations — already reflected",
+        "Confirmed rule: schema-org-v30-eu-digital-product-passport — already reflected",
+        "Confirmed rule: schema-org-v29-financial-incentives — already reflected",
+        "Confirmed rule: http-query-method-google-search — already reflected",
+        "Confirmed rule: google-august-2026-spam-update — already reflected",
+        "Confirmed rule: bing-ai-performance-citation-eligibility — already reflected",
+        "No actionable new rules extracted from Google Search Central Blog — page returned only a navigation/feedback shell with no article content",
+        "No actionable new rules extracted from Google Structured Data Search Gallery beyond confirming existing rules — gallery confirms all currently supported rich result types with no new types or requirements not already reflected in existing rules; Vacation Rental and Movie structured data types confirmed present in gallery but no existing rules cover them as they were not previously flagged as requiring rules; adding vacation-rental-schema and movie-schema as new info rules to document their availability"
+      ]
+    },
+    {
+      "date": "2026-08-29",
+      "version": "1.4.4",
+      "source": "Google AI Optimization Guide — https://developers.google.com/search/docs/fundamentals/ai-optimization-guide (scraped 2026-08-29) and Google AI Features in Search — https://developers.google.com/search/docs/appearance/ai-features (scraped 2026-08-29) and Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-08-29) and Google Structured Data Search Gallery — https://developers.google.com/search/docs/appearance/structured-data/search-gallery (scraped 2026-08-29)",
+      "changes": [
+        "Updated rule: favicon-aspect-ratio — changelog entry confirms supported favicon file formats are now explicitly listed in the favicon documentation; no change to requirements but documentation now lists formats explicitly rather than linking to external reference",
+        "Updated rule: preferred-sources-feature — changelog entry confirms new custom interactive button available for preferred sources; site owners can now implement a custom interactive button to guide their audience to set them as a preferred source",
+        "Updated rule: site-reputation-policy-eea — NEW RULE: Google has adjusted enforcement approach for the site reputation abuse policy within the European Economic Area (EEA)",
+        "Confirmed rule: social-video-platform-search-console — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: fake-incentivized-reviews-policy — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: package-tracking-early-adopters-closed — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: canonicalization-reevaluation-time — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: product-category-schema — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: sale-price-effective-date-schema — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: amp-direct-publisher-hosting — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: site-move-domain-variants — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: llms-txt-not-required — confirmed again in current changelog scrape and AI optimization guide; already reflected",
+        "Confirmed rule: faq-rich-result-documentation-removed — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: tennessee-small-business-search-notifications — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: third-party-seo-tools-guidance — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: preferred-sources-ai-mode — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: has-adult-consideration-schema — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: generative-ai-optimization — confirmed again in current AI optimization guide scrape; already reflected",
+        "Confirmed rule: spam-policies-apply-to-ai-responses — confirmed again; already reflected",
+        "Confirmed rule: faq-schema-deprecated — confirmed again; Search Gallery does not list FAQPage; already reflected",
+        "Confirmed rule: speakable-schema-deprecated — Search Gallery lists Speakable under legacy entry but Google no longer supports it as a rich result type; already reflected",
+        "Confirmed rule: ai-features-snippet-eligibility — confirmed again in current AI features guide scrape; already reflected",
+        "Confirmed rule: agent-friendly-website — confirmed again in current AI optimization guide scrape; already reflected",
+        "Confirmed rule: back-button-hijacking — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: robots-meta-outside-head — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: noindex-javascript-accessibility-outdated — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: crawling-docs-migrated — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: spam-reports-manual-action — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: read-more-deeplink — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: image-preferred-source-metadata — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: breadcrumbs-desktop-only — confirmed again; Search Gallery confirms breadcrumbs; already reflected",
+        "Confirmed rule: video-transparency — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: structured-data-javascript-initial-html — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: mobile-version-links — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: review-snippet-requires-comment — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: practice-problem-schema-deprecated — confirmed again; Search Gallery does not list PracticeProblem; already reflected",
+        "Confirmed rule: special-announcement-schema-deprecated — confirmed again; Search Gallery does not list SpecialAnnouncement; already reflected",
+        "Confirmed rule: missing-hreflang — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: hreflang-no-combined-attributes — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: robots-txt-unsupported-fields — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: merchant-shipping-policy-schema — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: video-indexing-criteria — confirmed again; Search Gallery confirms Video; already reflected",
+        "Confirmed rule: explicit-content-video-crawlable — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: indexing-api-spam-detection — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: avif-image-format-supported — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: c2pa-metadata — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: ai-mode-search-console — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: loyalty-program-schema — confirmed again; Search Gallery confirms merchant listings; already reflected",
+        "Confirmed rule: merchant-return-policy-schema — confirmed again; Search Gallery confirms merchant listings; already reflected",
+        "Confirmed rule: product-structured-data-single-product — confirmed again; Search Gallery confirms Product; already reflected",
+        "Confirmed rule: url-parameters-best-practice — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: safe-search-explicit-tagging — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: organization-markup — confirmed again; Search Gallery confirms Organization; already reflected",
+        "Confirmed rule: site-name-schema — confirmed again; Search Gallery confirms WebSite/site name context; already reflected",
+        "Confirmed rule: event-structured-data-requirements — confirmed again; Search Gallery confirms Event; already reflected",
+        "Confirmed rule: dataset-schema-phased-out — confirmed again; Search Gallery lists Dataset under Google Dataset Search only; already reflected",
+        "Confirmed rule: sitelinks-searchbox-removed — confirmed again; Search Gallery does not list SearchAction/sitelinks searchbox; already reflected",
+        "Confirmed rule: core-updates-continuous — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: googlebot-file-size-limits — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: recipe-thumbnail-property — confirmed again; Search Gallery confirms Recipe; already reflected",
+        "Confirmed rule: south-africa-carousel-structured-data — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: turkey-carousel-structured-data — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: noindex-in-javascript — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: canonical-javascript-best-practice — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: javascript-non-200-rendering — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: javascript-paywall-detection — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: follow-feature-removed — confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: schema-org-shipping-vocabulary-updated — confirmed again; already reflected",
+        "Confirmed rule: schema-org-iptc-digital-source-type — confirmed again; already reflected",
+        "Confirmed rule: schema-org-v30-equivalence-annotations — confirmed again; already reflected",
+        "Confirmed rule: schema-org-v30-eu-digital-product-passport — confirmed again; already reflected",
+        "Confirmed rule: schema-org-v29-financial-incentives — confirmed again; already reflected",
+        "Confirmed rule: http-query-method-google-search — confirmed again; already reflected",
+        "Confirmed rule: google-august-2026-spam-update — confirmed again; already reflected",
+        "Confirmed rule: bing-ai-performance-citation-eligibility — confirmed again; already reflected",
+        "No actionable new rules extracted from Google Search Central Blog — page returned only a navigation/feedback shell with no article content",
+        "No actionable new rules extracted from Google Structured Data Search Gallery beyond confirming existing rules — gallery confirms all currently supported rich result types with no new types or requirements not already reflected in existing rules"
+      ]
+    },
+    {
+      "date": "2026-08-20",
+      "version": "1.4.3",
+      "source": "Schema.org Release Notes — https://schema.org/docs/releases.html (scraped 2026-08-20) and Search Engine Land — https://searchengineland.com/library/seo (scraped 2026-08-20) and Search Engine Roundtable — https://www.seroundtable.com (scraped 2026-08-20) and Search Engine Journal — https://www.searchenginejournal.com/category/technical-seo/ (scraped 2026-08-20)",
+      "changes": [
+        "Added rule: schema-org-v30-equivalence-annotations — schema.org version 30.0 added GS1, Dublin Core, and Open Graph equivalence annotations and exports; EU Digital Product Passport examples aligned with UN/CEFACT codes; new CompoundPriceSpecification changes and credential vocabulary extensions",
+        "Added rule: schema-org-v30-eu-digital-product-passport — schema.org version 30.0 added EU Digital Product Passport (DPP) examples aligned with UN/CEFACT codes; relevant for ecommerce and product pages targeting EU markets",
+        "Added rule: schema-org-v29-financial-incentives — schema.org version 29.0 added vocabulary to represent financial incentives including sustainability incentives; new types and properties for use on Offer",
+        "Confirmed rule: schema-org-shipping-vocabulary-updated — schema.org version 29.0 deprecation of DeliveryTimeSettings and ShippingRateSettings confirmed again in current release notes scrape; already reflected",
+        "Confirmed rule: schema-org-iptc-digital-source-type — schema.org version 29.4 added missing enumeration values to IPTCDigitalSourceEnumeration confirmed again; already reflected",
+        "Confirmed rule: c2pa-metadata — schema.org version 28.1 IPTC values confirmed again; already reflected",
+        "Confirmed rule: loyalty-program-schema — schema.org version 28.0 MemberProgram/MemberProgramTier confirmed again; already reflected",
+        "Confirmed rule: has-adult-consideration-schema — schema.org version 14.0 hasAdultConsideration on MerchantReturnPolicy confirmed again; already reflected",
+        "Confirmed rule: merchant-return-policy-schema — schema.org version 13.0 and 14.0 MerchantReturnPolicy vocabulary confirmed again; already reflected",
+        "Confirmed rule: speakable-schema-deprecated — SpeakableSpecification introduced in schema.org 3.2, moved to core in 3.5, confirmed again; Google no longer supports it; already reflected",
+        "Confirmed rule: faq-schema-deprecated — FAQPage introduced in schema.org 3.4 confirmed again; already reflected",
+        "Confirmed rule: google-august-2026-spam-update — Google August 2026 Spam Update confirmed again in Search Engine Land and Search Engine Roundtable headlines; already reflected",
+        "No actionable new rules extracted from Search Engine Journal — page returned only navigation/category shell text with no article content",
+        "No actionable new rules extracted from Search Engine Roundtable beyond already-reflected items — headlines covering ChatGPT Ads expansion, Google update announcement timing, Google Search video carousel frequency, Google Ads bidding for loyalty members, Google Business Profiles Q&A, Google Trends maps, Google Analytics outage, Google Search HTTP QUERY method, and Bing related searches contain no distinct technical SEO implementation requirements not already reflected in existing rules; the Google Search HTTP QUERY method item is noted below as a new rule",
+        "Added rule: http-query-method-google-search — Google Search will eventually support the HTTP QUERY method for search interactions; no immediate implementation required but site owners should be aware of this emerging standard"
+      ]
+    },
+    {
+      "date": "2026-08-20",
+      "version": "1.4.2",
+      "source": "Bing Webmaster Blog — https://blogs.bing.com/webmaster (scraped 2026-08-20) and Lumar Blog — https://www.lumar.io/blog (scraped 2026-08-20) and W3C Blog — https://www.w3.org/blog/news/ (scraped 2026-08-20)",
+      "changes": [
+        "Confirmed rule: bing-ai-performance-citation-eligibility — Bing AI Performance public preview confirmed again in current Bing Webmaster Blog scrape; Copilot in Bing Webmaster Tools now generally available to all users; no new distinct technical SEO implementation requirements beyond what is already reflected in existing rule",
+        "No actionable new rules extracted from Lumar Blog — page returned only a category/navigation shell with no article content",
+        "No actionable new rules extracted from W3C Blog — page returned only a pagination shell ('This is page 1, displaying results 1-10') with no article content",
+        "No new, updated, or deprecated rules warranted — all content either confirms existing rules or contains no actionable technical SEO implementation requirements"
+      ]
+    },
+    {
+      "date": "2026-08-20",
+      "version": "1.4.1",
+      "source": "Google AI Optimization Guide — https://developers.google.com/search/docs/fundamentals/ai-optimization-guide (scraped 2026-08-20) and Google AI Features in Search — https://developers.google.com/search/docs/appearance/ai-features (scraped 2026-08-20) and Moz Blog — https://moz.com/blog (scraped 2026-08-20)",
+      "changes": [
+        "Updated rule: generative-ai-optimization — added new guidance on Generative AI performance report in Search Console for measuring AI feature visibility; added clarification that a site must be included in Search generative AI features in Search Console to be eligible for display; added explicit guidance on semantic HTML (not required to be perfect but good practice for human readability and screen readers); added explicit guidance on good page experience (displays well across devices, reduces latency, distinguishes main content); added guidance on local business and ecommerce details via Merchant Center feeds and Google Business Profiles; confirmed all existing myth-busting guidance; no structural rule changes",
+        "Updated rule: ai-features-snippet-eligibility — added new requirement: in addition to being indexed and snippet-eligible, a site must be included in Search generative AI features in Search Console to be eligible for display in generative AI features; added troubleshooting guidance on preview controls and recrawl timing",
+        "Confirmed rule: llms-txt-not-required — confirmed again in current article scrape; already reflected",
+        "Confirmed rule: agent-friendly-website — confirmed again in current article scrape; already reflected",
+        "Confirmed rule: spam-policies-apply-to-ai-responses — confirmed again in current article scrape; already reflected",
+        "Confirmed rule: ai-mode-search-console — confirmed again; AI Overviews and AI Mode traffic included in Search Console totals confirmed; already reflected",
+        "No actionable new rules extracted from Moz Blog — page returned only a single article teaser about LLM review sentiment with no distinct technical SEO implementation requirements not already reflected in existing rules"
+      ]
+    },
+    {
+      "date": "2026-08-20",
+      "version": "1.4.0",
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-08-20, last updated 2026-07-29 UTC) and Search Engine Roundtable — https://www.seroundtable.com (scraped 2026-08-20)",
+      "changes": [
+        "Added rule: social-video-platform-search-console — Google has added a new guide on analyzing social and video platform content performance in Search Console",
+        "Added rule: fake-incentivized-reviews-policy — Google has added a new guideline to review snippet documentation about fake and undisclosed incentivized reviews",
+        "Added rule: package-tracking-early-adopters-closed — Google's package tracking early adopters program is no longer accepting new partners",
+        "Added rule: canonicalization-reevaluation-time — Google has updated the canonicalization troubleshooting guide with clarifications on re-evaluation time",
+        "Added rule: product-category-schema — Google has updated product structured data documentation to detail how the google_product_category property can be used with both Product and Offer types",
+        "Added rule: sale-price-effective-date-schema — Google has added a new section on sale duration to the Merchant listing guide explaining how to use schema.org properties to set effective range for sale prices",
+        "Added rule: amp-direct-publisher-hosting — Google Search is updating how it connects users to AMP pages, now taking users directly to the publisher's AMP host pages; AMP Cache and signed exchanges no longer required",
+        "Added rule: google-august-2026-spam-update — Google has released an August 2026 spam update",
+        "Confirmed rule: site-move-domain-variants — site move guidance with domain variants confirmed again in current changelog scrape; already reflected",
+        "Confirmed rule: llms-txt-not-required — clarifying note on llms.txt files confirmed again; already reflected",
+        "Confirmed rule: faq-rich-result-documentation-removed — FAQ rich result documentation removal confirmed again; already reflected",
+        "Confirmed rule: tennessee-small-business-search-notifications — Tennessee small business notifications article confirmed again; already reflected",
+        "Confirmed rule: third-party-seo-tools-guidance — third-party SEO tools guidance confirmed again; already reflected",
+        "Confirmed rule: preferred-sources-ai-mode — preferred sources in AI Overviews and AI Mode confirmed again; already reflected",
+        "Confirmed rule: has-adult-consideration-schema — hasAdultConsideration property confirmed again; already reflected",
+        "Confirmed rule: generative-ai-optimization — AI optimization guide confirmed again; already reflected",
+        "Confirmed rule: spam-policies-apply-to-ai-responses — spam policies apply to AI responses confirmed again; already reflected",
+        "Confirmed rule: faq-schema-deprecated — FAQ rich result no longer shown confirmed again; already reflected",
+        "Confirmed rule: back-button-hijacking — back button hijacking spam policy confirmed again; already reflected",
+        "Confirmed rule: spam-reports-manual-action — spam reports manual action confirmed again; already reflected",
+        "No actionable new rules extracted from Search Engine Roundtable — headlines covering Google August 2026 Spam Update (captured as new rule), ChatGPT Ads expansion, Google Business Profiles Q&A feature, Google Trends maps, Google Analytics outage, Bing related searches UI, and Google AdSense payment changes contain no distinct technical SEO implementation requirements not already reflected in existing rules beyond the spam update announcement"
+      ]
+    },
+    {
+      "date": "2026-06-18",
+      "version": "1.3.7",
+      "source": "Google Structured Data Search Gallery — https://developers.google.com/search/docs/appearance/structured-data/search-gallery (scraped 2026-06-18) and Microsoft AI Blog — https://blogs.microsoft.com/ai/ (scraped 2026-06-18)",
+      "changes": [
+        "Confirmed rule: faq-schema-deprecated — FAQPage not listed in the current Search Gallery, confirming it is no longer a supported rich result type; already reflected",
+        "Confirmed rule: speakable-schema-deprecated — SpeakableSpecification listed in Search Gallery under 'Allow search engines and other applications to identify news content to read aloud on Google Assistant-enabled devices using text-to-speech (TTS)' — however this entry appears to be a legacy listing; Google has removed Speakable from supported rich result types; already reflected",
+        "Confirmed rule: practice-problem-schema-deprecated — practice problem structured data not listed in current Search Gallery, confirming it is no longer a supported rich result type; already reflected",
+        "Confirmed rule: special-announcement-schema-deprecated — SpecialAnnouncement not listed in current Search Gallery, confirming deprecation; already reflected",
+        "Confirmed rule: dataset-schema-phased-out — Dataset listed in Search Gallery under Education and Science as 'Large data sets that appear in Google Dataset Search' — note the description references Google Dataset Search specifically, not Google Search rich results, consistent with existing rule noting Dataset is being phased out from Google Search results but may still be used by Google Dataset Search; already reflected",
+        "Confirmed rule: sitelinks-searchbox-removed — SearchAction/sitelinks searchbox not listed in current Search Gallery, confirming removal; already reflected",
+        "Confirmed rule: event-structured-data-requirements — Event listed in Search Gallery as 'An interactive rich result that shows a list of organized events, such as concerts or art festivals, that people may attend at a particular time and place'; already reflected",
+        "Confirmed rule: video-indexing-criteria — Video listed in Search Gallery; already reflected",
+        "Confirmed rule: breadcrumbs-desktop-only — Breadcrumb listed in Search Gallery; already reflected",
+        "Confirmed rule: review-snippet-requires-comment — Review snippet listed in Search Gallery; already reflected",
+        "Confirmed rule: organization-markup — Organization listed in Search Gallery; already reflected",
+        "Confirmed rule: product-structured-data-single-product — Product listed in Search Gallery; already reflected",
+        "Confirmed rule: recipe-thumbnail-property — Recipe listed in Search Gallery; already reflected",
+        "Confirmed rule: merchant-shipping-policy-schema — Product/merchant listings listed in Search Gallery; already reflected",
+        "Confirmed rule: merchant-return-policy-schema — Product/merchant listings listed in Search Gallery; already reflected",
+        "Confirmed rule: loyalty-program-schema — Product/merchant listings listed in Search Gallery; already reflected",
+        "Confirmed rule: javascript-paywall-detection — Subscription and paywalled content listed in Search Gallery; already reflected",
+        "Confirmed rule: site-name-schema — WebSite/site name not explicitly listed but Organization and related markup confirmed; already reflected",
+        "Confirmed rule: missing-json-ld — structured data gallery confirms JSON-LD as the implementation path for all rich result types; already reflected",
+        "No actionable new rules extracted from Microsoft AI Blog — page returned only a single non-SEO article title ('Farming is risky business. This app helps Turkish growers succeed') with no technical SEO content",
+        "No new rules added — Search Gallery page confirms existing supported rich result types with no new types or requirements not already reflected in existing rules"
+      ]
+    },
+    {
+      "date": "2026-06-18",
+      "version": "1.3.6",
+      "source": "Search Engine Roundtable — https://www.seroundtable.com (scraped 2026-06-18) and Moz Blog — https://moz.com/blog (scraped 2026-06-18)",
+      "changes": [
+        "Confirmed rule: site-move-domain-variants — 'Google: For Site Moves, Add All Domain Variants To Change Of Address Tool' headline confirms existing rule; already reflected",
+        "Added rule: html-standard-for-seo — Google has stated that HTML is the standard for SEO, not Markdown files; this extends and reinforces the existing llms-txt-not-required rule with an explicit Google statement that Markdown files have no SEO advantage over HTML",
+        "No actionable new rules extracted from Moz Blog — page returned only a conference speaker announcement with no technical SEO content",
+        "No actionable new rules extracted from remaining Search Engine Roundtable headlines — items covering Google Ads interface changes, Bing country reporting, Google Business Profiles UI, Google Discover News Showcase, CMA regulatory news, and ranking volatility reports contain no distinct technical SEO implementation requirements not already reflected in existing rules"
+      ]
+    },
+    {
+      "date": "2026-06-18",
+      "version": "1.3.5",
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-06-18, last updated 2026-06-17 UTC)",
+      "changes": [
+        "Added rule: site-move-domain-variants — Google has updated site move guidance to include information on using the Change of Address tool for all subdomain variants (including www and non-www) during domain migrations",
+        "Added rule: faq-rich-result-documentation-removed — Google has removed the FAQ rich result documentation entirely, confirming the feature is no longer shown in Google Search results",
+        "Added rule: tennessee-small-business-search-notifications — Google has created a new article explaining how small business owners in Tennessee can receive notifications from Google Search when their web content is removed or restricted",
+        "Confirmed rule: llms-txt-not-required — changelog entry confirms Google added a clarifying note to the AI optimization guide about llms.txt files; already reflected",
+        "Confirmed rule: preferred-sources-ai-mode — preferred sources feature rolling out to AI Overviews and AI Mode confirmed again; already reflected",
+        "Confirmed rule: has-adult-consideration-schema — hasAdultConsideration property confirmed again; already reflected",
+        "Confirmed rule: generative-ai-optimization — new sections on non-commodity content, local/shopping/image/video content, AEO/GEO mythbusting, AI agents confirmed; already reflected",
+        "Confirmed rule: spam-policies-apply-to-ai-responses — spam policies apply to generative AI responses confirmed again; already reflected",
+        "Confirmed rule: faq-schema-deprecated — FAQ rich result feature no longer shown in Google Search confirmed; documentation now fully removed; already reflected",
+        "Confirmed rule: third-party-seo-tools-guidance — guidance on evaluating third-party SEO tools confirmed again; already reflected",
+        "Confirmed rule: spam-reports-manual-action — manual action based on spam reports confirmed again; already reflected",
+        "Confirmed rule: back-button-hijacking — back button hijacking spam policy confirmed again; already reflected",
+        "Confirmed rule: noindex-javascript-accessibility-outdated — outdated JavaScript accessibility section removal confirmed again; already reflected",
+        "Confirmed rule: preferred-sources-feature — preferred sources feature confirmed again; already reflected",
+        "Confirmed rule: read-more-deeplink — read more deep links confirmed again; already reflected",
+        "Confirmed rule: image-preferred-source-metadata — og:image and schema.org as thumbnail sources confirmed again; already reflected",
+        "Confirmed rule: robots-meta-outside-head — robots meta outside head behavior confirmed again; already reflected",
+        "Confirmed rule: noindex-in-javascript — noindex in JavaScript undefined behavior confirmed again; already reflected",
+        "Confirmed rule: canonical-javascript-best-practice — canonicalization best practices for JavaScript confirmed again; already reflected",
+        "Confirmed rule: core-updates-continuous — continuous core updates confirmed again; already reflected",
+        "Confirmed rule: crawling-docs-migrated — crawling documentation migration confirmed again; already reflected",
+        "Confirmed rule: follow-feature-removed — Follow feature no longer shown in Discover confirmed again; already reflected",
+        "Confirmed rule: review-no-multiple-reviewed-entities — avoiding multiple ways of indicating reviewed entity confirmed again; already reflected",
+        "Confirmed rule: merchant-shipping-policy-schema — merchant-level shipping policy markup confirmed again; already reflected",
+        "Confirmed rule: javascript-non-200-rendering — JavaScript execution on non-200 HTTP status codes confirmed again; already reflected",
+        "Confirmed rule: javascript-paywall-detection — JavaScript-based paywall considerations confirmed again; already reflected",
+        "Confirmed rule: south-africa-carousel-structured-data — South Africa carousel additional query types confirmed again; already reflected",
+        "Confirmed rule: turkey-carousel-structured-data — Turkey carousel expansion confirmed again; already reflected",
+        "Confirmed rule: image-url-consistency — consistent image URL references confirmed again; already reflected",
+        "Confirmed rule: sitelinks-searchbox-removed — sitelinks search box removal confirmed again; already reflected",
+        "Confirmed rule: practice-problem-schema-deprecated — practice problem structured data no longer shown confirmed again; already reflected",
+        "Confirmed rule: special-announcement-schema-deprecated — special announcement deprecated confirmed again; already reflected",
+        "Confirmed rule: dataset-schema-phased-out — dataset structured data phased out confirmed again; already reflected",
+        "Confirmed rule: hreflang-no-combined-attributes — hreflang combined attributes confirmed again; already reflected",
+        "Confirmed rule: merchant-return-policy-schema — merchant return policy confirmed again; already reflected",
+        "Confirmed rule: loyalty-program-schema — loyalty program markup confirmed again; already reflected",
+        "Confirmed rule: event-structured-data-requirements — event structured data requirements confirmed again; already reflected",
+        "Confirmed rule: recipe-thumbnail-property — recipe thumbnail property confirmed again; already reflected",
+        "Confirmed rule: safe-search-explicit-tagging — SafeSearch documentation confirmed again; already reflected",
+        "Confirmed rule: explicit-content-video-crawlable — explicit video crawlable confirmed again; already reflected",
+        "Confirmed rule: googlebot-file-size-limits — Googlebot file size limits confirmed again; already reflected",
+        "Confirmed rule: avif-image-format-supported — AVIF image format confirmed again; already reflected",
+        "Confirmed rule: c2pa-metadata — C2PA metadata confirmed again; already reflected",
+        "Confirmed rule: ai-mode-search-console — AI Mode Search Console confirmed again; already reflected",
+        "Confirmed rule: organization-markup — organization markup confirmed again; already reflected",
+        "Confirmed rule: site-name-schema — site name schema confirmed again; already reflected",
+        "Confirmed rule: breadcrumbs-desktop-only — breadcrumbs desktop only confirmed again; already reflected",
+        "Confirmed rule: review-snippet-requires-comment — review snippet requirements confirmed again; already reflected",
+        "Confirmed rule: structured-data-javascript-initial-html — structured data in initial HTML confirmed again; already reflected",
+        "Confirmed rule: mobile-version-links — mobile version links confirmed again; already reflected",
+        "Confirmed rule: video-indexing-criteria — video indexing criteria confirmed again; already reflected",
+        "Confirmed rule: video-transparency — video transparency confirmed again; already reflected",
+        "Confirmed rule: indexing-api-spam-detection — Indexing API spam detection confirmed again; already reflected",
+        "Confirmed rule: url-parameters-best-practice — URL parameters best practice confirmed again; already reflected",
+        "Confirmed rule: robots-txt-unsupported-fields — robots.txt unsupported fields confirmed again; already reflected",
+        "Confirmed rule: product-structured-data-single-product — product structured data single product confirmed again; already reflected",
+        "Confirmed rule: missing-hreflang — hreflang confirmed again; already reflected",
+        "Confirmed rule: schema-org-shipping-vocabulary-updated — shipping vocabulary deprecated types confirmed again; already reflected",
+        "Confirmed rule: speakable-schema-deprecated — SpeakableSpecification not supported confirmed again; already reflected",
+        "Confirmed rule: schema-org-iptc-digital-source-type — IPTCDigitalSourceEnumeration confirmed again; already reflected"
+      ]
+    },
+    {
+      "date": "2026-06-18",
+      "version": "1.3.4",
+      "source": "Search Engine Land — Technical SEO | https://searchengineland.com/library/seo and Search Engine Journal — Technical SEO | https://www.searchenginejournal.com/category/technical-seo/ (scraped 2026-06-18)",
+      "changes": [
+        "No actionable SEO rules extracted — Search Engine Land page returned only a single non-SEO article title ('How to build a Claude Code-powered second brain for agency work') with no technical SEO content; Search Engine Journal page returned only navigation/category shell text with no article content; no new, updated, or deprecated rules warranted"
+      ]
+    },
+    {
+      "date": "2026-06-18",
+      "version": "1.3.4",
+      "source": "Search Engine Journal — Technical SEO | https://www.searchenginejournal.com/category/technical-seo/ (scraped 2026-06-18)",
+      "changes": [
+        "No actionable SEO rules extracted — scraped page returned only a navigation/category shell with no article content; no new, updated, or deprecated rules warranted"
+      ]
+    },
+    {
+      "date": "2026-06-18",
+      "version": "1.3.4",
+      "source": "Google AI Features in Search — https://developers.google.com/search/docs/appearance/ai-features (scraped 2026-06-18) and Web.dev Blog — https://web.dev/blog (scraped 2026-06-18)",
+      "changes": [
+        "Confirmed rule: ai-features-snippet-eligibility — technical requirements for AI features confirmed; pages must be indexed and eligible to appear in Google Search with a snippet; no additional technical requirements beyond standard Search requirements; already reflected",
+        "Confirmed rule: generative-ai-optimization — foundational SEO best practices apply to AI features; query fan-out technique described; already reflected",
+        "Confirmed rule: spam-policies-apply-to-ai-responses — spam policies apply to AI features confirmed; already reflected",
+        "Confirmed rule: ai-mode-search-console — AI Mode and AI Overviews traffic included in Search Console totals confirmed; already reflected",
+        "Confirmed rule: llms-txt-not-required — no special AI-specific technical requirements beyond standard Search confirmed; already reflected",
+        "Confirmed rule: agent-friendly-website — agentic experiences guidance confirmed; already reflected",
+        "Confirmed rule: preferred-sources-ai-mode — preferred sources in AI Overviews and AI Mode confirmed; already reflected",
+        "No actionable new rules extracted — Web.dev Blog returned only a navigation shell with no article content; Google AI Features page content confirmed existing rules with no new distinct actionable requirements"
+      ]
+    },
+    {
+      "date": "2026-06-18",
+      "version": "1.3.3",
+      "source": "Google AI Optimization Guide — https://developers.google.com/search/docs/fundamentals/ai-optimization-guide (scraped 2026-06-18) and Bing Webmaster Blog — https://blogs.bing.com/webmaster (scraped 2026-06-18)",
+      "changes": [
+        "Confirmed rule: generative-ai-optimization — article content is the same guide already reflected in full; no new actionable rules extracted beyond what is already captured",
+        "Confirmed rule: llms-txt-not-required — llms.txt myth-busting confirmed again in current article scrape; already reflected",
+        "Confirmed rule: ai-features-snippet-eligibility — snippet and indexing eligibility requirement for AI features confirmed again; already reflected",
+        "Confirmed rule: agent-friendly-website — agentic experiences guidance confirmed again; already reflected",
+        "Confirmed rule: spam-policies-apply-to-ai-responses — scaled content abuse spam policy reference confirmed again; already reflected",
+        "Confirmed rule: bing-ai-performance-citation-eligibility — Bing AI Performance public preview and Copilot GA confirmed again; already reflected"
+      ]
+    },
+    {
+      "date": "2026-06-09",
+      "version": "1.3.2",
+      "source": "Schema.org Release Notes — https://schema.org/docs/releases.html (scraped 2026-06-09) and Web.dev Blog — https://web.dev/blog (scraped 2026-06-09)",
+      "changes": [
+        "No actionable SEO rules extracted from Web.dev Blog — page returned only a navigation shell with no article content",
+        "Added rule: speakable-schema-deprecated — SpeakableSpecification was introduced in schema.org 3.2 and moved to core in 3.5, but Google has since removed Speakable from its supported rich result types; existing implementations should be audited",
+        "Added rule: schema-org-iptc-digital-source-type — schema.org version 24.0 introduced IPTCDigitalSourceEnumeration with 14 coded values for AI-generated and algorithmically manipulated media; version 29.4 added missing enumeration values; aligns with existing c2pa-metadata rule",
+        "Added rule: schema-org-shipping-vocabulary-updated — schema.org version 29.0 deprecated DeliveryTimeSettings and ShippingRateSettings, superseding them with new types; ecommerce sites using these deprecated types should migrate to the updated shipping vocabulary",
+        "Added rule: has-adult-consideration-schema-v14 — schema.org version 14.0 formally introduced hasAdultConsideration property on MerchantReturnPolicy and AdultOrientedEnumeration; confirms and extends existing has-adult-consideration-schema rule with schema.org version provenance",
+        "Confirmed rule: c2pa-metadata — schema.org version 28.1 added new IPTC values to IPTCDigitalSourceEnumeration; compositeWithTrainedAlgorithmicMedia already reflected in existing rule",
+        "Confirmed rule: merchant-return-policy-schema — schema.org versions 13.0 and 14.0 added extensive MerchantReturnPolicy vocabulary; already reflected",
+        "Confirmed rule: merchant-shipping-policy-schema — schema.org version 13.0 added OfferShippingDetails and shipping vocabulary; already reflected",
+        "Confirmed rule: loyalty-program-schema — schema.org version 28.0 added loyalty program support through MemberProgram, MemberProgramTier, TierBenefitEnumeration; already reflected",
+        "Confirmed rule: faq-schema-deprecated — FAQPage type introduced in schema.org 3.4; Google deprecated FAQ rich results May 7 2026; already reflected",
+        "Confirmed rule: sitelinks-searchbox-removed — SearchAction type present in schema.org; Google removed sitelinks searchbox feature; already reflected",
+        "Confirmed rule: dataset-schema-phased-out — Dataset type present in schema.org; Google phasing out Dataset rich results; already reflected",
+        "Confirmed rule: special-announcement-schema-deprecated — SpecialAnnouncement type introduced in schema.org COVID-era releases; Google deprecated July 31 2025; already reflected",
+        "Confirmed rule: practice-problem-schema-deprecated — PracticeProblem type introduced in schema.org; Google no longer shows in Search; already reflected"
+      ]
+    },
+    {
+      "date": "2026-06-09",
+      "version": "1.3.1",
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-06-09, last updated 2026-06-05 UTC)",
+      "changes": [
+        "Confirmed rule: preferred-sources-ai-mode — already reflected from prior scrape",
+        "Confirmed rule: has-adult-consideration-schema — already reflected from prior scrape",
+        "Confirmed rule: third-party-seo-tools-guidance — already reflected from prior scrape",
+        "Confirmed rule: preferred-sources-feature — already reflected from prior scrape",
+        "Confirmed rule: faq-schema-deprecated — already reflected",
+        "Confirmed rule: back-button-hijacking — already reflected",
+        "Confirmed rule: robots-meta-outside-head — already reflected",
+        "Confirmed rule: noindex-in-javascript — already reflected",
+        "Confirmed rule: canonical-javascript-best-practice — already reflected",
+        "Confirmed rule: read-more-deeplink — already reflected",
+        "Confirmed rule: image-preferred-source-metadata — already reflected",
+        "Confirmed rule: breadcrumbs-desktop-only — already reflected",
+        "Confirmed rule: video-transparency — already reflected",
+        "Confirmed rule: structured-data-javascript-initial-html — already reflected",
+        "Confirmed rule: mobile-version-links — already reflected",
+        "Confirmed rule: review-snippet-requires-comment — already reflected",
+        "Confirmed rule: review-no-multiple-reviewed-entities — already reflected",
+        "Confirmed rule: practice-problem-schema-deprecated — already reflected",
+        "Confirmed rule: special-announcement-schema-deprecated — already reflected",
+        "Confirmed rule: missing-hreflang — already reflected",
+        "Confirmed rule: hreflang-no-combined-attributes — already reflected",
+        "Confirmed rule: robots-txt-unsupported-fields — already reflected",
+        "Confirmed rule: merchant-shipping-policy-schema — already reflected",
+        "Confirmed rule: video-indexing-criteria — already reflected",
+        "Confirmed rule: explicit-content-video-crawlable — already reflected",
+        "Confirmed rule: indexing-api-spam-detection — already reflected",
+        "Confirmed rule: avif-image-format-supported — already reflected",
+        "Confirmed rule: c2pa-metadata — already reflected",
+        "Confirmed rule: ai-mode-search-console — already reflected",
+        "Confirmed rule: loyalty-program-schema — already reflected",
+        "Confirmed rule: merchant-return-policy-schema — already reflected",
+        "Confirmed rule: product-structured-data-single-product — already reflected",
+        "Confirmed rule: url-parameters-best-practice — already reflected",
+        "Confirmed rule: safe-search-explicit-tagging — already reflected",
+        "Confirmed rule: organization-markup — already reflected",
+        "Confirmed rule: site-name-schema — already reflected",
+        "Confirmed rule: missing-og-locale — already reflected",
+        "Confirmed rule: sitemap-recommended — already reflected",
+        "Confirmed rule: json-ld-recommended-format — already reflected",
+        "Confirmed rule: javascript-non-200-rendering — already reflected",
+        "Confirmed rule: javascript-paywall-detection — already reflected",
+        "Confirmed rule: image-url-consistency — already reflected",
+        "Confirmed rule: dataset-schema-phased-out — already reflected",
+        "Confirmed rule: event-structured-data-requirements — already reflected",
+        "Confirmed rule: follow-feature-removed — already reflected",
+        "Confirmed rule: sitelinks-searchbox-removed — already reflected",
+        "Confirmed rule: south-africa-carousel-structured-data — already reflected",
+        "Confirmed rule: googlebot-file-size-limits — already reflected",
+        "Confirmed rule: recipe-thumbnail-property — already reflected",
+        "Confirmed rule: core-updates-continuous — already reflected",
+        "Confirmed rule: generative-ai-optimization — already reflected",
+        "Confirmed rule: spam-policies-apply-to-ai-responses — already reflected",
+        "Confirmed rule: llms-txt-not-required — already reflected",
+        "Confirmed rule: ai-features-snippet-eligibility — already reflected",
+        "Confirmed rule: agent-friendly-website — already reflected",
+        "Confirmed rule: bing-ai-performance-citation-eligibility — already reflected",
+        "Confirmed rule: missing-title — already reflected",
+        "Confirmed rule: missing-meta-description — already reflected",
+        "Confirmed rule: missing-favicon — already reflected",
+        "Confirmed rule: missing-json-ld — already reflected",
+        "Confirmed rule: missing-fid — deprecated rule confirmed disabled",
+        "Confirmed rule: accidental-noindex — already reflected",
+        "Confirmed rule: missing-canonical — already reflected",
+        "Added rule: noindex-javascript-accessibility-outdated — changelog explicitly states Google removed outdated accessibility/JavaScript section noting JS content is no longer harder for Google; rule documents that using JavaScript to load content is no longer considered an SEO accessibility concern",
+        "Added rule: crawling-docs-migrated — Google has migrated core crawling documentation to a new dedicated crawling infrastructure site with its own changelog feed; site owners and SEO tools should update references",
+        "Added rule: turkey-carousel-structured-data — structured data carousels (beta) feature expanded to Turkey",
+        "Added rule: spam-reports-manual-action — Google has clarified it may use spam report submissions to take manual action against violations; previously spam reports were not used for manual actions"
+      ]
+    },
+    {
+      "date": "2026-06-09",
+      "version": "1.3.0",
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-06-09)",
+      "changes": [
+        "Added rule: preferred-sources-ai-mode — preferred sources feature now available in AI Overviews and AI Mode (previously only available in standard Search)",
+        "Added rule: has-adult-consideration-schema — new hasAdultConsideration property added to merchant listing structured data for parity with Merchant Center feed specification",
+        "Added rule: third-party-seo-tools-guidance — Google has published new guidance on evaluating third-party SEO tools, services, and advice",
+        "Updated rule: preferred-sources-feature — updated description and references to reflect that preferred sources is now available in AI Overviews and AI Mode in addition to standard Search"
+      ]
+    },
+    {
+      "date": "2026-05-28",
+      "version": "1.2.5",
+      "source": "Bing Webmaster Blog — https://blogs.bing.com/webmaster (scraped 2026-05-28) and Web.dev Blog — https://web.dev/blog (scraped 2026-05-28)",
+      "changes": [
+        "Added rule: bing-ai-performance-citation-eligibility — new info rule documenting Bing's AI Performance feature in Bing Webmaster Tools showing when URLs are cited in AI-generated answers across Microsoft Copilot and Bing AI summaries; pages must meet standard Bing indexing and snippet eligibility requirements to be cited",
+        "No changes to existing rules — web.dev blog page returned only a navigation shell with no actionable SEO guidance; Bing Webmaster Blog content confirmed existing AI/snippet eligibility patterns already reflected in generative-ai-optimization and ai-features-snippet-eligibility rules"
+      ]
+    },
+    {
+      "date": "2026-05-24",
+      "version": "1.2.4",
+      "source": "Google AI Optimization Guide — https://developers.google.com/search/docs/fundamentals/ai-optimization-guide and Google AI Features in Search — https://developers.google.com/search/docs/appearance/ai-features (scraped 2026-05-24)",
+      "changes": [
+        "Updated rule: generative-ai-optimization — expanded description to reflect full official guide content including RAG/fanout query explanation, llms.txt myth-busting, chunking myth, inauthentic mentions myth, structured data overfocus myth, agentic experiences guidance, and Universal Commerce Protocol mention; updated references to include new ai-features URL",
+        "Added rule: llms-txt-not-required — new rule documenting that llms.txt and other AI-specific machine-readable files are not required or specially treated by Google for generative AI search inclusion",
+        "Added rule: ai-features-snippet-eligibility — new rule documenting that pages must be indexed and eligible to appear in Google Search with a snippet to be eligible for AI Overviews and AI Mode; no additional technical requirements beyond standard Search requirements",
+        "Added rule: agent-friendly-website — new info rule documenting emerging agentic experience best practices for browser agents including DOM structure, accessibility tree, and visual rendering considerations",
+        "Confirmed rule: spam-policies-apply-to-ai-responses — scaled content abuse and spam policy compliance confirmed as relevant to generative AI features (already reflected)",
+        "Confirmed rule: ai-mode-search-console — AI Mode traffic in Search Console totals confirmed (already reflected)"
+      ]
+    },
+    {
+      "date": "2026-05-24",
+      "version": "1.2.3",
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-05-24)",
+      "changes": [
+        "Confirmed rule: generative-ai-optimization — new guide on optimizing for generative AI features confirmed; non-commodity content, local/shopping/image/video content, AI agents guidance, SEO best practices remain relevant (already reflected)",
+        "Confirmed rule: spam-policies-apply-to-ai-responses — spam policies apply to generative AI responses confirmed (already reflected)",
+        "Confirmed rule: faq-schema-deprecated — FAQ rich results deprecated May 7, 2026 confirmed (already reflected)",
+        "Confirmed rule: back-button-hijacking — back button hijacking spam policy confirmed (already reflected)",
+        "Confirmed rule: robots-meta-outside-head — behavior confirmed (already reflected)",
+        "Confirmed rule: noindex-in-javascript — undefined behavior confirmed (already reflected)",
+        "Confirmed rule: canonical-javascript-best-practice — canonicalization before and after rendering confirmed (already reflected)",
+        "Confirmed rule: favicon-aspect-ratio — 1:1 aspect ratio, min 8x8px, recommended 48x48px confirmed (already reflected)",
+        "Confirmed rule: inp-core-web-vital — INP as Core Web Vital confirmed (already reflected)",
+        "Confirmed rule: image-preferred-source-metadata — og:image and schema.org as thumbnail sources confirmed (already reflected)",
+        "Confirmed rule: breadcrumbs-desktop-only — desktop-only confirmed (already reflected)",
+        "Confirmed rule: video-transparency — 80% opaque pixel requirement confirmed (already reflected)",
+        "Confirmed rule: structured-data-javascript-initial-html — initial HTML best practice confirmed (already reflected)",
+        "Confirmed rule: mobile-version-links — all links must be present on mobile version confirmed (already reflected)",
+        "Confirmed rule: review-snippet-requires-comment — comment and author name requirement confirmed (already reflected)",
+        "Confirmed rule: practice-problem-schema-deprecated — no longer shown in Google Search confirmed (already reflected)",
+        "Confirmed rule: special-announcement-schema-deprecated — deprecated July 31, 2025 confirmed (already reflected)",
+        "Confirmed rule: missing-hreflang — must not be combined with conflicting attributes confirmed (already reflected)",
+        "Confirmed rule: hreflang-no-combined-attributes — confirmed (already reflected)",
+        "Confirmed rule: review-no-multiple-reviewed-entities — confirmed (already reflected)",
+        "Confirmed rule: robots-txt-unsupported-fields — confirmed (already reflected)",
+        "Confirmed rule: merchant-shipping-policy-schema — confirmed (already reflected)",
+        "Confirmed rule: video-indexing-criteria — confirmed (already reflected)",
+        "Confirmed rule: explicit-content-video-crawlable — confirmed (already reflected)",
+        "Confirmed rule: indexing-api-spam-detection — confirmed (already reflected)",
+        "Confirmed rule: avif-image-format-supported — confirmed (already reflected)",
+        "Confirmed rule: c2pa-metadata — confirmed (already reflected)",
+        "Confirmed rule: ai-mode-search-console — confirmed (already reflected)",
+        "Confirmed rule: loyalty-program-schema — confirmed (already reflected)",
+        "Confirmed rule: merchant-return-policy-schema — confirmed (already reflected)",
+        "Confirmed rule: product-structured-data-single-product — confirmed (already reflected)",
+        "Confirmed rule: url-parameters-best-practice — confirmed (already reflected)",
+        "Confirmed rule: safe-search-explicit-tagging — confirmed (already reflected)",
+        "Confirmed rule: organization-markup — confirmed (already reflected)",
+        "Confirmed rule: site-name-schema — confirmed (already reflected)",
+        "Confirmed rule: missing-og-locale — confirmed (already reflected)",
+        "Confirmed rule: sitemap-recommended — confirmed (already reflected)",
+        "Confirmed rule: json-ld-recommended-format — confirmed (already reflected)",
+        "Confirmed rule: read-more-deeplink — confirmed (already reflected)",
+        "Confirmed rule: javascript-non-200-rendering — confirmed (already reflected)",
+        "Confirmed rule: javascript-paywall-detection — confirmed (already reflected)",
+        "Confirmed rule: image-url-consistency — confirmed (already reflected)",
+        "Confirmed rule: dataset-schema-phased-out — confirmed (already reflected)",
+        "Confirmed rule: event-structured-data-requirements — confirmed (already reflected)",
+        "Confirmed rule: preferred-sources-feature — confirmed (already reflected)",
+        "Confirmed rule: follow-feature-removed — confirmed (already reflected)",
+        "Confirmed rule: sitelinks-searchbox-removed — confirmed (already reflected)",
+        "Confirmed rule: south-africa-carousel-structured-data — confirmed (already reflected)",
+        "Confirmed rule: googlebot-file-size-limits — confirmed (already reflected)",
+        "Confirmed rule: recipe-thumbnail-property — confirmed (already reflected)",
+        "Confirmed rule: core-updates-continuous — confirmed (already reflected)",
+        "Confirmed rule: missing-title — heading tag content as title link source confirmed (already reflected)",
+        "Confirmed rule: missing-meta-description — primary source of snippets is page content confirmed (already reflected)",
+        "Confirmed rule: missing-favicon — crawlability requirements and domain/subdomain level support confirmed (already reflected)",
+        "Confirmed rule: missing-json-ld — deprecated schema types noted confirmed (already reflected)",
+        "Confirmed rule: missing-fid — deprecated rule confirmed disabled (already reflected)",
+        "Confirmed rule: accidental-noindex — noindex in JavaScript undefined behavior confirmed (already reflected)",
+        "Confirmed rule: missing-canonical — JavaScript canonicalization best practices confirmed (already reflected)"
+      ]
+    },
+    {
+      "date": "2026-05-19",
+      "version": "1.2.2",
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-05-19)",
+      "changes": [
+        "Added rule: generative-ai-optimization — New guide on optimizing for generative AI features on Search; non-commodity content, local/shopping/image/video content, and SEO best practices remain relevant",
+        "Added rule: spam-policies-apply-to-ai-responses — Google spam policies explicitly apply to generative AI responses in Google Search",
+        "Added rule: follow-feature-removed — The Follow feature is no longer shown in Google Discover; related markup guidance removed",
+        "Added rule: sitelinks-searchbox-removed — Sitelinks search box feature no longer available in Google Search; nositelinkssearchbox robots tag no longer needed",
+        "Added rule: south-africa-carousel-structured-data — Structured data carousels (beta) now available in South Africa with food delivery, car hire, and bus booking query types",
+        "Added rule: googlebot-file-size-limits — Googlebot has documented file size limits for HTML and subresources (JS/CSS); pages exceeding limits may not be fully crawled",
+        "Added rule: recipe-thumbnail-property — The thumbnail property in Recipe markup is only used for recipe rich results, not for text result images",
+        "Added rule: core-updates-continuous — Google continuously makes core updates including smaller ones; content improvements can cause ranking rises without waiting for next major update",
+        "Confirmed rule: missing-title — Google can use heading tag content to auto-generate title links (already reflected)",
+        "Confirmed rule: missing-meta-description — Primary source of snippets is page content itself (already reflected)",
+        "Confirmed rule: faq-schema-deprecated — FAQ rich results deprecated May 7, 2026 (already reflected)",
+        "Confirmed rule: back-button-hijacking — Back button hijacking spam policy confirmed (already reflected)",
+        "Confirmed rule: robots-meta-outside-head — Behavior confirmed (already reflected)",
+        "Confirmed rule: noindex-in-javascript — Undefined behavior confirmed (already reflected)",
+        "Confirmed rule: canonical-javascript-best-practice — Canonicalization before and after rendering confirmed (already reflected)",
+        "Confirmed rule: favicon-aspect-ratio — 1:1 aspect ratio, min 8x8px, recommended 48x48px confirmed (already reflected)",
+        "Confirmed rule: inp-core-web-vital — INP as Core Web Vital confirmed (already reflected)",
+        "Confirmed rule: image-preferred-source-metadata — og:image and schema.org as thumbnail sources confirmed (already reflected)",
+        "Confirmed rule: breadcrumbs-desktop-only — Desktop-only confirmed (already reflected)",
+        "Confirmed rule: video-transparency — 80% opaque pixel requirement confirmed (already reflected)",
+        "Confirmed rule: structured-data-javascript-initial-html — Initial HTML best practice confirmed (already reflected)",
+        "Confirmed rule: mobile-version-links — All links must be present on mobile version confirmed (already reflected)",
+        "Confirmed rule: review-snippet-requires-comment — Comment and author name requirement confirmed (already reflected)",
+        "Confirmed rule: practice-problem-schema-deprecated — No longer shown in Google Search confirmed (already reflected)",
+        "Confirmed rule: special-announcement-schema-deprecated — Deprecated July 31, 2025 confirmed (already reflected)",
+        "Confirmed rule: missing-hreflang — Must not be combined with conflicting attributes confirmed (already reflected)",
+        "Confirmed rule: hreflang-no-combined-attributes — Confirmed (already reflected)",
+        "Confirmed rule: review-no-multiple-reviewed-entities — Confirmed (already reflected)",
+        "Confirmed rule: robots-txt-unsupported-fields — Confirmed (already reflected)",
+        "Confirmed rule: merchant-shipping-policy-schema — Confirmed (already reflected)",
+        "Confirmed rule: video-indexing-criteria — Confirmed (already reflected)",
+        "Confirmed rule: explicit-content-video-crawlable — Confirmed (already reflected)",
+        "Confirmed rule: indexing-api-spam-detection — Confirmed (already reflected)",
+        "Confirmed rule: avif-image-format-supported — Confirmed (already reflected)",
+        "Confirmed rule: c2pa-metadata — Confirmed (already reflected)",
+        "Confirmed rule: ai-mode-search-console — Confirmed (already reflected)",
+        "Confirmed rule: loyalty-program-schema — Confirmed (already reflected)",
+        "Confirmed rule: merchant-return-policy-schema — Confirmed (already reflected)",
+        "Confirmed rule: product-structured-data-single-product — Confirmed (already reflected)",
+        "Confirmed rule: url-parameters-best-practice — Confirmed (already reflected)",
+        "Confirmed rule: safe-search-explicit-tagging — Confirmed (already reflected)",
+        "Confirmed rule: organization-markup — Confirmed (already reflected)",
+        "Confirmed rule: site-name-schema — Confirmed (already reflected)",
+        "Confirmed rule: missing-og-locale — Confirmed (already reflected)",
+        "Confirmed rule: sitemap-recommended — Confirmed (already reflected)",
+        "Confirmed rule: json-ld-recommended-format — Confirmed (already reflected)",
+        "Confirmed rule: read-more-deeplink — Confirmed (already reflected)",
+        "Confirmed rule: javascript-non-200-rendering — Confirmed (already reflected)",
+        "Confirmed rule: javascript-paywall-detection — Confirmed (already reflected)",
+        "Confirmed rule: image-url-consistency — Confirmed (already reflected)",
+        "Confirmed rule: dataset-schema-phased-out — Confirmed (already reflected)",
+        "Confirmed rule: event-structured-data-requirements — Confirmed (already reflected)",
+        "Confirmed rule: preferred-sources-feature — Confirmed (already reflected)"
+      ]
+    },
+    {
+      "date": "2026-05-08",
+      "version": "1.2.1",
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "changes": [
+        "Confirmed rule: missing-title — title link sources clarified; Google can use content within heading tags to auto-generate title links",
+        "Confirmed rule: missing-meta-description — primary source of snippets is page content itself; meta description is secondary source (already reflected)",
+        "Confirmed rule: faq-schema-deprecated — FAQ rich results deprecated May 7, 2026 (already reflected)",
+        "Confirmed rule: back-button-hijacking — back button hijacking spam policy confirmed (already reflected)",
+        "Confirmed rule: robots-meta-outside-head — behavior confirmed, previously undocumented (already reflected)",
+        "Confirmed rule: noindex-in-javascript — undefined behavior confirmed (already reflected)",
+        "Confirmed rule: canonical-javascript-best-practice — canonicalization before and after rendering confirmed (already reflected)",
+        "Confirmed rule: favicon-aspect-ratio — 1:1 aspect ratio, min 8x8px, recommended 48x48px confirmed (already reflected)",
+        "Confirmed rule: inp-core-web-vital — INP as Core Web Vital confirmed (already reflected)",
+        "Confirmed rule: image-preferred-source-metadata — og:image and schema.org as thumbnail sources confirmed (already reflected)",
+        "Confirmed rule: breadcrumbs-desktop-only — desktop-only confirmed (already reflected)",
+        "Confirmed rule: video-transparency — 80% opaque pixel requirement confirmed (already reflected)",
+        "Confirmed rule: structured-data-javascript-initial-html — initial HTML best practice confirmed (already reflected)",
+        "Confirmed rule: mobile-version-links — all links must be present on mobile version confirmed (already reflected)",
+        "Confirmed rule: review-snippet-requires-comment — comment and author name requirement confirmed (already reflected)",
+        "Confirmed rule: practice-problem-schema-deprecated — no longer shown in Google Search confirmed (already reflected)",
+        "Confirmed rule: special-announcement-schema-deprecated — deprecated July 31, 2025 confirmed (already reflected)",
+        "Confirmed rule: missing-hreflang — must not be combined with conflicting attributes confirmed (already reflected)",
+        "Confirmed rule: hreflang-no-combined-attributes — confirmed (already reflected)",
+        "Confirmed rule: review-no-multiple-reviewed-entities — confirmed (already reflected)",
+        "Confirmed rule: robots-txt-unsupported-fields — confirmed (already reflected)",
+        "Confirmed rule: merchant-shipping-policy-schema — confirmed (already reflected)",
+        "Confirmed rule: video-indexing-criteria — confirmed (already reflected)",
+        "Confirmed rule: explicit-content-video-crawlable — confirmed (already reflected)",
+        "Confirmed rule: indexing-api-spam-detection — confirmed (already reflected)",
+        "Confirmed rule: avif-image-format-supported — confirmed (already reflected)",
+        "Confirmed rule: c2pa-metadata — confirmed (already reflected)",
+        "Confirmed rule: ai-mode-search-console — confirmed (already reflected)",
+        "Confirmed rule: loyalty-program-schema — confirmed (already reflected)",
+        "Confirmed rule: merchant-return-policy-schema — confirmed (already reflected)",
+        "Confirmed rule: product-structured-data-single-product — confirmed (already reflected)",
+        "Confirmed rule: url-parameters-best-practice — confirmed (already reflected)",
+        "Confirmed rule: safe-search-explicit-tagging — confirmed (already reflected)",
+        "Confirmed rule: organization-markup — confirmed (already reflected)",
+        "Confirmed rule: site-name-schema — confirmed (already reflected)",
+        "Confirmed rule: missing-og-locale — confirmed (already reflected)",
+        "Confirmed rule: sitemap-recommended — confirmed (already reflected)",
+        "Confirmed rule: json-ld-recommended-format — confirmed (already reflected)",
+        "Confirmed rule: read-more-deeplink — confirmed (already reflected)",
+        "Confirmed rule: javascript-non-200-rendering — confirmed (already reflected)",
+        "Confirmed rule: javascript-paywall-detection — confirmed (already reflected)",
+        "Confirmed rule: image-url-consistency — confirmed (already reflected)",
+        "Confirmed rule: missing-fid — deprecated rule confirmed disabled (already reflected)",
+        "Updated rule: missing-title — added note that Google can use heading tag content to auto-generate title links",
+        "Updated rule: missing-favicon — added note that favicon file and home page must both be crawlable by Googlebot-Image and Googlebot respectively; favicons supported at domain and subdomain level only",
+        "Updated rule: missing-json-ld — added note that dataset structured data type is being phased out from Google Search",
+        "Updated rule: loyalty-program-schema — clarified that loyalty program information must be defined separately from offer-level loyalty benefits; shipping and returns loyalty benefits not supported",
+        "Updated rule: merchant-return-policy-schema — clarified offer-level return policies only support subset of org-level; product-level takes precedence over org-level; Merchant Center takes precedence over structured data for products in feeds",
+        "Updated rule: video-indexing-criteria — clarified that VideoObject now accepts duration property as another way to specify video duration",
+        "Updated rule: safe-search-explicit-tagging — clarified that explicit content should be grouped in a separate location; added guidance on moderating content and eliminating CSAM",
+        "Updated rule: c2pa-metadata — added compositeWithTrainedAlgorithmicMedia as a supported IPTC digital source type",
+        "Updated rule: organization-markup — clarified that some properties influence logo shown in Search while others are used behind the scenes for entity disambiguation; organization markup now includes contact info, legal name, and business identifiers",
+        "Updated rule: site-name-schema — clarified that site names are now available in all languages where Google Search is available; issue with site names not propagating to internal pages has been resolved",
+        "Added rule: preferred-sources-feature — preferred sources feature now available in all languages where Google Search is available",
+        "Added rule: event-structured-data-requirements — events must be bookable by general public and held at physical location to be eligible for event experience on Google",
+        "Added rule: dataset-schema-phased-out — dataset structured data type is being phased out from Google Search results"
+      ]
+    },
+    {
+      "date": "2026-05-08",
+      "version": "1.2.0",
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "changes": [
+        "Added rule: read-more-deeplink — Google supports 'read more' deep links in snippets; content structure can influence eligibility",
+        "Added rule: javascript-non-200-rendering — Googlebot may not execute JavaScript on non-200 HTTP status code pages",
+        "Added rule: javascript-paywall-detection — JavaScript-based paywall design makes it difficult for Google to determine paywalled vs free content",
+        "Added rule: hreflang-no-combined-attributes — hreflang alternate link elements must not be combined with attributes that change their meaning to denote a different device or language version",
+        "Added rule: review-no-multiple-reviewed-entities — Avoid using multiple ways of indicating what is being reviewed in review and aggregate rating structured data",
+        "Added rule: image-url-consistency — Image URLs should be referenced consistently across pages for easier crawling on larger websites",
+        "Added rule: robots-txt-unsupported-fields — Fields not listed in Google robots.txt documentation are not supported",
+        "Added rule: merchant-shipping-policy-schema — Google now supports merchant-level shipping policy markup in Search",
+        "Added rule: video-indexing-criteria — Videos must meet specific technical requirements and indexing criteria to appear in video search results",
+        "Added rule: explicit-content-video-crawlable — Sites hosting explicit videos must allow Googlebot to fetch video files or risk significant ranking drops in Video mode",
+        "Added rule: indexing-api-spam-detection — Indexing API submissions are subject to spam detection; exceeding quotas may result in revoked access",
+        "Added rule: avif-image-format-supported — AVIF is now a supported image format in Google Search",
+        "Added rule: c2pa-metadata — Google extracts C2PA metadata for use in the 'About this image' feature in Search",
+        "Added rule: ai-mode-search-console — AI Mode traffic now counts toward Search Console totals",
+        "Added rule: loyalty-program-schema — Google supports loyalty program markup in Search for eligible regions",
+        "Added rule: merchant-return-policy-schema — Google supports merchant return policy markup in Search",
+        "Added rule: product-structured-data-single-product — Product rich results only support pages about a single product, not category pages",
+        "Added rule: url-parameters-best-practice — URL parameters guidance: avoid unnecessary parameters that create duplicate content",
+        "Added rule: safe-search-explicit-tagging — Explicit content pages should use the rating=adult meta tag",
+        "Added rule: organization-markup — Organization markup can influence which logo is shown in Google Search and provides business identifiers",
+        "Added rule: site-name-schema — Site names help Google display your preferred site name in SERPs; supported at domain and subdomain level",
+        "Added rule: missing-og-locale — og:locale recommended for international pages",
+        "Updated rule: missing-meta-description — Clarified that primary source of snippets is page content itself, not meta description; meta description guides preferred snippet text",
+        "Updated rule: missing-json-ld — Added note that practice problem and special announcement schema deprecated; JSON-LD confirmed as recommended format",
+        "Updated rule: video-transparency — Confirmed 80% opaque pixel requirement for video thumbnails",
+        "Updated rule: review-snippet-requires-comment — Added clarification about avoiding multiple ways of indicating what is being reviewed",
+        "Updated rule: missing-hreflang — Added note that hreflang must not be combined with attributes that change meaning to denote different device or language version",
+        "Confirmed rule: faq-schema-deprecated — FAQ rich results deprecated May 7, 2026",
+        "Confirmed rule: back-button-hijacking — Back button hijacking spam policy confirmed",
+        "Confirmed rule: robots-meta-outside-head — Robots meta outside head behavior confirmed",
+        "Confirmed rule: noindex-in-javascript — noindex in JavaScript undefined behavior confirmed",
+        "Confirmed rule: canonical-javascript-best-practice — JavaScript canonicalization best practices confirmed",
+        "Confirmed rule: favicon-aspect-ratio — Favicon 1:1 aspect ratio and 48x48px recommendation confirmed",
+        "Confirmed rule: inp-core-web-vital — INP as Core Web Vital confirmed",
+        "Confirmed rule: image-preferred-source-metadata — og:image and schema.org as image thumbnail sources confirmed",
+        "Confirmed rule: breadcrumbs-desktop-only — Breadcrumbs desktop-only confirmed",
+        "Confirmed rule: structured-data-javascript-initial-html — Structured data in initial HTML best practice confirmed",
+        "Confirmed rule: mobile-version-links — Mobile version links requirement confirmed",
+        "Confirmed rule: practice-problem-schema-deprecated — Practice problem schema deprecated confirmed",
+        "Confirmed rule: special-announcement-schema-deprecated — Special announcement schema deprecated confirmed",
+        "Confirmed rule: json-ld-recommended-format — JSON-LD recommended format confirmed"
+      ]
+    },
+    {
+      "date": "2026-05-08",
+      "version": "1.1.0",
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "changes": [
+        "Added rule: faq-schema-deprecated — FAQ rich result feature deprecated by Google starting May 7, 2026",
+        "Added rule: back-button-hijacking — New spam policy for back button hijacking added to malicious practices",
+        "Added rule: robots-meta-outside-head — Google documents behavior of robots meta tags found outside HTML head",
+        "Added rule: noindex-in-javascript — Clarified that noindex in JavaScript-rendered pages has undefined behavior; must be in original HTML",
+        "Added rule: canonical-javascript-best-practice — Canonicalization best practices for JavaScript pages",
+        "Added rule: missing-og-locale — og:locale recommended for international pages",
+        "Added rule: favicon-aspect-ratio — Favicons must have 1:1 aspect ratio and be at least 8x8px (48x48px recommended)",
+        "Added rule: inp-core-web-vital — INP (Interaction to Next Paint) is now a Core Web Vital replacing FID",
+        "Added rule: image-preferred-source-metadata — Google uses both schema.org markup and og:image for image thumbnails in Search and Discover",
+        "Added rule: breadcrumbs-desktop-only — Breadcrumb rich results only appear on desktop, not mobile",
+        "Added rule: video-transparency — Video thumbnails must have at least 80% non-transparent pixels",
+        "Added rule: structured-data-javascript-initial-html — Product/ecommerce structured data should be in initial HTML for best results",
+        "Added rule: mobile-version-links — Mobile version of pages must include all links present on desktop version",
+        "Added rule: review-snippet-requires-comment — Reviews should require both a comment and author name to be eligible for review snippets",
+        "Added rule: practice-problem-schema-deprecated — Practice problem structured data type no longer shown in Google Search",
+        "Added rule: special-announcement-schema-deprecated — Special announcement structured data deprecated as of July 31, 2025",
+        "Added rule: missing-hreflang — hreflang tags for international/multilingual pages",
+        "Added rule: sitemap-recommended — Sitemaps help Google discover and index pages, especially on large sites",
+        "Added rule: json-ld-recommended-format — JSON-LD is the recommended format for structured data",
+        "Deprecated rule: missing-fid — FID is no longer a Core Web Vital as of March 2024; replaced by INP",
+        "Updated rule: missing-favicon — Updated to reflect favicon must have 1:1 aspect ratio, minimum 8x8px, recommended 48x48px",
+        "Updated rule: accidental-noindex — Updated to clarify noindex in JavaScript has undefined behavior and must be in original HTML",
+        "Updated rule: missing-canonical — Updated with JavaScript canonicalization best practices",
+        "Updated rule: missing-json-ld — Updated to note JSON-LD is Google's recommended format; FAQ and special announcement schema deprecated"
+      ]
+    }
+  ],
+  "rules": [
+    {
+      "id": "missing-title",
+      "name": "Missing <title> tag",
+      "severity": "critical",
+      "category": "meta",
+      "description": "Every page must have a unique <title> tag. This is the primary signal search engines use to understand page topic and display in SERPs. Note: Google can also use content within heading tags (h1-h6) to automatically generate title links in search results when no suitable title tag is present or when the title tag is deemed less relevant.",
+      "fixTemplate": "Add <title>Your Page Title (50-60 chars)</title> inside <head>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/title-link"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "titleTag"
+      }
+    },
+    {
+      "id": "title-too-long",
+      "name": "Title tag too long",
+      "severity": "warning",
+      "category": "meta",
+      "description": "Title tags over 60 characters are truncated in Google SERPs, reducing click-through rate. Current length: {{CURRENT_LENGTH}} chars.",
+      "fixTemplate": "Trim your <title> to under 60 characters. Current: {{CURRENT_LENGTH}} chars.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/title-link"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-length-gt",
+        "field": "titleTag",
+        "threshold": 60
+      }
+    },
+    {
+      "id": "title-too-short",
+      "name": "Title tag too short",
+      "severity": "warning",
+      "category": "meta",
+      "description": "Title tags under 30 characters miss opportunities to include keywords. Current length: {{CURRENT_LENGTH}} chars.",
+      "fixTemplate": "Expand your <title> to at least 30 characters. Current: {{CURRENT_LENGTH}} chars.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/title-link"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-length-lt",
+        "field": "titleTag",
+        "threshold": 30
+      }
+    },
+    {
+      "id": "missing-meta-description",
+      "name": "Missing meta description",
+      "severity": "critical",
+      "category": "meta",
+      "description": "Meta descriptions are used as SERP snippets. Without one, Google auto-generates one from page content, which is typically worse for click-through rates. Google has clarified that the primary source of snippets is the page content itself, not the meta description — but providing one still guides Google toward your preferred snippet text. The meta description is not the primary source for snippets; structured data and the meta description HTML element are secondary sources.",
+      "fixTemplate": "Add <meta name=\"description\" content=\"Your description here (150-160 chars)\" /> inside <head>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/snippet"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "metaDescription"
+      }
+    },
+    {
+      "id": "meta-description-too-long",
+      "name": "Meta description too long",
+      "severity": "warning",
+      "category": "meta",
+      "description": "Descriptions over 160 characters are truncated in SERPs. Current: {{CURRENT_LENGTH}} chars.",
+      "fixTemplate": "Shorten meta description to under 160 characters. Current: {{CURRENT_LENGTH}} chars.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/snippet"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-length-gt",
+        "field": "metaDescription",
+        "threshold": 160
+      }
+    },
+    {
+      "id": "meta-description-too-short",
+      "name": "Meta description too short",
+      "severity": "info",
+      "category": "meta",
+      "description": "Descriptions under 70 characters are too brief to convey page value. Current: {{CURRENT_LENGTH}} chars.",
+      "fixTemplate": "Expand meta description to at least 70 characters. Current: {{CURRENT_LENGTH}} chars.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/snippet"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-length-lt",
+        "field": "metaDescription",
+        "threshold": 70
+      }
+    },
+    {
+      "id": "missing-og-title",
+      "name": "Missing og:title",
+      "severity": "warning",
+      "category": "meta",
+      "description": "Open Graph title is required for proper social sharing previews on Facebook, LinkedIn, Slack, and others.",
+      "fixTemplate": "Add <meta property=\"og:title\" content=\"Your Page Title\" /> inside <head>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://ogp.me/"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "ogTitle"
+      }
+    },
+    {
+      "id": "missing-og-description",
+      "name": "Missing og:description",
+      "severity": "warning",
+      "category": "meta",
+      "description": "Open Graph description is displayed when pages are shared on social platforms.",
+      "fixTemplate": "Add <meta property=\"og:description\" content=\"Your description\" /> inside <head>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://ogp.me/"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "ogDescription"
+      }
+    },
+    {
+      "id": "missing-og-image",
+      "name": "Missing og:image",
+      "severity": "warning",
+      "category": "meta",
+      "description": "Social shares without og:image show no image, severely reducing engagement. Image should be at least 1200x630px. Google also uses og:image as a source when determining image thumbnails in Google Search and Discover, making this tag doubly important.",
+      "fixTemplate": "Add <meta property=\"og:image\" content=\"https://yourdomain.com/og-image.jpg\" /> inside <head>. Recommended size: 1200x630px.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://ogp.me/",
+        "https://developers.google.com/search/docs/appearance/google-images"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "ogImage"
+      }
+    },
+    {
+      "id": "missing-og-url",
+      "name": "Missing og:url",
+      "severity": "info",
+      "category": "meta",
+      "description": "og:url sets the canonical URL for social sharing, preventing duplicate content issues on social platforms.",
+      "fixTemplate": "Add <meta property=\"og:url\" content=\"https://yourdomain.com/page\" /> inside <head>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://ogp.me/"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "ogUrl"
+      }
+    },
+    {
+      "id": "missing-og-type",
+      "name": "Missing og:type",
+      "severity": "info",
+      "category": "meta",
+      "description": "og:type tells social platforms what kind of content this is (website, article, product, etc.).",
+      "fixTemplate": "Add <meta property=\"og:type\" content=\"website\" /> inside <head>. Use 'article' for blog posts.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://ogp.me/#types"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "ogType"
+      }
+    },
+    {
+      "id": "missing-og-locale",
+      "name": "Missing og:locale for international pages",
+      "severity": "info",
+      "category": "meta",
+      "description": "og:locale is recommended for international pages to specify the language and territory of the page content (e.g., en_US, fr_FR). This helps social platforms and search engines correctly identify the intended audience for the page.",
+      "fixTemplate": "Add <meta property=\"og:locale\" content=\"en_US\" /> inside <head>. Replace 'en_US' with the appropriate locale code for your page's language and region.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://ogp.me/#optional",
+        "https://developers.google.com/search/docs/specialty/international/localization"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "missing-twitter-card",
+      "name": "Missing twitter:card",
+      "severity": "warning",
+      "category": "meta",
+      "description": "Without twitter:card, X (Twitter) will not show a rich preview when your page is shared.",
+      "fixTemplate": "Add <meta name=\"twitter:card\" content=\"summary_large_image\" /> inside <head>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developer.twitter.com/en/docs/twitter-for-websites/cards/overview/markup"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "twitterCard"
+      }
+    },
+    {
+      "id": "missing-twitter-title",
+      "name": "Missing twitter:title",
+      "severity": "info",
+      "category": "meta",
+      "description": "twitter:title overrides og:title specifically for X (Twitter) cards.",
+      "fixTemplate": "Add <meta name=\"twitter:title\" content=\"Your Title\" /> inside <head>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developer.twitter.com/en/docs/twitter-for-websites/cards/overview/markup"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "twitterTitle"
+      }
+    },
+    {
+      "id": "missing-twitter-image",
+      "name": "Missing twitter:image",
+      "severity": "info",
+      "category": "meta",
+      "description": "twitter:image is shown in X (Twitter) card previews. Recommended minimum 1200x628px.",
+      "fixTemplate": "Add <meta name=\"twitter:image\" content=\"https://yourdomain.com/twitter-image.jpg\" /> inside <head>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developer.twitter.com/en/docs/twitter-for-websites/cards/overview/markup"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "twitterImage"
+      }
+    },
+    {
+      "id": "missing-h1",
+      "name": "Missing <h1> tag",
+      "severity": "critical",
+      "category": "headings",
+      "description": "Every page must have exactly one <h1> tag. It signals the primary topic of the page to search engines.",
+      "fixTemplate": "Add exactly one <h1>Your Primary Topic</h1> tag to the page",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/fundamentals/seo-starter-guide"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "multiple-h1",
+      "name": "Multiple <h1> tags",
+      "severity": "critical",
+      "category": "headings",
+      "description": "Having multiple <h1> tags dilutes the primary topic signal. Found {{COUNT}} <h1> tags.",
+      "fixTemplate": "Reduce to exactly one <h1>. Demote additional h1 tags to <h2>. Found {{COUNT}} h1 tags.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/fundamentals/seo-starter-guide"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "heading-hierarchy",
+      "name": "Broken heading hierarchy",
+      "severity": "warning",
+      "category": "headings",
+      "description": "Heading levels should not skip (e.g., going from {{FROM}} to {{TO}}). Broken hierarchy confuses screen readers and search crawlers.",
+      "fixTemplate": "Fix heading structure: {{FROM}} jumps directly to {{TO}}. Insert the missing level between them.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://www.w3.org/WAI/tutorials/page-structure/headings/"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "empty-heading",
+      "name": "Empty heading tag",
+      "severity": "warning",
+      "category": "headings",
+      "description": "Empty {{TAG}} tags confuse crawlers and screen readers. Every heading must have meaningful text.",
+      "fixTemplate": "Add descriptive text to your <{{TAG}}> tag or remove it entirely",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/fundamentals/seo-starter-guide"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "image-missing-alt",
+      "name": "Image missing alt attribute",
+      "severity": "critical",
+      "category": "images",
+      "description": "Images without alt attributes are invisible to search engines and fail accessibility standards (WCAG 2.1). Affects: {{SRC}}",
+      "fixTemplate": "Add alt=\"Descriptive text about the image\" to <img src=\"{{SRC}}\">",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/google-images"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "image-empty-alt",
+      "name": "Image has empty alt (possible oversight)",
+      "severity": "info",
+      "category": "images",
+      "description": "Image has alt=\"\" which is valid only for purely decorative images. Verify this is intentional for: {{SRC}}",
+      "fixTemplate": "If this image conveys information, add descriptive alt text. If purely decorative, alt=\"\" is correct — add role=\"presentation\" to confirm intent.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/google-images"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "image-missing-lazy-loading",
+      "name": "Image missing lazy loading",
+      "severity": "info",
+      "category": "images",
+      "description": "Images without loading=\"lazy\" are loaded immediately, increasing initial page load time and hurting Core Web Vitals. Affects: {{SRC}}",
+      "fixTemplate": "Add loading=\"lazy\" to <img src=\"{{SRC}}\"> (skip for above-the-fold hero images)",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://web.dev/lazy-loading-images/"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "image-url-consistency",
+      "name": "Inconsistent image URL references",
+      "severity": "info",
+      "category": "images",
+      "description": "Image URLs should be referenced consistently across pages for easier crawling on larger websites. Inconsistent URLs (e.g., using different query parameters, protocols, or path formats for the same image) can cause Google to treat the same image as multiple distinct images, wasting crawl budget and reducing indexing efficiency.",
+      "fixTemplate": "Ensure the same image is always referenced with the same canonical URL across all pages. Avoid mixing http/https, www/non-www, or different query parameter variations for the same image file.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/google-images"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "vague-link-text",
+      "name": "Vague link anchor text",
+      "severity": "warning",
+      "category": "links",
+      "description": "Link text like '{{TEXT}}' gives no context to crawlers or screen readers about the destination. Link: {{HREF}}",
+      "fixTemplate": "Replace anchor text '{{TEXT}}' with descriptive text that explains the link destination, e.g. 'Read our pricing guide'",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/fundamentals/seo-starter-guide"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "external-link-no-rel",
+      "name": "External link missing rel=\"noopener\"",
+      "severity": "info",
+      "category": "links",
+      "description": "External links without rel=\"noopener noreferrer\" expose users to tab-napping attacks and leak referrer information. Link: {{HREF}}",
+      "fixTemplate": "Add rel=\"noopener noreferrer\" to <a href=\"{{HREF}}\">",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://web.dev/external-anchors-use-rel-noopener/"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "missing-lang",
+      "name": "Missing lang attribute on <html>",
+      "severity": "critical",
+      "category": "technical",
+      "description": "The lang attribute on the <html> element tells search engines and screen readers what language the page is in.",
+      "fixTemplate": "Add lang=\"en\" to your <html> tag: <html lang=\"en\">. Replace 'en' with the correct BCP 47 language code.",
+      "enabled": true,
+      "appliesTo": [
+        "html"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/specialty/international/localization"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "langAttribute"
+      }
+    },
+    {
+      "id": "missing-viewport",
+      "name": "Missing viewport meta tag",
+      "severity": "critical",
+      "category": "technical",
+      "description": "Without a viewport meta tag, mobile browsers render the page at desktop width, causing poor mobile UX and hurting mobile rankings.",
+      "fixTemplate": "Add <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\" /> inside <head>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "viewportMeta"
+      }
+    },
+    {
+      "id": "missing-charset",
+      "name": "Missing charset declaration",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Without a charset declaration, browsers may misinterpret the page encoding, causing garbled text.",
+      "fixTemplate": "Add <meta charset=\"UTF-8\" /> as the first tag inside <head>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://html.spec.whatwg.org/#charset"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "charsetMeta"
+      }
+    },
+    {
+      "id": "missing-canonical",
+      "name": "Missing canonical tag",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Without a canonical tag, search engines may index duplicate versions of your page (e.g., with/without trailing slash, with query params). For JavaScript-rendered pages, Google has clarified that canonicalization happens both before and after rendering. Best practice: set the canonical URL to the same URL as in the original HTML. If that is not possible, omit the canonical tag from the original HTML entirely rather than setting an incorrect one.",
+      "fixTemplate": "Add <link rel=\"canonical\" href=\"https://yourdomain.com/this-page\" /> inside <head>. For JavaScript pages, ensure this matches the canonical in the pre-rendered HTML.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls",
+        "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-null",
+        "field": "canonicalUrl"
+      }
+    },
+    {
+      "id": "accidental-noindex",
+      "name": "noindex directive detected",
+      "severity": "critical",
+      "category": "technical",
+      "description": "A meta robots noindex tag was found. This will prevent search engines from indexing this page. Confirm this is intentional. Important: Google has clarified that if there is any possibility you want the page indexed, do not use a noindex tag in the original page code — even if the page uses JavaScript. While Google may be able to render a JavaScript page, the behavior of noindex in JavaScript-rendered content is not well defined and may change. Always place noindex in the original HTML if you intend to block indexing.",
+      "fixTemplate": "Remove 'noindex' from <meta name=\"robots\"> if this page should be indexed. If using JavaScript to conditionally add noindex, move it to the original static HTML instead.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/block-indexing",
+        "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-truthy",
+        "field": "hasNoindex"
+      }
+    },
+    {
+      "id": "missing-favicon",
+      "name": "Missing favicon",
+      "severity": "info",
+      "category": "technical",
+      "description": "A favicon improves brand recognition in browser tabs and bookmarks. Google displays favicons in SERPs. Google requires favicons to have a 1:1 aspect ratio and be at least 8x8px in size. A higher resolution favicon of at least 48x48px is strongly recommended. Both the favicon file and the home page of the site must be crawlable by Googlebot-Image and Googlebot respectively. Favicons are supported at the domain and subdomain level, not at the subdirectory level. You do not need to host the favicon on the same domain to be eligible.",
+      "fixTemplate": "Add <link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\" /> inside <head>. Ensure the favicon has a 1:1 aspect ratio and is at least 48x48px. Confirm Googlebot can crawl both the favicon file (via Googlebot-Image) and your home page (via Googlebot).",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/favicon-in-search"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-falsy",
+        "field": "hasFavicon"
+      }
+    },
+    {
+      "id": "missing-json-ld",
+      "name": "No structured data (JSON-LD) found",
+      "severity": "info",
+      "category": "schema",
+      "description": "Structured data helps search engines understand your content and can unlock rich results (star ratings, breadcrumbs, etc.). JSON-LD is Google's recommended format for structured data as it is generally the easiest to implement and maintain. Note: FAQ rich results are deprecated as of May 7, 2026. Special announcement structured data was deprecated July 31, 2025. Practice problem structured data is no longer shown in Google Search results. Dataset structured data is also being phased out from Google Search results.",
+      "fixTemplate": "Add a JSON-LD script block: <script type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"WebPage\",\"name\":\"Page Title\"}</script>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data",
+        "https://developers.google.com/search/docs/appearance/structured-data/faq"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "field-array-empty",
+        "field": "jsonLdBlocks"
+      }
+    },
+    {
+      "id": "invalid-json-ld",
+      "name": "Invalid JSON in JSON-LD block",
+      "severity": "critical",
+      "category": "schema",
+      "description": "A JSON-LD structured data block contains invalid JSON. Search engines will ignore it entirely.",
+      "fixTemplate": "Fix the JSON syntax error in your <script type=\"application/ld+json\"> block. Use https://validator.schema.org to validate.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "missing-preload-lcp",
+      "name": "No resource preloading hints",
+      "severity": "info",
+      "category": "performance",
+      "description": "Pages with images but no <link rel=\"preload\"> hints may have slower Largest Contentful Paint (LCP), a Core Web Vitals signal.",
+      "fixTemplate": "Add <link rel=\"preload\" as=\"image\" href=\"/path/to/hero-image.webp\" /> in <head> for your above-the-fold hero image",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://web.dev/lcp/",
+        "https://web.dev/preload-responsive-images/"
+      ],
+      "source": "original",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "faq-schema-deprecated",
+      "name": "FAQ structured data is deprecated",
+      "severity": "warning",
+      "category": "schema",
+      "description": "Google has deprecated the FAQ rich result feature. Starting May 7, 2026, FAQ rich results will no longer appear in Google Search. Implementing FAQ schema will have no effect on search appearance and may add unnecessary markup weight to your pages.",
+      "fixTemplate": "Remove or stop adding FAQ JSON-LD structured data blocks. If you have existing FAQ schema, you may leave it in place as it will not cause harm, but it will no longer produce rich results in Google Search.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/faqpage"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "jsonld-has-type",
+        "schemaType": "FAQPage"
+      }
+    },
+    {
+      "id": "back-button-hijacking",
+      "name": "Back button hijacking spam policy",
+      "severity": "critical",
+      "category": "technical",
+      "description": "Google has added 'back button hijacking' as a named malicious practice in its spam policies. This deceptive practice intercepts or overrides the browser's back button behavior to trap users on a page or redirect them to an unintended destination. Pages that implement this behavior may be subject to manual action.",
+      "fixTemplate": "Audit your JavaScript for any code that overrides history.pushState, history.replaceState, or the popstate event in ways that prevent users from navigating back normally. Remove any such manipulation.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/essentials/spam-policies#malicious-behavior"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "raw-all-match",
+        "patterns": [
+          "addEventListener\\s*\\(\\s*['\"`]popstate['\"`]|window\\.onpopstate\\s*=",
+          "history\\.pushState"
+        ]
+      }
+    },
+    {
+      "id": "robots-meta-outside-head",
+      "name": "Robots meta tag outside <head>",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Google has documented that robots meta tags found outside the HTML <head> element are processed differently. While Google does process them, the behavior was previously undocumented and may not be consistent. Always place robots meta tags inside <head> to ensure reliable crawling and indexing behavior.",
+      "fixTemplate": "Move <meta name=\"robots\" content=\"{{VALUE}}\" /> inside the <head> element. Do not place robots meta tags in <body> or elsewhere in the document.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "noindex-in-javascript",
+      "name": "noindex set via JavaScript (undefined behavior)",
+      "severity": "critical",
+      "category": "technical",
+      "description": "Google has clarified that using a noindex directive in JavaScript-rendered content has undefined behavior that may change. While Google may be able to render a page that uses JavaScript, if there is any possibility you want the page indexed, do not use a noindex tag in the original page code or inject it via JavaScript. If you intend to block indexing, place the noindex directive in the original static HTML.",
+      "fixTemplate": "Move noindex out of JavaScript and into the static HTML: <meta name=\"robots\" content=\"noindex\" /> inside <head> in the original HTML response. Do not rely on JavaScript to inject or conditionally set noindex.",
+      "enabled": true,
+      "appliesTo": [
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "canonical-javascript-best-practice",
+      "name": "Canonical tag inconsistent in JavaScript page",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Google has clarified that canonicalization happens both before and after rendering for JavaScript pages. To make the canonical URL as clear as possible: set the canonical URL in the original HTML to the same URL as the intended canonical. If that is not possible (e.g., the canonical is determined dynamically), leave the canonical tag out of the original HTML entirely rather than setting an incorrect one that conflicts with the post-render canonical.",
+      "fixTemplate": "Ensure <link rel=\"canonical\" href=\"{{CANONICAL_URL}}\" /> in the original static HTML matches the canonical URL you intend. If the canonical is set dynamically via JavaScript, remove it from the original HTML to avoid conflicting signals.",
+      "enabled": true,
+      "appliesTo": [
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls",
+        "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "favicon-aspect-ratio",
+      "name": "Favicon incorrect size, aspect ratio, or unsupported file format",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Google requires favicons to have a 1:1 (square) aspect ratio and be at least 8x8px in size. A higher resolution favicon of at least 48x48px is strongly recommended for display quality in SERPs. Non-square or undersized favicons will not be shown in Google Search results. Google has updated the favicon documentation to explicitly list the supported favicon file formats rather than linking to an external reference that evolved over time. Only use file formats explicitly listed in Google's favicon documentation to ensure eligibility. The supported formats have not changed; the documentation now makes them explicit.",
+      "fixTemplate": "Ensure your favicon is square (1:1 aspect ratio), at least 48x48px, and uses a file format explicitly listed in Google's favicon documentation (https://developers.google.com/search/docs/appearance/favicon-in-search). Update <link rel=\"icon\" href=\"/favicon.png\" /> to reference a correctly sized image in a supported format.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/favicon-in-search"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-08-29)",
+      "lastUpdated": "2026-08-29"
+    },
+    {
+      "id": "inp-core-web-vital",
+      "name": "INP (Interaction to Next Paint) not optimized",
+      "severity": "warning",
+      "category": "performance",
+      "description": "Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital in March 2024. INP measures the latency of all interactions on a page throughout its lifecycle, not just the first one. A good INP score is under 200ms. Poor INP directly impacts page experience ranking signals.",
+      "fixTemplate": "Measure INP using Chrome DevTools, PageSpeed Insights, or the web-vitals JavaScript library. Optimize by reducing long tasks, minimizing main thread blocking, and deferring non-critical JavaScript. Target an INP score below 200ms.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://web.dev/inp/",
+        "https://developers.google.com/search/docs/appearance/core-web-vitals"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "missing-fid",
+      "name": "FID (First Input Delay) optimization",
+      "severity": "info",
+      "category": "performance",
+      "description": "DEPRECATED: First Input Delay (FID) is no longer a Core Web Vital as of March 2024. It has been replaced by Interaction to Next Paint (INP). This rule has been disabled. See the inp-core-web-vital rule instead.",
+      "fixTemplate": "This rule is deprecated. Refer to the inp-core-web-vital rule for the current Core Web Vital interaction metric.",
+      "enabled": false,
+      "deprecationReason": "FID was removed as a Core Web Vital in March 2024 and replaced by INP (Interaction to Next Paint). Google Search Central documentation confirmed this change.",
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://web.dev/inp/"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "image-preferred-source-metadata",
+      "name": "Missing image metadata for Search/Discover thumbnails",
+      "severity": "info",
+      "category": "images",
+      "description": "Google uses both schema.org markup and the og:image tag as sources when determining image thumbnails in Google Search and Discover. To increase the likelihood of your preferred image being selected, specify it consistently using both og:image and schema.org image properties in your structured data.",
+      "fixTemplate": "Add og:image: <meta property=\"og:image\" content=\"https://yourdomain.com/preferred-image.jpg\" /> and include the same image URL in your JSON-LD: {\"@type\":\"Article\",\"image\":\"https://yourdomain.com/preferred-image.jpg\"}",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/google-images",
+        "https://developers.google.com/search/docs/appearance/structured-data/article"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "breadcrumbs-desktop-only",
+      "name": "Breadcrumb rich results only appear on desktop",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google has clarified that breadcrumb rich results only appear on desktop search results, not on mobile. This is because breadcrumbs get truncated on smaller screens and are not as useful to mobile searchers. Breadcrumb structured data is still recommended for desktop SEO benefit.",
+      "fixTemplate": "Breadcrumb structured data is still worth implementing for desktop rich results. Add JSON-LD: <script type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"BreadcrumbList\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https://yourdomain.com\"}]}</script>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/breadcrumb"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "video-transparency",
+      "name": "Video thumbnail has excessive transparency",
+      "severity": "warning",
+      "category": "images",
+      "description": "Google requires that at least 80% of video thumbnail pixels have little or no transparency to enable video indexing. Thumbnails with more than 20% transparent pixels may prevent the video from being indexed and appearing in video search results.",
+      "fixTemplate": "Replace your video thumbnail with an image where at least 80% of pixels are opaque. Avoid PNG thumbnails with large transparent areas. Use JPEG or a fully opaque PNG/WebP instead.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/video"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "structured-data-javascript-initial-html",
+      "name": "Structured data not in initial HTML (JavaScript-generated)",
+      "severity": "warning",
+      "category": "schema",
+      "description": "Google recommends putting structured data markup (especially for ecommerce/product pages) in the initial HTML response for best results. While JavaScript-generated structured data is supported, it requires Googlebot to fully render the page before the markup is available, which can delay indexing and rich result eligibility. Additionally, ensure your server can handle increased traffic if generating structured data with JavaScript.",
+      "fixTemplate": "Move your JSON-LD structured data into the initial server-rendered HTML response rather than injecting it via JavaScript. For Next.js/Nuxt/SvelteKit, render the JSON-LD block server-side.",
+      "enabled": true,
+      "appliesTo": [
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/javascript/generate-dynamic-content"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "mobile-version-links",
+      "name": "Mobile version missing links present on desktop",
+      "severity": "warning",
+      "category": "technical",
+      "description": "For large websites with separate HTML on mobile and desktop versions, Google has noted that the discovery of new pages can be slower if the mobile version does not include all the links present on the desktop version. Since Google uses mobile-first indexing, missing links on the mobile version means those linked pages may be discovered and indexed more slowly.",
+      "fixTemplate": "Audit your mobile HTML template to ensure all navigation links, internal links, and pagination links present in the desktop version are also present in the mobile version. Avoid hiding links in mobile-only CSS or JavaScript that Googlebot cannot access.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "review-snippet-requires-comment",
+      "name": "Review schema missing comment or author requirements",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google recommends implementing a review setup that only accepts ratings and reviews accompanied by both a review comment and the author's name. This approach helps users understand the context for a given rating and improves eligibility for review rich results. Additionally, avoid using multiple ways of indicating what is being reviewed in the same review or aggregate rating structured data block, as this creates ambiguity that can prevent Google from correctly interpreting your markup.",
+      "fixTemplate": "In your review structured data, always include both reviewBody and author fields: {\"@type\":\"Review\",\"reviewBody\":\"Detailed review text here\",\"author\":{\"@type\":\"Person\",\"name\":\"Reviewer Name\"},\"reviewRating\":{\"@type\":\"Rating\",\"ratingValue\":\"5\"}}. Ensure only one method is used to indicate what is being reviewed.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/review-snippet"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "practice-problem-schema-deprecated",
+      "name": "Practice problem structured data is deprecated",
+      "severity": "warning",
+      "category": "schema",
+      "description": "The practice problem structured data type is no longer shown in Google Search results. Implementing this schema will have no effect on search appearance.",
+      "fixTemplate": "Remove practice problem JSON-LD structured data from your pages. It will no longer produce rich results in Google Search.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/practice-problems"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "jsonld-has-type",
+        "schemaType": "PracticeProblem"
+      }
+    },
+    {
+      "id": "special-announcement-schema-deprecated",
+      "name": "Special announcement structured data is deprecated",
+      "severity": "warning",
+      "category": "schema",
+      "description": "Google deprecated the special announcement structured data feature starting July 31, 2025. This schema type will no longer appear in Google Search results. Implementing it will have no effect on search appearance.",
+      "fixTemplate": "Remove SpecialAnnouncement JSON-LD structured data from your pages. It will no longer produce rich results in Google Search as of July 31, 2025.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/special-announcements"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "jsonld-has-type",
+        "schemaType": "SpecialAnnouncement"
+      }
+    },
+    {
+      "id": "missing-hreflang",
+      "name": "Missing hreflang for multilingual/multiregional pages",
+      "severity": "warning",
+      "category": "technical",
+      "description": "For pages that have alternate versions in different languages or for different regions, hreflang tags tell Google which version to serve to which users. Without hreflang, Google may serve the wrong language version to users, reducing click-through rates and user satisfaction. Important: hreflang alternate link elements must not be combined with certain other attributes that change their meaning to denote a different device or language version — doing so will cause Google to ignore the hreflang annotation for canonicalization purposes.",
+      "fixTemplate": "Add hreflang link elements inside <head> for each language/region variant: <link rel=\"alternate\" hreflang=\"en\" href=\"https://yourdomain.com/en/page\" /> <link rel=\"alternate\" hreflang=\"fr\" href=\"https://yourdomain.com/fr/page\" /> <link rel=\"alternate\" hreflang=\"x-default\" href=\"https://yourdomain.com/page\" />. Do not add other attributes to these link elements that would change their meaning.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/specialty/international/localization"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "sitemap-recommended",
+      "name": "No sitemap detected",
+      "severity": "info",
+      "category": "technical",
+      "description": "Sitemaps help Google discover and index all pages on your site, especially important for large sites, new sites, or sites with pages that are not well linked internally. Google recommends submitting a sitemap via Google Search Console.",
+      "fixTemplate": "Create a sitemap.xml at the root of your domain (https://yourdomain.com/sitemap.xml) and submit it in Google Search Console. Reference it in your robots.txt: Sitemap: https://yourdomain.com/sitemap.xml",
+      "enabled": true,
+      "appliesTo": [
+        "html"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "json-ld-recommended-format",
+      "name": "Structured data not using recommended JSON-LD format",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google recommends JSON-LD as the preferred format for structured data because it is generally the easiest for website owners to implement and maintain. While Microdata and RDFa are also supported and equally valid, JSON-LD is the format used in all Google documentation examples and is the easiest to add without modifying existing HTML.",
+      "fixTemplate": "Convert your Microdata or RDFa structured data to JSON-LD format: <script type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"{{TYPE}}\", ...}</script> placed inside <head> or <body>.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "read-more-deeplink",
+      "name": "Content structure may not support 'read more' deep links",
+      "severity": "info",
+      "category": "meta",
+      "description": "Google supports 'read more' deep links in search result snippets, which allow users to jump directly to relevant sections of a page. To increase the likelihood of your content appearing with a 'read more' deeplink in Google Search results, ensure your page content is well-structured with clear sections and headings that Google can identify as distinct entry points.",
+      "fixTemplate": "Structure your page content with clear, descriptive headings (h2, h3) for each major section. Ensure sections have meaningful anchor IDs: <h2 id=\"section-name\">Section Title</h2>. This helps Google identify deep-linkable sections for 'read more' snippet features.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/snippet"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "javascript-non-200-rendering",
+      "name": "JavaScript may not execute on non-200 HTTP status pages",
+      "severity": "warning",
+      "category": "technical",
+      "description": "While pages with a 200 HTTP status code are sent to Googlebot's rendering pipeline, this may not be the case for pages with non-200 status codes (e.g., 404, 301, 500). If your page relies on JavaScript to render critical content or meta tags and returns a non-200 status code, that JavaScript may not be executed by Googlebot, meaning the rendered content will not be seen.",
+      "fixTemplate": "Ensure that pages returning non-200 HTTP status codes do not rely on JavaScript to render critical SEO signals (title, meta description, canonical, structured data, noindex). Place all critical signals in the static HTML response. Verify your server returns the correct HTTP status code for each page type.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "javascript-paywall-detection",
+      "name": "JavaScript-based paywall hinders Google content classification",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Using JavaScript to implement a paywall makes it difficult for Google to automatically determine which content is paywalled and which is freely accessible. This can lead to incorrect classification of your content, potentially causing indexing issues or misrepresentation in search results. Google recommends using structured data (NewsArticle with isAccessibleForFree and hasPart) to clearly signal paywalled content.",
+      "fixTemplate": "Implement paywall signaling using structured data instead of relying solely on JavaScript. Add JSON-LD: {\"@type\":\"NewsArticle\",\"isAccessibleForFree\":false,\"hasPart\":{\"@type\":\"WebPageElement\",\"isAccessibleForFree\":false,\"cssSelector\":\".paywall-content\"}}. Ensure the paywall boundary is clearly defined in both HTML structure and structured data.",
+      "enabled": true,
+      "appliesTo": [
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/paywalled-content"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "hreflang-no-combined-attributes",
+      "name": "hreflang link element has conflicting attributes",
+      "severity": "warning",
+      "category": "technical",
+      "description": "hreflang alternate link elements must not be combined with certain other attributes that change their meaning to denote a different device or language version. Adding such attributes causes Google to ignore the hreflang annotation for canonicalization purposes, breaking your international targeting signals.",
+      "fixTemplate": "Review your hreflang link elements and remove any additional attributes that alter their semantic meaning. A valid hreflang element should only have rel=\"alternate\", hreflang=\"{{LANG_CODE}}\", and href=\"{{URL}}\": <link rel=\"alternate\" hreflang=\"en\" href=\"https://yourdomain.com/en/page\" />",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/specialty/international/localization"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "review-no-multiple-reviewed-entities",
+      "name": "Review schema uses multiple ways to indicate reviewed entity",
+      "severity": "warning",
+      "category": "schema",
+      "description": "Google has clarified that site owners should avoid using multiple ways of indicating what is being reviewed in review and aggregate rating structured data. Using multiple methods to specify the reviewed entity creates ambiguity and can prevent Google from correctly interpreting your review markup, reducing eligibility for review rich results.",
+      "fixTemplate": "In your review or AggregateRating structured data, use only one method to indicate what is being reviewed. Choose either the itemReviewed property or nesting within the reviewed item's schema — do not use both simultaneously. Example: {\"@type\":\"AggregateRating\",\"itemReviewed\":{\"@type\":\"Product\",\"name\":\"Product Name\"},\"ratingValue\":\"4.5\",\"reviewCount\":\"100\"}",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/review-snippet"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "robots-txt-unsupported-fields",
+      "name": "robots.txt contains unsupported fields",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Google has clarified that fields not explicitly listed in its robots.txt documentation are not supported. Using unsupported fields in robots.txt will have no effect on Googlebot's crawling behavior and may cause confusion. Only use documented directives: User-agent, Allow, Disallow, Sitemap, and Crawl-delay (note: Crawl-delay is not supported by Google but is listed for reference).",
+      "fixTemplate": "Review your robots.txt file and remove any directives not listed in Google's robots.txt specification. Supported Google directives are: User-agent, Allow, Disallow, and Sitemap. Reference: https://developers.google.com/search/docs/crawling-indexing/robots/robots_txt",
+      "enabled": true,
+      "appliesTo": [
+        "html"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/robots/robots_txt"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "merchant-shipping-policy-schema",
+      "name": "Missing merchant shipping policy structured data",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google now supports merchant-level shipping policy markup in Search. Adding shipping policy structured data helps Google display accurate shipping information in merchant listings and product rich results, improving click-through rates for ecommerce pages.",
+      "fixTemplate": "Add shipping policy structured data to your merchant or organization schema: {\"@type\":\"Organization\",\"shippingDetails\":{\"@type\":\"OfferShippingDetails\",\"shippingRate\":{\"@type\":\"MonetaryAmount\",\"value\":\"5.99\",\"currency\":\"USD\"},\"deliveryTime\":{\"@type\":\"ShippingDeliveryTime\",\"handlingTime\":{\"@type\":\"QuantitativeValue\",\"minValue\":0,\"maxValue\":1,\"unitCode\":\"DAY\"},\"transitTime\":{\"@type\":\"QuantitativeValue\",\"minValue\":3,\"maxValue\":5,\"unitCode\":\"DAY\"}}}}",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/product"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "video-indexing-criteria",
+      "name": "Video may not meet indexing criteria for video search results",
+      "severity": "warning",
+      "category": "schema",
+      "description": "Videos must meet specific technical requirements and indexing criteria to appear in Google video search results. Key requirements include: the video must be accessible to Googlebot (not blocked by robots.txt or requiring login), a valid thumbnail image must be provided, the video must be the primary content of the page or clearly identified via structured data, and the video file itself must be crawlable. Sites hosting explicit videos must allow Googlebot to fetch video files or risk significant ranking drops in Video mode. VideoObject structured data now also accepts the duration property as another way to specify video duration.",
+      "fixTemplate": "Add VideoObject structured data: <script type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"VideoObject\",\"name\":\"Video Title\",\"description\":\"Video description\",\"thumbnailUrl\":\"https://yourdomain.com/thumbnail.jpg\",\"uploadDate\":\"2026-01-01T00:00:00Z\",\"contentUrl\":\"https://yourdomain.com/video.mp4\",\"duration\":\"PT5M30S\"}</script>. Ensure Googlebot can access both the page and the video file. Verify thumbnail has at least 80% opaque pixels.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/video",
+        "https://developers.google.com/search/docs/appearance/video"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "explicit-content-video-crawlable",
+      "name": "Explicit video content blocked from Googlebot",
+      "severity": "critical",
+      "category": "technical",
+      "description": "Google has updated its ranking algorithms to more strongly penalize sites that host explicit videos but do not allow Googlebot to fetch those video files. Sites that block Googlebot from accessing explicit video content may experience a significant drop in ranking, especially in Video mode. If you host explicit content, you must allow Googlebot to crawl the video files themselves.",
+      "fixTemplate": "Review your robots.txt and server configuration to ensure Googlebot is not blocked from fetching video files on your site. If you host explicit content, add explicit permission in robots.txt: User-agent: Googlebot\nAllow: /videos/\nAlso ensure video files are not behind authentication or JavaScript-only rendering.",
+      "enabled": true,
+      "appliesTo": [
+        "html"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/robots/robots_txt",
+        "https://developers.google.com/search/docs/appearance/video"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "indexing-api-spam-detection",
+      "name": "Indexing API usage subject to spam detection",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Google has clarified that submissions to the Indexing API are subject to spam detection. Attempts to exceed quotas may result in revoked API access. The default quota is intended for initial setup and testing only; additional approval is required for production usage and resource provisioning. Misuse of the Indexing API to submit spammy or low-quality URLs may result in penalties.",
+      "fixTemplate": "Use the Indexing API only for eligible content types (currently job postings and livestream video structured data). Do not attempt to use it as a general-purpose indexing shortcut. Request additional quota through the official approval process if needed. Monitor your usage to stay within approved limits.",
+      "enabled": true,
+      "appliesTo": [
+        "html"
+      ],
+      "references": [
+        "https://developers.google.com/search/apis/indexing-api/v3/quickstart"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "avif-image-format-supported",
+      "name": "Consider using AVIF image format for better compression",
+      "severity": "info",
+      "category": "images",
+      "description": "Google Search now supports AVIF as an indexable image format. AVIF offers significantly better compression than JPEG and WebP at equivalent quality levels, which can improve page load times and Core Web Vitals scores. Using AVIF for images can reduce bandwidth usage and improve LCP scores.",
+      "fixTemplate": "Convert images to AVIF format where browser support allows. Use the <picture> element to provide AVIF with WebP and JPEG fallbacks: <picture><source srcset=\"image.avif\" type=\"image/avif\" /><source srcset=\"image.webp\" type=\"image/webp\" /><img src=\"image.jpg\" alt=\"Description\" /></picture>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/google-images"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "c2pa-metadata",
+      "name": "Missing C2PA metadata for AI-generated or edited images",
+      "severity": "info",
+      "category": "images",
+      "description": "Google Search now extracts C2PA (Coalition for Content Provenance and Authenticity) metadata from images for use in the 'About this image' feature. C2PA metadata provides provenance information about how an image was created or edited, including whether AI was used. Including C2PA metadata in images helps Google accurately represent image provenance to users and supports content authenticity signals. Google now also supports the compositeWithTrainedAlgorithmicMedia IPTC digital source type for AI-composite images.",
+      "fixTemplate": "If your images are AI-generated or have been significantly edited with AI tools, embed C2PA metadata using a compatible tool or library. Ensure the IPTC digital source type is set appropriately (e.g., compositeWithTrainedAlgorithmicMedia for AI-composite images). This is especially important for news and editorial content.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/google-images"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "ai-mode-search-console",
+      "name": "AI Mode traffic now included in Search Console totals",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google has confirmed that AI Mode traffic now counts toward the overall search traffic totals in Search Console Performance reports. This means clicks, impressions, and position data from AI Mode interactions are included in your aggregate metrics. Site owners should be aware that changes in AI Mode traffic may affect their overall Search Console performance data.",
+      "fixTemplate": "No code change required. Review your Search Console Performance reports with awareness that AI Mode traffic is now included in totals. Segment your data using the Search Type filter in Search Console to distinguish between different search experience types if needed.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/ai-overviews"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "loyalty-program-schema",
+      "name": "Missing loyalty program structured data for eligible merchants",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google supports loyalty program markup in Search for merchants in eligible regions (Australia, Brazil, Canada, France, Germany, Mexico, the UK, and the US), on both desktop and mobile. Loyalty program information must be defined separately from offer-level loyalty benefits (price and points). Shipping and returns loyalty benefits are not currently supported by Google.",
+      "fixTemplate": "Add loyalty program structured data to your merchant schema. Define loyalty program information at the organization level, separate from offer-level pricing: {\"@type\":\"Organization\",\"memberOf\":{\"@type\":\"ProgramMembership\",\"name\":\"Your Loyalty Program\",\"url\":\"https://yourdomain.com/loyalty\"}}. Check Google's merchant documentation for the full property list.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/product"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "merchant-return-policy-schema",
+      "name": "Missing merchant return policy structured data",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google supports merchant return policy markup in Search. Return policy structured data must be defined under MerchantReturnPolicy. Offer-level return policies only support a subset of organization-level return policies. Product-level return policy markup takes precedence over organization-level markup. If both structured data and Merchant Center return policy settings are used, Merchant Center takes precedence for products submitted in product feeds.",
+      "fixTemplate": "Add return policy structured data: {\"@type\":\"MerchantReturnPolicy\",\"applicableCountry\":\"US\",\"returnPolicyCategory\":\"https://schema.org/MerchantReturnFiniteReturnWindow\",\"merchantReturnDays\":30,\"returnMethod\":\"https://schema.org/ReturnByMail\",\"returnFees\":\"https://schema.org/FreeReturn\"}. Place this under your Organization or Offer schema as appropriate.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/product"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "product-structured-data-single-product",
+      "name": "Product structured data on non-single-product page",
+      "severity": "warning",
+      "category": "schema",
+      "description": "Google's product rich results only support pages that focus on a single product, not category pages or pages listing multiple products. Adding Product structured data to category or listing pages will not produce rich results and may be flagged as a structured data issue in Search Console. Product variants with distinct URLs are supported as individual product pages.",
+      "fixTemplate": "Only add Product structured data to pages that feature a single product. Remove Product schema from category pages, search results pages, or any page listing multiple products. For product variants, ensure each variant has its own distinct URL with its own Product schema.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/product"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "url-parameters-best-practice",
+      "name": "URL parameters may create duplicate content",
+      "severity": "warning",
+      "category": "technical",
+      "description": "URL parameters (query strings) can cause Google to crawl and index multiple versions of the same page, wasting crawl budget and diluting ranking signals. Common problematic parameters include session IDs, tracking parameters, and sorting/filtering parameters that do not change the primary content of the page. Use canonical tags to consolidate duplicate parameter-based URLs.",
+      "fixTemplate": "For URLs with parameters that do not change page content (e.g., tracking params like ?utm_source=), add a canonical tag pointing to the clean URL: <link rel=\"canonical\" href=\"https://yourdomain.com/page\" />. For faceted navigation parameters, consider using robots.txt or noindex to prevent crawling of low-value parameter combinations.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/url-structure"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "safe-search-explicit-tagging",
+      "name": "Explicit content page missing SafeSearch rating tag",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Pages containing explicit adult content should use the rating=adult meta tag to help Google's SafeSearch system correctly classify the content. Without this tag, Google's algorithms attempt to automatically detect explicit content, which may result in incorrect classification. Explicit content should also be grouped in a separate location on the site where possible. Sites must also moderate content and eliminate CSAM and non-consensual content to comply with Google's policies.",
+      "fixTemplate": "Add the SafeSearch rating meta tag to explicit content pages: <meta name=\"rating\" content=\"adult\" /> inside <head>. Additionally, consider organizing explicit content under a dedicated subdirectory (e.g., /adult/) to help Google's algorithms correctly identify and classify the content.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/safesearch"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "organization-markup",
+      "name": "Missing Organization structured data",
+      "severity": "info",
+      "category": "schema",
+      "description": "Organization markup helps Google understand your business and can influence which logo is shown in Google Search knowledge panels and search results. Some properties are used visibly (such as logo), while others are used behind the scenes for entity disambiguation. Organization markup can include business identifiers, contact information, legal name, and social profile links. The organization markup documentation has been updated to clarify that some properties influence which logo is shown while others are used behind the scenes.",
+      "fixTemplate": "Add Organization structured data to your homepage or site-wide template: <script type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"Organization\",\"name\":\"Your Company Name\",\"url\":\"https://yourdomain.com\",\"logo\":\"https://yourdomain.com/logo.png\",\"sameAs\":[\"https://www.linkedin.com/company/yourcompany\",\"https://twitter.com/yourcompany\"]}</script>",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/organization"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "site-name-schema",
+      "name": "Missing WebSite structured data for site name",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google uses WebSite structured data to determine the preferred site name to display in search results. Site names are supported at the domain and subdomain level (not subdirectory level) and are now available in all languages where Google Search is available. Without WebSite schema, Google will attempt to determine the site name automatically from page content, which may not match your preferred name. A previous issue preventing site names from propagating to internal pages has been resolved.",
+      "fixTemplate": "Add WebSite structured data to your homepage: <script type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"WebSite\",\"name\":\"Your Site Name\",\"url\":\"https://yourdomain.com\"}</script>. This should be placed on the homepage only.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/site-names"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "preferred-sources-feature",
+      "name": "Missing preferred sources markup or configuration",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google's preferred sources feature is now available in all languages where Google Search is available, and has been expanded to also appear in AI Overviews and AI Mode. This feature allows publishers to help their audience find their site as a preferred source in Google Search, AI Overviews, and AI Mode. Publishers can now implement a custom, interactive button to guide their audience to set them as a preferred source, ensuring a seamless experience where users are brought right back to where they left off. Publishers should ensure their site is properly configured to take advantage of this feature, which can increase visibility and direct traffic from users who prefer specific sources across all Google Search surfaces.",
+      "fixTemplate": "Review Google's preferred sources documentation to understand eligibility and configuration requirements. Implement the new custom interactive button to guide your audience to set your site as a preferred source — instructions are available in the preferred sources documentation. Ensure your site's identity signals (Organization schema, site name schema, canonical URLs) are correctly implemented to help Google identify your site as a preferred source for relevant queries across Search, AI Overviews, and AI Mode. Download and use the updated translated button assets available in the preferred sources documentation.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/preferred-sources",
+        "https://developers.google.com/search/docs/appearance/ai-features",
+        "https://developers.google.com/search/docs/appearance/ai-overviews"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-08-29)",
+      "lastUpdated": "2026-08-29"
+    },
+    {
+      "id": "event-structured-data-requirements",
+      "name": "Event structured data on ineligible event page",
+      "severity": "warning",
+      "category": "schema",
+      "description": "To be eligible for the event experience on Google, events must be bookable by the general public and held at a physical location. Online-only events and events that are not publicly bookable are not eligible for the event rich result experience. Adding Event structured data to ineligible events will not produce rich results.",
+      "fixTemplate": "Only add Event structured data to events that are (1) bookable by the general public and (2) held at a physical location. Ensure your Event schema includes a valid location property with a Place type: {\"@type\":\"Event\",\"name\":\"Event Name\",\"startDate\":\"2026-06-01T10:00\",\"location\":{\"@type\":\"Place\",\"name\":\"Venue Name\",\"address\":{\"@type\":\"PostalAddress\",\"streetAddress\":\"123 Main St\",\"addressLocality\":\"City\",\"addressCountry\":\"US\"}}}",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/event"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08"
+    },
+    {
+      "id": "dataset-schema-phased-out",
+      "name": "Dataset structured data is being phased out from Google Search",
+      "severity": "warning",
+      "category": "schema",
+      "description": "As part of Google's ongoing efforts to simplify the search results page, the Dataset structured data type is being phased out from Google Search results. Implementing Dataset schema will have diminishing effect on search appearance in Google Search. Note: Dataset structured data may still be used by other Google products such as Google Dataset Search.",
+      "fixTemplate": "Be aware that Dataset structured data will no longer produce rich results in Google Search. You may leave existing Dataset schema in place for use by other search engines and Google Dataset Search, but do not prioritize implementing it for Google Search rich result purposes.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/dataset"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates",
+      "lastUpdated": "2026-05-08",
+      "check": {
+        "type": "jsonld-has-type",
+        "schemaType": "Dataset"
+      }
+    },
+    {
+      "id": "generative-ai-optimization",
+      "name": "Content not optimized for generative AI Search features",
+      "severity": "info",
+      "category": "meta",
+      "description": "Google has published an official guide on optimizing content for generative AI features in Search (AI Overviews, AI Mode, etc.). Key guidance includes: (1) Provide non-commodity content with a unique point of view — first-hand reviews and expert takes outperform summaries of existing content; commodity content (e.g., generic listicles) adds little unique value. (2) Standard SEO best practices remain the foundation — generative AI features use RAG (Retrieval-Augmented Generation) grounded in Google's core Search ranking systems, so pages must be indexed and eligible to appear in Search with a snippet. In addition, a site must be included in Search generative AI features in Search Console to be eligible for display in generative AI features. (3) Add high-quality images and video where relevant — generative AI features can surface images and video, creating additional visibility opportunities beyond web page links. (4) Avoid creating content primarily to target fanout queries or every variation of a search — doing so to manipulate rankings violates Google's scaled content abuse spam policy. (5) Semantic HTML: it is not required to have perfectly semantic HTML, but using semantic HTML is generally a good idea as it helps screen readers and other users parse and navigate pages more easily. (6) Good page experience matters: ensure your site displays well across all devices, reduces latency, and makes it easy for people to distinguish main content from other elements. (7) Local business and ecommerce: use Merchant Center feeds and Google Business Profiles to help products and services appear in AI responses and other Google Search results. (8) Myth-busting: you do NOT need to create llms.txt files, Markdown files, or other AI-specific machine-readable files — Google may crawl them but treats them no differently. You do NOT need to chunk content into small pieces. You do NOT need to rewrite content in a specific style for AI. You do NOT need to seek inauthentic mentions. You do NOT need to over-invest in structured data specifically for AI features (structured data is still recommended for rich results generally). (9) Agentic experiences: browser agents may access your site by analyzing visual renderings, DOM structure, and the accessibility tree — review Google's agent-friendly website best practices if relevant to your business. The Universal Commerce Protocol (UCP) is an emerging standard for Search agents. (10) Spam policies apply to generative AI responses — content violating spam policies may be excluded from AI features. (11) Measure AI feature visibility using the Generative AI performance report in Search Console.",
+      "fixTemplate": "Review Google's official AI optimization guide at https://developers.google.com/search/docs/fundamentals/ai-optimization-guide. Focus on: (1) creating non-commodity, uniquely valuable content based on first-hand expertise; (2) ensuring your structured data, meta tags, canonical tags, and page signals are correctly implemented per standard SEO best practices; (3) providing rich images and video content with proper alt text and structured data; (4) ensuring pages are indexed and eligible to appear in Google Search with a snippet (no nosnippet directive); (5) verifying your site is included in Search generative AI features in Search Console; (6) using semantic HTML where possible for human readability and accessibility; (7) ensuring good page experience across all devices; (8) using Merchant Center feeds and Google Business Profiles for local and ecommerce content; (9) avoiding scaled content abuse tactics such as creating large volumes of pages targeting fanout query variations; (10) monitoring AI feature performance via the Generative AI performance report in Search Console. Do not invest time in llms.txt files, content chunking, or other AI-specific tactics not supported by Google's documentation.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/fundamentals/ai-optimization-guide",
+        "https://developers.google.com/search/docs/appearance/ai-features",
+        "https://developers.google.com/search/docs/essentials/spam-policies"
+      ],
+      "source": "Google AI Optimization Guide — https://developers.google.com/search/docs/fundamentals/ai-optimization-guide and Google AI Features in Search — https://developers.google.com/search/docs/appearance/ai-features (scraped 2026-08-20)",
+      "lastUpdated": "2026-08-20"
+    },
+    {
+      "id": "spam-policies-apply-to-ai-responses",
+      "name": "Spam policies apply to generative AI Search responses",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Google has explicitly clarified that its spam policies apply to all of Google Search, including generative AI responses such as AI Overviews and AI Mode. Content that violates Google's spam policies — including cloaking, doorway pages, scaled content abuse, site reputation abuse, and other tactics — may be excluded from or penalized in generative AI features, not just traditional search results. This means spam policy compliance is now doubly important as it affects both organic rankings and AI feature inclusion.",
+      "fixTemplate": "Audit your site against Google's spam policies at https://developers.google.com/search/docs/essentials/spam-policies. Ensure your content does not use cloaking, doorway pages, scaled content abuse, site reputation abuse, or other prohibited tactics. Compliance is required for both traditional search results and generative AI features.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/essentials/spam-policies",
+        "https://developers.google.com/search/docs/appearance/ai-overviews"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-05-19)",
+      "lastUpdated": "2026-05-19"
+    },
+    {
+      "id": "follow-feature-removed",
+      "name": "Google Discover Follow feature no longer available",
+      "severity": "info",
+      "category": "technical",
+      "description": "The Follow feature in Google Discover is no longer shown. Google has removed guidance on the Follow feature from its Discover documentation. If you previously implemented RSS feed best practices specifically for the Follow feature (e.g., descriptive feed titles, single consolidated feed), those practices remain good general RSS hygiene but will no longer affect Follow feature eligibility since the feature no longer exists.",
+      "fixTemplate": "No immediate action required. If you have RSS feeds configured specifically for the Follow feature, you may leave them in place as they serve general syndication purposes. Remove any Follow-specific implementation guidance from your internal documentation to avoid confusion.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/google-discover"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-05-19)",
+      "lastUpdated": "2026-05-19",
+      "check": {
+        "type": "raw-match",
+        "pattern": "application\\/(rss|atom)\\+xml"
+      }
+    },
+    {
+      "id": "sitelinks-searchbox-removed",
+      "name": "Sitelinks search box no longer available in Google Search",
+      "severity": "info",
+      "category": "schema",
+      "description": "The sitelinks search box feature is no longer available in Google Search. The nositelinkssearchbox robots meta tag is therefore no longer needed. Any SearchAction structured data implemented specifically to enable the sitelinks search box will have no effect on search appearance. Google has removed the sitelinks search box documentation.",
+      "fixTemplate": "Remove or stop adding SearchAction structured data that was implemented specifically for the sitelinks search box feature. You may also remove any nositelinkssearchbox robots meta tags as they are no longer needed. Existing SearchAction markup will not cause harm but will have no effect on Google Search.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/sitelinks-searchbox"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-05-19)",
+      "lastUpdated": "2026-05-19",
+      "check": {
+        "type": "jsonld-has-type",
+        "schemaType": "SearchAction"
+      }
+    },
+    {
+      "id": "googlebot-file-size-limits",
+      "name": "Page or resource may exceed Googlebot file size limits",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Googlebot has documented file size limits for the pages it fetches. Pages or subresources (JavaScript, CSS) that exceed these limits may not be fully crawled or rendered by Googlebot, potentially causing critical SEO signals (structured data, meta tags, content) to be missed. The 15MB fetch size limit applies to the initial HTML fetch as well as individual subresources referenced in the HTML, particularly JavaScript and CSS files.",
+      "fixTemplate": "Audit your page HTML size and the size of critical JavaScript and CSS files. Ensure no individual resource exceeds 15MB. Use code splitting, lazy loading, and minification to reduce resource sizes. Verify using Google Search Console's URL Inspection tool that Googlebot can fully render your pages.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/googlebot"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-05-19)",
+      "lastUpdated": "2026-05-19"
+    },
+    {
+      "id": "recipe-thumbnail-property",
+      "name": "Recipe thumbnail property used for non-recipe image selection",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google has clarified that the thumbnail property in Recipe structured data is only used for recipe rich results, not for selecting text result images. If you want to influence which image Google uses for text search results or Discover thumbnails for recipe pages, use og:image or the image property in your structured data instead of relying on the thumbnail property.",
+      "fixTemplate": "For recipe pages, use the image property (not thumbnail) in your Recipe JSON-LD to specify the preferred image for text search results: {\"@type\":\"Recipe\",\"image\":\"https://yourdomain.com/recipe-image.jpg\", ...}. Also add <meta property=\"og:image\" content=\"https://yourdomain.com/recipe-image.jpg\" /> for Discover thumbnail selection.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/recipe"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-05-19)",
+      "lastUpdated": "2026-05-19"
+    },
+    {
+      "id": "core-updates-continuous",
+      "name": "Site not prepared for continuous Google core updates",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google has clarified that it continuously makes updates to its search algorithms, including smaller core updates in addition to major named core updates. Site owners that make content improvements can see a rise in position in Google Search results without having to wait for the next major core update. This means ongoing content quality improvements have a more immediate impact than previously understood, and sites should treat SEO as a continuous process rather than waiting for major update cycles.",
+      "fixTemplate": "No specific code change required. Treat content quality improvements as an ongoing process rather than waiting for major Google core update cycles. Monitor Google Search Console performance data regularly and make incremental improvements to content quality, E-E-A-T signals, and technical SEO. Improvements may be reflected in rankings sooner than expected.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/core-updates"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-05-19)",
+      "lastUpdated": "2026-05-19"
+    },
+    {
+      "id": "south-africa-carousel-structured-data",
+      "name": "South Africa carousel structured data supports additional query types",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google's structured data carousels (beta) feature in South Africa now supports additional query types including food delivery, car hire, and bus booking, in addition to previously supported types. If you operate a site in South Africa in these verticals, implementing the carousel structured data markup may make your content eligible for carousel rich results in Google Search.",
+      "fixTemplate": "If your site operates in South Africa and covers food delivery, car hire, or bus booking verticals, review Google's structured data carousels (beta) documentation to implement the appropriate carousel markup. The markup must be placed on summary pages that link out to detail pages on your website.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/carousels"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-05-19)",
+      "lastUpdated": "2026-05-19"
+    },
+    {
+      "id": "llms-txt-not-required",
+      "name": "llms.txt and AI-specific markup files not required",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google has explicitly clarified that creating llms.txt files, Markdown files, or any other special machine-readable files or markup specifically for generative AI search is not required and confers no special treatment. Google may discover, crawl, and index such files as it would any other file on a website, but they are not treated in a special way for AI feature inclusion. Similarly, there is no requirement to 'chunk' content into smaller pieces for AI systems — Google's systems can understand the nuance of multiple topics on a page and show the relevant piece to users. Site owners should not invest time in creating these files as an AI optimization tactic.",
+      "fixTemplate": "Do not create llms.txt or other AI-specific markup files as an SEO tactic. If you have already created such files, they will not cause harm but will have no special effect on your visibility in Google's generative AI features. Focus on standard SEO best practices instead.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/fundamentals/ai-optimization-guide"
+      ],
+      "source": "Google AI Optimization Guide — https://developers.google.com/search/docs/fundamentals/ai-optimization-guide (scraped 2026-05-24)",
+      "lastUpdated": "2026-05-24",
+      "check": {
+        "type": "raw-match",
+        "pattern": "llms\\.txt"
+      }
+    },
+    {
+      "id": "ai-features-snippet-eligibility",
+      "name": "Page not eligible for AI features due to snippet, indexing, or Search Console requirements",
+      "severity": "critical",
+      "category": "technical",
+      "description": "To be eligible to appear as a supporting link in Google AI Overviews or AI Mode, a page must meet three conditions: (1) it must be indexed by Google, (2) it must be eligible to be shown in Google Search with a snippet, and (3) the site must be included in Search generative AI features in Search Console. Pages that are noindexed, blocked from crawling via robots.txt, or that have snippet preview controls set to 'nosnippet' will not appear in AI features. There are no additional technical requirements beyond the standard Google Search technical requirements. Ensuring crawling is allowed in robots.txt and by any CDN or hosting infrastructure, making content findable through internal linking and sitemaps, ensuring important content is available in textual form, and keeping information up-to-date are all worthwhile practices. If you apply a preview control (e.g., nosnippet) and still see your content appearing in AI features, verify the control is correct and visible to Googlebot using the URL Inspection tool, then allow time for Google to recrawl and process the change — crawling can take several days to several months.",
+      "fixTemplate": "Verify your page meets all standard Google Search technical requirements: (1) confirm the page is not blocked by robots.txt — check with Google Search Console's robots.txt tester; (2) confirm no noindex meta tag or X-Robots-Tag header is present; (3) confirm no 'nosnippet' robots directive is set, as this will prevent the page from appearing in AI features; (4) ensure the page returns a 200 HTTP status code; (5) verify your site is included in Search generative AI features in Search Console. Use Google Search Console URL Inspection to verify indexing status. If you have applied a preview control and still see content in AI features, use the URL Inspection tool to confirm Googlebot received the correct HTML, then allow several days to months for recrawling.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/ai-features",
+        "https://developers.google.com/search/docs/fundamentals/ai-optimization-guide",
+        "https://developers.google.com/search/docs/crawling-indexing/block-indexing"
+      ],
+      "source": "Google AI Features in Search — https://developers.google.com/search/docs/appearance/ai-features (scraped 2026-08-20)",
+      "lastUpdated": "2026-08-20",
+      "check": {
+        "type": "field-contains",
+        "field": "metaRobots",
+        "value": "nosnippet"
+      }
+    },
+    {
+      "id": "agent-friendly-website",
+      "name": "Website not optimized for AI browser agents",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google has introduced guidance on preparing websites for AI browser agents, which are autonomous systems that can perform tasks on behalf of users such as booking reservations or comparing product specifications. Browser agents may access websites by analyzing visual renderings (screenshots), inspecting the DOM structure, and interpreting the accessibility tree. Emerging protocols such as the Universal Commerce Protocol (UCP) are being developed to allow Search agents to perform more complex tasks. While this is an emerging area and not yet a ranking factor, sites that are well-structured for agent access may benefit as agentic search experiences mature.",
+      "fixTemplate": "Review Google's agent-friendly website best practices guide. Key considerations include: (1) ensure your DOM structure is clean and semantically meaningful so agents can interpret page structure; (2) ensure your accessibility tree is well-formed (proper ARIA labels, roles, and landmarks) as agents use it to understand interactive elements; (3) ensure critical actions (e.g., booking, purchasing) are accessible without JavaScript-only interactions where possible; (4) review the Universal Commerce Protocol (UCP) documentation as it becomes available for ecommerce and booking use cases.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/fundamentals/ai-optimization-guide",
+        "https://developers.google.com/search/docs/appearance/ai-features"
+      ],
+      "source": "Google AI Optimization Guide — https://developers.google.com/search/docs/fundamentals/ai-optimization-guide (scraped 2026-05-24)",
+      "lastUpdated": "2026-05-24"
+    },
+    {
+      "id": "bing-ai-performance-citation-eligibility",
+      "name": "Page not optimized for Bing AI citation visibility",
+      "severity": "info",
+      "category": "technical",
+      "description": "Bing has launched 'AI Performance' in Bing Webmaster Tools (now in public preview), which shows when your site's URLs are cited in AI-generated answers across Microsoft Copilot, AI-generated summaries in Bing, and select partner integrations. To be eligible for citation in Bing AI-generated answers, pages must be indexed by Bing and eligible to appear in Bing Search with a snippet. Pages blocked by robots.txt, carrying noindex directives, or carrying nosnippet directives will not be cited in Bing AI features. Site owners should monitor citation activity and URL-level citation data via Bing Webmaster Tools to understand their visibility in AI-generated answers. Standard Bing webmaster best practices — clean crawlable HTML, descriptive titles and meta descriptions, structured data, and fast page load — remain the foundation for AI citation eligibility.",
+      "fixTemplate": "Verify your pages meet Bing's standard indexing and snippet eligibility requirements: (1) confirm pages are not blocked by robots.txt; (2) confirm no noindex or nosnippet meta tags or X-Robots-Tag headers are present; (3) ensure pages return 200 HTTP status codes; (4) submit your sitemap in Bing Webmaster Tools; (5) monitor AI citation performance via the AI Performance report in Bing Webmaster Tools at https://www.bing.com/webmasters.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://blogs.bing.com/webmaster",
+        "https://www.bing.com/webmasters/help/webmaster-guidelines-30fba23a"
+      ],
+      "source": "Bing Webmaster Blog — https://blogs.bing.com/webmaster (scraped 2026-05-28)",
+      "lastUpdated": "2026-05-28"
+    },
+    {
+      "id": "preferred-sources-ai-mode",
+      "name": "Preferred sources not configured for AI Mode and AI Overviews",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google has updated the preferred sources feature to now be available in AI Overviews and AI Mode, in addition to standard Google Search. Publishers who have configured preferred sources can now benefit from increased visibility in AI-generated search experiences. To take advantage of this, sites must meet the eligibility requirements for the preferred sources feature and ensure their identity signals (Organization schema, site name schema, canonical URLs) are correctly implemented.",
+      "fixTemplate": "Review Google's preferred sources documentation to understand eligibility and configuration requirements for AI Overviews and AI Mode. Ensure your site's identity signals are correctly implemented: Organization schema, WebSite schema with site name, and consistent canonical URLs. Download and use the updated translated button assets if applicable.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/preferred-sources",
+        "https://developers.google.com/search/docs/appearance/ai-features"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-06-09)",
+      "lastUpdated": "2026-06-09"
+    },
+    {
+      "id": "has-adult-consideration-schema",
+      "name": "Missing hasAdultConsideration property on adult merchant listings",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google has added support for the hasAdultConsideration property in merchant listing structured data, bringing parity with the Merchant Center feed specification. This property should be used on product or offer pages that contain adult content to help Google correctly classify and filter the content in shopping experiences. Without this property, Google's algorithms must attempt to automatically detect adult content in merchant listings, which may result in incorrect classification.",
+      "fixTemplate": "Add the hasAdultConsideration property to your Product or Offer structured data for adult content listings: {\"@type\":\"Product\",\"name\":\"Product Name\",\"hasAdultConsideration\":true, ...}. This brings your structured data markup into parity with the Merchant Center feed specification for adult products.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/product"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-06-09)",
+      "lastUpdated": "2026-06-09"
+    },
+    {
+      "id": "third-party-seo-tools-guidance",
+      "name": "Third-party SEO tool recommendations not critically evaluated",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google has published new guidance on evaluating third-party SEO tools, services, and advice, including important considerations when assessing recommendations from SEO tools and consultants. Key points include: (1) not all SEO tool recommendations reflect Google's actual ranking signals or guidelines; (2) site owners should cross-reference tool recommendations against official Google Search Central documentation; (3) some SEO advice may be outdated, incorrect, or based on correlation rather than causation; (4) Google's own documentation and Search Console data should be the primary reference for SEO decisions. The guidance has been added to the page on evaluating SEO recommendations and tools.",
+      "fixTemplate": "When evaluating SEO tool recommendations: (1) cross-reference all recommendations against official Google Search Central documentation at https://developers.google.com/search/docs; (2) use Google Search Console as the primary source of truth for your site's performance data; (3) be skeptical of recommendations that cannot be traced to official Google guidance; (4) prioritize fixes flagged by Google Search Console over third-party tool warnings when they conflict.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/fundamentals/do-i-need-seo"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-06-09)",
+      "lastUpdated": "2026-06-09"
+    },
+    {
+      "id": "noindex-javascript-accessibility-outdated",
+      "name": "JavaScript content loading is not an SEO accessibility concern",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google has removed outdated guidance stating that using JavaScript to load content makes it 'harder for Google Search' or harder for assistive technologies. Google Search has been rendering JavaScript for multiple years and most assistive technologies now work with JavaScript. Site owners and SEO tools should not flag JavaScript-rendered content as an inherent SEO or accessibility problem. The concern about JavaScript content being invisible to Googlebot is no longer valid for standard client-side rendering scenarios, though server-side rendering remains a best practice for performance and reliability.",
+      "fixTemplate": "No action required if you are using JavaScript to load content. Standard client-side rendering is supported by Google Search. If you have internal documentation or tooling that flags JavaScript content loading as an SEO issue, update it to reflect current Google guidance. Server-side rendering (SSR) or static rendering is still recommended for performance and Core Web Vitals reasons, but is not required for indexing.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-06-09)",
+      "lastUpdated": "2026-06-09"
+    },
+    {
+      "id": "crawling-docs-migrated",
+      "name": "Google crawling documentation migrated to new infrastructure site",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google has migrated its core crawling documentation to a new dedicated site at Google's crawling infrastructure documentation. The migrated documentation includes: overview of Google crawlers and fetchers, verifying requests from Google crawlers, reducing Google crawl rate, Google common crawlers, how Google interprets the robots.txt specification, managing crawling of faceted navigation URLs, optimizing crawl budget, how HTTP status codes affect crawlers, and debugging DNS and network errors. The functionality and guidance has not changed — only the location of the documentation. A separate changelog feed is now available for crawling infrastructure updates at https://developers.google.com/crawling/docs/changelog/crawling_docs_updates.rss. This migration reflects that Google's crawling infrastructure is shared across multiple Google products beyond Search, including Google Shopping, News, Gemini, AdSense, and more.",
+      "fixTemplate": "Update any internal documentation, bookmarks, or tooling that references the old crawling documentation URLs to point to the new Google crawling infrastructure site. Subscribe to the new crawling infrastructure changelog feed at https://developers.google.com/crawling/docs/changelog/crawling_docs_updates.rss to receive updates about crawling behavior changes that may affect your site across all Google products, not just Search.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/googlebot",
+        "https://developers.google.com/crawling/docs/changelog/crawling_docs_updates.rss"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-06-09)",
+      "lastUpdated": "2026-06-09"
+    },
+    {
+      "id": "turkey-carousel-structured-data",
+      "name": "Structured data carousels (beta) available in Turkey",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google's structured data carousels (beta) feature has been expanded to Turkey, in addition to South Africa and other previously supported regions. If you operate a site in Turkey with summary pages that link out to detail pages (such as travel, local, shopping, or other supported query types), implementing carousel structured data markup may make your content eligible for carousel rich results in Google Search in Turkey. The markup must be placed on the summary page; you do not need to add markup to the detail pages.",
+      "fixTemplate": "If your site operates in Turkey and has summary pages that link to detail pages in supported verticals (travel, local, shopping, and others), review Google's structured data carousels (beta) documentation to implement the appropriate carousel markup. Place the markup on the summary page only. Use the interest form in the documentation to express interest in the feature.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/carousels"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-06-09)",
+      "lastUpdated": "2026-06-09"
+    },
+    {
+      "id": "spam-reports-manual-action",
+      "name": "Spam report submissions may trigger manual actions",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Google has clarified that spam report submissions may now be used to take manual action against sites that violate Google's spam policies. Previously, spam reports were used primarily to improve Google's automated systems and were not directly used to trigger manual actions. Site owners should be aware that user-submitted spam reports can now result in manual penalties. This makes compliance with Google's spam policies more important than ever, as violations are now more likely to result in direct manual action in addition to algorithmic penalties.",
+      "fixTemplate": "Audit your site against Google's full spam policies at https://developers.google.com/search/docs/essentials/spam-policies. Ensure your site does not engage in cloaking, doorway pages, scaled content abuse, site reputation abuse, back button hijacking, or any other prohibited practices. Monitor Google Search Console for any manual action notifications. If you receive a manual action, follow the reconsideration request process after resolving the violation.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/essentials/spam-policies",
+        "https://developers.google.com/search/docs/monitor-debug/manual-actions"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-06-09)",
+      "lastUpdated": "2026-06-09"
+    },
+    {
+      "id": "speakable-schema-deprecated",
+      "name": "SpeakableSpecification structured data no longer supported",
+      "severity": "warning",
+      "category": "schema",
+      "description": "The SpeakableSpecification schema type was introduced in schema.org 3.2 and promoted to core in schema.org 3.5. It was designed to indicate sections of a document particularly suitable for text-to-speech rendering. However, Google has removed Speakable from its list of supported rich result types and no longer processes SpeakableSpecification structured data for Search features. Implementing this schema type will have no effect on Google Search appearance. The schema.org type itself remains in the vocabulary for other consumers, but Google Search does not use it.",
+      "fixTemplate": "Remove or stop adding SpeakableSpecification JSON-LD structured data blocks. If you have existing Speakable schema, you may leave it in place as it will not cause harm to Google Search, but it will not produce any rich result or Search feature benefit. Example of markup to remove: {\"@type\":\"WebPage\",\"speakable\":{\"@type\":\"SpeakableSpecification\",\"cssSelector\":[\".speakable\"]}}",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://schema.org/SpeakableSpecification",
+        "https://developers.google.com/search/docs/appearance/structured-data"
+      ],
+      "source": "Schema.org Release Notes — https://schema.org/docs/releases.html (scraped 2026-06-09)",
+      "lastUpdated": "2026-06-09",
+      "check": {
+        "type": "jsonld-has-type",
+        "schemaType": "SpeakableSpecification"
+      }
+    },
+    {
+      "id": "schema-org-iptc-digital-source-type",
+      "name": "Missing IPTCDigitalSourceEnumeration for AI-generated media",
+      "severity": "info",
+      "category": "schema",
+      "description": "Schema.org version 24.0 introduced the IPTCDigitalSourceEnumeration vocabulary with 14 coded values to describe the digital source type of media, including AI-generated and algorithmically manipulated content (e.g., TrainedAlgorithmicMediaDigitalSource, CompositeWithTrainedAlgorithmicMediaDigitalSource). Schema.org version 29.4 added additional missing enumeration values to IPTCDigitalSourceEnumeration. This vocabulary is used via the digitalSourceType property on MediaObject and its subtypes (ImageObject, VideoObject, AudioObject). Correctly tagging AI-generated or AI-assisted media with the appropriate IPTC digital source type supports content provenance signals used by Google's 'About this image' feature and aligns with C2PA metadata standards. This rule complements the c2pa-metadata rule.",
+      "fixTemplate": "Add the digitalSourceType property to your ImageObject or VideoObject structured data using the appropriate IPTCDigitalSourceEnumeration value. For AI-generated images: {\"@type\":\"ImageObject\",\"contentUrl\":\"https://yourdomain.com/image.jpg\",\"digitalSourceType\":\"https://cv.iptc.org/newscodes/digitalsourcetype/trainedAlgorithmicMedia\"}. For AI-composite images use: \"https://cv.iptc.org/newscodes/digitalsourcetype/compositeWithTrainedAlgorithmicMedia\". For human-captured original content use: \"https://cv.iptc.org/newscodes/digitalsourcetype/originalDigitalCapture\".",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://schema.org/IPTCDigitalSourceEnumeration",
+        "https://schema.org/digitalSourceType",
+        "https://developers.google.com/search/docs/appearance/google-images",
+        "https://cv.iptc.org/newscodes/digitalsourcetype/"
+      ],
+      "source": "Schema.org Release Notes — https://schema.org/docs/releases.html (scraped 2026-06-09)",
+      "lastUpdated": "2026-06-09"
+    },
+    {
+      "id": "schema-org-shipping-vocabulary-updated",
+      "name": "Deprecated shipping schema types in use",
+      "severity": "warning",
+      "category": "schema",
+      "description": "Schema.org version 29.0 deprecated the DeliveryTimeSettings and ShippingRateSettings types, superseding them with new updated shipping vocabulary types. Ecommerce sites that implemented shipping structured data using the older DeliveryTimeSettings or ShippingRateSettings types should migrate to the replacement types introduced in schema.org 29.0. Using deprecated schema.org types may reduce the accuracy of shipping information displayed in Google merchant listings and product rich results over time as search engines adopt the updated vocabulary.",
+      "fixTemplate": "Audit your shipping structured data for use of the deprecated DeliveryTimeSettings and ShippingRateSettings types. Migrate to the replacement types introduced in schema.org version 29.0. Review the schema.org shipping vocabulary documentation and Google's merchant shipping policy structured data guidance for the current recommended implementation. Update your OfferShippingDetails markup to use the new type references.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://schema.org/docs/releases.html",
+        "https://schema.org/OfferShippingDetails",
+        "https://developers.google.com/search/docs/appearance/structured-data/product"
+      ],
+      "source": "Schema.org Release Notes — https://schema.org/docs/releases.html (scraped 2026-06-09)",
+      "lastUpdated": "2026-06-09",
+      "check": {
+        "type": "raw-match",
+        "pattern": "DeliveryTimeSettings|ShippingRateSettings",
+        "flags": "i"
+      }
+    },
+    {
+      "id": "site-move-domain-variants",
+      "name": "Site move guidance: include all domain variants",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Google has updated its site move guidance to explicitly include information on using the Change of Address tool for all subdomain variants (including www and non-www) during domain migrations. When performing a domain migration, domain moves work best when all variants of a site are migrated properly. Failing to migrate all subdomain variants (e.g., migrating example.com but not www.example.com, or vice versa) can result in incomplete migration signals and slower consolidation of ranking signals to the new domain.",
+      "fixTemplate": "When performing a domain migration, use the Change of Address tool in Google Search Console for all subdomain variants of your site, including both www and non-www versions. Ensure 301 redirects are in place from all variants of the old domain to the corresponding variants of the new domain. Verify each variant is submitted separately in Search Console if they are tracked as separate properties.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-06-18)",
+      "lastUpdated": "2026-06-18"
+    },
+    {
+      "id": "faq-rich-result-documentation-removed",
+      "name": "FAQ rich result documentation fully removed",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google has fully removed the FAQ rich result documentation from Google Search Central, confirming that the FAQ rich result feature is no longer shown in Google Search results. This follows the deprecation notice added in May 2026. The removal of documentation is the final confirmation that FAQ structured data will produce no rich result benefit in Google Search. The faq-schema-deprecated rule already covers the actionable guidance; this rule documents the documentation removal milestone for audit trail purposes.",
+      "fixTemplate": "No additional action required beyond what is described in the faq-schema-deprecated rule. Remove or stop adding FAQPage JSON-LD structured data. The feature is fully retired and its documentation has been removed from Google Search Central.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/faqpage"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-06-18)",
+      "lastUpdated": "2026-06-18",
+      "check": {
+        "type": "jsonld-has-type",
+        "schemaType": "FAQPage"
+      }
+    },
+    {
+      "id": "html-standard-for-seo",
+      "name": "Markdown files have no SEO advantage over HTML",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google has explicitly stated that HTML is the standard for SEO, not Markdown files. Publishing content as Markdown files (e.g., .md files served directly, or llms.txt-style Markdown documents) confers no SEO advantage over standard HTML pages. Google's crawlers and ranking systems are built around HTML as the canonical document format for the web. This complements the llms-txt-not-required rule: not only are AI-specific Markdown files unnecessary, but Markdown as a general content delivery format is not a recommended or advantaged format for SEO purposes. Content intended to rank in Google Search should be served as properly structured HTML.",
+      "fixTemplate": "Ensure your content is served as HTML pages rather than raw Markdown files. If you use a static site generator or CMS that outputs Markdown, confirm it is compiled to HTML before being served to users and Googlebot. Do not create .md files or Markdown-formatted documents as a strategy to improve SEO or AI search visibility — serve standard HTML instead.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics",
+        "https://developers.google.com/search/docs/fundamentals/ai-optimization-guide"
+      ],
+      "source": "Search Engine Roundtable — https://www.seroundtable.com (scraped 2026-06-18); headline: 'Google: HTML The Standard For SEO, Not Markdown Files'",
+      "lastUpdated": "2026-06-18",
+      "check": {
+        "type": "raw-match",
+        "pattern": "\\.md[\"'\\s]",
+        "flags": "i"
+      }
+    },
+    {
+      "id": "social-video-platform-search-console",
+      "name": "Social and video platform content not tracked in Search Console",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google has added a new guide on how to analyze social and video platform content performance in Search Console. Content creators, social media managers, and SEO professionals can now understand how their social and video platform content (e.g., YouTube videos, social posts) performs on Google Search through dedicated Search Console reporting. Site owners with social or video platform content should review this guide to understand how to measure and optimize their content's search performance across platforms.",
+      "fixTemplate": "Review the new Search Console guide on social and video platform content performance. Connect your social and video platform accounts to Search Console where supported. Monitor performance data for your platform content in Search Console Performance reports to understand how it appears in Google Search results.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/social-video-platform"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-08-20)",
+      "lastUpdated": "2026-08-20"
+    },
+    {
+      "id": "fake-incentivized-reviews-policy",
+      "name": "Fake or undisclosed incentivized reviews violate review snippet guidelines",
+      "severity": "critical",
+      "category": "schema",
+      "description": "Google has added a new guideline to the review snippet documentation specifically addressing fake and undisclosed incentivized reviews. Sites that collect or display fake reviews, or reviews where an incentive was provided but not disclosed, risk losing eligibility for review rich results and may be subject to manual action under Google's spam policies. This applies to both first-party reviews collected on your site and third-party review markup you implement. All incentivized reviews must be clearly disclosed as such. Fake reviews of any kind are prohibited.",
+      "fixTemplate": "Audit your review collection and display practices: (1) remove any fake or fabricated reviews from your structured data and visible content; (2) ensure any reviews where an incentive was provided (discount, free product, payment) are clearly labeled as incentivized; (3) update your review schema to only include genuine, unbiased reviews or properly disclosed incentivized reviews; (4) implement review policies that prohibit fake reviews and require disclosure of incentives. Do not implement ReviewSnippet structured data for reviews that violate these guidelines.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/review-snippet"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-08-20)",
+      "lastUpdated": "2026-08-20"
+    },
+    {
+      "id": "package-tracking-early-adopters-closed",
+      "name": "Package tracking early adopters program no longer accepting new partners",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google has updated the package tracking documentation to reflect that the package tracking early adopters program is no longer accepting new partners. Sites that were not already accepted into the program cannot apply to participate. Existing partners should review the updated feature availability and eligibility requirements sections of the package tracking documentation to ensure continued compliance.",
+      "fixTemplate": "If you are an existing package tracking early adopter partner, review the updated feature availability and eligibility requirements in the package tracking documentation to ensure your implementation remains compliant. If you are not yet a partner, the program is closed to new applicants — monitor Google Search Central for any future announcements about program expansion.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/package-tracking"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-08-20)",
+      "lastUpdated": "2026-08-20"
+    },
+    {
+      "id": "canonicalization-reevaluation-time",
+      "name": "Canonicalization changes take time to re-evaluate",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google has updated the canonicalization troubleshooting guide with clarifications on re-evaluation time. When you make changes to canonical tags, hreflang annotations, or other canonicalization signals, Google does not immediately re-evaluate and update its canonical selection. Site owners should set realistic expectations: canonicalization changes can take days to weeks to be reflected in Google Search, depending on crawl frequency and site size. Do not make rapid successive changes to canonical signals while waiting for previous changes to take effect, as this can create conflicting signals and further delay resolution.",
+      "fixTemplate": "After making canonicalization changes (updating canonical tags, fixing hreflang, resolving duplicate content): (1) use Google Search Console URL Inspection to request indexing of affected pages; (2) allow sufficient time (days to weeks) for Google to re-crawl and re-evaluate canonical signals before concluding a change has not worked; (3) monitor Search Console Coverage and URL Inspection reports to track canonicalization status; (4) avoid making additional conflicting canonicalization changes while waiting for previous changes to propagate.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-08-20)",
+      "lastUpdated": "2026-08-20"
+    },
+    {
+      "id": "product-category-schema",
+      "name": "Missing google_product_category in Product structured data",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google has updated the product structured data documentation to detail how the google_product_category property can be used with both Product and Offer types. This aligns with the Google Merchant Center feed specification for the google_product_category attribute. Providing both merchant-defined category information and Google-defined category information within schema.org markup enhances product information for Google Search and Shopping, improving product discoverability and classification accuracy in merchant listings.",
+      "fixTemplate": "Add category information to your Product or Offer structured data using the appropriate property for google_product_category. Include both your merchant-defined category and the Google product taxonomy category where applicable: {\"@type\":\"Product\",\"name\":\"Product Name\",\"category\":\"Your Category > Subcategory\"}. Review the Google Merchant Center product category taxonomy and the updated product structured data documentation for the specific property and value format required.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/product",
+        "https://support.google.com/merchants/answer/6324436"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-08-20)",
+      "lastUpdated": "2026-08-20"
+    },
+    {
+      "id": "sale-price-effective-date-schema",
+      "name": "Missing sale price effective date in Product structured data",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google has added a new section on 'Sale duration' to the Merchant listing guide explaining how to use schema.org properties to set the effective range for sale prices. This aligns schema.org usage with the Merchant Center feed attribute sale_price_effective_date. Specifying sale price effective dates helps Google accurately display sale pricing information in merchant listings and product rich results, including the duration of the sale. Without effective date information, Google cannot determine when a sale price is valid, which may result in incorrect or missing sale price display.",
+      "fixTemplate": "Add sale price effective date information to your Offer structured data using the priceValidUntil property and, where applicable, the priceValidFrom equivalent. Example: {\"@type\":\"Offer\",\"price\":\"19.99\",\"priceCurrency\":\"USD\",\"priceValidUntil\":\"2026-12-31\"}. For sale prices with both start and end dates, review the updated Merchant listing guide for the recommended schema.org property combination. Ensure your implementation aligns with the sale_price_effective_date attribute format used in Merchant Center feeds.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/product",
+        "https://support.google.com/merchants/answer/6324371"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-08-20)",
+      "lastUpdated": "2026-08-20"
+    },
+    {
+      "id": "amp-direct-publisher-hosting",
+      "name": "AMP Cache and signed exchanges no longer required for AMP pages",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google Search has updated how it connects users to AMP pages. Starting with this change, Google will now take users directly to the publisher's AMP host pages rather than serving them from the AMP Cache or via signed exchanges. This simplifies and reduces maintenance efforts for publishers creating AMP content. Publishers no longer need to update the AMP Cache or configure signed exchanges for their AMP content. AMP content will continue to rank just like any other web page. Existing AMP Cache configurations and signed exchange setups will not cause harm but are no longer required for AMP pages to appear in Google Search.",
+      "fixTemplate": "No immediate action required. If you maintain AMP pages: (1) you no longer need to configure or maintain signed exchanges (SXG) specifically for AMP; (2) you no longer need to manually update the AMP Cache; (3) ensure your AMP pages are accessible at their canonical publisher URLs as Google will now link directly to those URLs; (4) review and update any internal documentation that references AMP Cache or signed exchange requirements for AMP. AMP content continues to be supported and will rank normally.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/amp"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-08-20)",
+      "lastUpdated": "2026-08-20"
+    },
+    {
+      "id": "google-august-2026-spam-update",
+      "name": "Google August 2026 Spam Update released",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Google has released an August 2026 Spam Update. Spam updates target sites that violate Google's spam policies, including cloaking, doorway pages, scaled content abuse, site reputation abuse, back button hijacking, fake reviews, and other prohibited practices. Sites affected by spam updates may experience significant ranking drops or removal from Google Search results. Recovery from a spam update requires identifying and resolving the spam policy violation, then submitting a reconsideration request if a manual action was applied.",
+      "fixTemplate": "Audit your site against Google's full spam policies at https://developers.google.com/search/docs/essentials/spam-policies. Check Google Search Console for any manual action notifications. If your site experienced a traffic drop around August 2026, review your content and practices against all spam policies including: cloaking, doorway pages, scaled content abuse, site reputation abuse, back button hijacking, fake or undisclosed incentivized reviews, and link spam. Resolve any violations and submit a reconsideration request if a manual action was applied.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/essentials/spam-policies",
+        "https://developers.google.com/search/docs/monitor-debug/manual-actions"
+      ],
+      "source": "Search Engine Roundtable — https://www.seroundtable.com (scraped 2026-08-20); headline: 'Google August 2026 Spam Update Has Been Unleashed'",
+      "lastUpdated": "2026-08-20"
+    },
+    {
+      "id": "schema-org-v30-equivalence-annotations",
+      "name": "schema.org v30 equivalence annotations for GS1, Dublin Core, Open Graph",
+      "severity": "info",
+      "category": "schema",
+      "description": "Schema.org version 30.0 added GS1, Dublin Core, and Open Graph equivalence annotations and exports to the schema.org vocabulary. This means schema.org properties now have formally declared equivalences to terms in these widely-used external vocabularies. For ecommerce sites using GS1 identifiers, publishers using Dublin Core metadata, and sites using Open Graph markup, these equivalence annotations improve interoperability between schema.org structured data and other metadata systems. Sites that implement both schema.org structured data and Open Graph tags can now benefit from formally declared cross-vocabulary alignment. Additionally, version 30.0 extended credential vocabulary to allow specification of credentials beyond just educational credentials, and extended CompoundPriceSpecification to have the more generic UnitPriceSpecification.",
+      "fixTemplate": "No immediate code change required. If your site uses GS1 product identifiers, Dublin Core metadata, or Open Graph tags alongside schema.org structured data, review the schema.org version 30.0 release notes to understand the new equivalence mappings. Ensure your structured data and Open Graph tags are consistent with each other, as the formal equivalence annotations may affect how search engines and other consumers interpret cross-vocabulary signals.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://schema.org/docs/releases.html",
+        "https://schema.org/version/latest"
+      ],
+      "source": "Schema.org Release Notes — https://schema.org/docs/releases.html (scraped 2026-08-20)",
+      "lastUpdated": "2026-08-20"
+    },
+    {
+      "id": "schema-org-v30-eu-digital-product-passport",
+      "name": "EU Digital Product Passport (DPP) schema.org examples available",
+      "severity": "info",
+      "category": "schema",
+      "description": "Schema.org version 30.0 added EU Digital Product Passport (DPP) examples aligned with UN/CEFACT codes. The EU Digital Product Passport is a regulatory requirement under the EU Ecodesign for Sustainable Products Regulation (ESPR) that will require products sold in the EU to carry a digital record of sustainability, repairability, and lifecycle information. Schema.org now provides vocabulary and examples for implementing DPP data in structured data. Ecommerce sites targeting EU markets should be aware of this emerging structured data vocabulary as DPP requirements come into force.",
+      "fixTemplate": "Review the schema.org version 30.0 release notes and EU Digital Product Passport examples at https://schema.org/docs/releases.html. If your site sells products in EU markets, evaluate whether implementing DPP-aligned structured data is relevant to your compliance and SEO strategy. The vocabulary is aligned with UN/CEFACT codes for interoperability with regulatory and supply chain systems.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://schema.org/docs/releases.html",
+        "https://schema.org/version/latest"
+      ],
+      "source": "Schema.org Release Notes — https://schema.org/docs/releases.html (scraped 2026-08-20)",
+      "lastUpdated": "2026-08-20"
+    },
+    {
+      "id": "schema-org-v29-financial-incentives",
+      "name": "Missing financial incentive structured data for eligible offers",
+      "severity": "info",
+      "category": "schema",
+      "description": "Schema.org version 29.0 added vocabulary to represent financial incentives, for example in the area of sustainability. New types and enumeration types (including IncentiveQualifiedExpenseType) were added, along with new properties for use on Offer including eligibleWithSupplier. This vocabulary is particularly relevant for ecommerce sites that offer sustainability-related incentives, rebates, or government-backed financial incentives on products. Implementing financial incentive structured data can help search engines accurately represent offer conditions in merchant listings and product rich results.",
+      "fixTemplate": "If your site offers products with associated financial incentives (e.g., sustainability rebates, government incentives, supplier-specific pricing), review the schema.org version 29.0 financial incentives vocabulary at https://schema.org/docs/releases.html. Add the appropriate incentive properties to your Offer structured data. Example: {\"@type\":\"Offer\",\"price\":\"299.99\",\"priceCurrency\":\"USD\",\"eligibleWithSupplier\":{\"@type\":\"Organization\",\"name\":\"Supplier Name\"}}. Review the full vocabulary for IncentiveQualifiedExpenseType and related enumeration values.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://schema.org/docs/releases.html",
+        "https://schema.org/version/latest"
+      ],
+      "source": "Schema.org Release Notes — https://schema.org/docs/releases.html (scraped 2026-08-20)",
+      "lastUpdated": "2026-08-20"
+    },
+    {
+      "id": "http-query-method-google-search",
+      "name": "Google Search will eventually support HTTP QUERY method",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google has indicated that Google Search will eventually support the HTTP QUERY method, an emerging web standard for safe, cacheable requests with a request body (unlike GET which has no body, and unlike POST which is not safe or cacheable). The HTTP QUERY method is being standardized to enable more expressive search and query interactions on the web. No immediate implementation is required, but site owners and developers building search interfaces or APIs should be aware of this emerging standard and monitor its adoption timeline.",
+      "fixTemplate": "No immediate action required. Monitor the HTTP QUERY method standardization progress and Google Search's implementation timeline. If you build search APIs or query interfaces, evaluate whether adopting the HTTP QUERY method when it becomes available would benefit your architecture. Do not implement HTTP QUERY for SEO purposes until Google formally announces support and provides implementation guidance.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs",
+        "https://www.ietf.org/archive/id/draft-ietf-httpbis-safe-method-w-body-02.txt"
+      ],
+      "source": "Search Engine Roundtable — https://www.seroundtable.com (scraped 2026-08-20); headline: 'Google Search Will Eventually Support HTTP QUERY Method'",
+      "lastUpdated": "2026-08-20"
+    },
+    {
+      "id": "site-reputation-policy-eea",
+      "name": "Site reputation abuse policy adjusted for EEA",
+      "severity": "warning",
+      "category": "technical",
+      "description": "Google has adjusted its enforcement approach for the site reputation abuse policy within the European Economic Area (EEA). The site reputation abuse policy prohibits hosting third-party content on a site in an attempt to exploit the site's ranking signals, regardless of whether there is first-party involvement or oversight of the content. Site owners operating in the EEA should review the updated site reputation policy to understand how enforcement differs in that region and ensure their content hosting practices comply with both the global policy and the EEA-specific enforcement approach.",
+      "fixTemplate": "Review the updated site reputation abuse policy at https://developers.google.com/search/docs/essentials/spam-policies#site-reputation-abuse for EEA-specific enforcement guidance. Audit any third-party content hosted on your site to ensure it is not being used to exploit your site's ranking signals. If you operate in the EEA, review the specific enforcement adjustments that apply to your region.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/essentials/spam-policies#site-reputation-abuse"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-08-29)",
+      "lastUpdated": "2026-08-29"
+    },
+    {
+      "id": "european-search-dataset-licensing",
+      "name": "European Search Dataset Licensing Program eligibility",
+      "severity": "info",
+      "category": "technical",
+      "description": "Google has refreshed the European Search Dataset Licensing Program page with updated program overview, eligibility criteria, and application details. Publishers in the European Economic Area (EEA) who wish to license their content to Google Search should review the updated eligibility criteria and application process. This program is distinct from standard indexing and is relevant only to publishers seeking a formal licensing arrangement with Google for their content in European Search.",
+      "fixTemplate": "Review the updated European Search Dataset Licensing Program page at https://developers.google.com/search/docs/appearance/european-search-dataset-licensing to determine eligibility and apply if appropriate for your organization. No code change is required; this is an administrative and contractual process.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/european-search-dataset-licensing"
+      ],
+      "source": "Google Search Central Documentation Changelog — https://developers.google.com/search/updates (scraped 2026-09-04)",
+      "lastUpdated": "2026-09-04"
+    },
+    {
+      "id": "vacation-rental-schema",
+      "name": "Missing Vacation Rental structured data",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google Search supports Vacation Rental structured data, which allows vacation property listings to appear as rich results in Google Search. The structured data can include the property name, description, images, location, rating, and reviews. Sites that list vacation rental properties should implement this structured data to improve discoverability and eligibility for rich result appearances in Google Search.",
+      "fixTemplate": "Add VacationRental structured data to your vacation property listing pages: <script type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"LodgingBusiness\",\"name\":\"Property Name\",\"description\":\"Property description\",\"image\":\"https://yourdomain.com/property-image.jpg\",\"address\":{\"@type\":\"PostalAddress\",\"streetAddress\":\"123 Main St\",\"addressLocality\":\"City\",\"addressCountry\":\"US\"},\"aggregateRating\":{\"@type\":\"AggregateRating\",\"ratingValue\":\"4.5\",\"reviewCount\":\"100\"}}</script>. Review Google's vacation rental structured data documentation for the full list of supported properties.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/vacation-rental"
+      ],
+      "source": "Google Structured Data Search Gallery — https://developers.google.com/search/docs/appearance/structured-data/search-gallery (scraped 2026-09-04)",
+      "lastUpdated": "2026-09-04"
+    },
+    {
+      "id": "movie-schema",
+      "name": "Missing Movie structured data for movie listing pages",
+      "severity": "info",
+      "category": "schema",
+      "description": "Google Search supports Movie structured data, which enables movie carousel rich results in Google Search (for example, 'best movies of 2023'). Sites that publish movie listing pages, movie databases, or editorial movie content can implement Movie structured data to provide details such as the movie title, director information, and images, making the content eligible for the movie carousel rich result experience.",
+      "fixTemplate": "Add Movie structured data to your movie listing or detail pages: <script type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"Movie\",\"name\":\"Movie Title\",\"director\":{\"@type\":\"Person\",\"name\":\"Director Name\"},\"image\":\"https://yourdomain.com/movie-poster.jpg\",\"dateCreated\":\"2026-01-01\",\"description\":\"Movie description\"}</script>. Review Google's movie structured data documentation for the full list of supported properties and carousel eligibility requirements.",
+      "enabled": true,
+      "appliesTo": [
+        "html",
+        "jsx",
+        "tsx",
+        "vue",
+        "svelte"
+      ],
+      "references": [
+        "https://developers.google.com/search/docs/appearance/structured-data/movie"
+      ],
+      "source": "Google Structured Data Search Gallery — https://developers.google.com/search/docs/appearance/structured-data/search-gallery (scraped 2026-09-04)",
+      "lastUpdated": "2026-09-04"
+    }
+  ]
+}