Linux 软件免费装
Banner图

GEO Rank Optimizer - Generative Engine Optimization

开发者 alexbarbosa
更新时间 2026年10月27日 23:43
PHP版本: 7.4 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

ai seo llms.txt generative engine optimization answer engine optimization aeo

下载

3.9.21 3.9.24 3.9.39 3.9.19

详情介绍:

Be Found and Cited by AI. For a long time, the goal was to master SEO and rank on Google. Now the game has changed: with GEO (Generative Engine Optimization), your site can be found and cited by AI models like ChatGPT, Claude, Gemini, Perplexity, and others. GEO Rank Optimizer covers both sides of AI search. GEO (Generative Engine Optimization) is about being the source a generative engine cites by name. AEO (Answer Engine Optimization) is about structuring your content so those engines can lift it as the direct answer. This plugin is the AI SEO layer that handles both, on top of whatever you already do for Google. Who it is for This plugin is built for bloggers and publishers who want their articles quoted instead of ignored, WooCommerce stores that want their products named when someone asks an AI for a recommendation, agencies running AI visibility for client sites, and anyone who wants to know whether AI crawlers are actually reading their content. It is designed to sit alongside your existing SEO plugin, not replace it. GEO Rank Optimizer reads the data you already filled in — it picks up meta titles, Open Graph fields and focus keywords from Yoast SEO, Rank Math and All in One SEO instead of asking you to type them again, and its AI crawler rules are appended to robots.txt after those plugins run, so it never overwrites what they wrote. With the GEO Rank Optimizer plugin: No complex setup required: install, activate, and your site starts speaking the language of AI. The future of search isn't a link. It's a citation. Agent Ready: the ACP and UCP manifests AI agents are starting to browse — and buy — on their own, and before they do they look for a manifest at /.well-known/agent.json. GEO Rank Optimizer checks whether your site publishes one, and whether it publishes the UCP manifest alongside it, right on the dashboard next to your llms.txt and ai.txt status. It runs the same check against any competitor you enter, so you can see who in your market is already agent-ready and who is not. This is still an emerging standard, which is exactly why it is worth knowing where you stand before your competitors do. Generating the agent.json manifest for a WooCommerce store, following the ACP (Agentic Commerce Protocol) standard, is available in Pro + WooCommerce, together with llms-shop.txt — a structured product catalog for commerce agents. Analysis Categories
  1. Generative Search - Quick answers, FAQ structure, definitions
  2. Structure - Heading hierarchy, paragraphs, lists
  3. Semantic - Keywords, variations, named entities
  4. Readability - Flesch-Kincaid, active voice, transitions
  5. Context - Introduction, conclusion, internal/external links
  6. Authority - Author info, dates, sources cited
  7. Technical Formatting - Images, videos, tables, code blocks
  8. Technical SEO - Meta title, description, Open Graph, Schema
Why GEO Matters Traditional SEO focuses on ranking in search results. GEO focuses on being cited by AI in generative responses. As AI-powered search becomes more prevalent, optimizing for AI understanding is crucial for visibility.

安装:

  1. Upload the geo-rank-optimizer folder to the /wp-content/plugins/ directory
  2. Activate the plugin through the 'Plugins' menu in WordPress
  3. Go to any post and look for the "GEO Score" metabox
  4. Click "Analyze" to get your content's GEO score and recommendations

屏幕截图:

  • Dashboard with AI visibility and GEO Score overview
  • Post GEO diagnostics with score and optimization criteria
  • AI Bot Tracker for visits from AI assistants and crawlers
  • Competitor analysis for GEO files and AI directives
  • Settings and AI file generation (llm-full.txt, llms.txt, ai.txt)

升级注意事项:

