8 Claude Workflows for Search Console and Technical SEO (2027)

Connect Google Search Console, GA4, PageSpeed Insights, and your CMS to Claude via Otto MCP to run eight approval-gated technical SEO workflows without CSV exports.

As seen in

  • Fox News
  • ABC News
  • CBS
  • NBC
  • Associated Press
  • USA Today
  • Bloomberg
  • HuffPost
Otto the beaver next to the Google Search Console logo
On this page7

Connect Google Search Console, GA4, PageSpeed Insights, Google Business Profile, and your CMS to Claude through Otto's hosted MCP server (/mcp/claude) using a single otto_mcp__ token to run eight live technical SEO workflows without exporting CSVs. Across 227 tools and 15 integrations, Otto MCP keeps Search Console, GA4, and PageSpeed Insights (psi_analyze_url) read-only, queries aggregated metrics through the server (Otto documents 80–90% lower token use versus uploading a raw 3,000-row Ads Manager CSV at 40,000 to 80,000 tokens per turn), and stages website fixes as WordPress drafts across 29 tools or GitHub pull requests with human approval.

Copy-paste Claude prompts for Search Console and technical SEO (start here)

Run these five starter prompts directly in Claude once your Otto MCP connection is active:

Example prompt — copy-paste this into Claude:

# Prompt 1: High-Impression, Low-CTR Query Audit with GA4 Conversions
List our top 20 queries from Google Search Console over the last 28 days that have over 500 impressions but an organic click-through rate under 3.0%. For each query, pull the target landing page, its average position, and match it against GA4 session conversion data. Flag URLs where an updated title tag or meta description could lift clicks without losing existing rankings.

Example prompt — copy-paste this into Claude:

# Prompt 2: Page Indexing Status Triage
Review our Google Search Console Page Indexing report. Group excluded pages into two buckets: benign exclusions (such as canonical tags and normal 301 redirects) versus true indexing blockers (such as soft 404s, unintended noindex tags, robots.txt blocks, and pages marked crawled or discovered but currently not indexed). Inspect the top 5 blocker URLs and explain what needs fixing.

Example prompt — copy-paste this into Claude:

# Prompt 3: Mobile Core Web Vitals and Lighthouse Audit via psi_analyze_url
Run `psi_analyze_url` on our top 5 organic landing pages for mobile. Report the trailing 28-day CrUX 75th-percentile field metrics for LCP, INP, and CLS, along with the Lighthouse SEO and Performance scores. Identify which specific images, render-blocking scripts, or layout shifts fail Google's Good thresholds.

Example prompt — copy-paste this into Claude:

# Prompt 4: Google Business Profile vs. Website NAP Consistency Audit
Compare our Google Business Profile primary name, physical address, phone number, operating hours, and business categories against the footer and location page on our live website. Flag any discrepancies between our GBP listing and our site schema, and check if our holiday hours are populated.

Example prompt — copy-paste this into Claude:

# Prompt 5: Stage a WordPress Draft or GitHub Pull Request Fix
Based on the title tag and meta description recommendations for our striking-distance queries, draft updated metadata for [Target URL]. If running on WordPress, save the updates as an unapproved draft. If running on GitHub, prepare the change as a pull request on a new branch with a preview deployment for review.

Exporting Search Console CSVs by hand vs. DIY Search Console MCP vs. Claude + Otto MCP

Feature / CapabilityExporting Search Console CSVs by HandDIY Local Search Console MCPClaude + Otto MCP Server
Setup & AuthenticationManual web logins; repeated CSV downloads from Google Search Console and GA4Requires Google Cloud Console setup, custom OAuth client IDs, and local Python or Node scriptsSingle otto_mcp__ token over HTTP; OAuth handled server-side
Context Window UsageLarge hand-exported Search Console and GA4 CSVs can consume heavy context in Claude; Otto documents a raw 3,000-row Ads Manager CSV upload at 40,000 to 80,000 tokens per turnModerate token usage; depends on custom script pagination80–90% lower token consumption through filtered server queries versus that Ads Manager CSV benchmark
Integrations CoveredNone; requires manual tab-switching across Search Console, GA4, PSI, and wp-adminSearch Console only (Search Analytics, Sitemaps, Sites, URL Inspection)227 tools across 15 integrations including GSC, GA4, PSI, GBP, WordPress, and GitHub
Core Web Vitals ToolingManual testing in web PageSpeed Insights or web.devNone unless you write a separate script and provide an API keyBuilt-in psi_analyze_url using platform keys with no user API key needed
Execution of FixesManual edits inside wp-admin, Webflow, or code repositoriesRead-only; cannot modify CMS content or codebases29 WordPress tools (draft-first) and GitHub pull request staging with previews
Safety GuardrailsHigh risk of direct manual errors in productionRead-only; no execution capabilitySearch Console and GA4 are read-only; CMS writes stage as drafts or PRs

You connect accounts once in Otto via OAuth; Claude holds only an otto_mcp__ token. See the Connect Google Search Console to Otto setup guide, then connect Claude to Otto MCP.

