Autonomous technical SEO

Technical SEO that fixes itself.

An agent for your AI coding client. Point it at your site: it finds what's broken, fixes it in your repo, and proves it's live.

your terminal
# add Searchlight to your AI coding client
claude mcp add searchlight -- npx -y @ajmalaksar/searchlight serve

# then just ask
"why isn't my site showing up on Google? fix it."
Reads & writes
Google Search Console Search ConsoleGoogle Analytics AnalyticsGoogle Tag Manager Tag Manager
The loop

From “why isn't Google indexing me?” to fixed and deployed.

Most tools stop at the diagnosis. Searchlight runs the whole loop and proves the last step.

01

Detect

Reads your real Search Console and Analytics data and crawls your key pages.

02

Explain

Triages every finding in plain language: fix now, worth improving, or safe to ignore.

03

Fix

Edits your repository, framework-aware — canonical, redirects, sitemaps, metadata, the tag.

04

Deploy

Commits and ships through your pipeline. The deploy isn't handed back to you.

05

Verify

Re-audits the live site in a real browser: the redirect resolves, the tag fires.

Proof

One real site, the whole run.

A live session on zawaaj.in — a custom Next.js site with a host and canonical conflict and missing analytics. Not a summary; the actual loop.

Google Search Console zawaaj.insession · 2026-06-28
Detect4m

Homepage audit 90/100. Both https://zawaaj.in and https://www.zawaaj.in return 200 with no canonical, so Google reports Duplicate without user-selected canonical. Meta description 198 chars (truncates). No GA4 tag on the page.

Explain2m

Fix now: the apex and www both resolve, fighting for the canonical. Worth improving: trim the meta description. Fine: sitemap reachable, mobile usability clean.

Fix11m

One canonical host, enforced in code and agreed by the redirect.

app/layout.tsx
-metadataBase: new URL("https://www.zawaaj.in"),
+metadataBase: new URL("https://zawaaj.in"),
+alternates: { canonical: "https://zawaaj.in" },
next.config.mjs
+redirects: [{ source: "/:p*", has: [host www.zawaaj.in],
+ destination: "https://zawaaj.in/:p*", permanent: true }],
Deploy22m idle

git push → Vercel build → live. Most of this step is waiting on the platform, not work.

Verify3m

curl -I https://www.zawaaj.in → 308 → https://zawaaj.in 200; GA4 G-… fired in-browser.

audit 90 → 98 · canonical set · redirect www→apex · meta 198 → 155 · GA4 live · sitemap submitted

~50 min audit → verified-live (~25 min active; the rest idle on redeploy)A skilled developer does the same remediation on a custom site in ~4–6 hours; non-experts, 1–3 days.

How to read this. The before/after state and the ~50-minute wall-clock are measured; the manual hours are typical estimates for the same scope, not a stopwatch. Searchlight automates the diagnosis and the fix (canonical, host, redirects, sitemap, the GA4 install and verification). It does not design your ecommerce event-tracking plan; that part is still a human's job.

What it covers

One agent for the whole technical surface.

Search Console tells you what is wrong. Searchlight works out what to change, makes the change, and proves it worked.

Indexing and coverage

Which pages Google has indexed, which it hasn't, and why.

Canonical and host conflicts

The www-vs-apex split that fights your ranking, aligned to one host.

Redirect chains

Loops and chains collapsed to one clean hop.

Sitemaps that resolve

A sitemap that returns 200, with the right URLs, submitted.

Google Analytics

GA4 set up, not pasted

The tag installed and firing. No copy-pasting IDs.

Core Web Vitals

LCP, INP and CLS from real-user field data.

On-page audits

Titles, meta, canonical, OG and schema, as concrete edits.

Scores and reportin progress

A 'fix these first' list and a shareable report.

Install once

Add it to your client. The agent does the rest.

An MCP server with a companion /searchlight skill. Add both, sign in once, then ask.

01

Add the server and the skill

One command adds the MCP server; one more installs the /searchlight skill.

claude mcp add searchlight -- npx -y @ajmalaksar/searchlight servesearchlight skill install
02

Sign in with Google

One local OAuth sign-in for Search Console and Analytics. The token stays on your machine.

searchlight login --setup
03

Ask

Run the loop in plain language. It reports back with the before and after.

/searchlight audit yoursite.com
Anthropic Claude Code Codex Any MCP client Hosted (ChatGPT, Pi) soon
Local-first and private

Your data never leaves your machine.

Searchlight runs as a local server. You sign in with your own Google account. No hosted backend, no warehouse.

  • Read-only Search Console and Analytics scopes for diagnosis. Write and provisioning scopes are opt-in, requested only when you ask it to set things up.
  • OAuth tokens are stored locally under ~/.searchlight and never transmitted to us.
  • No hosted backend and no shared database. Your site's data stays yours.
  • Open source and MIT licensed. Read every line.

See what is actually broken on your site.

Point it at a site, get a triaged, plain-language picture in minutes, then let it fix the things worth fixing.