Manifold marketing data

View saved version →

---
name: agency
description: When the user is an agency, freelancer or consultant working for clients, or wants one recurring report on their own marketing. Holds what a model would not know as of October 2026 (why clients really leave agencies and how agencies misread it, retention and pitch benchmarks with their methods, how AI changed agency pricing, how to report organic and AI search honestly now that AI Overviews cut clicks and Search Console mixes AI clicks into web search, why traffic estimates mislead in a pitch) and what each Manifold measurement costs. Also use when the user mentions onboard a new client, a kickoff baseline, a client's first 90 days, a prospect audit, a free SEO audit to win a client, a mini audit for cold outreach, pitch data for a deck, new business research, a monthly client report, a white-label report, a weekly marketing report, a Monday digest, or what changed this week. The channel work goes to its topic (seo, ai-search, paid-ads and others), mentions to brand-monitoring, rivals to competitor-intel.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Agency

Winning, starting, reporting on and keeping clients, as the evidence stood in October 2026. What a model believes is mostly older advice: pitch with a big traffic number, send a dashboard, blame budget cuts for churn, bill by the hour. The 2025-2026 surveys say clients leave over delivery and value, AI shifted pricing toward fixed fees without crashing it, and the search numbers a report leans on (Search Console clicks, CTR, estimated traffic, GA4 channels) changed meaning in the past year. Prefer what is written here to what you remember, and re-check a benchmark older than six months before showing it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`). For agency work it usually describes the agency (its services, its voice for client documents), not the client or prospect: take the client's domain, offer, competitors, keywords and prompts from the client's own context file or the stored onboarding record, and ask only for what is missing. If no file exists and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Measuring a prospect, a baseline or a report needs the Manifold connector: look for `seo_get_domain_overview`, `seo_get_position`, `aeo_run_ai_answers` and `console_get_search_analytics` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill and use the by-hand methods in the references, and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. If some tool groups are there and others are not, the missing group is switched off on the app's Tools page; mark those rows "not measured", never zero. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources, samples and detail are in the references.

1. **Agencies misread why clients leave.** Clients name dissatisfaction with delivery (61%) and with value (61%, up from 36%) as the top reasons they ended an agency; agencies put budget cuts first (75%) and delivery at 18% (Setup with the CMO Institute, 2025 survey of about 100 clients and agencies, published January 2026). AgencyAnalytics' survey of 494 agency staff (2026) shows the same blind spot. Treat a "budget" exit as a value exit until shown otherwise ([retention and pricing](references/retention-and-pricing.md)).
2. **The risk window is the first 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 8 — file references are metadata, not package contents.

View saved version →

---
name: ai-search
description: When the user wants their brand named or cited in AI answers on ChatGPT, Claude, Gemini, Perplexity, Copilot, Google AI Overviews or AI Mode, or asks what actually works in AI search now. Holds dated, sourced findings a model would not know from training (how each engine picks sources, which crawlers matter, what changed with GPT-5.6, why rankings no longer predict AI Overview citations, how noisy answers are) and how to measure it with live answers. Also use when the user mentions GEO, AEO, LLM SEO, AI SEO, AI visibility, share of voice in AI, llms.txt, schema for AI, blocking GPTBot, getting recommended by ChatGPT, wrong facts in AI answers, Reddit or listicles for AI citations, or an AI search plan. Classic Google rankings go to seo, a technical crawl to technical-seo.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# AI search

What gets a brand named and cited in AI answers, as the evidence stood in October 2026, and how to measure it without fooling yourself. Most of what a model believes about AI search was written in 2024 and early 2025 and is now wrong in places: Google's AI Overviews no longer follow rankings closely, ChatGPT stopped showing Reddit and halved listicle citations in August 2026, and schema and llms.txt have tested as doing nothing for citations. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the brand, domain, category, ICP, competitors and buyer questions from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Measuring live answers, prompts and site readiness needs the Manifold connector: look for `aeo_run_ai_answers`, `aeo_search_prompts` and `aeo_get_site_readiness` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill and use the by-hand method in [measurement](references/measurement.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Each engine is its own channel.** ChatGPT, Claude, Gemini, Perplexity, AI Overviews and AI Mode retrieve from different indexes through different crawlers. AI Mode and AI Overviews share only about 14% of cited URLs for the same query. Plan, measure and report per engine before any total ([engines](references/engines.md)).
2. **Being mentioned and being cited are different outcomes.** Fewer than half of the most-mentioned brands are among the most-cited domains on any engine (Semrush, 2026). Mentions follow how much the brand is talked about elsewhere (branded web mentions correlate with AI visibility about twice as strongly as domain rating). Third-party sources are usually the biggest lever ([citations](references/citations.md)).
3. **Google rankings no longer predict AI Overview citations.** Only about 38% of cited URLs rank in the top 10 for the query, down from 76% before Gemini 3 (Ahrefs, January 2026); 31% rank beyond position 100. Measure citation directly ([Google's AI answers](references/google-ai-overviews.md)).
4. **ChatGPT changed shape with GPT-5.6 (August 2026).** Its searches name the brands it already has in mind, it cites l

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 8 — file references are metadata, not package contents.

View saved version →

---
name: amazon
description: When the user sells on Amazon or plans to, and asks how to rank, what a listing should say, what rivals charge, who holds the Buy Box, or how big demand is on Amazon. Holds dated, sourced findings a model lacks (the 75-character title cap and Item Highlights from July 2026, Rufus renamed Alexa for Shopping and picking products that do not rank, the Buy Box eligibility gate removed, reviews split across variations, 2026 fees, Amazon blocking ChatGPT) and how to read Amazon search volume and results data without overclaiming. Also use when the user mentions Amazon SEO, A9 or A10, Amazon keyword research, backend search terms, a listing audit, product titles, bullets or main image rules, an ASIN teardown, rival listings, resellers undercutting us, Vine, getting reviews, Sponsored Products, ACoS, Brand Analytics, an Amazon launch, or a 30-60-90 day Amazon plan. Google Shopping and feeds go to google-shopping, other ad platforms to paid-ads, review mining to voice-of-customer, market sizing to market-research.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Amazon

How products get found, chosen and bought on Amazon as the evidence stood in October 2026, and how to read Amazon's public results and listings without claiming more than they show. A model's picture of Amazon is mostly from 2023 and 2024 and is wrong in places: titles are capped at 75 characters, Amazon's assistant (now Alexa for Shopping) sits in the search bar and recommends products that often do not rank, the Buy Box no longer screens sellers first, and reviews stopped pooling across unlike variations. "A10" is seller folklore, not an Amazon spec. Prefer what is written here to what you remember, and re-check any policy or fee older than six months in Seller Central before acting on it.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the product, its ASINs, price, margin, marketplace, whether the user is the brand owner (Brand Registry) or a reseller, fulfilment (FBA or merchant), and competitors with their ASINs from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Reading live results pages, listings, sellers and Amazon search volume needs the Manifold connector: look for `amazon_search_products`, `amazon_get_product`, `amazon_get_sellers` and `amazon_get_keywords` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill, use the by-hand methods in the references (a logged-out private window on the right marketplace, the user's own Seller Central and Brand Analytics exports), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a measurement.
- **The user's own numbers are not in Manifold.** Sales, sessions, conversion, Brand Analytics, ad spend and ACoS live in Seller Central and the Amazon Ads console. Ask for exports; never estimate them from public data and present the estimate as theirs.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Titles are 75 characters now.** From 27 July 2026 every category except media caps titles at 75 characters with spaces; Amazon's AI rewrites longer titles gradually, and brand owners get 14 days to review. The new Item Highlights field (125 characters) is searchable and shows with the title (Amazon Seller Forums, update

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 12 — file references are metadata, not package contents.

View saved version →

---
name: app-store
description: When the user wants more installs from Apple's App Store or Google Play search, or research on apps in a category. Holds dated, sourced findings a model lacks (what each store indexes, App Store tags, custom product pages in search, AI review summaries, more Apple Ads slots since March 2026, conversion benchmarks, rating prompt rules, why store volumes are models) and how to read Manifold's store data. Also use when the user mentions ASO, app store optimization, App Store keywords, the keyword field, app title or subtitle, Play Store description, app screenshots or icon tests, product page optimization, store listing experiments, competitor apps, app reviews, replying to reviews, raising an app rating, top charts, Apple Search Ads and organic, apps in ChatGPT, finding app developers to contact, or an ASO plan. Web search goes to seo, AI answers in general to ai-search, rivals beyond the store to competitor-intel, review themes to voice-of-customer, ad budgets to paid-ads.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# App store

How apps get found and installed on Apple's App Store and Google Play, as the evidence stood in October 2026, and how to read store data without overclaiming. A model's memory of app store optimisation is mostly 2023 and is now wrong in places: Apple generates search tags from listings with an LLM, custom product pages rank in organic search, both stores write an AI summary of the reviews above them, Play answers questions about an app with Gemini, and App Store search carries several ads since March 2026. It is also likely to quote third-party keyword volumes as searches; no store publishes counts. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the app, its store links and ids, the platforms, the category, the ICP, competitors and the words customers use from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first. Ask the user for what no public tool shows: the App Store keyword field, App Store Connect or Play Console analytics, and Apple Ads data.
- **Connector.** The knowledge here needs no tools. Reading listings, store keywords, competitors, reviews and charts needs the Manifold connector: look for `apps_get_app`, `apps_get_keywords`, `apps_get_competitors` and `apps_get_reviews` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill and use the by-hand method in [keywords](references/keywords.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. If some tool groups are there and others are not, they are switched off on the app's Tools page: say which, and mark those rows "not checked". Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Apple indexes 160 characters, Play indexes the description.** Apple ranks on the name (30), subtitle (30), keyword field (100) and categories, plus downloads, ratings and reviews; promotional text and the description do not count (Apple's search docs, 2026), and practitioner tests show words combining across the three fields. Play has no keyword field: title (30), short description (80) and full description (4,000) carry the terms, and Google c

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 10 — file references are metadata, not package contents.

View saved version →

---
name: brand-monitoring
description: When the user wants to know who is talking about the brand, be alerted to new mentions, or measure how well known the brand is against competitors. Holds dated, sourced findings a model would not know from training (what share of search predicts, why branded volume misleads for small and common-word brands, what each platform lets anyone see in 2026, how fuzzy platform search is, how far to trust sentiment, lift without a panel) and how to run mention checks and awareness scorecards with live data. Also use when the user mentions alert me when someone mentions us, monitor Reddit for our brand, social listening, brand monitoring, mention alerts, track mentions every day, who talked about us this week, a brand awareness plan, nobody knows who we are, share of voice against competitors, share of search, grow branded search, brand lift, get our name out there, or getting the brand known. AI answers alone go to ai-search, rivals' moves to competitor-intel, client reporting to agency.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Brand monitoring

Who is talking about the brand, how many people know it, and how to tell a real change from noise, as the evidence stood in October 2026. What a model likely has wrong: it treats a social listening tool as seeing everything (no tool does; the platforms closed most of their doors in 2024 to 2026), treats platform search as exact (TikTok and YouTube match loosely enough that most rows for a short brand name are about something else), quotes share of search as "83% accurate" (it is an average ratio, not an accuracy), and reads branded search volume as a weekly number (it is bucketed, monthly and a month or more behind). Prefer what is written here to what you remember, and re-check any platform fact older than six months.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the brand, product and founder names, the domain, the competitors, the audience and the brand's own social accounts from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Watching mentions and measuring awareness live needs the Manifold connector: look for `reddit_get_new_posts`, `reddit_search_comments` and `seo_get_keyword_metrics` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill and use the by-hand methods in [monitoring](references/monitoring.md#without-the-connector) and [share of search](references/share-of-search.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. If some tool groups are present and others are not, they are switched off on the app's Tools page: mark those platforms "not watched" or "not measured", never zero. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Share of search tracks market share, and leads it, as a share, not a volume.** A brand's searches over all brands' searches in the category correlated with and led market share in cars, energy and phones (Binet, IPA, October 2020; up to about a year ahead for cars, weeks for energy). Across 30 cases in 12 categories and 7 countries it averaged 83% of share of market, with the ratio varying by category (IPA think tank, October 2021). The "83% accuracy" in vendor posts is a misreading

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 7 — file references are metadata, not package contents.

View saved version →

---
name: competitor-intel
description: When the user wants to know who their competitors are, what a rival is doing, or how to beat one. Holds what a model gets wrong about competitive research in 2026 (how far off traffic and keyword estimates are, the DataForSEO traffic model change on 1 November 2026, what ad libraries show, why AI answers now set the shortlist, what battlecard surveys can prove, the legal lines) and what each Manifold tool costs and hides. Also use when the user mentions real competitors, competitors we have never heard of, the competitive landscape, alternatives to X, a competitor teardown or profile, what is X doing in marketing, competitor alerts, a sales battlecard, landmine questions, competitor messaging or pricing side by side, what people hate about X, why customers leave X, competitive strategy, how do we beat X, or a 90-day plan against the incumbents. Positioning and objections go to voice-of-customer, ad creative to paid-ads, market maps to market-research, comparison pages to seo.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Competitor intelligence

Who the user really competes with, what each rival does and can afford, what buyers and AI engines say about them, and how to turn that into a plan, a battlecard or a weekly watch, as the evidence stood in October 2026. A model tends to get three things wrong: it reads Similarweb, Semrush, Ahrefs or DataForSEO traffic as a visit count, it takes the domains sharing a site's keywords for its competitors, and it fills in a rival's prices, features and headcount from memory. Every number about a competitor needs a source and a date, or it stays out.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the product, domain, category, ICP, known competitors with their domains and handles, differentiation, proof points and the objections sales hears from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first. After delivering, offer to write the competitors, their claims and the counters back into that file.
- **Connector.** The knowledge here needs no tools. Measuring a rival needs the Manifold connector: look for `seo_get_domain_overview`, `ads_get_advertiser_ads`, `aeo_run_ai_answers` and `reddit_search_posts` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill and use the by-hand methods in the references (the public ad libraries, the rival's own pages, AI engines asked in a private window), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. If some tool groups are there and others are not, they are switched off on the app's Tools page: say which, and mark those rows "not checked" so nobody reads a gap as a zero. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Traffic estimates are off by about half for a typical site, and far more for small ones.** Median error against Search Console was 49.5% for Ahrefs and 68.4% for Semrush (Ahrefs, 1,635 sites, May 2022, vendor-run); against Google Analytics no provider was consistently accurate and ±100% errors were common, though trends correlated well (SparkToro, 641 sites, November 2022). On five small sites of our own, DataForSEO estimated 0.2 to 1,168 visits a month against 0 to 9 real US clicks. Compare sites with one tool; never quote an estimate as visits ([readin

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 10 — file references are metadata, not package contents.

View saved version →

---
name: creators
description: When the user wants to work with influencers, creators, UGC makers, affiliates or brand fans on TikTok, Instagram or YouTube, from a plan to a shortlist, a vetting, a fair price and a brief. Holds dated, sourced findings a model lacks (what creators are paid in 2026, why smaller creators return more per dollar, which fraud signals hold up, the FTC reviews rule, usage rights for Spark Ads and partnership ads) and how to read Manifold's creator data without trusting follower counts, the is_ad flag or the audience sample. Also use when the user mentions an influencer strategy or creator program, KOLs, micro or nano influencers, TikTokers, Reels creators, YouTubers to sponsor, UGC creators, vet this influencer, fake followers, engagement rate, is this creator worth the fee, a creator brief, influencer disclosure, gifting or seeding, affiliate partners, who promotes our competitor, brand advocates, or Spark Ads. The user's own accounts go to tiktok, instagram or youtube, creator posts run as ads to paid-ads.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Creators

How to find, size, vet, price and brief creators, UGC makers, affiliates and fans on TikTok, Instagram and YouTube, as the evidence stood in October 2026. A model's instincts here are mostly wrong in the same direction: it prices on followers, trusts the platform's paid flag, quotes fraud percentages nobody can trace, and treats a platform's partnership label as legal cover. Followers are what a creator charges for; median views on recent posts are what the user gets. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the product, niche, ICP and what they watch, the markets, competitors, budget and claims the user can prove from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Finding and measuring creators needs the Manifold connector: look for `tiktok_search_videos`, `instagram_search_posts`, `youtube_search_videos` and `tiktok_get_audience` (hosts often add a prefix such as `mcp__manifold__`). If one platform's group is missing, it is switched off on the app's Tools page; work on the platforms that are on and say so. If no Manifold tool is there, still answer from this skill with the by-hand method in [vetting](references/vetting.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Most paid creator deals are small.** On Collabstr's marketplace the average paid collaboration in its 2026 report was about $186 on TikTok, $193 on Instagram and $255 on YouTube, and roughly 80% cost under $300; UGC campaigns grew 133% while TikTok-only campaigns fell 48%. These describe small creators who sell through a marketplace, not agency-priced names ([rates](references/rates.md)).
2. **Smaller creators return more per dollar, but the smallest are not the most engaging.** Targeting low-follower creators returned an ROI an order of magnitude higher than high-follower ones, explained by engagement (Beichert et al., Journal of Marketing, 1.88M purchases and three field studies). Engagement on sponsored posts fol

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 9 — file references are metadata, not package contents.

View saved version →

---
name: digital-pr
description: When the user wants earned media (press coverage, journalists writing about them, expert quotes, guest spots on podcasts) and the links, mentions and AI citations it brings. Holds dated, sourced findings a model lacks (what journalists said they want in the 2026 Muck Rack and Cision surveys, why mass pitching earns fewer links, what replaced HARO and Connectively, how much AI answers lean on earned media, why YouTube views understate a podcast) and how to build media and booking lists from live data. Also use when the user mentions a digital PR strategy or plan, how do we get press coverage, data-led PR, a survey for press, newsjacking, reactive PR, expert comment, a media list, journalists or reporters to pitch, press contacts, a HARO alternative, who covered our competitor, launch press, an embargo or exclusive, podcasts I could guest on, getting our founder on podcasts, or a podcast tour. Links and site contacts go to link-building, AI answers to ai-search, launch timing to growth-strategy.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Digital PR

How to earn coverage from journalists and hosts, as the evidence stood in October 2026: what reporters say they want, which stories earn links, where sourcing requests went after HARO's shutdown and revival, how podcast audiences are really sized, and why earned media now matters as much for AI answers as for Google. A model's picture of PR is mostly pre-2024: HARO as a free link source, press releases as an SEO tactic, "follow up three times", subscriber counts as audience. Much of that is wrong now. Prefer what is written here, and re-check any survey figure older than a year before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the brand, domain, category, ICP, competitors, spokespeople, proof points and any data the user holds from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Finding the coverage competitors earned, reporters on a beat, their addresses and podcasts to guest on needs the Manifold connector: look for `seo_get_backlinks`, `leads_get_domain_emails` and `youtube_search_videos` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill and use the by-hand method in [media lists](references/media-lists.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a measurement, a reporter or an address.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Pitches still start stories, but relevance is the whole game.** 86% of journalists say at least some of their stories began with a PR pitch, yet 88% delete pitches outside their beat and 43% say a relevant pitch is rare (Muck Rack, 897 journalists, March 2026). 72% say fewer than a quarter of the pitches they get are relevant (Cision, 1,899 journalists in 19 markets, May 2026). A reporter's own recent article is the only proof of a beat ([pitching](references/pitching.md)).
2. **Short, one-to-one, one follow-up.** 62% prefer a one-to-one email and 69% prefer under 200 words (Muck Rack 2026). One follow-up is what most journalists ask for; repeated chasing gets a sender ignored. About half seldom or never reply to pitches at all, so silence is not a no.
3. **Mass

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 9 — file references are metadata, not package contents.

View saved version →

---
name: facebook
description: When the user wants to grow or understand an organic Facebook page or the Facebook groups its buyers are in, or asks what works on Facebook now. Holds dated, sourced findings a model lacks (recommendations fill over a third of the feed, the July 2025 penalty on reposts, the link post cap, Reels ranked on viewer surveys, who uses Facebook by age, group threads ranking in Google while AI answers skip Facebook for local picks) and how to read Manifold's Facebook data without its traps. Also use when the user mentions a Facebook strategy, a 90-day Facebook plan, Facebook for a local business, a Facebook page audit, a competitor's Facebook page, is our Facebook page working, Facebook engagement, Facebook video scripts, the comments on our Facebook posts, Facebook comment analysis, Facebook group research or listening, what people ask in a Facebook group, or groups where Airbnb hosts, parents or local trades talk. Meta ads go to paid-ads, Instagram to instagram, pains across sources to voice-of-customer.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Facebook

What works for an organic Facebook page and in Facebook groups as the evidence stood in October 2026, and how to read Manifold's Facebook data correctly. A model's picture of Facebook is mostly a page talking to its followers; that is out of date. Over a third of what Americans see in the feed is now recommended from accounts they do not follow, reposted content is penalised across a whole page, link posts are nearly invisible and capped for some pages, and Reels are ranked on what viewers say matches their interests. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the page, area or niche, ICP, competitors and their pages, and brand voice from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Reading pages, posts, comments, groups and transcripts needs the Manifold connector: look for `facebook_get_posts`, `facebook_get_group_posts` and `facebook_get_comments` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill: the user can read their own Professional Dashboard and Meta Business Suite, and the scoring in [page audit](references/page-audit.md) works on numbers copied by hand from a page. Tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. If other Manifold tools are there but the Facebook ones are not, that tool group is switched off on the app's Tools page. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Followers do not decide reach.** In Q1 2026, 39.0% of US Feed views were recommendations from accounts people do not follow, against 48.1% from friends, joined groups and followed accounts; in 2022 recommendations were about 15% (Meta, Widely Viewed Content Report). Judge a page on engagement per post and per 1,000 followers, never on its follower count ([feed](references/feed.md)).
2. **Reposting other people's content now hurts the whole page.** Since 14 July 2025, accounts that repeatedly reuse others' videos, photos or text lose monetisation and get reduced distribution on everything they post; duplicate videos are demo

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 8 — file references are metadata, not package contents.

View saved version →

---
name: google-shopping
description: When the user sells products online and wants them found on Google Shopping and free listings, in AI Mode and AI Overviews product results, or in ChatGPT, Gemini and Perplexity shopping answers. Holds dated, sourced findings a model lacks (ChatGPT took most product picks from merchant feeds from July 2026 and dropped Instant Checkout, Google removed free listings from European search in September 2026 and turned native checkout on by default for Shopify stores, the review floors for stars, the 2026 feed attributes) and how to read live Shopping prices, sellers and reviews. Also use when the user mentions Google Shopping, Merchant Center, a product feed, free listings, price comparison, who sells our product cheaper, price competitiveness, product reviews or star ratings, seller ratings, product structured data, ChatGPT shopping, the Agentic Commerce Protocol, UCP, agentic checkout, or a Shopping plan. Amazon goes to amazon, bids and campaigns to paid-ads, brand answers in AI to ai-search, web rankings to seo.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Google Shopping and AI shopping

How products get found on Google Shopping and in AI shopping answers as the evidence stood in October 2026, and how to read live Shopping data without overclaiming. A model's picture of this is mostly from 2024, before merchant feeds became the main source for ChatGPT's product picks, Google's AI answers began linking products straight to Shopping listings, and free listings left European web search. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the store, domain, platform (Shopify, WooCommerce or other), top products, countries sold to, competitors and price position from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Reading live Shopping results, prices, sellers, reviews and AI answers needs the Manifold connector: look for `shopping_search_products`, `shopping_get_sellers`, `shopping_get_reviews` and `aeo_run_ai_answers` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill and use the by-hand method at the end of each reference, and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. If only the Shopping group is missing it is switched off on the app's Tools page. Never invent a measurement.
- **The user's own numbers are exports.** No tool reads Merchant Center, the feed file, price competitiveness or AI performance insights; ask for them when the job needs them.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **ChatGPT's product picks now come mostly from feeds.** The feed-sourced share jumped from 8.26% to 61.54% on 10 July 2026 and was about 65% by September; the top 10 stores' share of references nearly doubled (22.5% to 41.8%) and a fifth of merchants dropped out (Profound, 1.76M prompt runs; vendor data, unconfirmed by OpenAI). Shopify and Etsy stores are connected automatically; others apply or connect through an Agentic Commerce Protocol provider ([AI shopping answers](references/ai-shopping.md#chatgpt)).
2. **Before that, Google Shopping supplied ChatGPT's carousel.** 83% of 43,000 carousel produ

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 7 — file references are metadata, not package contents.

View saved version →

---
name: growth-strategy
description: When the user wants to choose channels to grow, or wants a growth plan, a go-to-market plan, a launch, content ideas, a content calendar or repurposing. Holds dated, sourced findings a model lacks (how the channel mix shifted in 2025-2026, what a Product Hunt launch yields now, cadence and repurposing evidence, the attribution gap, which benchmarks to distrust) and how to take a cheap cross-channel baseline. Also use when the user mentions how do I grow my startup, a growth strategy or marketing plan, more traffic, signups, leads or customers with no channel named, traction, which channels should we be on, channel mix, a GTM plan, ICP and positioning for a new product, a launch plan or checklist, Product Hunt, Show HN, a waitlist, launch reactions, a posting schedule, content pillars, what to post, or turning a video or podcast into posts. One named channel goes to its own topic (seo, ai-search, reddit, linkedin, tiktok, paid-ads, outbound, creators, digital-pr).
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Growth strategy

Choosing channels, planning growth, go-to-market and launches, and keeping a content schedule, as the evidence stood in October 2026. A model's instincts here were formed when a Google ranking reliably sent clicks, organic social reached followers, Product Hunt featured most launches and "post at the best time" was advice. Since then Google sends a click on under a third of searches, AI answers shape shortlists while sending almost no traffic, Product Hunt became an editorial shelf, and the platforms penalise reposted content. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the product, price, ICP and the problem in their words, competitors, goal, the conversion that counts, budget, team and accounts from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Measuring demand, communities, competitors' ads and reactions needs the Manifold connector: look for `seo_search_keywords`, `reddit_get_new_posts` and `aeo_run_ai_answers` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill and use the by-hand checks in [channel selection](references/channel-selection.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. If some tool groups are present and others not, the missing ones are switched off on the app's Tools page: mark those channels "not measured", never "weak". Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Google sends a click on under a third of searches.** 68% of US Google searches ended with no click in January to April 2026, up from 60% in 2024, and clicks of any kind fell 23% (SparkToro on Similarweb's clickstream panel, June 2026). Search is still the largest referrer, but a ranking captures less than any plan written before 2025 assumed ([channel selection](references/channel-selection.md#what-changed-in-2025-2026)).
2. **AI answers decide shortlists, not traffic.** Across 54 sites, AI assistants sent 0.24% of sessions against 31.9% from organic search, and converted no differently (4.87% against 4.60%, p = 0.79

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 10 — file references are metadata, not package contents.

View saved version →

---
name: instagram
description: When the user wants to grow on Instagram, audit an Instagram account, or know what Instagram rewards now. Holds dated, sourced findings a model would not know from training (what Mosseri says Instagram ranks on, the April 2026 rule that drops reposting accounts from recommendations, Trial Reels, the 3-minute limit for recommended Reels, the five-hashtag cap, Your Algorithm, teen account limits, 2025-2026 engagement benchmarks by format) and how to read Manifold's Instagram data without its traps. Also use when the user mentions an Instagram or IG strategy, content plan or 90-day plan, how to grow on Instagram, reels or carousels, how often to post reels, an Instagram audit, a competitor's Instagram, Instagram engagement rate, best performing posts, Reels hooks or caption hooks, reels skipped early, Reels trends or what to film next, mining Instagram comments, objections under reels, or why a reel went viral. Creators and influencers go to creators, Meta ads to paid-ads, TikTok to tiktok, Facebook to facebook.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Instagram

What gets organic reach on Instagram as the evidence stood in October 2026, and how to read Manifold's Instagram data without fooling yourself. Much of what a model believes about Instagram dates from before 2025 and is now wrong: hashtags do not add reach and are capped at five, an account that mostly reposts others' work is cut out of recommendations, sends to non-followers matter more than likes, and follower count says little about how many people a reel reaches. Prefer what is written here to what you remember, and re-check anything older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the brand, the Instagram handle, the ICP, the competitors and their accounts, the brand voice and the goal from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Measuring accounts, reels, hashtags and comments needs the Manifold connector: look for `instagram_get_profile`, `instagram_get_reels` and `instagram_search_posts` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill and use the by-hand method in [the data notes](references/data.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. If other Manifold tools are there but not the `instagram_*` ones, the Instagram tool group is switched off on the app's Tools page. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Watch time, likes and sends are the signals Instagram names**, measured per reach. Likes weigh more with followers, sends (shares by DM) more with non-followers (Mosseri, January 2025 and May 2026). Reaching new people means making something people send ([ranking](references/ranking.md)).
2. **Mostly reposting gets an account cut from recommendations.** Since 30 April 2026, an account whose posts over a rolling 30 days are mostly unoriginal, photos and carousels included, is not shown to non-followers; a credit, a crop or a watermark does not make a repost original. Collabs, Remix and Reposts are the allowed routes ([ranking](references/ranking.md#originality)).
3. **Reels are recommended up to 3 minutes**, though

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 10 — file references are metadata, not package contents.

View saved version →

---
name: link-building
description: When the user wants backlinks that help Google rankings, or a contact at any site to ask for a link, a list entry or a correction. Holds dated, sourced findings a model would not know (how much links still correlate with rankings, what Google's 2025-2026 spam updates neutralise, what paid placements cost and how to disclose them, how fast links decay, what domain rank, Ahrefs DR and spam score measure and where Manifold's backlink fields mislead), and the one copy of the steps that find and verify a publisher's contact. Also use when the user mentions link building, off-page SEO, growing DA or DR, link prospects, sites that link to competitors but not to us, guest posts, link insertions, unlinked mentions, lost or broken backlinks, link reclamation, 404 pages with links, broken link building, best X lists that rank on Google, disavow, toxic links, or buying links. Rankings and content go to seo, press campaigns to digital-pr, AI citations to ai-search, redirects and migrations to technical-seo.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Link building

Links for Google rankings, and how to find the person at any site who can add one, as the evidence stood in October 2026. Links still correlate with rankings, but weakly and less than in 2019; Google neutralises most bought links silently rather than penalising them; and the authority scores everyone quotes are tool inventions Google does not use. A model's memory of link building is full of 2019 benchmarks and "raise your DA" advice; prefer what is written here, and check any figure older than six months before quoting it to a client. Links for AI answers are a different job: engines pick sources by what they cite, not by domain rank (see [ai-search](../ai-search/SKILL.md)).

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the site, competitors and their domains, the pages that need links, brand and founder names, the team and the budget from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Pulling backlinks, rating domains and finding contacts needs the Manifold connector: look for `seo_get_referring_domains`, `seo_get_domain_ratings` and `leads_get_domain_emails` (hosts often add a prefix such as `mcp__manifold__`). If the `seo_*` tools are there but the `leads_*` tools are not, the leads tool group is switched off on the app's Tools page (https://www.manifoldmcp.com/docs/authentication#turn-tool-groups-off): deliver the site list without contacts. If none is there, still answer from this skill and the by-hand notes in [contacts](references/contacts.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Links still correlate with rankings, weakly.** Referring domains correlated with top-20 position at 0.255 across Ahrefs' top 1M US keywords (January 2025), down from about 0.29 in its 2019 sample, and at about 0.33 for local queries. Semrush's January 2024 study (16,298 keywords) put referring domains at 0.18, behind page traffic at 0.33 and text relevance at 0.47. Google says links are not a top-three factor (Illyes, 2023). Links are one input; promise net referring domains, not page one.
2. **Trust beats count.** Go

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 8 — file references are metadata, not package contents.

View saved version →

---
name: linkedin
description: When the user wants to grow on LinkedIn without paying for it, as a founder, a team or a company page, or asks what works on LinkedIn now. Holds dated, sourced findings a model lacks (the 2026 feed rebuilt on LLM retrieval, reach for active posters down by a third to a half since 2024, the July 2026 cut to comment-keyword bait, what links and polls cost, the AI slop and pod crackdowns, how AI answers cite LinkedIn) and how to read Manifold's LinkedIn data honestly. Also use when the user mentions a LinkedIn strategy or 90-day plan, founder-led content, personal branding or thought leadership on LinkedIn, a company page audit or a competitor's LinkedIn page, what LinkedIn posts work, hooks, post length, why our posts get no reach, posts to comment on, a commenting routine, social selling, top LinkedIn voices in a niche, or people on LinkedIn asking for a tool like ours or complaining about a competitor. LinkedIn ads go to paid-ads, emails and outreach to the people found to outbound, X to x-twitter.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# LinkedIn

What gets a person or a company page seen on LinkedIn, as the evidence stood in October 2026, and how to read LinkedIn's public data honestly. Much of what a model believes about LinkedIn comes from 2022 to 2024 creator advice and is now wrong or overstated: the feed was rebuilt in March 2026 around topic matching rather than who follows whom, reach for active posters roughly halved over two years, "comment GUIDE to get it" posts lost about half their reach overnight in July 2026, putting the link in the first comment is no longer free, and the "golden hour" decides far less than folklore says. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the brand, the founder's profile and the company page, the ICP, competitors and the goal from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Reading posts, profiles and pages needs the Manifold connector: look for `linkedin_search_posts`, `linkedin_get_post` and `linkedin_get_profile` (hosts often add a prefix such as `mcp__manifold__`). If other Manifold tools are there but these are not, the LinkedIn tool group is switched off on the app's Tools page (https://www.manifoldmcp.com/docs/authentication#turn-tool-groups-off); say so. If none are there, still answer from this skill and use the by-hand method in [reading the data](references/data.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **The feed is now matched on topic, not on your network.** One LLM-embedding retrieval now draws from network and out-of-network posts alike, and a ranker reads a member's last 1,000+ interactions in order to predict clicks, skips, long dwells, likes, comments and shares (LinkedIn Engineering, 12 March 2026). Posting steadily inside one topic area matters more than followers or hashtags ([the feed](references/feed.md)).
2. **Reach fell hard for people who post often.** Down about 60% over two years for active creators, engagement down 20% to 25% (Richard van der Blom, 1.3

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 10 — file references are metadata, not package contents.

View saved version →

---
name: local-seo
description: When the user wants a business that serves a town or an area found on Google Maps, in the local pack and in AI answers, or asks what works in local SEO now. Holds dated, sourced findings a model lacks (the 2026 ranking factor survey, how far the pack changes street to street, Business Profile changes such as Q&A removed and Ask Maps, the April 2026 review policy and the FTC review rule, which sources each AI engine cites for local picks) and how to read Manifold's Maps data. Also use when the user mentions Google Maps ranking, the map pack, Google Business Profile or GMB, a profile audit, NAP and citations, a service area business, a suspended or unverified profile, getting more reviews, replying to reviews, fake reviews, a local rank grid or heatmap, near me searches, local competitors, multi-location SEO, local businesses without websites to pitch, or being recommended by ChatGPT for a local service. Classic rankings go to seo, AI answers beyond local to ai-search, pitching and reporting to agency.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Local SEO

How a business that serves an area gets found on Google Maps, in the local pack and in AI answers, as the evidence stood in October 2026, and how to measure it without fooling yourself. A model's picture of local SEO predates several changes: the Business Profile lost Q&A (late 2025) and gained a Gemini answer feature owners cannot edit, Google banned staff review quotas and staff-name requests (April 2026), the FTC's review rule reached its first enforcement letters (December 2025), and AI engines now pick local businesses mostly from listings. Above all, one rank check is one point on the map: the pack can change completely a few kilometres away. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the business name, address or service area, categories, services, towns served, competitors and main searches from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Measuring rankings, profiles and AI answers needs the Manifold connector: look for `maps_search_places`, `maps_get_place`, `maps_search_businesses`, `seo_get_serp` and `aeo_run_ai_answers` (hosts often add a prefix such as `mcp__manifold__`). If the `maps_*` tools are missing while other Manifold tools are there, the Maps group is switched off on the app's Tools page; say so and use `seo_get_serp` for the local pack. If none are there, still answer from this skill with the by-hand methods in the references, and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a ranking, a review count or a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Category and proximity decide the pack.** The 2026 Local Search Ranking Factors survey (Whitespark, 47 experts scoring 187 factors, November 2025) puts primary category, proximity to the searcher, keywords in the business name, an address in the searched city, and being open at the time of search at the top. Google's own help page names relevance, distance and prominence and says no one can pay for a better local rank ([ranking factors](references/ranking-factors.md)).
2. **The pack ch

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 9 — file references are metadata, not package contents.

View saved version →

---
name: manifold-get-started
description: When the user is new to the Manifold marketing skills, asks where to start, or wants to set up or update the context every other skill reads first. Writes .agents/product-marketing.md (the business type, what it sells, the customers, competitors, positioning, customer language, proof, goals, accounts and what to track) for any kind of business, from B2B software to a shop, a local service, an app, a creator or a nonprofit, drafting from the site and asking only for the gaps. Then recommends the two or three skills that fit the goal, and the first job to do in each, with what it costs. Also use when the user mentions getting started, I just installed this, which skill should I use, what can Manifold do, product or marketing context, describe my business, ICP, target audience, brand voice, or update our context after a pivot, a new competitor or a price change. A growth plan built on real data goes to growth-strategy.
compatibility: Works without the Manifold MCP connector. With it, the draft also reads search data for the site at about 35 credits, asked first.
---

# Manifold get started

The first skill to run. It writes down once what every marketing task needs to know about the business, so no other skill has to ask again, and then picks the skills that fit the user's goal and the first job in each. Each skill covers one area of marketing (AI search, SEO, Reddit, outbound and so on) and holds what changed in that area since models were trained. Setting up the context costs nothing without the connector and about 35 credits with it; picking the skills runs no tools.

## The file

The context lives in the project at `.agents/product-marketing.md`, plain Markdown, the same path and sections other marketing skill libraries use, so one file serves them all. Every other skill reads it before its first question and asks only for what it lacks.

Sections, in this order. Keep each short: bullets, the user's own words, no filler. A section the user cannot answer yet says "Unknown" rather than a guess. The sections are the same for every business, but what each one asks depends on the business type: read them through [business-types.md](references/business-types.md).

1. **Product overview**: the business type, the one-line description of what it sells, the category buyers would put it in, how it makes money and the price points.
2. **Target audience**: who buys (a company, a person, both sides of a marketplace), who decides, and the main reason they buy.
3. **Personas**: each person involved in a purchase and what each one values.
4. **Problems and pain points**: the problem or the want, what it costs the buyer, and the emotional side.
5. **Competitive landscape**: direct competitors, secondary ones, and the indirect option (doing it yourself, a cheaper substitute, doing nothing).
6. **Differentiation**: the main advantages and why customers choose this business.
7. **Objections and anti-personas**: the top three objections with the answer to each, and who is not a fit.
8. **Switching dynamics**: push, pull, habit and anxiety, the four forces behind a switch.
9. **Customer language**: verbatim phrases customers use, with the source, and words to use and to avoid.
10. **Brand voice**: tone, style and personality, with one example line.
11. **Proof points**: numbers, customer names, reviews and testimonials the user can stand behind.
12. **Goals**: the business goal now, the conversion that counts (a purchase, a booking, a signup, a demo, a donation), the stage (idea, pre-launch, launched, growing) and the monthly marketing budget.
13. **Accounts and markets**: the site's domain, the Search Console property and Google Analytics property if any, each social account's handle or URL, store or app listings, the competitors' domains and handles, the countries, cities and languages that matter.
14. **Tracking set**: the 10 to 20 keywords and the AI prompts the business wants to win, with the date th

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: market-research
description: When the user wants to size a market, map the players in a category, check whether there is demand for an idea, or decide whether to enter a new country, language or segment. Holds dated, sourced findings a model gets wrong (search volume is a bucketed 12-month mean, Trends disagrees with itself, AI search volume is a model, stated interest overstates paying, other countries use other search engines) and how to count accounts, demand and players with live data. Also use when the user mentions TAM, SAM, market size, how many companies fit our ICP, is the market big enough, a market map or landscape, who are all the players in X, segment the market, idea validation, is there demand for X, is anyone searching for X, is this market growing or dying, should we build X, a fake door or smoke test, expand into Germany, which country first, international expansion, localization, or moving into enterprise. Named rivals go to competitor-intel, pain points to voice-of-customer, a go-to-market plan to growth-strategy.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Market research

How big a market is, who serves it, whether people want what the user plans, and whether a new country or segment is worth entering, as the evidence stood in October 2026. A model is likely to treat search volume as a count, Google Trends as stable, "AI search volume" as a measurement of what people ask ChatGPT, a waitlist as proof of demand, and Google as the search engine everywhere. None of those hold. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the product, category, ICP, buyer titles, competitors, home market and price points from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Counting accounts, pricing keywords and reading answers live needs the Manifold connector: look for `seo_search_keywords`, `seo_get_keyword_metrics`, `leads_search_companies` and `aeo_search_prompts` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill and use the by-hand method at the end of each reference, and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Search volume is a bucket and a 12-month mean, not a count.** Keyword Planner reports about 60 to 80 fixed values, groups close variants under one figure (so summing variants double-counts) and shows low-spend accounts only ranges. Ahrefs found 54% of Keyword Planner figures more than 50% above Search Console impressions (72,635 keywords, 2021, vendor study). Manifold's default Labs volume is the same buckets, a month behind Keyword Planner ([demand signals](references/demand-signals.md)).
2. **Some head terms jumped in 2026, in Google's own data.** In our October 2026 pull, generic English software terms ("crm software", "email marketing software") rose 4x to 100x between March and May 2026 and again in September, in the US and in Germany, while long-tail and German terms did not: "email marketing software" shows 135,000 a month against a median month of about 38,000. Read `trend[12]` and size from the median mont

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 6 — file references are metadata, not package contents.

View saved version →

---
name: outbound
description: When the user wants B2B outbound that gets replies, a lead list, or to know what works in cold email now. Holds dated, sourced findings a model would not know (which Gmail, Yahoo and Microsoft sender rules bite on cold email to company domains, 2025-2026 reply-rate benchmarks and what moves them, whether AI personalisation works, why a third of B2B addresses cannot be verified, GDPR, PECR and CAN-SPAM basics) and how to read Manifold's leads data, email waterfall and verification statuses. Also use when the user mentions an outbound or ABM plan, cold outreach strategy, leads, a prospect or ICP list, decision makers by job title, enrich this CSV, append emails, verify or clean an email list, bounces, catch-all, intent data, buying signals, companies that just raised, champion or job-change tracking, lookalike companies, first lines or icebreakers, account research or call prep, or our first 100 customers. LinkedIn content and social selling go to linkedin, rivals to competitor-intel, client work to agency.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Outbound

Who to contact, why now, how to reach their inbox and what makes them reply, as the evidence stood in October 2026, plus the rules for Manifold's lead data. Much of what a model believes about cold email dates from 2022 to 2024 and is now wrong in places: the 2024 bulk-sender rules formally cover personal Gmail and Outlook.com mailboxes, not the company inboxes cold email goes to; reply rates are reported against different denominators and differ tenfold; "valid" from an email finder is not proof on the third of B2B domains that accept every address; and evidently AI-written email now costs replies. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the offer, ICP, best customers, buyer titles, countries and competitors from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Counting accounts, finding buyers, revealing and verifying emails and reading signals needs the Manifold connector: look for `leads_search_companies`, `leads_search_people`, `leads_get_email` and `leads_get_email_status` (hosts often add a prefix such as `mcp__manifold__`). If other Manifold tools are there but not the `leads_*` ones, the leads group is switched off on the app's Tools page; say so. If none are there, still answer from this skill with the by-hand methods in the references, and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a count, an address or a verification result.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **The 2024 sender rules cover consumer mailboxes, not company ones.** Google says its requirements apply "only when sending email to personal Gmail accounts" (not Workspace); Microsoft's, in force since 5 May 2025, cover Outlook.com, Hotmail, Live and MSN. Most B2B recipients sit on Google Workspace or Microsoft 365, so cold email to company domains is judged by the same filters but not the formal 5,000-a-day regime. Authenticate anyway: Gmail began rejecting non-compliant mail in November 2025, and its spam-rate line (under 0.1%, never 0.3%) is the one to plan around ([deliverability](references/de

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 9 — file references are metadata, not package contents.

View saved version →

---
name: paid-ads
description: When the user wants to plan, research or brief paid ads on Meta, Google, LinkedIn, TikTok or ChatGPT. Holds dated, sourced findings a model would not know from training (Meta's Andromeda and why creative diversity now does the targeting, Performance Max controls and AI Max results, ads in Google AI Overviews, AI Mode and ChatGPT with reported prices, CPC and CPM benchmarks from large datasets, brand bidding law) and how to read ad library data without overclaiming. Also use when the user mentions a paid ads strategy, Meta or Google ads, where to spend an ad budget, PPC, paid social, whether LinkedIn ads are worth it, the Meta, TikTok or LinkedIn ad library, the Google Ads Transparency Center, a swipe file, winning ads in a niche, competitors' ads, PPC or negative keywords, CPC, who bids on our brand, conquesting, an ad creative brief, ad fatigue, Advantage+ or Performance Max. Creators who make the ads go to creators, a competitor beyond its ads to competitor-intel, which channels at all to growth-strategy.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Paid ads

How paid ads are bought and judged as of October 2026, and how to read the public ad libraries without claiming more than they show. A model's memory of paid ads is mostly 2023 and 2024 and is wrong in places: on Meta the creative now does the targeting, Performance Max has negatives and search terms, Dynamic Search Ads began upgrading to AI Max in September 2026, ads run inside ChatGPT and Google's AI answers, and the TikTok ad library covers Europe only. Prefer what is written here to what you remember, and re-check any price or policy older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the product, price, buyer, competitors with their pages and domains, market and ad budget from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Reading the ad libraries and keyword prices needs the Manifold connector: look for `ads_get_advertiser_ads`, `ads_search_ads`, `ads_get_ad` and `seo_search_keywords` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill, read the libraries by hand (Meta Ad Library, TikTok's library, LinkedIn's Ad Library, Google's Ads Transparency Center) with the rules in [ad libraries](references/ad-libraries.md), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Ad libraries show survival, never results.** No library publishes clicks, conversions or spend for commercial ads, or the keywords a search ad bids on. An ad that has run 30 days and still runs is the best available proxy for a winner, but no study has tested that proxy, and automated campaigns keep weak ads alive at low spend ([ad libraries](references/ad-libraries.md#winners-what-run-length-means)).
2. **EU-shown ads carry far more data.** The Digital Services Act makes platforms keep ads shown in the EU for a year with targeting and reach; US-only ads carry none of that. TikTok's library holds European ads only, so a US-only TikTok advertiser is invisible, and it lagged about three weeks in our October 2026 run ([field notes](references/field-notes.md)).
3. **On Meta,

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 10 — file references are metadata, not package contents.

View saved version →

---
name: reddit
description: When the user wants to market on Reddit, or asks what works there now. Holds dated, sourced findings a model lacks (ChatGPT stopped citing Reddit in August 2026 while Perplexity and Google kept it, member counts gave way to weekly visitors, how subreddits now ban promotion and AI-written text, karma and account-age filters, silent removals) and how to read Manifold's Reddit tools without miscounting. Also use when the user mentions a Reddit strategy or marketing plan, should we be on Reddit, the founder on Reddit without getting banned, Reddit threads to reply to, posts asking for a tool like ours, where to comment this week, Reddit pain points, what Redditors complain about, customer language from subreddits, which subreddits to post in, subreddit rules, is self promotion allowed there, can I post my product in r/SaaS, Reddit threads that Google or AI answers show, Reddit SEO, or Reddit ads. Pains across every source go to voice-of-customer, AI answers as a whole to ai-search, paid campaigns to paid-ads.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Reddit

How to find the communities, take part without losing the account, mine what people say, and judge Reddit's weight in Google and AI answers, as the evidence stood in October 2026. Much of what a model believes about Reddit marketing is out of date: "Reddit is the way into ChatGPT" stopped being true in August 2026, the member counts it would size communities by are gone, and the communities a B2B brand most wants have written rules since 2025 that ban the product mention, the AI-drafted reply and the "what are your pain points" post outright. Prefer what is written here to what you remember, and re-read a community's rules before every post.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the problem the product solves, the ICP, the competitors and the customer language from it; the customer language becomes the search phrasings and match terms. Ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **The account.** No tool can see the user's Reddit account. Ask how old it is, roughly how much karma it has, and whether it is a personal account or a brand one: half of what the user may do depends on it ([rules](references/rules.md#the-account)).
- **Connector.** The knowledge here needs no tools. Measuring live Reddit needs the Manifold connector: look for `reddit_search_posts`, `reddit_get_new_posts` and `reddit_get_subreddit` (hosts often add a prefix such as `mcp__manifold__`). If other Manifold tools are there but the `reddit_*` ones are not, the Reddit tool group is switched off on the app's Tools page (https://www.manifoldmcp.com/docs/authentication#turn-tool-groups-off). If none are there, still answer from this skill and use the by-hand method in [reading the data](references/data.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a count, a rule or a thread.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **ChatGPT stopped citing Reddit in August 2026; the other engines did not.** Reddit fell from 3.83% to 0.52% of ChatGPT Search citations within a week (Promptwatch, 14 to 17 August), and by 95% in a fixed brand cohort (Qwairy). Perplexity's Reddit citations rose (+93%, Pierview, 44,488 citations), Google's AI Overviews barely moved

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 8 — file references are metadata, not package contents.

View saved version →

---
name: seo
description: When the user wants more organic traffic from Google, or asks what works in SEO now. Holds dated, sourced findings a model lacks (what the 2025 and 2026 updates rewarded and punished, CTR by position with and without AI Overviews, what the September 2025 num=100 change did to Search Console, how far keyword volumes and traffic estimates miss) and how to read that data without being fooled. Also use when the user mentions an SEO strategy or roadmap, keyword research, a content plan, topic clusters, pillar pages, an SEO brief or outline, quick wins, striking distance keywords, low-hanging fruit, title tags and meta descriptions, optimize this page, on-page SEO, content decay, refreshing or pruning old posts, keyword cannibalization, two pages competing, vs pages, alternatives pages, rank tracking, where do we rank, watching Search Console, or traffic drop alerts. Crawling, indexing, diagnosing a drop and migrations go to technical-seo, AI answers to ai-search, backlinks to link-building.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# SEO

What earns organic traffic from Google as the evidence stood in October 2026, and how to read the data without fooling yourself. A model's picture of SEO is mostly from before three changes: Google's 2025 and 2026 updates turned against commodity and self-serving content and toward sites that sell something, let people do something and own something; AI Overviews now take about half the clicks at the top of informational results; and in September 2025 Search Console's impressions and average position changed meaning overnight. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the site, product, ICP, competitors, market and money pages from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Measuring rankings, keywords and the user's own clicks needs the Manifold connector: look for `seo_get_ranked_keywords`, `seo_get_serp` and `console_list_properties` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill, work by hand from the user's own Search Console export and Google's live results, and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a measurement.
- **Search Console is optional.** Most accounts have not connected it. When the `console_*` tools are present, use them first; when not, use the estimates and label them, and do not ask the user to connect unless the job is about their own clicks ([Search Console](references/search-console.md#connecting)).

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Winners sell, do and own something.** Across 400+ sites over the December 2025 and March 2026 updates, winners far more often offered a product (70% against 35% of losers), let visitors complete a task (84% against 50%) and had proprietary data, tools or templates (93% against 57%); first-hand experience and UGC did not separate them (Zyppy, April 2026; correlational). Build pages around an asset the site owns, not a summary of what ranks ([updates](references/google-updates.md#what-winners-had)).
2. **Self-ranking "best X" lists are a risk, though the evidence is s

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 11 — file references are metadata, not package contents.

View saved version →

---
name: technical-seo
description: When the user wants to know if Google can crawl, render and index their site, why organic traffic fell, or how to move a site without losing rankings. Holds dated, sourced findings a model lacks (the September 2025 num=100 change that cut Search Console impressions with no real loss, the 2MB fetch limit, 2025 and 2026 update dates, how JavaScript, noindex and canonicals are handled now, how little Core Web Vitals weigh, how slowly domain migrations recover) and how to read crawl and Search Console data right. Also use when the user mentions technical SEO, an SEO audit or health check, crawl our site, broken links, duplicate titles, noindex or canonical problems, redirect chains, crawled currently not indexed, indexing problems, Core Web Vitals or INP, our traffic dropped, we lost rankings, was it a Google update, clicks down but impressions flat, a site migration, changing domains, a redirect map, a replatform, redesign or subdomain merge. Content and rankings go to seo, AI crawlers and llms.txt to ai-search.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Technical SEO

Whether Google can crawl, render, index and choose the right pages, why traffic fell, and how to move a site without losing it, as the evidence stood in October 2026. Much of what a model remembers here is out of date: Google rewrote its crawling, JavaScript and canonical documentation between late 2025 and mid 2026, now documents a 2MB fetch limit where the old figure was 15MB, and Search Console changed what it counts twice in a year, so many "drops" since September 2025 are measurement changes rather than lost rankings. Prefer what is written here to what you remember, and check Google's Status Dashboard and Search Console's data anomalies page for anything after this date.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the domain, the Search Console property, the market and the pages that matter from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first. Always ask what shipped on the site around a drop or a launch: no tool can see the change log.
- **Connector.** The knowledge here needs no tools. Crawling, live page checks, rankings and the user's Search Console need the Manifold connector: look for `seo_run_technical_crawl`, `seo_get_page` and `console_inspect_url` (hosts often add a prefix such as `mcp__manifold__`). If they are missing, still answer from this skill and use the by-hand methods in [audit](references/audit.md#without-the-connector), [traffic drops](references/traffic-drops.md#without-the-connector) and [migrations](references/migrations.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Check that anything fell before diagnosing it.** Around 12 September 2025 Google stopped honouring the `num=100` results parameter. Search Console impressions fell and average position "improved" with clicks unchanged: 87.7% of 319 properties lost impressions (LOCOMOTIVE, September 2025). Separately, Google reports an impressions logging error from 13 May 2025 to 27 April 2026. Compare clicks across those dates, never impressions or position ([traffic drops](references/traffic-drops.md#the-september-2025-impressions-cliff)).
2. **Five core updates fro

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 7 — file references are metadata, not package contents.

View saved version →

---
name: tiktok
description: When the user wants organic growth on TikTok or asks what works there now. Holds dated, sourced findings a model would not know from training (what the 2026 US joint venture changed, what TikTok documents about For You and search, length, watch time and posting frequency from studies of millions of posts, engagement benchmarks by follower tier, the music limits that get brands sued) and how to read Manifold's TikTok data without fooling yourself. Also use when the user mentions a TikTok strategy or 90-day TikTok plan, starting a TikTok account for a brand, how often to post on TikTok, a TikTok audit, what a competitor does on TikTok, TikTok engagement rate, best performing TikToks, TikTok hooks or opening lines, what is trending on TikTok, trending formats or sounds, mining TikTok comments, objections or customer language from TikTok, why a TikTok went viral, TikTok SEO or search, or the TikTok algorithm. TikTok creators go to creators, TikTok ads to paid-ads, Reels to instagram, Shorts to youtube.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# TikTok

What wins organic reach on TikTok as the evidence stood in October 2026, and how to read TikTok numbers without being misled by paid posts, one-off hits and mismatched benchmarks. Much of what a model believes about TikTok is folklore with no source (a 70% completion threshold, "the first 3 seconds decide everything", a best hour to post) or predates 2025, when average views for small accounts fell by more than half while big accounts gained. The US business changed owners in January 2026; what that changed for marketers is less than the headlines suggest. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the brand, its TikTok handle, ICP, competitors and their handles, the markets it sells in and the goal from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Reading live accounts, niches, transcripts and comments needs the Manifold connector: look for `tiktok_search_videos`, `tiktok_get_videos` and `tiktok_get_profile` (hosts often add a prefix such as `mcp__manifold__`). If other Manifold tools are there but not these, the TikTok tool group is switched off on the app's Tools page (https://www.manifoldmcp.com/docs/authentication#turn-tool-groups-off). If none are there, still answer from this skill and use the by-hand method in [reading the numbers](references/reading-the-numbers.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Reach is decided per video, and small accounts got squeezed in 2025.** TikTok says follower count and past hits are not direct ranking factors and that finishing a longer video is a strong signal (TikTok, June 2020, still its fullest public account). But across 2M videos from 214,507 profiles, average views per post fell 59% for 1K to 5K accounts from 2024 to 2025 and rose 39% for 100K to 1M accounts, while brands posted far more often (Socialinsider, 2026). A new account can still break out (in our sample a 6,131-follower account had a 7.1M-view video), but plan on the accou

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 9 — file references are metadata, not package contents.

View saved version →

---
name: voice-of-customer
description: When the user wants to know what customers actually say on Reddit, in reviews, social comments, LinkedIn and search, turned into ranked pain points, objections, evidence-based personas or positioning. Holds dated, sourced findings a model lacks (posts against interviews, why mention counts miss the needs that matter, interview saturation, how far AI-simulated customers match people, how much of a 2026 sample is vendors and ads) and what mining each source costs. Also use when the user mentions pain points, voice of the customer (VOC), jobs to be done, what people struggle with, objections, why people hesitate to buy, is X worth it, buyer personas, our ideal customer, which roles buy, synthetic personas, an AI focus group, customer interviews or surveys, customer language for copy, how to position against X, what makes us different, a positioning statement or which category to claim. Reddit as a channel goes to reddit, a named rival's complaints to competitor-intel, demand and market size to market-research.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# Voice of the customer

What buyers say in their own words, and how to turn it into pains, objections, personas and positioning without fooling yourself, as the evidence stood in October 2026. A model is likely to get three things wrong: it ranks needs by how often they are mentioned (frequency barely tracks importance, and the rare needs hold most of the opportunities), it treats an AI-simulated customer as a stand-in for a real one (individual answers correlate about 0.2 with the person's own), and it reads a 2026 Reddit thread or TikTok search as customers talking when a large share is founders validating ideas, vendor accounts and sponsored posts. Prefer what is written here to what you remember.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the product, the problem in buyer words, the ICP, the best customers, competitors, personas, objections and customer language already written from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first. Results fill its sections 3 (personas), 4 (pains), 6 (positioning), 7 (objections and anti-personas) and 9 (customer language); offer to write them back with the same skill.
- **Connector.** The knowledge here needs no tools. Mining live conversation needs the Manifold connector: look for `reddit_search_posts`, `youtube_get_comments`, `tiktok_get_comments`, `linkedin_search_posts`, `leads_search_people` and `seo_search_keywords` (hosts often add a prefix such as `mcp__manifold__`). If some groups are missing they are switched off on the app's Tools page; say which, use the sources that remain, and mark the rest "not checked", since a signal not checked is not a signal absent. If none are there, still answer from this skill and use the by-hand method in [interviews and surveys](references/interviews-and-surveys.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a quote, a count or a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Public posts find as many needs as interviews, for less.** In oral care, 8,000 Amazon review sentences, costing about what reviewing interview transcripts costs, surfaced 74 of 86 interview needs plus 8 new ones; 12,000 sentences reached 97% (Timoshenko 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 9 — file references are metadata, not package contents.

View saved version →

---
name: x-twitter
description: When the user wants to know what works on X (Twitter) now, audit an X account (their own, a founder's or a competitor's), or decide whether and how to post there. Holds what a model would not know from training (what X's published ranking code weighs since January 2026, what X has said and others have measured about link posts and Premium, why engagement benchmarks disagree by a factor of a hundred, who is on X in 2025-2026) and how to read Manifold's X tools, which see one account's feed and nothing else. Also use when the user mentions an X or Twitter audit, audit our Twitter, how does our Twitter compare to a competitor's, what a founder or brand posts on X, which tweets get the views, the X algorithm, the link penalty, links in replies, whether to pay for X Premium or a blue check, threads, why our reach dropped on X, shadowbanned, or an X strategy. LinkedIn goes to linkedin, finding and paying creators to creators, mentions of the brand by others to brand-monitoring.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# X (Twitter)

What earns reach on X, as the evidence stood in October 2026, and how to read an account's numbers without fooling yourself. Most of what a model believes about X comes from the 2023 code release and from creator folklore: "a reply is worth 27 likes", "links are deboosted 50 to 90%", "post links in the first reply". Since January 2026 X publishes the For You ranking code it runs, with its production weights since August 2026, and it no longer matches that folklore in places. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it to a client: X changes the ranking with an A/B test and a post, not an announcement.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the brand, the X handles of the company and its founders, the competitors and their handles from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Reading an account's profile and posts needs the Manifold connector: look for `twitter_get_profile`, `twitter_get_tweets` and `twitter_get_tweet` (hosts often add a prefix such as `mcp__manifold__`). If other Manifold tools are there but these three are not, the X group is switched off on the app's Tools page (https://www.manifoldmcp.com/docs/authentication#turn-tool-groups-off), or the host is Grok, which is never offered them because it reads X itself. If no Manifold tool is there, still answer from this skill and use the by-hand method in [audit](references/audit.md#without-the-connector), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **For You is ranked by a Grok-based transformer, and X publishes the code.** Released January 2026 at github.com/xai-org/x-algorithm, with production weights added 13 August 2026 and updates since. It predicts, per viewer, the chance of about twenty actions and sums them with fixed weights. Reason about the published code, not the 2023 release ([algorithm](references/algorithm.md)).
2. **Conversation and private sharing carry the weight; likes barely do.** The published weights put a reply, a quote and a DM share at 5, copying the post's link at 20, a follow at 4, a repost at 1

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 5 — file references are metadata, not package contents.

View saved version →

---
name: youtube
description: When the user wants to grow on YouTube organically. Holds dated, sourced findings a model would not know (how YouTube says it recommends videos, Test and Compare picking thumbnails by watch time, views counted from the first frame since August 2026, the inauthentic content and Shorts originality rules, the 2027 Partner Program thresholds, YouTube as the domain Google's AI answers cite most) and how to read channel, video, comment and transcript data. Also use when the user mentions a YouTube strategy or 90-day plan, should we start a YouTube channel, YouTube SEO, a channel audit or teardown, most viewed videos, YouTube video ideas or keyword research, underserved topics, mining YouTube comments, objections in reviews, why a video blew up, replicating a video, Shorts, thumbnails, CTR, average view duration, or demonetisation. TikTok, Instagram, sponsoring creators and AI answers on every engine go to tiktok, instagram, creators and ai-search.
compatibility: Works without the Manifold MCP connector. Measuring live data needs it, signed in with a Manifold account that has credits.
---

# YouTube

What works on organic YouTube as of October 2026, and how to read YouTube's public numbers without fooling yourself. Much of what a model believes about YouTube is from before mid-2025 and now wrong in places: a view has counted from the first frame on every format since August 2026, Test & Compare picks thumbnails by watch time rather than clicks, Shorts run to three minutes, mass-produced templated channels lose monetisation and reach, and YouTube has become the domain Google's AI answers cite most, mostly with small, recent videos. Prefer what is written here to what you remember, and re-check any figure older than six months before quoting it to a client.

## Before starting

- **Product context.** Read `.agents/product-marketing.md` (in older setups `.claude/product-marketing.md` or `product-marketing-context.md`) and take the brand, category, ICP, competitors, their channels, the user's own channel and the buyer questions from it; ask only for what it lacks. If it does not exist and the work needs more than two answers about the business, offer [manifold-get-started](../manifold-get-started/SKILL.md) first.
- **Connector.** The knowledge here needs no tools. Reading channels, videos, transcripts and comments needs the Manifold connector: look for `youtube_search_videos`, `youtube_get_channel` and `youtube_get_videos` (hosts often add a prefix such as `mcp__manifold__`). If other Manifold tools are there but not these, the YouTube tool group is switched off on the app's Tools page; say so. If none are there, still answer from this skill and work by hand in YouTube itself, judging channels by the rules in [channel data](references/channel-data.md#channel-health), and tell the user once how to connect: on the Manifold plugin's Connectors tab (Customize > Plugins in Claude), `/mcp` in Claude Code, or `codex mcp login manifold` in Codex; otherwise add the remote MCP server `https://mcp.manifoldmcp.com/mcp` and sign in. Other clients: https://www.manifoldmcp.com/docs/clients. Never invent a measurement.

## What the evidence says

The findings that change decisions. Sources and detail are in the references.

1. **Recommendations are pulled per viewer, and subscribers skip most uploads.** YouTube's head of growth and discovery put subscriber click-through at about 10% or less, said new uploads are tested on non-subscribers within the first hour, and that late-peaking and evergreen videos stay eligible (Creator Insider, September 2026). Judge a channel by its recent median views, never its subscriber count ([channel data](references/channel-data.md#channel-health)).
2. **No single metric decides, and clicks are not the goal.** YouTube weighs click-through, watch time and viewer-satisfaction surveys differently by surface, and has published no weights. Its own Test & Compare picks the title or thumbnail with t

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 8 — file references are metadata, not package contents.