Workflows 1–3: Striking-distance query mining, GSC + GA4 conversion attribution, and query fan-out cluster gaps

Workflow 1: Mining high-impression, low-CTR striking-distance queries

Google's Search Console API Reference documents Search Analytics queries grouped by query, page, country, or device—without exporting multi-thousand-row CSVs.

Example prompt — copy-paste this into Claude:

Using searchAnalytics.query via Otto MCP, pull all queries for the last 28 days where average position is between 8.0 and 20.0 and impressions exceed 300. Group the output by query and page. Sort by impressions descending. For the top 10 rows, suggest revised H2 subheadings and an updated title tag under 60 characters to improve organic click-through rate.

Workflow 2: Reconciling Search Console organic clicks with read-only GA4 conversions

GA4 and Search Console stay read-only in Otto MCP, so Claude can cross-reference clicks and conversions without changing tracking. Connect Google Analytics 4 to Otto first.

Example prompt — copy-paste this into Claude:

Pull our top 15 organic landing pages by clicks from Search Console over the past 30 days. Next, query GA4 for those same page paths to retrieve engaged sessions, average engagement time, and lead event completions. Flag any URL receiving over 200 organic clicks but converting at under 1.0%, and identify missing call-to-action elements on those pages.

Workflow 3: Mapping Google AI search query fan-out gaps across service and bilingual pages

Google Search Central's AI optimization guide describes query fan-out across sub-questions in AI Overviews. Map gaps with the Otto AI SEO Agent and audit English plus /es/* Spanish paths where both locales ship. See how Google's query fan-out works.

Example prompt — copy-paste this into Claude:

