SEO

Split brand vs non-brand search traffic

Separate branded searches from non-brand organic traffic to see whether SEO is actually growing, how dependent the site is on people already searching for the brand, and which trend the headline Search Console numbers are hiding.

The playbook

Headline organic traffic blends two different things: people who already knew the brand and typed it in, and people who found the site by searching for a problem. Only the second one is SEO. A site whose total clicks are growing while non-brand clicks are flat is not gaining ground in search; it is gaining ground in brand awareness.

Steps

  1. Get the brand terms. Ask the user for the brand name, product names and common misspellings if they are not obvious. Build one case-insensitive regex from them, for example (?i)acme|acmehq|ackme. Search Console regex is RE2 syntax.

  2. Pull the two trends. Two calls to google_search_console.query with dimensions: ["date"] over the last 16 weeks ending 3 days ago. One with filters: [{ dimension: "query", operator: "includingRegex", expression: "<brand regex>" }], one with operator: "excludingRegex" and the same expression. Also run the unfiltered call so you have the true total.

  3. Pull the page view. Repeat both filtered calls with dimensions: ["page"] over the last 28 days. This shows which pages carry non-brand traffic, which is the list of pages doing real SEO work.

  4. Compute share and trend. Non-brand share of clicks, non-brand week-over-week trend, brand trend. Compare the two slopes. Non-brand growth is the SEO KPI; report it as such.

  5. Report. Two trend lines (brand, non-brand), the current non-brand share, the top ten non-brand pages and queries, and one sentence on what the headline number is hiding. If the unattributed gap from the first gotcha is large, say so and give its size.

Gotchas

  • Filtered totals do not sum to the unfiltered total. Search Console omits anonymised low-volume queries from any query-filtered result, so brand plus non-brand will come in below the true total. Report the difference as "unattributed", never fold it into non-brand.
  • Brand plus a modifier is still brand. "acme pricing" and "acme vs competitor" are branded queries. The regex catches them; do not hand-correct them into non-brand.
  • Homepage traffic is mostly brand. If non-brand clicks land heavily on the homepage, check the queries; a generic homepage rarely ranks non-brand and this usually means the regex missed a brand variant.
  • Search Console lags 2 to 3 days. End every window 3 days back.

Sequel CLI

Install Sequel skills into your agent

One command connects your agent to Sequel and installs the Sequel skill, so it knows this playbook exists and reads it when a question matches. The CLI signs you in, provisions a scoped API key and writes the config for you.

Already have an MCP client?

https://api.sequel.sh/mcp

Point it at this URL and sign in when prompted, or send an API key from Settings as a Bearer token. Skills come with it; nothing else to install. Manual setup per client

  1. 1

    Install the Sequel CLI

    One line installs the latest CLI with whatever package manager you have.

    curl -fsSL https://sequel.sh/install | sh
  2. 2

    Sign in

    Authenticate in your browser and pick an organization.

    sequel login
  3. 3

    Install into your agent

    Writes the MCP config and installs the Sequel skill file for agents that support skills. Pick an agent from the list, or target one directly by its slug.

    sequel install
    • Claude Code
      sequel install claude-code
    • Claude
      sequel install claude
    • Cursor
      sequel install cursor
    • VS Code
      sequel install vscode
    • Windsurf
      sequel install windsurf
    • Zed
      sequel install zed
    • Codex
      sequel install codex
    • OpenClaw
      sequel install openclaw
    • Hermes
      sequel install hermes

More like this

Other SEO skills

Analyze high-ranking landing pages

See which pages perform best in organic search: the landing pages that earn the most clicks and impressions, the queries behind each one, and how they compare with competitor estimates from Ahrefs.

Audit internal links to important pages

Audit the site's own internal linking: crawl navigation and body links between the site's pages to find valuable pages with too few inbound internal links, orphan pages, and the handful of cross-links that would lift striking-distance rankings.

Audit or draft an llms.txt

Check whether the site has an llms.txt, whether it follows the spec and points at the pages that matter, and if it is missing draft one from the pages Search Console shows people actually find, so AI assistants get a curated map of the site instead of guessing.

Audit redirect chains and loops

Follow every redirect on the URLs Search Console still sends traffic to, on the sitemap, and on backlinked pages, to find chains, loops, redirects to the homepage, and temporary redirects that should be permanent, so link equity and crawl budget stop leaking.

Audit referring domain quality

Grade the domains linking to a site by authority, traffic and link count, spot concentration risk and link-farm patterns, and separate the referring domains that carry weight from the ones that are noise.

Audit titles and meta descriptions

Compare the title and meta description of each top page against the queries it actually ranks for in Search Console, and find missing, duplicate, truncated or misaligned metadata on the pages where a rewrite would earn the most clicks.

Put this playbook to work

Connect a source, ask the question, and the agent follows these steps. Free to start.