- Resolve the input. The skill works from a URL, keyword, or domain, depending on the selected command.
- Inspect page evidence. URL paths review the accessible product content, images, internal paths, and visible Product or Offer markup.
- Check paid access. Marketplace paths require
DATAFORSEO_USERNAME and DATAFORSEO_PASSWORD, followed by the cost guardrail before any request.
- Collect a provider snapshot. When approved, DataForSEO can return Google Shopping or internal Amazon helper results for a chosen location and language.
- Separate findings from limits. The output should distinguish observed page evidence, structured-data issues, provider data, recommended actions, and unknowns.
Cost and permission boundary
Claude SEO is MIT licensed, but paid provider calls are not free. The products and gaps commands require the optional DataForSEO extension. The full URL command can use that extension, while the schema command does not need it. The workflow must check the configured daily budget before each Merchant API request. Amazon endpoints are warning endpoints in the pinned guardrail and always require explicit approval.
The cost guardrail reads or writes ~/.config/claude-seo/dataforseo-costs.json and ~/.config/claude-seo/dataforseo-ledger.json. Review the configured budget before a paid call, and do not publish either local file.
Failure behavior
| Condition | Documented response |
| Invalid or non-product URL | Reject malformed input. For a category or homepage, identify the page type and suggest the schema path. |
| No Product schema | Analyze available page content and recommend markup instead of claiming validation success. |
| Missing DataForSEO credentials | Continue without marketplace data and label the limitation. |
| Blocked cost check | Stop the paid request and offer the page-only analysis. |
| Empty Shopping results | Suggest a broader keyword and re-check location settings. |
| Amazon provider timeout | Retry with backoff, then fall back to Google-only evidence. |
Outputs
- Page and visible structured-data findings for the supplied URL
- Product or Offer property findings and truthful correction recommendations
- Marketplace snapshots only when the paid path is configured and approved
- A prioritized action list with evidence, source, and limitation labels
What the result cannot prove
Valid Product markup can create eligibility for richer search appearances, but it does not guarantee that Google will show one. Provider snapshots are not first-party Merchant Center or Seller Central truth. Marketplace results can vary by location, language, and collection time. No live marketplace request was made for this page update.