The prompt pack · 16 prompts

Claude Code SEO prompts that run on your real data.

12 prompts read your own Search Console, Analytics and Bing numbers through the Murkuz MCP server, then draft the fix in your repo as a diff. 4 more need no setup at all. Copy one, paste it into Claude Code, and swap in your site.

Connect in one commandJump to the prompts

Updated

~/your-site

# once

$ claude mcp add --transport http --scope user murkuz https://murkuz.com/mcp

$ claude

> /mcp murkuz, Authenticate

# then paste a prompt

> Use Murkuz on [your-site.com]. Run Live_Quick_Wins for the last 28 days with max_position 15.

murkuz · Live_Quick_Winsyour repo · diffs

Step 1

Connect Murkuz to Claude Code in one command.

Murkuz is a hosted MCP server that hands Claude Code your own Search Console, Google Analytics 4 and Bing Webmaster rows for every site on your account. Nothing to install: run the command, sign in once, and the 12 data prompts below work in every project.

Using Claude on the web, ChatGPT or Cursor instead? The setup for each is on the Murkuz MCP server page.

  1. 1Sign in to Murkuz and connect your Search Console property. Analytics and Bing are optional.

  2. 2Run this once in your terminal. The user scope makes Murkuz available in every project.

    Terminal
    claude mcp add --transport http --scope user murkuz https://murkuz.com/mcp

  3. 3Start Claude Code, type /mcp, pick murkuz and choose Authenticate. Sign in on the page that opens, then paste any prompt below.

Step 2

12 prompts that read your search data.

Replace [your-site.com] with one of your connected sites. The grey chips are the Murkuz tools each prompt calls; the blue ones say what it needs connected.

  1. 01

    Morning check across every site

    What you get: Every site you run in one table, biggest movers first, with the engine behind each move.

    Prompt
    Use Murkuz. Run All_Sites_Overview for all my sites.
Sort the sites by the change in clicks against the previous 28 days.
For the two biggest movers up and the two biggest down, say whether Google or Bing drove it.
Give me one table, then three bullets on what I should look at first. Say how fresh the data is.
    All_Sites_OverviewSearch Console
  2. 02

    Push the pages sitting just off page one

    What you get: The five pages closest to page one, with a new title, H1 and section drafted in your repo.

    Prompt
    Use Murkuz on [your-site.com]. Run Live_Quick_Wins for the last 28 days with max_position 15.
Group the queries by landing page and rank the pages by total impressions.
For the top 5 pages, find the source file for each page in this repo and propose a new title, H1 and one new section aimed at the queries it is closest on.
Show me the diffs. Do not apply anything until I say so.
    Live_Quick_WinsSearch Console
  3. 03

    Rewrite titles people see but skip

    What you get: Three new title options for each page that shows up in search but rarely gets the click.

    Prompt
    Use Murkuz on [your-site.com]. Run Live_CTR_Opportunities with min_impressions 500.
For the top 10 pages, show the current title, the top 3 queries and the CTR.
Write 3 new titles for each, under 60 characters, matching what the top query is really asking for.
Tell me which page to fix first and why, then find that page's title in this repo.
    Live_CTR_OpportunitiesSearch Console
  4. 04

    Find out why traffic dropped

    What you get: The pages that lost clicks, each with a likely cause and Google's index status.

    Prompt
    Use Murkuz on [your-site.com]. Run Live_Traffic_Drops for the last 28 days against the 28 before.
For the 3 pages that lost the most clicks, run Inspect_URL and report index status, last crawl and the canonical Google picked.
Label each drop as ranking loss, CTR collapse, falling demand or indexing problem, and tell me what you would check next.
    Live_Traffic_DropsInspect_URLSearch Console
  5. 05

    Catch pages sliding for three months

    What you get: A refresh, merge or leave-it call for every page on a steady decline.

    Prompt
    Use Murkuz on [your-site.com]. Run Live_Content_Decay.