Analyze our core service pages for both our English pages and our Spanish pages under /es/*. Identify related informational sub-questions and transactional variations that appear in search suggestions but lack dedicated sections on our site. Group them into a topic cluster and draft clear answer sections under 80 words for each sub-heading.

Workflows 4–5: Page Indexing status triage, URL Inspection checks, and Core Web Vitals (psi_analyze_url) audits

Workflow 4: Triaging Search Console Page Indexing statuses and URL inspection

As documented in Google Search Console Help (Page indexing report), the label "Not indexed" does not automatically signify a site malfunction. Many exclusions are standard parts of healthy technical hygiene. Chasing full Page Indexing coverage in Search Console is a mistake; the goal is eliminating genuine blockers while letting normal canonical and redirect rules function as intended.

Status in Search ConsoleBenign or blocker?Next step in Claude
Alternate page with proper canonical tagBenignNone; canonical target is indexed.
Page with redirectBenignPoint internal links to the destination URL.
Duplicate without user-selected canonicalBenignAdd rel=canonical if you want this URL to win.
URL marked noindexBlocker (if unintended)Remove noindex on public landing pages.
URL blocked by robots.txtBlockerPer the Page indexing report in Google Search Console Help: robots.txt does not guarantee a page won't be indexed; remove the block and use noindex to ensure non-indexing.
Soft 404BlockerReturn a real 404 or add substantive content.
Server error (5xx)BlockerFix hosting errors first.
Crawled - currently not indexedBlocker on money pagesImprove content and internal links; run URL Inspection.
Discovered - currently not indexedBlocker on money pagesAdd sitemap links and nav links to raise crawl priority.

Through Otto MCP, Claude calls urlInspection.index.inspect per Google's Search Console API Reference to audit individual URLs:

Example prompt — copy-paste this into Claude:

Query urlInspection.index.inspect for [Target URL]. Report the crawl status, indexing state, user-declared canonical, and Google-selected canonical. Confirm whether the page is blocked by robots.txt or marked noindex, and state if any remediation is necessary.

Workflow 5: Auditing mobile Core Web Vitals and Lighthouse SEO with psi_analyze_url

Otto MCP exposes read-only psi_analyze_url with Otto's platform key—no user Google API key required. Google's PageSpeed Insights documentation reports 28-day CrUX at the 75th percentile (FCP Good up to 1800ms, LCP up to 2500ms, CLS up to 0.1, INP up to 200ms, experimental TTFB up to 800ms) plus Lighthouse SEO, where 90+ is good. See how Core Web Vitals drift leaks conversions and Connect PageSpeed Insights to Otto.

Otto compresses newly uploaded images automatically and re-processes existing images during scheduled maintenance runs to prevent LCP degradation.

Example prompt — copy-paste this into Claude:

Call psi_analyze_url on our primary booking URL for mobile. Report the 28-day CrUX 75th-percentile field values for LCP, INP, and CLS, plus the Lighthouse SEO and Performance scores. Identify any uncompressed image assets, excessive CSS, or third-party tags pushing LCP past 2500ms or INP past 200ms.

Workflows 6–8: Google Business Profile NAP consistency audits, approval-gated WordPress or GitHub fixes, and weekly SEO briefings

Workflow 6: Auditing Google Business Profile NAP consistency for local search and AI Overviews

Google Business Profile Help (Tips to improve your local ranking on Google) states that local results are mainly based on relevance, distance, and popularity, and that there is no way to request or pay for a better local ranking on Google. In Otto MCP you can read your profile and publish local posts on every plan; review replies are on Pro. Connect Google Business Profile to Otto and read why NAP inconsistencies hurt local SEO.

Example prompt — copy-paste this into Claude:

Query our Google Business Profile integration for our primary location. Retrieve the registered business name, street address, primary phone number, operating hours, holiday hours, and business categories. Next, fetch our live contact page. Highlight any discrepancies in name, address, phone (NAP), or business hours, and verify that our LocalBusiness JSON-LD markup matches our profile exactly.

Workflow 7: Shipping title, snippet, content, and speed fixes via WordPress drafts or GitHub pull requests

Otto works on the site you already have: WordPress updates default to draft across 29 tools, and GitHub changes open as pull requests with Vercel previews. Checkout, contact, and legal pages still need human approval in Otto core. Use the Otto AI Website Manager and connect WordPress to Otto. Enrique Gomez of Enzo Maverick Pilates and Experiences Sensory said Otto made on-the-fly site changes easy for their team.

Example prompt — copy-paste this into Claude:

Using our WordPress integration, retrieve the draft for our upcoming service guide. Update the meta description to focus on our target striking-distance query, add the missing schema markup, and keep the post in draft status. Do not publish the post to production.

Example prompt — copy-paste this into Claude:

Create a new branch titled `fix/lcp-image-optimization` on our repository. Convert hero image tags to modern responsive formats with explicit width and height attributes to fix our CLS issues. Open a pull request against main with a link to the Vercel preview deployment.

Every update stays in draft mode or waits on a preview link until you review and approve it.

Workflow 8: Automating the Monday technical SEO briefing and change-log verification

Otto ships automated weekly SEO reports (v1.2.0) and one-tap WhatsApp approvals (v1.1.0). Claude can pair otto_get_change_log with Search Console trends.

Example prompt — copy-paste this into Claude:

Run `otto_get_change_log` for the past 14 days to see all staging updates and code deploys. Cross-reference this timeline against our Search Console performance data and GA4 organic sessions. Generate a concise Monday briefing summarizing ranking movements, new indexing notices, and upcoming items requiring sign-off.

What Google actually requires for AI Overviews and AI Mode in 2027 (and which AEO/GEO myths to ignore)

Google Search Central's AI optimization guide still starts with crawlable, indexable pages eligible for snippets, tracked in Search Console's Generative AI performance report. Google does not require llms.txt files, token-level content chunking, or special schema for AI Overviews. Serving in generative features is not assured even when technical requirements are met.

Otto structures sites and listings so Google and AI assistants can read the business; Otto does not promise rankings, Map Pack placement, or third-party AI citations. Read the AEO vs. SEO guide for AI Overviews visibility.

Otto MCP permission boundaries, Starter/Pro/Enterprise plans, and technical SEO FAQs

Search Console, GA4, PSI, YouTube, and Sheets are read-only in Otto MCP. WordPress and GitHub follow draft or pull-request rules above. Ad changes need Pro with approval; LinkedIn Ads start as DRAFT, and Facebook Pages, Instagram, LinkedIn, or Google Business Profile posts work on every plan and go live only for reviewers or admins. Starter is $9.99/week or $29.99/month and is MCP only; Pro is $199/mo or $99/mo billed annually, starting with $1 for 3 days with a homepage redesign included; Enterprise is a call with the founder. See Otto Starter, Pro, and Enterprise pricing. Synter covers 40+ ad networks without site deploys; Ryze AI skips live GitHub PRs, WordPress drafts, and GBP management. Otto ties Search Console diagnosis to the same workflow that opens the fix.

Technical SEO FAQs

Does Otto MCP require a Google Cloud Console project or my own PageSpeed Insights API key?

No. Connecting Search Console, GA4, or Google Business Profile happens through OAuth inside the Otto dashboard, storing credentials securely server-side. PageSpeed Insights runs through the built-in psi_analyze_url tool using platform keys, requiring no personal API key.

Can Claude accidentally publish unapproved SEO changes to my live site?

No. In Otto MCP, website edits do not go live automatically: WordPress posts and pages default to draft status, and GitHub changes open as pull requests with preview deployments. Critical pages such as checkout, contact, and legal sections always require human approval in Otto core.

Why should I avoid blocking non-indexed pages in robots.txt?

As Google Search Console Help explains in the Page indexing report for "URL blocked by robots.txt," blocking does not guarantee that the page won't be indexed through other means, and to ensure a page is not indexed you should remove the robots.txt block and use a noindex directive so Googlebot can read it.

Is the Otto CLI available for terminal use today?

The Otto CLI for terminal agents is coming soon; hosted MCP over HTTP at https://otto.islaintel.com/api/mcp is the supported path today across Claude, ChatGPT, and Cursor. Wix, Webflow, and TikTok are not currently supported in the live MCP catalog.

Connect Claude to Otto MCP to audit your Search Console performance, test Core Web Vitals, and stage website fixes with human approval.

Written by

Guillermo Marti

Creative Director & Head of Growth at IslaIntel

Leads Otto's brand, creative, and growth, from paid ads and SEO to the AI workflows behind them.