3.9.30 Fixes "OpenAI" appearing as "Open" in all translated languages, plus a broken French string and incorrect score thresholds. 3.9.29 Completes the icon alignment fix from 3.9.28, which was not taking effect. 3.9.28 Visual fix: icons are now vertically centered in every plugin button, including Test Connection. 3.9.27 Visual fix: the trash icons in the Settings danger buttons are now vertically centered with their labels. 3.9.26 Readability fix: the AI Bot Tracker card subtitles are now large enough to read. 3.9.25 The AI Bot Tracker cards now explain what each kind of visit means instead of repeating the star ranking. 3.9.24 Listing update: new Agent Ready section covering the ACP and UCP manifest checks, and the editor score moved to the top of the feature list. No functional changes. 3.9.23 Maintenance release: version parity with the PRO build. No functional changes in the free version. 3.9.22 Directory listing update: new tags, clearer short description, and new sections explaining GEO vs AEO, who the plugin is for, and how it works alongside Yoast SEO and Rank Math. No functional changes. 3.9.21 Refines the contextual Pro block in the sidebar: merged with the Pro button, clearer call to action. 3.9.20 Adds contextual Pro feature information in the plugin sidebar and fixes untranslated LLM accessibility messages. Recommended update. 3.9.19 Maintenance and accuracy release: cleaner free build (removed unused integration code) plus several diagnostic improvements. Recommended update.

常见问题:

What is GEO?

GEO stands for Generative Engine Optimization. It's the practice of optimizing content to be better understood, summarized, and cited by AI engines like ChatGPT, Google AI Overview, Perplexity, and others.

What is the difference between GEO and AEO?

AEO (Answer Engine Optimization) is about structuring your content so an answer engine can lift it as the direct answer — clear question-style headings, a short answer near the top, lists and tables, and valid schema. GEO (Generative Engine Optimization) is about being the source the engine cites by name once it has that answer. They overlap heavily, and this plugin scores and fixes both.

Does this plugin require Yoast SEO or other plugins?

No. GEO Rank Optimizer works completely independently without requiring any other SEO plugins.

Will it conflict with Yoast SEO or Rank Math?

It is built to run alongside them. GEO Rank Optimizer reads the meta titles, Open Graph fields and focus keywords you already set in Yoast SEO, Rank Math or All in One SEO rather than asking you to fill them in twice, and its AI crawler rules are appended to robots.txt after those plugins have run, so your existing directives are preserved. One thing to be aware of: if your SEO plugin already outputs Article or Organization schema and you also enable schema output here, both will be present on the page. If that is your setup, turn off schema generation in one of the two plugins.

How is the GEO Score calculated?

The score is calculated based on 40+ criteria across 8 categories, each with different weights. Generative Search optimization has the highest weight as it directly impacts AI citability.

Will this plugin slow down my site?

No. The analysis runs only in the admin area when you click "Analyze". It does not affect frontend performance.

What languages are supported?

English, Portuguese (Brazil), Spanish, French, and German.

更新日志:

