Developer Hooks and Filters

Use the hooks implemented in the installed release and keep output factual. This reference covers a small verified set rather than hypothetical integration names.

Verified Free hooks

Hook	Purpose
citelayer_llmstxt_content	Filter generated llms text; receives content and is_full
citelayer_llmstxt_enhancement_block	Filter the enhancement block lines
citelayer_llms_txt_max_posts	Limit listed posts per type
citelayer_organization_schema	Filter Organization output
citelayer_person_schema	Filter Person output
citelayer_website_schema	Filter WebSite output
citelayer_article_schema	Filter Article data; receives schema and post
citelayer_bot_analytics_cleanup_days	Set local log retention
citelayer_ability_called	Observe ability execution through the audit action

Example: change retention deliberately

add_filter( 'citelayer_bot_analytics_cleanup_days', function ( $days ) {
    return 30;
} );

Put custom integration code in your own plugin. Test on a separate environment before production. A lower retention window makes older activity unavailable; it is not a correction to a score.

Integration verification

1. Match the hook signature in your installed release source.
2. Return the expected type and sanitize custom input.
3. Test generator and public output, including cached reads and SEO enhancement mode.
4. Check the relevant Woo/EDD route contract separately; do not assume add-ons expose the same hooks.

Current source reference

Free hook definitions: Free 1.13.5 source. Public REST interfaces are described in the API reference.

Next step

Continue with the quick start checklist, or check the common questions. For a reproducible problem, send the plugin versions, affected URL, expected result and actual response through Support. Do not include passwords, license keys or customer details.

Reviewed 6 October 2026 against citelayer® Free 1.13.5, WooCommerce add-on 1.2.19 and EDD add-on 1.2.1. Features depend on the active components and settings on your site.