FAQ

Not at all. Install it like any WordPress plugin — upload, activate, done. Everything is configured through the standard WordPress admin. No PHP, no command line, no config files.

WordPress 6.0+ and PHP 8.0+. Most hosting providers have been on PHP 8.x for a while — this shouldn't be an issue. If you're unsure, your host's control panel shows the PHP version.

Both. The meta description meta box and GEO Quick Overview meta box appear in both editors. BreznGEO uses standard WordPress meta boxes, which are editor-agnostic.

No. BreznGEO works without an API key. In that case it uses a built-in fallback: it extracts the first 150–160 characters from your post content using sentence-boundary detection. No AI involved, but your posts always get a description.

Yes. BreznGEO is GPL-licensed, so you can install it on as many sites as you own or manage. Each site uses its own API key and settings independently.

Five providers, switchable at any time from the settings — no reinstall required:

• OpenAI (GPT-4.1, GPT-4o, GPT-4o mini)
• Anthropic Claude (3.5 Sonnet, 3 Haiku)
• Google Gemini (2.0 Flash, 1.5 Pro)
• xAI Grok (3, Grok 3 mini)
• OpenRouter — a single API that routes to 600+ models including Claude, GPT, Gemini, Llama, Mistral, DeepSeek, and more. See the OpenRouter section below for details.

Very little. A single meta description is roughly 150–200 tokens — fractions of a cent per post. Even processing 500 posts in bulk, the total API cost is typically under €1. You pay your provider directly; BreznGEO takes nothing.

Check your provider's pricing page for exact numbers — they vary by model.

No. If a post already has a meta description — whether you wrote it or another plugin set it — BreznGEO leaves it alone. It only generates when the field is empty, unless you explicitly click the regenerate button in the post editor.

Yes. BreznGEO automatically detects Rank Math, Yoast SEO, AIOSEO, and SEOPress and writes AI-generated descriptions directly into their meta fields. Your SEO plugin of choice stays in control — BreznGEO just fills in the content.

BreznGEO falls back to its built-in text extraction — the same sentence-boundary fallback that runs without an API key. Your post always gets a description, even if the AI provider is temporarily unavailable.

Yes, fully. The prompt is editable in Settings → Meta Generator. Available placeholders: {title}, {content}, {excerpt}, and {language}. Tune the tone, target length, or language for your audience.

OpenRouter is a single API that routes to 600+ AI models — Claude, GPT, Gemini, Llama, Mistral, DeepSeek, Grok, and many more — through one key and one billing account. Instead of signing up with OpenAI, Anthropic, and Google separately, you pay OpenRouter and pick any model you want.

In BreznGEO this means: one provider slot gives you access to essentially every relevant text AI, with pricing pulled automatically from the OpenRouter API. Great if you like to experiment with different models, or want a single invoice instead of four.

Model IDs on OpenRouter follow the pattern provider/model-name, for example anthropic/claude-opus-4.7, openai/gpt-4o-mini, google/gemini-2.0-flash-exp, or meta-llama/llama-3.3-70b-instruct.

Three ways to find the exact ID:

1. Click "Load models" in the plugin settings — the curated marketing/SEO selection loads directly as a dropdown with pricing already filled in.
2. Visit openrouter.ai/models, find your model, and copy the ID shown under its name.
3. Pick "Custom model ID…" from the dropdown and paste any ID — even one not in the curated list.

OpenRouter is a routing aggregator. Your request goes first to OpenRouter, which forwards it to the upstream provider of the model you picked — OpenAI if you chose a GPT model, Anthropic for Claude, Google for Gemini, Meta for Llama, and so on. Both OpenRouter and the upstream provider may process your content under their respective terms.

If that matters for your compliance setup (GDPR, enterprise DPA), consider using the direct provider integrations (OpenAI, Anthropic, Gemini, Grok) instead — the data path is shorter and the DPA sits directly with the actual model operator. OpenRouter's privacy policy: openrouter.ai/privacy.

On click, the plugin fetches the curated "marketing" category from openrouter.ai/api/v1/models and caches the result for 12 hours. That populates the model dropdown and fills in input/output pricing per million tokens automatically. No content of yours is sent during this call — it's purely a catalogue lookup.