3.9.39 3.9.30 Translation fixes: "OpenAI" was rendering as "Open" in every language 3.9.29 Fix: the button icon alignment rule now actually applies 3.9.28 Fix: dashicon alignment in every plugin button, once 3.9.27 Fix: trash icons misaligned in the Settings danger buttons 3.9.26 AI Bot Tracker: larger card subtitles 3.9.25 AI Bot Tracker: the four cards now say what each visit means 3.9.24 Listing: Agent Ready section and feature order 3.9.23 Maintenance: version sync 3.9.22 Directory listing: tags, positioning and compatibility clarity 3.9.21 Refined contextual Pro block in the sidebar 3.9.20 Contextual Pro information in the sidebar and translation fixes 3.9.19 Cleanup: free build no longer contains unused AI-provider code 3.9.18 Maintenance: version sync 3.9.17 Maintenance: version sync 3.9.16 Maintenance: version sync 3.9.15 Fix: post score no longer penalized for missing optional elements 3.9.14 Improvement: clearer post recommendations (cohesion vs. transition) 3.9.13 Maintenance: version sync 3.9.12 Improvement: competitor re-analysis cooldown 3.9.11 Fix: icon alignment in the Settings buttons 3.9.10 Fix: search icon alignment in the Analyze / Re-analyze buttons 3.9.9 Maintenance: version sync 3.9.8 Maintenance: version sync 3.9.7, 3.9.6, 3.9.5 Fix: Diagnostics action buttons keep their pill shape in all states The "See Recommendations / Edit Post / View Post" anchors were distorted by wp-admin's native anchor styles across :active and :focus (square shape, then a blue ring, then a red rectangular border). Added :active/:focus rules pinning the pill shape and switched the focus ring to :focus-visible (keyboard-only). CSS-only fix. 3.9.4 Fix: Competitors tab — Analyze and Delete buttons now work A nonce action name mismatch (introduced in v3.7.5 when admin JS was externalized) made check_ajax_referer() fail silently in the ?tab=competitors page. Nonce aligned with the handlers. Same fix applied to the step-6 onboarding auto-refresh, which was failing for the same reason. 3.9.3 Defense-in-depth: explicit nonce check on bulk-action handler GeoIaWpCore::handle_bulk_actions() now calls check_admin_referer( 'bulk-posts' ) explicitly. WordPress core already verifies this nonce before dispatching the filter, but the explicit check makes the security contract visible to auditors and protects against future refactors. No functional change. 3.9.2 Plugin Check cleanup: zero errors, zero warnings Tested up to bumped to 7.0. Changelog rewritten to fit the 5000-char limit (full history in CHANGELOG.md). All foreach loop variables in 8 admin templates renamed to the $georankopt_* prefix to satisfy WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedVariableFound. Zero functional changes. 3.9.1 Fix: Save Settings button — icon and text now stay white in all states Corrected the CSS selector targeting (was using a legacy ID; now uses the actual .geo-save-config-btn class). The dashicon and label remain white on the pink background during base, hover, and :disabled (saving) states. Hover suppressed during save. Same fix in FREE and PRO. 3.9.0 Fix: Save Settings button visual during saving state :disabled rules added that preserve pink background and white text/icon (overriding the browser's graytext default). Hover effect suppressed while disabled. Consolidates several UI polish fixes since v3.8.0 (onboarding button "square flash", sidebar focus ring, Bot Tracker legend/disclaimer parity). 3.8.9, 3.8.8, 3.8.7 UI polish: :focus-visible on sidebar tabs to hide blue ring after mouse click while preserving keyboard accessibility. FREE/PRO parity for Bot Tracker (User-Agent disclaimer + "What each category means" 4-card legend in 5 locales). 3.8.6 Definitive fix: onboarding navigation buttons converted from <a> to <button> Root cause of the "button turns square on click" glitch: anchors inherited wp-admin :active styles (border-radius: 3px, reduced padding). Converting the 5 navigation anchors to <button type="button"> eliminates the issue entirely. The defensive CSS :active rule remains as secondary safeguard. 3.8.5, 3.8.4, 3.8.3, 3.8.2, 3.8.1 Iterative attempts to fix the onboarding button "square flash" via CSS specificity, scoped overrides, and :active declarations. All superseded by the structural fix in v3.8.6. v3.8.3 reverted earlier CSS changes that had inadvertently broken the hover state. 3.8.0 Post-Google I/O 2026 release 3.7.5 Resolves WP.org Plugin Review feedback (T5, 21 May 2026) 3.7.4 Fix: Dashboard could show contradictory file-accessibility status for LLM files. Now re-verifies after each generation/deletion; upgrade clears stale alerts. 3.7.3 Resolves WP.org review T4: wp_enqueue for inline assets, ob_start refactored, menu position, ABSPATH guards, all geo_* globals renamed to georankopt_*. Earlier versions For releases 3.5.0 through 3.7.2, see CHANGELOG.md in the plugin directory.