View Documentation Download Lite
Browse documentation
Start Here Getting Started with AIVOW Lite Core Setup Using the AI Systems Registry Managing Active, Draft, and Inactive AI Systems Notices and Labels Adding and Customizing AI Content Badges Configuring the Global AI Banner Using the Disclosure Shortcode Using the Interaction Gate Shortcode Transparency and Readiness Creating and Reviewing the Transparency Page Understanding the Article 50 Readiness Matrix Using the AI Literacy Checklist Metadata and Integrations Enabling Lightweight AI Metadata Using AIVOW Lite with WooCommerce Privacy and Maintenance Privacy and Data Storage in AIVOW Lite Understanding Reports and Logs in AIVOW Lite Uninstall Behavior and Data Cleanup Troubleshooting Common Issues
AIVOW Lite

Enabling Lightweight AI Metadata

Enable conservative opt-in metadata only for labelled content and supported archive contexts.

Product boundary

This guide explains plugin configuration. It does not provide legal advice or certify compliance.

The Lightweight AI Metadata feature in AIVOW Lite 1.0.0 outputs only plugin-specific custom HTML meta tags. It does not generate JSON-LD or modify structured data produced by WordPress, the active theme, Yoast SEO, WooCommerce, or other plugins.

When to use this guide

Use this guide when you want labelled WordPress content or supported public archive contexts to include lightweight AI-related meta tags in the page source.

Configure metadata output

  1. Add an AI badge to the post, page, WooCommerce product, assigned Shop page, or supported taxonomy term that should produce metadata.
  2. Open AIVOW → AIVOW Settings → Metadata.
  3. Enable Lightweight AI Metadata to add AI usage information as custom HTML meta tags.
  4. If WooCommerce is active, enable Shop page metadata only when the assigned Shop page has an AI badge and should produce metadata.
  5. Enable taxonomy archive metadata only when labelled taxonomy terms and their public archive pages should produce metadata.
  6. Save the settings.
  7. Open a labelled content item or supported archive on the frontend.
  8. Inspect the final HTML source and confirm that the expected metadata appears.
  9. Open an unlabelled page and confirm that AIVOW Lite does not add AI metadata there.

Metadata output is disabled by default. Enabling a global metadata option does not add AI metadata to every page. The current content or supported archive must also have an AI badge enabled.

Understand the metadata output

Lightweight AI Metadata adds a small set of plugin-specific values to the page <head>.

<meta name="aitm-ai-content" content="ai-assisted">

The exact aitm-ai-content value depends on the AI usage status selected for the labelled content.

When content is assigned the AI-generated, human reviewed status, AIVOW Lite also outputs the following human-review metadata:

<meta name="aitm-human-reviewed" content="true">

AIVOW Lite does not output the aitm-human-reviewed flag for AI-assisted, No AI Used, or other statuses that do not represent confirmed human review.

The aitm-* names are custom plugin metadata. They are not a standardized provenance format, provider-level marking mechanism, watermark, or guarantee that another service will read or interpret them.

Understand where metadata can appear

AIVOW Lite can output Lightweight AI Metadata for:

  • labelled WordPress posts and pages;
  • labelled WooCommerce products;
  • the assigned WooCommerce Shop page when the dedicated setting is enabled and the Shop page has an AI badge;
  • supported public taxonomy archives when the dedicated setting is enabled and the corresponding taxonomy term has an AI badge.

AIVOW Lite does not output this metadata on unlabelled content or unsupported contexts such as search results, author archives, date archives, and general post type archives.

Metadata boundary

AIVOW Lite adds WordPress-level custom meta tags based on administrator-selected labels and settings.

AIVOW Lite 1.0.0 does not generate JSON-LD or modify structured data produced by WordPress, the active theme, SEO plugins, WooCommerce, or other integrations.

The plugin does not detect AI-generated content, verify whether the selected label is accurate, modify the original media file, add a durable watermark, provide C2PA or Content Credentials, or perform provider-level machine-readable marking.

The presence of these custom meta tags does not prove content origin, legal compliance, or that a provider’s marking obligation has been satisfied.

Lightweight AI Metadata is not a visible disclosure and does not replace an AI Content Badge, notice, or other information that should be presented directly to visitors.

Check the generated page source

  1. Open the labelled content item or supported archive on the frontend.
  2. Use the browser’s View Page Source action.
  3. Search for aitm-ai-content.
  4. Confirm that its value matches the AI usage status assigned to the content or archive.
  5. When the content uses the AI-generated, human reviewed status, search for aitm-human-reviewed and confirm that its value is true.
  6. For statuses that do not represent confirmed human review, confirm that aitm-human-reviewed is absent.
  7. Repeat the check on an unlabelled page and confirm that AIVOW Lite does not add its AI metadata there.
  8. If you enabled metadata for the WooCommerce Shop page or supported taxonomy archives, repeat the same source check on those public archive pages.

Expected result

Labelled posts, pages, WooCommerce products, and enabled supported archive contexts include the applicable custom aitm-* meta tags in the HTML source.

Unlabelled content and unsupported pages do not receive AI metadata from the plugin. The aitm-human-reviewed flag appears only for content explicitly assigned the AI-generated, human reviewed status.

Common mistakes

  • Enabling Lightweight AI Metadata without assigning an AI badge to the content.
  • Expecting metadata to appear on every page of the site.
  • Enabling WooCommerce Shop page metadata when the assigned Shop page does not have an AI badge.
  • Enabling taxonomy archive metadata without labelling the corresponding taxonomy term.
  • Expecting metadata changes to appear before saving or updating the content or settings.
  • Assuming that the plugin automatically detects or verifies whether content was created with AI.
  • Expecting aitm-human-reviewed to appear for AI-assisted, No AI Used, or another status that does not represent confirmed human review.
  • Treating custom aitm-* meta tags as standardized provenance, watermarking, C2PA, Content Credentials, or provider-level machine-readable marking.
  • Assuming that metadata provides a visible disclosure to visitors.
  • Checking only the visible page instead of inspecting its HTML source.
  • Expecting unsupported archive types to produce AI metadata.

Troubleshooting

  • Confirm that Lightweight AI Metadata is enabled under AIVOW → AIVOW Settings → Metadata.
  • Confirm that the current content item or taxonomy term has an AI badge enabled.
  • Save or update the content after changing its AI usage status or badge settings.
  • Check the raw page source rather than only the visible frontend page.
  • Search the source for aitm-ai-content and confirm that its value matches the selected AI usage status.
  • Search for aitm-human-reviewed only when the content is assigned the AI-generated, human reviewed status.
  • If aitm-human-reviewed is missing, confirm that the exact AI-generated, human reviewed status has been selected and saved.
  • If aitm-human-reviewed appears unexpectedly, confirm that the content is not using a different AI usage status.
  • For the WooCommerce Shop page, confirm that the dedicated Shop page metadata setting is enabled and that the assigned Shop page has an AI badge.
  • For a taxonomy archive, confirm that taxonomy archive metadata is enabled and that the corresponding taxonomy term has an AI badge.
  • Test the same configuration on a simple labelled post or page.
  • Clear any active page, CDN, or optimization caches if the source still contains older values.
  • Temporarily disable HTML optimization if the generated meta tags are removed or changed after page generation.
  • Remember that search results, author archives, date archives, general post type archives, and other unsupported contexts do not produce AI metadata.