Skip to content

Releases: cod3fran/geo-optimizer-pro

Release list

v0.2.0 - Phase 2 Complete

v0.2.0 - Phase 2 Complete Latest
Latest

Choose a tag to compare

View all tags
@cod3fran cod3fran released this 04 Aug 05:28
v0.2.0
efce2b2

GEO Optimizer Pro

Enterprise WordPress plugin for Traditional SEO + Generative Engine Optimization (GEO/AISO/AI Search Optimization).

GEO Optimizer Pro prepares your WordPress site to be understood, indexed, and correctly cited by both traditional search engines (Google, Bing, DuckDuckGo, Brave Search) and AI/LLM engines (ChatGPT, Claude, Gemini, Perplexity, Copilot, Mistral, DeepSeek, Meta AI, and future crawlers) — while keeping full compatibility with traditional SEO plugins.

Status: Phase 1 (MVP / Foundation) — architecture, core modules, and CI/CD are implemented and functional. See ROADMAP.md for what is implemented today, what is partial, and what depends on third parties.

Why this exists

Traditional SEO optimizes for crawlers that rank pages. GEO optimizes for models that read, summarize, and cite pages. Those are different problems:

SEO GEO
Consumer Search engine ranking algorithm LLM / generative answer engine
Unit of value Ranking position Being cited / correctly represented
Format HTML + structured data HTML + structured data + clean Markdown + explicit usage policy
Risk Poor ranking Hallucination, misattribution, no citation

GEO Optimizer Pro closes that gap without breaking your existing SEO setup.

Core capabilities (Phase 1 - 2)

  • GEO Score engine — 0-100 score evaluating structure, schema, headings, FAQ, tables, lists, links, images/alt, canonical, robots/llms directives, and AI readability.
  • AI-optimized Markdown generation — every indexable URL gets a clean Markdown representation (title, summary, structured content, FAQ, references) cached via transients/object cache.
  • llms.txt generator — allow/disallow rules, priorities, preferred sources, citation rules, allowed/disallowed models.
  • ai-policy.json generator — machine-readable usage policy (no hallucination, no fact alteration, always cite source, respect license, etc.).
  • Intelligent robots.txt module — independent rules per known AI/search bot (GPTBot, ClaudeBot, PerplexityBot, CCBot, Google-Extended, Bytespider, AmazonBot, and more), extensible via a bot-provider registry.
  • AI bot detection & logging — identifies known crawlers by User-Agent/IP heuristics and stores visit history.
  • REST API — endpoints for score, markdown, llms.txt status, and bot logs.
  • React (Vite) + Tailwind + Chart.js dashboard scaffold — foundation for the visual dashboard.
  • Enterprise engineering baseline — PSR-4, Composer, DI container, WordPress Coding Standards, PHPUnit, PHPCS, GitHub Actions CI.

Modules for Phase 2/3 (advanced analytics, third-party integrations, full auditor, recommendation engine, multisite scale) are designed and documented, not yet fully implemented — see the roadmap.

Requirements

  • PHP 8.2+
  • WordPress 6.4+
  • Composer 2.x, Node.js 18+ (for the dashboard build)

Installation (development)

git clone https://github.com/cod3fran/geo-optimizer-pro.git
cd geo-optimizer-pro
composer install
npm install --prefix admin
npm run build --prefix admin

Symlink or copy the resulting folder into wp-content/plugins/geo-optimizer-pro and activate it from Plugins in wp-admin.

Documentation

Important note on AI standards

There is currently no official cross-vendor protocol by which AI providers (OpenAI, Anthropic, Google, Microsoft, etc.) report which pages they queried, confirm compliance with llms.txt/ai-policy.json, or guarantee citation behavior. llms.txt and ai-policy.json are community conventions, not enforced standards — no crawler is contractually required to obey them. This plugin implements everything that is technically possible today (bot-level robots.txt rules, clean Markdown, structured data, provenance metadata) and is architected with adapters/providers/feature flags so new standards can be plugged in as they emerge, without breaking existing sites. See ROADMAP.md for the explicit today/partial/third-party-dependent breakdown.

Branching model

  • main — stable, released code.
  • develop — integration branch for ongoing work.
  • Feature branches merge into develop via pull request; develop merges into main at release time (SemVer tags).

License

GPL-2.0-or-later. See LICENSE.

Contributing

See CONTRIBUTING.md and CODE_OF_CONDUCT.md.

Security

See SECURITY.md for how to report vulnerabilities.

Assets 2
Loading