SEO audit with Aether Connect

Use Aether Connect and a coding agent to audit a website, fix technical SEO issues, and check the result with a repeatable before-and-after workflow.

The audit tool inspects your website. The coding agent uses Aether Connect to explain the findings and edit your project. Start with a local copy of your own website so you can review the changes before publishing them.

1. Prepare your project

You need Node.js 22 or newer, npm, Chrome or Chromium, Claude Code, and an Aether account with Connect access. Open a terminal in your website repository. Start your production build locally and keep that server running. In the commands below, replace port 4173 with your server's port. The audit itself makes no paid model requests; work in the coding agent uses your Connect allowance.

npm install -g @seomator/[email protected]
seomator --version
# Start your website's production server in a separate terminal.
# For Aether's landingpage: npm run build && PORT=4173 npm start

2. Connect your coding agent

Install the Aether CLI, log in, and connect Claude Code. Complete the browser login, then start the agent from your website repository. On Windows, use the PowerShell installer from the Connect documentation. Aether's Claude Code overlay keeps the normal project settings, plugins, and skills available.

curl -fsSL https://aetherapi.dev/install | sh
aether login
aether connect claude-code
aether claude

3. Save the first audit

Run this in another terminal in the same repository. The crawl is limited to 20 pages and two simultaneous requests. This first run skips Core Web Vitals; it is a technical baseline, not a full performance assessment. If the CLI exits with code 1 but writes a report, the audit completed and its score was below the tool's threshold. Code 2 means the audit failed to run; resolve that error before asking the agent to use the report.

seomator audit http://localhost:4173 --crawl --max-pages 20 --concurrency 2 --no-cwv --format json -o seo-before.json

4. Let the agent fix verified issues

Paste the prompt below into the Aether-connected agent. It asks for evidence and a reviewable patch. Check the crawl coverage: a high score from a single empty page does not establish that the rest of the website is healthy. Findings about localhost, HTTPS, or server headers may belong to production hosting rather than application code.

Read seo-before.json and inspect this website's source. Prioritize missing page content in the initial HTML, incorrect canonicals, broken internal links, and missing pages returning HTTP 200. Reproduce each issue before fixing it. Make focused changes, run the project's checks, and preserve the public URL structure. Compare titles, descriptions, canonicals, and social metadata before and after JavaScript loads. Explain which findings need hosting changes. Do not deploy. Treat crawl coverage and unmeasured rules separately from the score.

5. Rebuild and compare

Rebuild the website and restart its production server before running the second audit. Compare the affected URLs and rule IDs in the two JSON files. The same pages and options must be used for a meaningful comparison. If you also want performance measurements, run a separate audit without --no-cwv on a representative deployed page. Review the diff, publish through your normal deployment process, and audit the public URL again.

seomator audit http://localhost:4173 --crawl --max-pages 20 --concurrency 2 --no-cwv --format json -o seo-after.json
# For this Aether repository, also run:
# cd landingpage
# npm run check:seo

Technical SEO makes pages easier to crawl and understand. Search demand, useful content, and actual registrations still need separate measurement. Keep both audit reports as evidence instead of treating a higher score as a ranking promise.

Connect setup · SEO audit tool documentation

Aether API — OpenAI-compatible access to 13+ providers through one API key.