Technical Audit extracts structured data and schema findings #8

Closed
opened 2026-05-28 18:14:35 +01:00 by bingoss · 1 comment
Owner

What to build

Type: AFK.

Extend Technical Audit checks to extract structured data from audited pages and record schema/entity-readiness findings that matter for SEO and GEO. The product should distinguish unsupported, malformed, missing, and valid structured data without guessing entity facts.

Acceptance criteria

  • JSON-LD and other supported structured-data signals are extracted safely from audited pages.
  • Missing, malformed, or contradictory schema creates Technical Findings only when evidence supports the issue.
  • Findings explain SEO/GEO impact and include safe implementation and verification guidance.
  • Tests are written first for valid schema, malformed schema, missing schema, and dashboard rendering.

Blocked by

None - can start immediately

## What to build Type: AFK. Extend Technical Audit checks to extract structured data from audited pages and record schema/entity-readiness findings that matter for SEO and GEO. The product should distinguish unsupported, malformed, missing, and valid structured data without guessing entity facts. ## Acceptance criteria - [ ] JSON-LD and other supported structured-data signals are extracted safely from audited pages. - [ ] Missing, malformed, or contradictory schema creates Technical Findings only when evidence supports the issue. - [ ] Findings explain SEO/GEO impact and include safe implementation and verification guidance. - [ ] Tests are written first for valid schema, malformed schema, missing schema, and dashboard rendering. ## Blocked by None - can start immediately
Author
Owner

Issue #8 completion audit

Requirements checked:

  • Technical Audit extracts JSON-LD application/ld+json blocks safely without storing raw response bodies.
  • Valid JSON-LD with supported @type is accepted without a false finding.
  • Missing, malformed, unsupported, and URL-conflicting structured-data signals create normalized Technical Findings only from observed page evidence.
  • Findings include SEO/GEO impact, safe implementation guidance, and verification methods; no entity facts are guessed.
  • Dashboard rendering is covered through the existing Technical Findings read model and structured_data issue-type counts.
  • Tests were written first for valid schema, malformed schema, missing schema, and dashboard output.

Verification on codex-server:

  • python3 -m unittest tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_worker_accepts_valid_json_ld_structured_data tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_worker_records_malformed_json_ld_schema_finding tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_worker_records_missing_structured_data_and_dashboard_output -> OK
  • python3 -m unittest tests.test_site_crawler tests.test_technical_audit_worker -> 32 tests OK
Issue #8 completion audit Requirements checked: - Technical Audit extracts JSON-LD application/ld+json blocks safely without storing raw response bodies. - Valid JSON-LD with supported @type is accepted without a false finding. - Missing, malformed, unsupported, and URL-conflicting structured-data signals create normalized Technical Findings only from observed page evidence. - Findings include SEO/GEO impact, safe implementation guidance, and verification methods; no entity facts are guessed. - Dashboard rendering is covered through the existing Technical Findings read model and structured_data issue-type counts. - Tests were written first for valid schema, malformed schema, missing schema, and dashboard output. Verification on codex-server: - python3 -m unittest tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_worker_accepts_valid_json_ld_structured_data tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_worker_records_malformed_json_ld_schema_finding tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_worker_records_missing_structured_data_and_dashboard_output -> OK - python3 -m unittest tests.test_site_crawler tests.test_technical_audit_worker -> 32 tests OK
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
bingoss/owned-growth-engine#8
No description provided.