bingoss/owned-growth-engine
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Technical Audit uses server GSC API crawl and index evidence #10

New issue
Closed
opened 2026-05-28 18:14:39 +01:00 by bingoss · 1 comment
bingoss commented 2026-05-28 18:14:39 +01:00
Owner
Copy link

What to build

Type: AFK.

Add server-side Google Search Console API evidence to Technical Audit where available. The agent should use the configured GSC API access path on the server, not a local import workflow, and record crawl/index evidence as normalized findings or metric evidence.

Acceptance criteria

  • Technical Audit can read configured server GSC API evidence for audited URLs or site-wide index signals.
  • GSC evidence is linked to Technical Findings or metric evidence without storing secrets or raw credential material.
  • Missing optional GSC evidence is visible as safe diagnostics; required GSC failure blocks according to requirement settings.
  • Tests are written first with a deterministic GSC seam for measured, skipped, and failed-required paths.

Blocked by

None - can start immediately

## What to build Type: AFK. Add server-side Google Search Console API evidence to Technical Audit where available. The agent should use the configured GSC API access path on the server, not a local import workflow, and record crawl/index evidence as normalized findings or metric evidence. ## Acceptance criteria - [ ] Technical Audit can read configured server GSC API evidence for audited URLs or site-wide index signals. - [ ] GSC evidence is linked to Technical Findings or metric evidence without storing secrets or raw credential material. - [ ] Missing optional GSC evidence is visible as safe diagnostics; required GSC failure blocks according to requirement settings. - [ ] Tests are written first with a deterministic GSC seam for measured, skipped, and failed-required paths. ## Blocked by None - can start immediately
bingoss commented 2026-05-28 23:16:33 +01:00
Author
Owner
Copy link

Issue #10 completion audit

Requirements checked:

  • Technical Audit now has a server-side Google Search Console URL Inspection adapter seam for audited URLs; local imports/export files are not used as the product path.
  • GSC index evidence writes run_stage_adapter_results, retention-managed raw_provider_payloads, and normalized Technical Findings for index, robots, sitemap, and fetch-status blockers when evidence supports them.
  • Missing optional GSC evidence records skipped diagnostics; required GSC failure blocks promotion through the existing required-adapter gate.
  • Dashboard output exposes GSC adapter state and diagnostics without raw inspection payloads or credential material.
  • Tests were written first for measured GSC evidence, skipped optional configuration, and failed-required promotion blocking.

Docs checked through ctx7:

  • Google Search Console URL Inspection API , using , , and fields.

Verification on codex-server:

  • python3 -m unittest tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_worker_records_measured_gsc_index_evidence tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_worker_records_skipped_optional_gsc_adapter_when_unconfigured tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_required_gsc_adapter_failure_blocks_weekly_promotion -> OK
  • python3 -m unittest tests.test_site_crawler tests.test_technical_audit_worker -> 38 tests OK
Issue #10 completion audit Requirements checked: - Technical Audit now has a server-side Google Search Console URL Inspection adapter seam for audited URLs; local imports/export files are not used as the product path. - GSC index evidence writes run_stage_adapter_results, retention-managed raw_provider_payloads, and normalized Technical Findings for index, robots, sitemap, and fetch-status blockers when evidence supports them. - Missing optional GSC evidence records skipped diagnostics; required GSC failure blocks promotion through the existing required-adapter gate. - Dashboard output exposes GSC adapter state and diagnostics without raw inspection payloads or credential material. - Tests were written first for measured GSC evidence, skipped optional configuration, and failed-required promotion blocking. Docs checked through ctx7: - Google Search Console URL Inspection API , using , , and fields. Verification on codex-server: - python3 -m unittest tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_worker_records_measured_gsc_index_evidence tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_worker_records_skipped_optional_gsc_adapter_when_unconfigured tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_required_gsc_adapter_failure_blocks_weekly_promotion -> OK - python3 -m unittest tests.test_site_crawler tests.test_technical_audit_worker -> 38 tests OK
Commenting is not possible because the repository is archived.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
codex-token-write-test-1780004082
Temporary token write test; safe to delete.

No labels
codex-token-write-test-1780004082
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#10
No description provided.