Linux 软件免费装

在这里免费安装WordPress以及其他软件

Banner图

Bavarian Rank Engine

开发者 mifupadev
更新时间 2026年3月5日 22:51
PHP版本: 8.0 及以上
WordPress版本: 6.9
版权: GPL-2.0-or-later
版权网址: 版权信息

标签

seo meta description ai schema llms.txt

下载

1.3.5

详情介绍:

Bavarian Rank Engine is a WordPress SEO plugin that automates AI meta descriptions, adds Schema.org structured data, and helps your content get discovered by AI-driven search. It covers GEO — Generative Engine Optimization — preparing your pages for AI overviews, answer engines, and retrieval-augmented search alongside traditional search engine optimization. No subscription required. The plugin was originally built for Donau2Space.de and has run on the developer's own production sites since version 1.0. Stability is the priority: when something breaks, it affects the developer first. There are no upsells, no subscription tiers, and no features added just to expand the feature list. It works as a focused complement to your existing SEO setup — not a replacement. All AI features are optional. Without an API key, the plugin falls back to local logic and keeps running normally — meta descriptions are extracted from post content, internal link suggestions use text-based matching, and all Schema.org, llms.txt, and robots.txt features work without any external service. Learn more Website: bavarianrankengine.com FAQ: Read the FAQ Live demo: Try the live demo At a glance What makes Bavarian Rank Engine different AI Meta Generator Generates a 150–160 character meta description the moment a post is published. The prompt is fully customizable using {title}, {content}, {excerpt}, and {language} placeholders. Language is detected automatically from Polylang, WPML, or the WordPress site locale. If no API key is configured or the AI request fails, a clean fallback excerpt is extracted from the post content — no description is left empty. GEO Block Adds an AI-generated Quick Overview block to each post: a short summary, key bullet points, and an optional FAQ. Rendered as a native <details> element — configurable as collapsible (default), always open, or stored without frontend output. Supports three generation modes: automatic on publish, hybrid (auto only when fields are empty), or manual. Insertion position is configurable: after the first paragraph (default), top, or bottom. A quality gate suppresses FAQ generation on posts below a configurable word-count threshold. The post editor meta box includes live generate and clear buttons, a per-post enable toggle, and an optional prompt add-on field for author-level customization. Four built-in themes: Light, Dark, Minimal, Bavarian. Internal Link Suggestions An editor meta box that surfaces relevant internal links while you write. Each suggestion is a phrase–target pair: a phrase found in your content, paired with an existing post that covers the same topic. Text-based matching (title, tag, category, and excerpt overlap) works without AI. An optional AI upgrade sends the top 20 candidates to your connected provider for semantic ranking. Trigger options: manual button, on post save, or a timed interval. A settings page lets you exclude posts (such as legal pages) and boost specific pillar pages. Supported in both Gutenberg and Classic Editor. Bulk Generator Finds all published posts without a meta description (including descriptions set by Rank Math, Yoast, AIOSEO, or SEOPress) and generates them in configurable batches with rate-limiting between batches. A live progress log and per-batch cost estimate are shown during the run. Multi-Provider AI Support Choose from four AI providers and switch at any time without losing your settings: Schema.org Enhancer (GEO) Injects JSON-LD structured data for search engines and AI retrieval systems: llms.txt Serves a machine-readable index of your published content at /llms.txt, following the emerging llms.txt convention increasingly supported by AI indexing tools. Supports custom title, description sections, featured resource links, pagination for large sites, and HTTP ETag / Last-Modified caching. robots.txt Manager Block individual AI training and data-harvesting bots directly from the WordPress admin — no manual file editing. Supports 13 known bots: GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, DataForSeoBot, ImagesiftBot, Omgili, Diffbot, FacebookBot, and Amazonbot. Crawler Log Automatically logs visits from known AI bots. Stores the bot name, a SHA-256-hashed IP address, and the requested URL. Entries older than 90 days are purged automatically. A 30-day summary is shown on the plugin dashboard. Post Editor Integration A "Meta Description" meta box in the post and page editor shows the current description, its source (AI / Fallback / Manual), a live character counter, and a "Regenerate with AI" button. A sidebar SEO widget displays word count, reading time, heading structure, and link counts with live warnings. Link Analysis Dashboard Identifies posts without internal links, posts with an unusually high external-link count, and your top pillar pages by inbound internal link count — loaded on demand with a one-hour cache. Secure API Key Storage API keys are obfuscated using XOR with a key derived from your WordPress authentication salts before being written to the database. Keys never appear in plain text in database dumps or export files. No OpenSSL extension required. Compatibility Works standalone or alongside any major SEO plugin. When Rank Math, Yoast SEO, AIOSEO, or SEOPress is active, generated descriptions are written to that plugin's own meta field. Existing descriptions set by those plugins are always respected and never overwritten.