For the 5 steepest slides, run Landing_Page_Diagnosis on each page.
For every page, decide: refresh, merge into another page, or leave it. One line of reasoning each, based on the queries it lost.
    Live_Content_DecayLanding_Page_DiagnosisSearch Console + Analytics 4
  6. 06

    Stop your own pages competing

    What you get: Each query two of your pages fight over, which page should own it, and what to do with the other.

    Prompt
    Use Murkuz on [your-site.com]. Run Live_Cannibalization for the last 90 days.
For each query, list the competing URLs with their clicks and positions.
Recommend which page should own the query and what to do with the other: merge with a 301, retarget it, or add an internal link to the winner.
If you recommend a 301, find where redirects live in this repo and draft the rule.
    Live_CannibalizationSearch Console
  7. 07

    Check new pages actually got indexed

    What you get: Which of your newest URLs Google has indexed, plus any sitemap errors.

    Prompt
    Use Murkuz on [your-site.com]. Find the sitemap in this repo or at /sitemap.xml and take the 10 newest URLs.
Run Inspect_URL on each and give me a table: URL, indexed or not, last crawl, Google's canonical.
Then run List_Sitemaps and report any errors or warnings.
Ask me before you run Submit_Sitemap.
    Inspect_URLList_SitemapsSubmit_SitemapSearch Console
  8. 08

    Put effort where it converts

    What you get: Pages split into push now, fix the page first, protect and skip, judged on conversions as well as rankings.

    Prompt
    Use Murkuz on [your-site.com]. Run Opportunity_Matrix for the last 90 days.
Show me the rank_up_now and improve_page_first groups with each page's position and conversion rate.
If quadrants are not assigned, tell me why and use the ranked_by_potential_only list instead.
Finish with the one page I should work on this week.
    Opportunity_MatrixSearch Console + Analytics 4
  9. 09

    Learn why visitors leave one page

    What you get: What a page is found for, next to what visitors do on it, and three changes to the top of the page.

    Prompt
    Use Murkuz on [your-site.com]. Run Page_Search_To_Behaviour for [/your-page] over the last 28 days.
Compare the intent of its top queries with what the page offers in its first screen.
Open the page's source file in this repo and suggest 3 changes above the fold that answer those queries faster. Show diffs only.
    Page_Search_To_BehaviourSearch Console + Analytics 4
  10. 10

    Compare what Bing and Google reward

    What you get: Queries one engine sends clicks for and the other ignores.

    Prompt
    Use Murkuz on [your-site.com]. Run Bing_Search_Performance for the last 28 days, then Keyword_Rankings with source google for the last 28 days.
List the queries where Bing sends clicks and Google does not, and the reverse.
For the top 3 in each list, say what the ranking page has that the other engine might be missing.
    Bing_Search_PerformanceKeyword_RankingsSearch ConsoleBing Webmaster
  11. 11

    Check Analytics is not losing visits

    What you get: Whether Analytics and Search Console agree, and where in your code the tag could be leaking.

    Prompt
    Use Murkuz on [your-site.com]. Run Traffic_Health_Check for the last 28 days.
If the diagnosis is tracking_gap or over_counting, search this repo for how the Google Analytics tag is loaded (consent banner, script strategy, redirects, single-page navigation) and list what could explain the gap.
If it is healthy, say so in one line and stop.
    Traffic_Health_CheckSearch Console + Analytics 4
  12. 12

    Turn a competitor's rankings into a brief

    What you get: Topics a competitor ranks for that you do not, grouped, with a first article brief.

    Prompt
    Use Murkuz. First run My_Data_Credits and tell me what this will cost before going on.
Then run Competitor_Gap for [your-site.com] against [competitor.com] with limit 50.
Drop branded terms, group the rest into topics, and pick the 3 topics I could realistically win.
Run Keyword_Metrics on the main keyword of each, then write a one-page brief for the strongest one.
    My_Data_CreditsCompetitor_GapKeyword_MetricsResearch credits

Want the example question and credit cost for every tool? See the Murkuz MCP tool reference.

No setup

4 prompts that need only your repo.

