Copy, localization & SEO · Audit

SEO GEO Audit

Inspect the selected public routes for crawlable content, accurate metadata and useful answers. Define the relevant engine/site goal from the request; a valid build or Lighthouse score does not establish indexing, rankings or AI citations.

MCP library 1.6.1 · Instruction library 1.6.1 · English technical instructions

← Back to search

Use this workflow

Connect Vibe Coding Library to a coding agent that supports MCP over Streamable HTTP. Choose Other / MCP agent for a neutral prompt, or a ready-made Codex or Claude Code invocation. Add your task details below.

Scope

Inspect the selected public routes for crawlable content, accurate metadata and useful answers. Define the relevant engine/site goal from the request; a valid build or Lighthouse score does not establish indexing, rankings or AI citations.

Procedure

  1. Fetch or render the actual public output where available. Check status/redirects, access/noindex/robots, initial content, canonical and sitemap; distinguish server output from post-JavaScript links and content.
  2. Compare title, description, headings, visible claims, internal links and social metadata with the implemented product and page purpose.
  3. For supported locales, verify reciprocal language alternatives, self-canonical URLs and matching translated content; do not invent translated variants for a language selector alone.
  4. Validate existing or relevant structured data against its real entity and supported search feature. Missing optional schema, FAQ or a special AI file is not itself a defect.
  5. Assess whether readers can identify the product/subject, supported outcomes, constraints and evidence. Recommend structure or content only when it improves the selected page’s usefulness.
  6. Check relevant rendering/performance and regression evidence. Use connected search-console/citation data for visibility claims; mark unavailable account or field data explicitly.

Result

Give the route and defining source, expected/observed output, concrete public impact and one repair with validation. Bound source, rendering, crawler and account observations separately. Consult current Google AI-search guidance and engine-specific documentation for eligibility; do not manufacture rankings from technical compliance.

Pass the actual fetched/rendered route, status, canonical/locale relationships and violated content/metadata expectation into Improve Search Visibility. Keep public-output defects separate from unavailable console data or optional enhancements. A successful local build does not close a failed deployed route or prove that a search engine has indexed it.

Workflow ID: seo-geo-audit · View the versioned source · Shared workflow and authority rules