安装:

  1. Download the plugin zip and go to Plugins → Add New → Upload Plugin in your WordPress admin.
  2. Upload the zip file and click Install Now, then Activate.
  3. Go to Bavarian Rank → AI Provider.
  4. Select your preferred AI provider, paste your API key, and click Test connection.
  5. Choose a model and optionally enter token costs for cost estimation.
  6. Go to Bavarian Rank → Meta Generator to select post types and configure Schema.org types.
  7. To serve a content index, go to Bavarian Rank → llms.txt, enable it, and save.
  8. To manage AI crawler access, go to Bavarian Rank → robots.txt and select the bots to block.
The plugin works without an API key — fallback meta extraction runs automatically on publish.

屏幕截图:

  • AI Provider settings — provider selector, API key entry, connection test, model picker, cost configuration.
  • Meta Generator settings — post type selection, token limit, prompt editor, Schema.org toggles.
  • Bulk Generator — batch controls, live progress log, cost estimate.
  • llms.txt configuration — enable toggle, custom sections, post types, pagination settings.
  • robots.txt / AI Bots — per-bot block checkboxes.
  • Post editor — Meta Description meta box with source badge and AI regeneration button.
  • Post editor — SEO Analysis sidebar widget with live stats and warnings.

升级注意事项:

1.1.0 No database changes. Deactivate and reactivate the plugin after updating to register the new GEO Block rewrite rules. 1.0.0 Initial release. No upgrade steps required.

常见问题:

Do I need an API key?

An API key is required for AI-generated meta descriptions. Without one, the plugin automatically falls back to extracting a clean 150–160 character excerpt from the post content. All other features (Schema.org, llms.txt, robots.txt manager, crawler log) work without an API key.

How much does it cost to generate meta descriptions?

Cost depends on the AI provider and model you choose. A single meta description typically uses fewer than 1,500 tokens (input + output combined). As a rough reference, 1,000 descriptions with GPT-4o mini has cost around $0.50–$1.00 at recent rates — but AI provider pricing changes over time. The AI Provider settings page links directly to the current pricing page for each supported provider.

Are my API keys stored securely?

Keys are obfuscated using XOR encryption with a key derived from your WordPress authentication salts before being written to the database. They do not appear in plain text in database dumps or export files. For the highest level of protection, define your API keys as constants in wp-config.php — the plugin will use them automatically and nothing is stored in the database.

What is llms.txt?

llms.txt is an emerging convention (similar in spirit to robots.txt or sitemap.xml) that gives AI language models and retrieval-augmented generation (RAG) tools a structured, machine-readable index of a site's content. Support varies by tool and is still evolving. The plugin serves it at yourdomain.com/llms.txt with proper HTTP caching headers.

Is this compatible with Rank Math / Yoast SEO / AIOSEO / SEOPress?

Yes. When one of these plugins is active, Bavarian Rank Engine writes generated descriptions directly into that plugin's meta field. It also checks for existing descriptions from all four plugins before generating, and skips posts that already have one. Breadcrumb and standalone meta description output is suppressed automatically to avoid conflicts.

Does it work with Polylang or WPML?

Yes. The meta generator detects the post language from Polylang (pll_get_post_language()), WPML (ICL_LANGUAGE_CODE), or the WordPress site locale, and includes it in the prompt so the AI writes in the correct language.

How does the Bulk Generator handle rate limits?

Posts are processed in configurable batches (1–20 per batch) with a 6-second pause between batches. Each post is retried up to three times with a 1-second delay between attempts. A transient-based lock prevents simultaneous runs. The lock expires automatically after 15 minutes and can also be released manually from the Bulk Generator page.

Does the Crawler Log store personal data?

No. IP addresses are hashed with SHA-256 before storage — the original IP is never saved. Entries are purged automatically after 90 days.

Will it slow down my site?

No front-end overhead beyond the inline JSON-LD and optional meta tags in wp_head. The llms.txt response is cached via WordPress transients and served with HTTP 304 when the ETag matches. No external HTTP requests are made during normal page loads — AI API calls only happen on post publish or when explicitly triggered from the admin.

Can I add a custom AI provider?

Yes. Implement the BavarianRankEngine\Providers\ProviderInterface interface (five methods: getId, getName, getModels, testConnection, generateText), place the class in includes/Providers/, and register it in Core::register_hooks(). It will appear in all admin dropdowns automatically.

更新日志:

1.3.5 1.3.4 1.3.3 1.3.2 1.3.1 1.3.0 1.2.4 1.2.3 1.2.2 1.2.1 1.2.0 1.1.0 1.0.0