---
name: review-website-quality
description: Review website releases and SEO monitoring integrations with GuGuData non-mutating website quality APIs. Use when reviewing pull requests that change public pages, SEO metadata, DNS or TLS configuration, monitoring code, or keyword visibility checks and require evidence from documented GuGuData endpoints.
---

# Review Website Quality

Review website changes with documented GuGuData website-quality APIs and return concise, evidence-backed GitHub review comments.

## Target Users

- Web developers reviewing public-site releases
- SEO and growth engineers validating discoverability changes
- Platform teams reviewing DNS, TLS, and uptime-related integrations

## Invocation Boundary

- Review public URLs and repository changes only.
- Do not query private, authenticated, preview, or internal URLs unless the user explicitly authorizes them.
- Do not modify DNS, TLS, hosting, search campaigns, subscriptions, API keys, or account settings.
- Treat search visibility checks as credit-consuming queries and run them only with explicit user authorization.
- Report measured evidence; do not promise rankings, traffic, or availability.

## Read-Only Tools

Use only documented GuGuData operations that inspect a site:

- `getPagespeedScore` for public page performance evidence
- `getDnslookup` for DNS resolution evidence
- `getSslcertinfo` for public certificate metadata
- `getWhois` for public registration metadata
- `postSearchVisibility` for authorized keyword visibility checks

Use the published OpenAPI description at `https://gugudata.io/.well-known/openapi.json` to confirm operation names and parameters. Use `https://mcp.gugudata.io/mcp` only for account-authorized discovery and read-only calls.

## Review Workflow

1. Identify the public URL, SEO metadata, DNS, TLS, or monitoring behavior changed by the pull request.
2. Match the change to the smallest relevant operation from the published OpenAPI description.
3. Inspect the code path before calling an API. Skip live calls when static contract review is sufficient.
4. If authorized, run the minimum read-only check needed to validate the change.
5. Review handling for `400`, `401`, `403`, `429`, `5xx`, and timeout responses.
6. Cite the affected file and exact evidence. Separate confirmed defects from optional improvements.

## GitHub Code Review Example

User request:

> Review this pull request with `$review-website-quality`. It changes canonical tags and the production hostname. Use public, read-only checks only.

Expected review behavior:

- Compare canonical, Open Graph, and structured-data URLs with the changed production hostname.
- Use `getDnslookup` or `getSslcertinfo` only when a live public check materially confirms the finding.
- Write actionable GitHub comments with file paths, line references, observed evidence, and a proposed fix.
- State when no blocking issue is found.

## Output

Return findings ordered by severity. For each finding include the affected file, evidence, user impact, and smallest safe fix. End with checks performed and checks skipped.