Opens in a new tab
Deliver toTennessee
0 0 0Cart
Get a Project Quote

Athenian SEO (Lean)

v0.2.1 October 6, 2026
A lightweight WordPress SEO foundation for metadata, social previews, structured data, and discoverability.

Overview

Product overview

Many WordPress and WooCommerce sites do not need a sprawling SEO platform with dozens of features, opinionated content scoring, or heavy dashboard bloat. What they do need is reliable control over the tags and structured data that affect indexing, social sharing, and crawlability.

Athenian SEO (Lean) solves that by focusing on the essential SEO layer. It generates titles and descriptions from configurable templates, outputs canonical URLs and robots directives, publishes OpenGraph and Twitter metadata, emits JSON-LD schema, and produces XML sitemaps with cache control and inclusion rules. It also gives editors per-post overrides and gives developers extension points for custom implementations, including WPGraphQL support for social image resolution.

SEO settings, title, description, robots, and canonical surfaces.
Open Graph, social-image, schema, and sitemap integration.
Admin and frontend rendering boundaries documented from source.
A baseline for later rendered-head, sitemap, and search-preview verification.

Use cases

  • Search metadata
  • Social previews
  • Structured data
  • Site discoverability

Developer

Developer starting point

This baseline documents the Lean SEO implementation. It does not claim that production head output, a sitemap, a social preview, structured data result, or search-engine indexing outcome has been exercised.

Ecosystem integration story

WordPress core

Athenian SEO (Lean) works with native WordPress title, head, archive, taxonomy, and post metadata flows rather than replacing the platform. It fits into the existing rendering pipeline and extends standard content types with a focused SEO layer.

WooCommerce

For WooCommerce sites, Athenian SEO (Lean) adds product-aware schema, social-image fallbacks for product experiences, and sitemap support for product URLs. It gives merchants a better SEO baseline for commerce content without requiring a large commerce-specific SEO system.

WPGraphQL and headless applications

When WPGraphQL is active, the plugin can expose a normalized social image field to GraphQL consumers. That makes it useful in hybrid and headless architectures where social preview logic still needs to be resolved centrally.

Existing SEO plugin environments

Athenian SEO (Lean) includes conflict detection for common SEO plugins such as Yoast SEO, Rank Math, SEOPress, and All in One SEO. This helps administrators recognize when duplicate SEO output may occur and manage coexistence more safely.

Install

Source and dependencies
  • Reviewed source folder: athenian-seo-lean
  • Plugin version reviewed: 0.2.1
  • Local source inventory: 21 files (temporary, test, and Git metadata excluded).
  • GitHub baseline: https://github.com/Athenian-Brands/athenian-seo-lean at baseline/devdocs-0.2.1-20261006f / cea2de18bda7ab2f4d4be444ac179f9b6497249f.
  • WordPress and the active site theme.
  • Frontend head rendering, canonical URLs, schema output, sitemaps, and search-engine behavior require separate verification.

Configuration

Implementation reference sections
  • Working positioning — see the linked technical reference excerpt.
  • Executive summary — see the linked technical reference excerpt.
  • Core marketing message — see the linked technical reference excerpt.
  • The problem Athenian SEO (Lean) solves — see the linked technical reference excerpt.
  • What Athenian SEO (Lean) does — see the linked technical reference excerpt.
  • Ecosystem integration story — see the linked technical reference excerpt.
  • Why this matters commercially — see the linked technical reference excerpt.
  • Key differentiators — see the linked technical reference excerpt.
  • Suggested messaging pillars — see the linked technical reference excerpt.
  • Short-form copy options — see the linked technical reference excerpt.
  • Sales narrative — see the linked technical reference excerpt.
  • Best-fit use cases — see the linked technical reference excerpt.
  • Positioning statement — see the linked technical reference excerpt.
  • Platform-focused primary functionality copy — see the linked technical reference excerpt.

Usage

Detected extension surface
  • Shortcodes detected in local PHP source: 0
  • Static action/filter hooks detected in local PHP source: 24
  • REST route registrations detected in local PHP source: 0

Shortcodes

Detected shortcodes
  • No static add_shortcode registrations were detected by the baseline scanner.

REST Endpoints

Detected REST routes
  • No register_rest_route calls were detected by the baseline scanner.

Hooks

Detected hooks
  • add_meta_boxes — includes/class-admin.php
  • admin_enqueue_scripts — includes/class-admin.php
  • admin_init — includes/class-admin.php
  • admin_menu — includes/class-admin.php
  • aseo/content_changed — includes/class-sitemaps.php
  • created_ — includes/class-social-images.php
  • deleted_post — includes/class-sitemaps.php
  • document_title_parts — includes/class-meta.php
  • edited_ — includes/class-social-images.php
  • graphql_register_types — includes/class-graphql.php
  • init — includes/class-sitemaps.php
  • plugins_loaded — athenian-seo.php
  • query_vars — includes/class-sitemaps.php
  • robots_txt — includes/class-sitemaps.php
  • save_post — includes/class-admin.php
  • save_post — includes/class-sitemaps.php
  • switch_theme — includes/class-sitemaps.php
  • template_redirect — includes/class-sitemaps.php
  • wp_ajax_aseo_preview_meta — includes/class-admin-ajax.php
  • wp_ajax_aseo_preview_schema — includes/class-admin-ajax.php
  • wp_ajax_aseo_sitemap_regen — includes/class-admin-ajax.php
  • wp_head — includes/class-meta.php
  • wp_head — includes/class-opengraph.php
  • wp_head — includes/class-schema.php

Data Model

Persistence and integration boundary
  • Ecosystem integration story — described in the local technical reference.

API Reference

Source inventory and provenance
  • Local source digest: bba475e2058af8e5f2f78a1ef49ffd6dd3e29ea19b61b3e105da8c5843de7126
  • Repository URL: https://github.com/Athenian-Brands/athenian-seo-lean
  • Repository reference: baseline/devdocs-0.2.1-20261006f
  • Repository commit: cea2de18bda7ab2f4d4be444ac179f9b6497249f
  • Source files include: .gitignore, assets/admin.css, assets/admin.js, athenian-seo-lean.png, athenian-seo.php, athenian-seo.zip, docs/aseo-marketing-document.md, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, docs/technical-marketing.md, includes/bootstrap.php, includes/class-admin-ajax.php, includes/class-admin.php, includes/class-graphql.php, includes/class-meta.php, includes/class-opengraph.php, includes/class-plugin.php, includes/class-schema.php, includes/class-sitemaps.php, includes/class-social-images.php, includes/class-utils.php

Troubleshooting

Baseline review boundary
  • This baseline documents the Lean SEO implementation. It does not claim that production head output, a sitemap, a social preview, structured data result, or search-engine indexing outcome has been exercised.

  • Confirm the deployed plugin version, active dependencies, and current repository tree before using implementation details as a release contract.
  • Treat payment, carrier, vendor, shipment, inventory, account, credential, tax, AI, and external-provider behavior as integration-dependent until exercised in the target environment.

FAQ

What is this page intended to establish?

A versioned, product-linked starting point for iterative developer documentation. It combines the local implementation reference with a detected-code inventory and a committed GitHub baseline.

Is the linked repository baseline verified?

Yes. The repository URL, ref, and commit recorded on this page were verified from the clean GitHub baseline prepared for this documentation pass. That does not by itself prove fleet deployment parity.

What remains for release-grade documentation?

Reconcile the recorded source baseline with the deployed plugin version, then exercise the relevant authenticated, store, provider, payment, tax, carrier, or generated-artifact paths in the target environment.

Changelog

0.2.1 2026-10-06