Open Claude Code in your site's folder and paste. These read your source code, not search data, so they work before you connect anything.

  1. 13

    On-page audit of your codebase

    What you get: A file-by-file list of missing titles, duplicate H1s, absent meta descriptions and stray noindex tags.

    Prompt
    Audit every page in this repo for on-page SEO basics: exactly one H1, a title between 30 and 60 characters, a meta description, a self-referencing canonical, alt text on images, and no leftover noindex.
Give me a table with file, line, problem and fix. Do not edit anything yet.
    Claude Code only
  2. 14

    Structured data that matches the page

    What you get: JSON-LD drafted for each page type, built only from content that is visible on the page.

    Prompt
    Find the page types in this repo (articles, FAQs, how-tos, products, the homepage).
For each, draft JSON-LD using only content that is visible on that page, never invented ratings or reviews.
Show where each block would go and the diff. Ask before applying.
    Claude Code only
  3. 15

    Find orphan pages and link them in

    What you get: Pages with no internal links pointing at them, each with two links to add and the sentence to put them in.

    Prompt
    Map the internal links between pages in this repo.
List every page with no inbound internal link.
For each one, suggest 2 existing pages that should link to it, with the anchor text and the exact sentence to place the link in.
    Claude Code only
  4. 16

    Broken links and redirect chains

    What you get: Every internal link that points at a missing route or runs through more than one redirect, with the fix.

    Prompt
    List every internal link and every redirect rule in this repo.
Flag links that point to routes that do not exist, and redirects that chain into another redirect.
Propose the fix for each, grouped by file.
    Claude Code only

Better answers

Four habits that make any SEO prompt sharper.

01

Name the site and the window

One connector covers every site on your account, so say which one, and give a date range when it matters.

02

Ask for diffs, not edits

Claude Code asks before it changes a file. Asking for diffs first keeps every change in front of you.

03

Save the ones you reuse

Put a prompt in .claude/commands/quick-wins.md and it becomes /quick-wins in every session in that project.

04

Ask how fresh the numbers are

Every Murkuz answer carries the property, the window and the data's age, so the agent can tell you.

Questions

Claude Code for SEO, answered

Can Claude Code do SEO?

Yes, on two fronts. On its own, Claude Code reads your site's source, so it can audit titles, headings, canonicals, structured data and internal links and draft the fixes as diffs. With an MCP server such as Murkuz connected, it also reads your real Search Console, Google Analytics 4 and Bing Webmaster data, so it can decide which pages to fix from what search is actually doing.

What makes a good Claude Code SEO prompt?

Name the site, name the date window, say which data to use, and ask for a table or a diff rather than an essay. Ending with an instruction such as 'show me the diffs, do not apply anything yet' keeps every change in front of you before a file is touched.

Do these prompts need Murkuz?

The first 12 do, because they read your own search data through the Murkuz MCP server. The last 4 need nothing but Claude Code opened in your site's folder.

Will Claude Code change my site?

Not without asking. Claude Code asks for permission before it edits a file, and these prompts ask for diffs first. On the data side, the Murkuz MCP server only reads, with one exception: Submit_Sitemap, which asks Google to recrawl a sitemap you already publish, and only when you ask for it.

Do the data prompts work in Claude, ChatGPT or Cursor?

The Murkuz parts do: any client connected to the Murkuz MCP server can run the same tools. The steps that open or edit files in your repo need an agent with access to your code, such as Claude Code or Cursor.

How do I save a prompt as a Claude Code command?

Create a Markdown file in your project's .claude/commands folder, for example .claude/commands/quick-wins.md, and paste the prompt into it. In any Claude Code session in that project, typing /quick-wins runs it.

Murkuz MCP server

Setup for Claude, Claude Code, ChatGPT and Cursor.

MCP tool reference

Every tool, with an example question for each.

SEO agent

Claude or ChatGPT as an SEO agent on your own data.

Google Search Console MCP

The Search Console side in depth.

Give Claude Code your numbers. Then paste a prompt.

Sign in with Google, pick your properties, and run one command. Every site you run, through one connector.

Connect your sitesView Plans