Read-only local campaign artifact

schema-spider-audit.md

direct-content-wave-24/schema-spider-audit.md

# Schema Spider -- retained homepage audit

## Result: PARTIAL

The direct local generation task completed against the retained HTML capture. The result is not a fresh crawl, does not establish the current deployed markup, and was not injected into the site.

## Captured-markup observations

The retained HTML contains several JSON-LD payloads added by scripts. The capture includes homepage, residential-cleaning, and office-cleaning identifiers in the same source. That is a collision-risk signal, not proof of a current production defect.

| Check | Retained-capture result | Treatment in candidate |
|---|---|---|
| Business identity | name, address, phone, hours, CID, and homepage URL were present | retained |
| Visible FAQ | five homepage Q&A pairs were present | copied exactly |
| AggregateRating / review markup | not used in the clean candidate | omitted |
| Price range | a captured script included a range, but the retained visible homepage text does not state one | omitted |
| Social profiles | script values were present but not independently checked | omitted |
| Other page schema | residential and office identifiers occurred in the homepage capture | omitted from homepage candidate |

## Candidate scope

`schema-spider-homepage-candidate.json` is a clean homepage graph with one business focus, `WebPage`, `WebSite`, and the page-visible `FAQPage`. It does not create multiple service entities, a QAPage, review markup, or unavailable field placeholders.

## Implementation gate

Before any WordPress change, recapture the homepage and compare IDs, NAP, visible FAQ text, and existing markup. Resolve the cross-page schema collision, if confirmed, before adding this candidate. Validate in the Schema.org Validator and Google Rich Results Test only after the markup is present in a staging or approved production HTML response.