https://github.com/mizcausevic-dev/wordpress-block-seo-governance-auditor
PHP control plane for auditing WordPress block hierarchy, answer-surface readiness, and schema opportunities.
https://github.com/mizcausevic-dev/wordpress-block-seo-governance-auditor
answer-engine-optimization content-governance generative-engine-optimization php plugin schema-markup seo wordpress
Last synced: 12 days ago
JSON representation
PHP control plane for auditing WordPress block hierarchy, answer-surface readiness, and schema opportunities.
- Host: GitHub
- URL: https://github.com/mizcausevic-dev/wordpress-block-seo-governance-auditor
- Owner: mizcausevic-dev
- Created: 2026-05-17T04:14:22.000Z (27 days ago)
- Default Branch: main
- Last Pushed: 2026-05-17T05:04:38.000Z (27 days ago)
- Last Synced: 2026-05-17T07:11:56.447Z (27 days ago)
- Topics: answer-engine-optimization, content-governance, generative-engine-optimization, php, plugin, schema-markup, seo, wordpress
- Language: PHP
- Homepage: https://kineticgain.com/
- Size: 1.24 MB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
Awesome Lists containing this project
README
# WordPress Block SEO Governance Auditor
WordPress Block SEO Governance Auditor is a PHP control plane for auditing WordPress block hierarchy, answer-surface readiness, and schema opportunities across editorial pages.
It focuses on the real WordPress content problem:
- which pages have weak heading structure
- which FAQ and HowTo opportunities are still hidden inside generic blocks
- which promotional layouts are weakening answer-engine trust
- which content surfaces are structurally safe enough to repeat
## Routes
- `/` overview dashboard
- `/block-audit` page-by-page audit lane
- `/schema-opportunities` block-level schema and FAQ opportunities
- `/verification` proof posture
- `/docs` route and payload reference
## What this repo proves
- block-level SEO and AEO governance can be treated as an operator system, not just an editorial checklist
- WordPress block composition affects answer-surface quality as much as the copy itself
- schema opportunities are easier to capture when the page anatomy is already visible and scored
- PHP can still ship clean operator tooling in a modern portfolio context
## Screenshots
## Local development
```powershell
cd wordpress-block-seo-governance-auditor
php -S 127.0.0.1:5172 router.php
```
## Validation
- `php -l public/index.php`
- `php -l src/Services/AuditService.php`
- `php scripts/run_demo.php`
- `powershell -ExecutionPolicy Bypass -File .\scripts\smoke_check.ps1`
- `powershell -ExecutionPolicy Bypass -File .\scripts\render_readme_assets.ps1`