Geoleaper — AI Schema & Structured Data
Geoleaper helps WordPress sites become easier for search engines and AI systems to understand.
It analyzes your content, generates Schema.org JSON-LD structured data, scores your content for AI visibility signals, strengthens your organization identity, and can generate llms.txt files for large language models.
Beyond basic static markup, Geoleaper focuses on semantic clarity: what the page is, who published it, which entities it is about, and how it should be understood by AI-powered search systems.
Features:
- AI-Powered Schema Generation: Generate Schema.org JSON-LD for posts, pages, products, custom post types, and taxonomy archives.
- AI Visibility Score: See how well each page is structured for search engines, schema quality, entity clarity, and AI-powered discovery.
- Identity Center: Strengthen your organization entity with sameAs profile links and verified brand information.
- llms.txt Generation: Create an llms.txt file to help large language models understand your site structure and key content.
- AI Crawler Tracking: Track visits from known AI crawlers and AI-related user agents when enabled.
- Taxonomy Support: Generate structured data for category and tag archive pages.
- Auto-Analysis: Automatically analyze posts when they are published or updated.
- AI Layer: Optionally append a user-controlled content section to selected post types to improve semantic clarity for AI systems. This feature can be enabled, disabled, and configured by the site owner.
- SEO Plugin Compatibility: Works alongside Yoast SEO, Rank Math, SEOPress, and other SEO plugins.
Supported Schema Types:
Geoleaper can generate structured data for:
- Articles and blog posts
- Pages and home pages
- Product pages
- Category and tag archives
- Collection pages
- Author and profile pages
- Organization and WebSite entities
- Breadcrumbs and ItemList structures where relevant
Schema types are auto-detected based on WordPress context and page content, with manual overrides available where supported.
External Services
Geoleaper connects to the Geoleaper API service at https://app.geoleaper.com to provide AI-powered schema generation, scoring, identity features, llms.txt generation, and optional AI crawler analytics.
A Geoleaper account is required to use the plugin. API requests are made when you connect your site, run an analysis, use automatic analysis, generate llms.txt, or enable crawler tracking features.
The following data may be sent to the Geoleaper API:
- Post content and metadata (endpoint:
/api/wordpress/v1/analyses, trigger: manual analyze action or auto-analysis on publish/update when enabled): Post title, content, URL, excerpt, categories, tags, featured image URL, post type, and publish/update metadata. Author display name, nickname, public biography, public author URL, and Gravatar URL are sent for schema.org Person nodes. Author email, username, first/last name, and role lists are never sent. - Term/taxonomy data (endpoint:
/api/wordpress/v1/analyses, trigger: manual analyze action on a taxonomy archive): Term name, description, archive URL, taxonomy type, and listed posts. - Site information (sent with each analysis): Site URL, site name, language, WordPress context flags, and the organization identity fields configured under Settings.
- SEO plugin metadata (sent with each analysis when present): Public metadata such as social profile links or SEO fields used for schema generation.
- Crawler visit data (endpoint:
/api/wordpress/v1/visits, trigger: page load detected as an AI crawler request, only when AI Crawler Tracking is enabled): Page URL, user agent, referrer, UTM source, and timestamp. Visitor IP addresses are never sent. Crawler tracking is off by default and must be explicitly enabled under Settings → AI Crawler Tracking. - Crawler signature refresh (endpoint:
/api/wordpress/v1/visit-sources, trigger: daily background cron, only when AI Crawler Tracking is enabled): No data sent — this is a one-way GET to download the latest AI-bot user-agent allow-list. Scheduled cron is cleared automatically when tracking is disabled. - External-data deletion (endpoint:
/api/wordpress/v1/sites/{id}/delete, trigger: plugin uninstall): A best-effort request to remove the site’s analysis history and identity profile from Geoleaper servers.
Geoleaper does not collect personal data from regular site visitors. AI crawler tracking is optional and can be disabled from the Settings page; doing so clears the daily refresh cron and the locally cached crawler signature list immediately.
The data is used to generate structured data, calculate AI visibility scores, build identity signals, generate llms.txt files, and provide analytics inside the Geoleaper dashboard.