The fetch is explicitly opt-in: nothing hits OpenRouter until you click the button. That keeps the plugin well-behaved for WordPress.org review and for users who prefer to minimise outbound calls.

Because prices on OpenRouter change frequently (new models, discounts, routing changes) and are already published via the API. Letting you type your own cost numbers would invite stale values and wrong estimates. BreznGEO shows the current pricing from OpenRouter's own data, so the bulk-cost estimate in the Generator stays honest.

For a custom model ID that isn't in the cached list, pricing shows as "Unknown" until you reload models. Generation still works — only the cost estimate is missing.

GEO stands for Generative Engine Optimization — the practice of structuring your content so AI systems like ChatGPT, Perplexity, and Claude can read, understand, and cite it accurately.

Traditional SEO targets search engine crawlers. GEO targets the AI models that are increasingly replacing search as the first point of contact between readers and content.

Three things: a short summary of your post, a bullet-point list of key takeaways, and an optional FAQ section — all generated from your post content. It appears inside your post as a collapsible <details> block. Fully editable, no JavaScript required on the frontend.

No. The block outputs plain HTML — a native <details> element with static text. No JavaScript is loaded on the frontend. It's as fast as a regular paragraph.

If you manually edit the AI-generated summary, bullets, or FAQ in the post editor, BreznGEO automatically locks that post. On the next save or publish, the AI won't overwrite your edits. You can unlock it manually in the meta box at any time.

By default, yes — on every post that meets the word-count threshold (default: 350 words). You can disable it per post via the meta box in the editor, or switch the generation mode to manual-only in the global settings.

Internal links — links from one of your posts to another on the same site — are one of the strongest on-page SEO signals. They help search engines map your site structure, distribute page authority, and understand topical relevance. They also keep readers on your site longer.

The problem: finding the right phrase in your current post and the right target page is slow, manual work. BreznGEO does it automatically while you write.

No. BreznGEO only suggests — you decide. The editor sidebar shows a list of phrase → target post pairs ranked by relevance. You tick the ones you want and click confirm. Links are then inserted at the first unlinked occurrence of each phrase. Nothing is touched without your explicit approval.

No. The core matching runs entirely without an AI key, using keyword overlap and n-gram phrase scoring. If you have an API key configured and have enabled "Link Suggestions" in the AI Features card on the Dashboard, the top candidates are optionally re-ranked by your AI provider for improved semantic relevance. AI re-ranking is an optional upgrade — off by default, enabled per feature in the Dashboard.

Yes — that's exactly the point. Internal link suggestion is typically locked behind premium tiers in tools like LinkWhisper ($77/year), Surfer SEO, or Yoast Premium. BreznGEO includes it for free, with no subscription and no upsell. It's one of the features that makes BreznGEO genuinely competitive with paid tools.

BreznGEO tokenises your current post content and scores every published post against it using four weighted signals: title keyword overlap (×3, highest), tag overlap (×2), post excerpt overlap (×1.5), and category overlap (×1). Each candidate's title + tags + excerpt + categories together form its "topic". BreznGEO then finds the best phrase in your current text that shares a word with that topic — so a post about the Danube can correctly link to a Deggendorf post if "Deggendorf" carries "danube" as a tag and the word "danube" appears in your article, even if "Deggendorf" itself never does. Posts you've excluded in the Link Suggestions settings are never shown. Posts you've boosted rank higher when they match.

Ten on-page SEO factors: whether your focus keyword appears in the title, headings (H2–H6), URL slug, first paragraph, last paragraph, meta description, image alt text, image title/caption, and excerpt — plus keyword density against a configurable target range.

No. All ten checks run locally without any API key. The optional AI features — keyword suggestions, content optimization tips, and semantic keyword analysis — require a configured API key and are triggered manually from the meta box.

The primary keyword is your main focus term — it's checked against all ten factors with stricter thresholds. Secondary keywords are supporting terms (you can add multiple); they use relaxed minimum occurrences. Both are saved per post and included in the analysis.

BreznGEO automatically generates variations of your keyword based on your site's language. For English: trailing-s, -es, -ing, -ed. For German: -er, -en, -e. It also matches compound forms (spaces vs. hyphens). So if your keyword is “keyword analysis”, it also finds “keyword-analysis” and “keyword analyses”.

