Ostheimer SEO

Ostheimer SEO handles the technical foundations of search visibility using WordPress core features. Settings live on one page. There are no advertising banners, SEO scores, subscriptions or keyword-density targets.

Included features

• Title and description templates for posts, pages, public content types, taxonomy archives and special pages.

• Per-post SEO fields in the block editor and classic editor, with a server-rendered search preview.

• Canonical URLs and robots directives, including archive and content-type indexing controls.

• Open Graph and X cards, with per-post images and a fallback image.

• WordPress core XML sitemaps with noindex exclusions and modification dates.

• Permanent redirects from the old Yoast SEO sitemap URLs, such as sitemap_index.xml and post-sitemap.xml, to the WordPress sitemap index. The Yoast import switches them on.

• One connected JSON-LD graph: Organization, optional LocalBusiness (with contact, address, service area and opening hours) or Person, WebSite, WebPage, Article and BreadcrumbList.

• An accessible breadcrumbs block, the [native_seo_breadcrumbs] shortcode and a theme template function.

• Read-only import from Yoast SEO: post metadata, supported site templates, social profiles, identity and archive settings. Source data stays intact.

• Optional IndexNow notifications, disabled by default.

• Optional AI drafts for SEO titles and meta descriptions, created either by the AI provider set up in WordPress (WordPress 7.0 or later, Settings → Connectors) or through your own OpenRouter key and a model you choose. Review the suggestions in the post or page editor before saving. Automatic suggestions are a separate opt-in.

• One settings page with a status line (whether search engines may index the site and where the sitemap is), numbered sections and an at-a-glance summary of the saved settings: facts, no scores.

• Live template examples and editor previews, native image selection and explained advanced controls.

• Translation-ready PHP and JavaScript with WordPress.org language-pack support.

AI visibility

Connected structured data describes your content and its publisher to systems that support it. Ostheimer SEO does not promise rankings, inclusion in AI answers or citations. Optional AI writing uses the AI provider set up in WordPress or your own OpenRouter key.

txt or a Markdown endpoint.

Privacy

The plugin does not collect visitor analytics, store IP addresses, set tracking cookies, load CDN assets or require an external account. IndexNow and OpenRouter are optional external services, each disabled until explicitly enabled. With AI enabled, article titles and text (including drafts) are sent when generating SEO text: either to OpenRouter and the selected model provider, or through WordPress’s own AI Client to the AI provider set up under Settings → Connectors.

No visitor data is sent.

Compatibility

Ostheimer SEO pauses its frontend metadata output when Yoast SEO, Rank Math, All in One SEO or SEOPress is detected. This helps prevent duplicate tags while migrating. Import first, then deactivate the other SEO plugin and verify your pages.

Other plugins or themes may also output metadata; check the rendered page when switching.

For developers

at/leistungen/wordpress-plugins

All runtime PHP and JavaScript source is included in the plugin download.

Readable JavaScript uses WordPress-provided packages directly. There is no JavaScript compilation step. Composer is needed for development tools only, not at runtime.

Filters include native_seo_title, native_seo_description, native_seo_canonical, native_seo_robots, native_seo_open_graph, native_seo_schema_graph, native_seo_breadcrumbs_markup and native_seo_sitemap_exclude.

External services

IndexNow is disabled by default. org/indexnow. No post content or visitor data is sent.

Search engines decide whether to crawl or index the URLs. A notification is not confirmation of indexing.

• Documentation: https://www.indexnow.org/documentation

• Terms: https://www.indexnow.org/terms

• Microsoft privacy statement: https://privacy.microsoft.com/privacystatement

OpenRouter AI writing is disabled by default. ai/api/v1/chat/completions and the selected model provider. Password-protected posts are excluded.

Requests happen when an editor clicks Generate, or when the explicitly enabled autofill mode finds missing SEO text in an open editor. Generated text is a draft until the post is saved. Existing custom SEO text is preserved unless the editor explicitly selects replacement.

Provider usage costs are billed by OpenRouter. No key is included with this plugin and no credit is sold by Ostheimer SEO.

ai/api/v1/models. This sends no API key or article content and does not enable AI writing. The searchable list shows text models advertising JSON response-format support and input/output prices in USD per million tokens.

The catalogue is not loaded in the background or stored. Account/provider restrictions can still affect availability. Existing selections are preserved, and model IDs can also be entered manually.

ai/api/v1/key. The key is sent to OpenRouter for authentication, with no article content or text generation. Testing does not save a newly entered key, enable AI suggestions or verify model availability and generation credit.

The API key is encrypted with the site’s WordPress authentication salt in a non-autoloaded option, never returned to the browser. Changing that salt requires reconnecting the key. php.

A separate short-lived database lock limits generation to one request per editor per minute; it is reclaimed on demand and removed on uninstall. There are no scheduled AI jobs.

• OpenRouter documentation: https://openrouter.ai/docs/quickstart

• Terms: https://openrouter.ai/terms

• Privacy policy: https://openrouter.ai/privacy

0 or later when an AI provider is set up under Settings → Connectors. It is disabled by default and uses the same switch in Ostheimer SEO → AI assistance. With this choice, Ostheimer SEO itself sends nothing to an external endpoint: it hands the article title and up to 16,000 characters of plain article text, including drafts, to WordPress’s AI Client (wp_ai_client_prompt()), and WordPress sends them to the provider configured there, under that provider’s terms and privacy policy.

Which provider and model WordPress uses, and what it costs, is set up and billed outside this plugin. Showing this choice on the settings page sends no request. Password-protected posts are excluded, generated text is a draft until the post is saved, and existing custom SEO text is preserved unless the editor explicitly selects replacement.