How to Run an SEO Audit in Claude Code With Live Search Data

Start with a bounded SEO audit

To run an SEO audit in Claude Code with live data, connect a search-data provider, define the URL and crawl scope, request evidence-backed findings and review the fixes before applying them. The SEO/AEO/GEO plugin packages those tasks around DataForSEO, with separate code-review guidance for Next.js and Sanity.

A useful first request is: "Audit this page and its immediate internal links. Report the data source, crawl date, confirmed problems and anything unavailable. Recommend changes, but do not edit or deploy." A single page is easier to validate than an unbounded whole-site crawl.

What Problem Does It Solve — and What's the Difference Between SEO, AEO, and GEO?

SEO covers search visibility and technical eligibility. AEO and GEO are industry terms for making content useful to answer-oriented and generative search experiences. They overlap; none provides a separate guarantee of inclusion in an AI answer.

Define which surface you want to measure: a Google result, an AI Overview source or a supported provider's brand-mention response. A missing result from one query is not proof that a brand never appears. Record the query, location, language, provider and date.

How Does the Plugin Work?

Skills supply reusable instructions; namespaced commands provide explicit entry points. Install the plugin, confirm that the DataForSEO connection works, then use /seo-aeo-geo:seo-audit with the agreed URL and limits. Review the request scope before a paid crawl begins.

The released plugin has seven skills. Live crawl, search, keyword and backlink requests need DataForSEO access. Content-editing guidance and Next.js/Sanity code review can work on supplied material without a live data call. Keep that distinction visible when a data connection is unavailable.

What Skills Does the Plugin Ship With?

Select the skill for the job. A trigger description can help the assistant find it, but an explicit command is useful when you want to make the chosen workflow clear.

What Commands Does the Plugin Ship With?

Commands provide a workflow, not a guarantee of complete evidence or approved edits. Reports should identify partial crawls, provider failures and missing measurements. Writing code and deploying it remain separate authorized steps.

How Do You Actually Use the Plugin?

You use it the same way you'd talk to a colleague running the audit — describe the site, page, or question, and the right skill or command activates. Here are three example prompts pulled directly from real workflows:

Audit a page: /seo-aeo-geo:seo-audit https://example.com/service. State the crawl limit and whether JavaScript rendering is needed. Ask for each finding's affected URL, evidence and verification step. A health score is a summary, not a substitute for that list.

Check AI visibility separately: /seo-aeo-geo:ai-visibility example.com. Review which provider endpoints and query set were used. Treat the result as a dated sample, and distinguish unavailable observations from zero mentions.

Review code when appropriate: /seo-aeo-geo:code-seo-review apps/web inspects a Next.js/Sanity codebase. Ask for a report first, then authorize scoped changes. Check generated metadata and structured data against the public page before deploying.

After the first audit, prioritize issues that block access or mislead users, then improve the page's answer to its intended query. Keyword research can inform a revision, but only use measured fields actually returned by the provider. Recheck the affected page after an approved fix instead of treating a changed file as a verified public result.

What Do You Need to Get Started?

For live requests, the released plugin needs DATAFORSEO_USERNAME and DATAFORSEO_PASSWORD. On macOS, its launcher can obtain them through the Keychain helper; supported Claude hosts can also inherit explicitly supplied environment variables. Keep credentials out of prompts, article drafts and committed configuration.

The current Codex manifest uses the bundled secret launcher and expects the documented Keychain setup rather than exported shell credentials. For Claude Code, verify the environment or helper used by the launched process. A missing connection should be reported as unavailable; do not replace live measurements with model guesses. /content-optimize and code-facing review can still work on supplied content without a live data call.

The plugin ships advisory hooks for SEO-related edits and reads. Its former standalone SessionStart banner has been removed. Hooks can remind an operator to review metadata or schema, but they do not establish that a crawl completed or that a public page is correct.

Who Is This Plugin For?

This workflow suits a marketer or developer who can review the evidence and act on a bounded set of findings. The live-data tools are not limited to Next.js; the code implementation skill is. Confirm provider access, usage charges and site ownership before expanding the crawl.

In Claude Code, add the marketplace with /plugin marketplace add https://github.com/Rhize-Media/rhize-plugins, install seo-aeo-geo@rhize-plugins and start a fresh session. Follow the current credential setup at https://github.com/Rhize-Media/rhize-plugins/tree/main/seo-aeo-geo. Start with one page and one reviewed action list. If you want a self-service starting point for your business visibility, use the Rhize Scan.