Live — analysis runs automatically while you type, with a configurable debounce delay (default 800ms). Manual — you click the “Analyze” button when ready. Save — analysis runs when you save or publish the post. Choose your preferred mode in BreznGEO → Keywords.

Structured data (Schema.org JSON-LD) is machine-readable metadata embedded invisibly in your page. Google uses it for rich results — star ratings, recipe cards, FAQ dropdowns in search. AI engines use it to understand context, authorship, and content type. It's invisible to readers, very visible to algorithms.

14 types: Organization, Article / BlogPosting, Author (Person), ImageObject, VideoObject (auto-detected from YouTube/Vimeo embeds), FAQPage (auto-generated from GEO block data), Speakable, BreadcrumbList, HowTo, Review, Recipe, and Event. Each type can be enabled or disabled independently.

No. BreznGEO detects active SEO plugins and automatically suppresses BreadcrumbList output when Rank Math or Yoast is active — since they already handle that type. Other schema types from BreznGEO complement rather than duplicate what those plugins output.

For the automatic types (Organization, BlogPosting, BreadcrumbList, Author) — no. They pull from your site settings and post meta automatically.

For post-specific types (Recipe, HowTo, Review, Event) — yes, you fill them in once per post via the BreznGEO Schema meta box in the post editor. It only appears when at least one of these types is enabled in settings.

BreznGEO focuses on posts and pages. It does not generate meta descriptions or schema for WooCommerce products. If you need product SEO, use a dedicated WooCommerce SEO plugin alongside BreznGEO — they won't conflict.

BreznGEO can be network-activated on a Multisite installation, but settings are per-site. Each site in the network manages its own API key, provider choice, and configuration independently.

Yes. BreznGEO generates meta tags and JSON-LD in the <head> at request time on the server side. There is nothing on the frontend that caching would interfere with. Caching plugins will simply cache the output, which is exactly the intended behaviour.

Yes. BreznGEO hooks into post save and publish events at the WordPress level, independent of which editor or builder was used to create the content. Meta descriptions and schema are attached to the post object, not to the builder's content structure.

Yes. BreznGEO has been fully tested on ClassicPress and is 100% compatible. All features work — AI meta descriptions, GEO blocks, Schema.org, llms.txt, robots.txt manager, crawler log, internal link suggestions, keyword analysis, and the full admin UI including German translations. Since BreznGEO uses Classic Editor meta boxes exclusively (no Gutenberg blocks), it is a natural fit for ClassicPress.

API keys are XOR-encrypted with a key derived from your WordPress authentication salts before being written to the database. The salts are unique per installation, so the encrypted value is useless outside your site. Keys are never stored in plain text and never appear in logs.

Only to the AI provider you configured — and only when you trigger a generation. Your post title and content are sent as part of the prompt to OpenAI, Anthropic, Google, or xAI, whoever you chose.

No data is ever sent to BreznGEO, Donau2Space.de, or any third party beyond your chosen AI provider. Your provider's standard data processing terms apply.

The Crawler Log records visits from known AI bots (GPTBot, ClaudeBot, etc.). It stores: the bot name, a SHA-256 hash of the IP address (the original IP is never stored and cannot be recovered), the URL visited, and the timestamp. Entries are automatically deleted after 90 days. Human visitor data is never collected.

BreznGEO itself does not collect personally identifiable information. The Crawler Log stores only hashed IPs — not reversible to real addresses. Your AI provider's data processing agreement (DPA) covers the content sent for generation. Standard practice is to name your AI provider in your site's privacy policy.

No catch. BreznGEO is GPL-2.0 licensed and free to use. The only cost is your AI API usage, billed directly by your provider. There is no freemium model, no feature gating, no premium tier, and no upsell emails. Prost.

That's the intention. BreznGEO was built because I didn't want to pay a monthly SaaS fee for my own blog. That motivation hasn't changed. If new features get added, they go into the free plugin — not behind a paywall.

Yes. GPL-2.0 allows installation on any number of sites. There are no licence checks, activation limits, or per-site fees. Each client site needs its own API key from the provider of their choice.

No current plans for a paid tier. The model is simple: BreznGEO stays free, you pay your AI provider directly. That's it.

Open an issue at github.com, use the WordPress.org support forum.