SEO for web agencies

SEO for web agencies that build client sites in code.

Each client site gets its own plan, one change at a time from your coding agent, and a dated record of every change.

From $49/mo · up to 10 client sites · works in Claude Code and Cursor

On each client site

What you get when a client asks you to do the SEO too.

You built the site and you look after it. This gives you the SEO part in the same place you already work: their repo.

01 The plan

A plan for each client, read from that client's repo.

Open the client's repo and ask what the site should go after. Your agent reads what the client sells and proposes the searches their buyers type. QueryScope sizes each one and shows where the site stands on it in the client's own Search Console, and who ranks above it.

02 The work

One change at a time, made by your coding agent.

Ask what to work on and you get one search, one page and one move, with what is ranking above it. Your agent makes the edit in the repo. You do not need to be an SEO to act on it, and you do not get a backlog to triage.

03 The sign-off

Anything a visitor reads waits for a commit.

A new title or a rewritten paragraph is written into a plan file in the repo first. You, or the client, read it as a diff and commit it. That commit is the approval, in the tooling you already use for every other change to their site.

04 The record

A dated record of every change, for the client.

Each change is logged against the search it was made for. The clock starts when Google recrawls the page, and the change is read on a set date against that site's own Search Console. The page is held until then, so a second edit cannot blur the first.

How a change is tracked

Which client sites fit

It works where the pages live in a repo.

The framework does not matter, because your agent edits files. What matters is where the words a visitor reads are stored.

The site For example How it works
Content in the repo Astro or Next.js with Markdown or MDX, a static site, templates in Laravel or Rails. Fits. Your agent makes every edit and the commit approves it.
A headless CMS holds the copy Templates in the repo, titles and body text in Sanity, Contentful or similar. Partly. Templates, links and technical changes are edited in the repo. A change to CMS-held copy is named and tracked here, and made by hand in the CMS.
No repo WordPress, Shopify, Webflow. Use a tool built for that CMS. QueryScope works through a repo and a commit.

Checked against how QueryScope records a change: copy and title changes are approved by a commit in the site's repo.

Across your clients

One account, a separate plan for every client.

Sign in with a Google account that has full access to each client's Search Console property. Each site keeps its own plan, history and record of changes, and you run it from that client's repo.

Every feature is in every plan, so you pick by how many client sites you look after: $49 a month for 1 site, $99 a month for 3 sites, $149 a month for 10 sites. Search Console keeps 16 months of data. QueryScope stores each site's daily history from the day you connect it, so a client's record does not expire.

Try it on one client site.

Add the server to your IDE with the line below, then authorize Search Console in the browser that opens.

install.sh
claude mcp add --transport http queryscope https://mcp.queryscope.dev/mcp

Works the same in Cursor, Cline and Windsurf. Your IDE opens a browser once to authorize.

Then ask: “what should this site go after?”

Add SEO to the sites you already look after.

Every feature in every plan. Connect one client site in two minutes and get the first change to make.

7-day free trial · nothing due today · cancel in one click

FAQ

SEO for client sites: common questions.

Can I run all my client sites from one account?

Yes, up to the number of sites in your plan: $49 a month for 1 site, $99 a month for 3 sites, $149 a month for 10 sites. Sign in with a Google account that has full access to each client's Search Console property. Each site keeps its own plan, history and record of changes.

What does my client see?

Two things you can put in front of them. The plan file in their repo, which shows each proposed change as a diff before it ships. And the record of changes in your dashboard: what was changed, on which search, when Google reread the page, and the reading once its date arrives.

Does it work with Astro and Next.js?

It works with any site whose pages live in a repo, because your coding agent makes the edits as file changes. The fit is cleanest when the content is in the repo too, as Markdown, MDX or templates. If a headless CMS holds the titles and body text, QueryScope still names and tracks the change, and you make that edit in the CMS.

I am a developer, not an SEO. Can I use this?

That is who it is built for. It names the search, the page and the move, and shows what ranks above the client now. Your agent makes the change. The judgement that stays with you is whether a search is really the client's business.

Does it write content for the client's site?

It picks the change and briefs it: the search, the reader, and what already ranks. The words come from you or your coding agent, and nothing a visitor reads ships before a commit.

Will it show the client more sales?

It measures up to the click: position, impressions and clicks on the searches in the plan, from the client's own Search Console. What happens after the click is measured in their analytics.