Part of Write and Optimize Blog Posts at Scale
Content Blueprint
Query External Data Sources
Access Google Search Console, PageSpeed Insights, CrUX, GA4, YouTube, and NotebookLM for sourced research and performance data.
What problem does this solve?
Fetches Google API data (PSI, CrUX, GSC, GA4, NLP, YouTube, Keywords) and runs source-grounded research via NotebookLM. Removes manual API setup, data pulling, and external research.
How does it work?
- Run
/blog google [command] [args]to fetch Google data: PageSpeed Insights (PSI), Core Web Vitals (CrUX 25-week history), Search Console performance, URL Inspection, GA4 organic traffic, YouTube video search, NLP entity analysis, or Ads Keyword Planner. 2. Run/blog notebooklm <question>to query your uploaded NotebookLM documents for Tier 1 source-grounded research. Output: Performance reports, SERP data, analytics, or research findings from your own documents.
Included Skills
No skills in this group
What's required to run this?
Google API requires free API keys (PageSpeed Insights, CrUX, YouTube, NLP) and optional OAuth (Search Console, Indexing API, GA4) or Ads credentials (Keyword Planner). NotebookLM requires Google account with NotebookLM access. Config is stored at ~/.config/claude-seo/google-api.json and shared with the claude-seo skill.
Key Features
/blog google
Google API integration: PSI, CrUX, GSC, GA4, NLP, YouTube, Keywords across 4 credential tiers (all free at normal usage).
CrUX Data
Core Web Vitals historical data (25 weeks) for your domain and competitive analysis.
/blog notebooklm
Query Google NotebookLM for source-grounded research from your uploaded documents (zero hallucination risk).
Automated Reports
CWV audit, GSC performance, indexation status, and GA4 reports with markdown and PDF output.
About This Blueprint
- Industry
- Marketing Technology
More Blueprints to explore
Answer pre-purchase questions to convert hesitant shoppers with AI
Shoppers get accurate answers about fit, compatibility, ingredients, and delivery even when your team is offline, so fewer leave before checkout. Conversation insights also reveal which product-page details could prevent the next unanswered question.
Urska B.
GTM Lead
Find the root cause behind repeat support tickets with AI
Catch a few unusual tickets before a product or fulfillment issue turns into hundreds of refunds, chargebacks, and bad reviews. Cluster transcript evidence by SKU, order date, location, and carrier so operations can trace the cause and support can reach affected customers early.
Urska B.
GTM Lead