Earn accurate third-party presence
Improve accurate third-party coverage across reviews, communities, partners, media, video, and expert resources.
Improve accurate presence on the review sites, editorial pages, communities, and directories your buyers use and your audit observed in answers.
You will have a source map and a 90-day plan to improve the third-party evidence surrounding the brand.
Your website can describe the product, while third-party sources also shape buyer research and sometimes appear in answer citations. Source work means earning accurate presence where buyers already learn, then measuring outcomes without assuming a source caused them.
IF YOU SKIP IT / If important third-party profiles and buyer resources are inaccurate or omit you, buyers may form an incomplete shortlist. The audit tells you where to investigate, not which source caused an answer.
Observed citations do not prove source authority
Prioritize recurrent sources for investigation, then verify buyer relevance, accuracy, coverage, freshness, and repeatability. Do not label a source trusted or causal from citation frequency alone.
- Owned source
- Third-party surfaces you control the content of: your G2 profile, directory listings, marketplace pages.
- Earned source
- Surfaces someone else controls: listicles, press, community threads. You influence them with value, not edits.
- Entity consistency
- Material facts agree across surfaces while wording adapts to each audience and platform. This prevents contradictions; it does not prove a ranking or citation effect.
- Astroturfing
- Fake grassroots activity: sockpuppet accounts, undisclosed shills, bought reviews. The one mistake in this course you cannot undo.
Each phase feeds the next. Don't skip ahead, the artifact at the end is only trustworthy if every phase ran.
- 01Harvest
Collect every cited domain and URL across priority prompts and engines.
- 02Classify
Label owned, review, media, community, partner, directory, academic, or public data.
- 03Score
Measure prompt overlap, citation frequency, trust, relevance, feasibility, and current brand state.
- 04Audit entity
Compare category, audience, features, pricing, leadership, and evidence across priority profiles.
- 05Plan value
Offer data, expertise, customer proof, integration material, or a useful tool rather than a generic pitch.
- 06Earn
Work through customer, partner, PR, community, and expert channels with disclosure.
- 07Measure
Track source wins, corrected facts, citation share, referral quality, and answer changes.
- ✓You now have
Third-party source plan
Map the source ecosystem
Start with sources observed in answers and sources buyers use for the category.
You already hold the target list and paid for it in Module 06: the citation export. Those URLs are receipts, proof of which pages engines actually lean on, which beats any guess about which sites 'seem authoritative'.
Rank them by how often they were cited, how relevant they are, and how realistic they are to earn. Expect the ranking to insult your instincts. A consultant's roundup with modest traffic, cited in five Tier 1 answers, outranks the famous publication engines never quote. In this game influence is measured in citations, and domain authority is a rumor from a different sport.
“The top options for agency reporting are…”
These shares describe this sample only. Inspect and retest before assigning influence.- 01
Export cited domains from the audit and top-ranking domains from commercial queries.
- 02
Group them into reviews, communities, editorial, partners, video, data, marketplaces, and associations.
- 03
Score recurrence in your sample, buyer relevance, attainability, accuracy, and current brand presence; verify before calling any source influential.
- Start from the sources tab you built in Module 06.3; it is already ranked by citation recurrence. Add columns: relevance, attainability, current presence, accuracy.
- Score the top 20 and cut the list to ten targets. Each target gets an owner and a next action in the same row.
- Revisit the ranking after every monthly baseline re-run, because the engines' source diet shifts.
Every source on the map has a documented origin, and the top ten combine recurrence, buyer relevance, coverage, accuracy, freshness, attainability, and confidence.
- PRO TIP
Include the boring directories and integration marketplaces. They carry entity weight far beyond their traffic.
- WATCH OUT
Do not sort by domain authority alone. Combine observed citation recurrence with buyer relevance, coverage, accuracy, freshness, attainability, and confidence.
OPTIONAL / AI CO-PILOTRun this lesson with AI, the prompt, sources and expected output+
Choose the business priority, interpret exceptions, protect confidential data, challenge weak evidence, and approve the final decision.
Clean, classify, compare, calculate, and draft rows from supplied evidence. AI may surface patterns; it does not own strategy.
Citation tracker, plus source context from Ahrefs / Semrush.
| Prompt | Engine | Cited domain | Cited URL | Source class | Frequency | Captured |
|---|---|---|---|---|---|---|
| Best agency reporting tool | Perplexity | g2.com | /categories/agency-reporting | Review | 9 | Yes |
CLAUDE / CHATGPT PROMPTAnalyze the evidence without outsourcing the decision+
Remove personal or confidential data. Attach the named exports, explain every column, and tell the model when the dataset was collected.
You are assisting a human B2B SaaS SEO and AEO operator with Module 08: Earn accurate third-party presence. Current lesson: Map the source ecosystem Objective: Start with sources observed in answers and sources buyers use for the category. Required artifact: Third-party source plan BUSINESS CONTEXT I WILL PROVIDE - Product, category, target market, pricing model, sales motion, and geography - The priority customer segment and the commercial outcome for this 90-day cycle - Source overlap export exported from Citation tracker - Source context exported from Ahrefs / Semrush - Definitions for any internal fields, stages, scores, and abbreviations TASK 1. Export cited domains from the audit and top-ranking domains from commercial queries. 2. Group them into reviews, communities, editorial, partners, video, data, marketplaces, and associations. 3. Score recurrence in your sample, buyer relevance, attainability, accuracy, and current brand presence; verify before calling any source influential. REQUIRED OUTPUT Return a table using these exact columns: Prompt | Engine | Cited domain | Cited URL | Source class | Frequency | Captured. For every recommendation, cite the source row, URL, call note, or data point that supports it. Add a confidence column in your analysis: High, Medium, or Low. List missing evidence separately instead of guessing. Finish with a section named HUMAN DECISIONS REQUIRED. RULES - Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts. - Do not treat correlation as causation. - Preserve contradictory evidence and explain why it conflicts. - Do not make the final priority or publishing decision. Prepare the evidence for a human owner. - Use this example only as a format reference, not as evidence: A niche consultant roundup cited across five Tier 1 runs is a candidate to inspect, not proof that it controls the category.
Influential sources are ranked using audit evidence. A named human owner must verify this before the lesson is complete.
A niche consultant roundup cited across five Tier 1 runs is a candidate to inspect, not proof that it controls the category.
Fix owned third-party profiles
Basic inconsistency creates avoidable ambiguity.
Before pitching a single stranger, fix the mentions you already control. Your G2 profile, the Capterra listing, a dozen partner directories: most were written years ago and now describe a product you no longer sell at a price you no longer charge. Every one of them is a vote on what you are, and right now your own votes disagree with each other.
This is the cheapest win in the entire course. No outreach, no waiting, no budget. Just an afternoon making every surface you own say the same category, the same audience, the same facts as your site. Consensus starts with the votes you already hold.
- 01
Audit category, description, logo, URL, features, integrations, pricing state, and company facts.
- 02
Align language to real positioning while respecting each platform’s format.
- 03
Set a quarterly review owner for marketplaces, partner directories, and review profiles.
- List every profile you control: G2, Capterra, TrustRadius, partner directories, integration marketplaces, LinkedIn, Crunchbase. Most vendors have 10-15 they forgot.
- Audit each against the battlecard-in-progress: category sentence, audience, pricing state, integration list, logo, screenshots. Log every mismatch.
- Fix them through each platform's vendor portal (G2 and Capterra both have seller consoles), and put a quarterly review with a named owner in the calendar.
Every owned profile matches your category sentence and current facts, and each one has a named owner and a quarterly review date.
- PRO TIP
This is the cheapest win in the entire course: no outreach, no waiting, just making surfaces you already own agree with each other.
- WATCH OUT
Pricing fields go stale quickly and outdated numbers can propagate into buyer research and generated answers. If a platform cannot represent your current model, link to the canonical pricing page instead of leaving an old number.
OPTIONAL / AI CO-PILOTRun this lesson with AI, the prompt, sources and expected output+
Choose the business priority, interpret exceptions, protect confidential data, challenge weak evidence, and approve the final decision.
Clean, classify, compare, calculate, and draft rows from supplied evidence. AI may surface patterns; it does not own strategy.
Ahrefs / Semrush, plus corrected listings from Review / partner portals.
| Source | Prompt overlap | Citation frequency | Buyer trust | Feasibility | Current state | Priority |
|---|---|---|---|---|---|---|
| G2 category | 18 / 24 | High | High | Medium | Weak profile | P1 |
CLAUDE / CHATGPT PROMPTAnalyze the evidence without outsourcing the decision+
Remove personal or confidential data. Attach the named exports, explain every column, and tell the model when the dataset was collected.
You are assisting a human B2B SaaS SEO and AEO operator with Module 08: Earn accurate third-party presence. Current lesson: Fix owned third-party profiles Objective: Basic inconsistency creates avoidable ambiguity. Required artifact: Third-party source plan BUSINESS CONTEXT I WILL PROVIDE - Product, category, target market, pricing model, sales motion, and geography - The priority customer segment and the commercial outcome for this 90-day cycle - Source context exported from Ahrefs / Semrush - Corrected listings exported from Review / partner portals - Definitions for any internal fields, stages, scores, and abbreviations TASK 1. Audit category, description, logo, URL, features, integrations, pricing state, and company facts. 2. Align language to real positioning while respecting each platform’s format. 3. Set a quarterly review owner for marketplaces, partner directories, and review profiles. REQUIRED OUTPUT Return a table using these exact columns: Source | Prompt overlap | Citation frequency | Buyer trust | Feasibility | Current state | Priority. For every recommendation, cite the source row, URL, call note, or data point that supports it. Add a confidence column in your analysis: High, Medium, or Low. List missing evidence separately instead of guessing. Finish with a section named HUMAN DECISIONS REQUIRED. RULES - Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts. - Do not treat correlation as causation. - Preserve contradictory evidence and explain why it conflicts. - Do not make the final priority or publishing decision. Prepare the evidence for a human owner. - Use this example only as a format reference, not as evidence: The site says “revenue intelligence” while profiles say “CRM analytics”; choose and substantiate the category relationship.
Third-party profiles are accurate and consistent. A named human owner must verify this before the lesson is complete.
The site says “revenue intelligence” while profiles say “CRM analytics”; choose and substantiate the category relationship.
Create an earnable reason to mention
Outreach without value produces weak placements.
Editors can smell 'please mention us' from the subject line, and they delete it on scent alone. The only pitch that survives is one where their readers gain something: original benchmark data, a tested comparison, a working template, with a method note attached.
So package the asset first, then match it to the source. Two other conversions worth knowing: pitching an update to a list you are already on ('your 2024 entry cites our old pricing, here is the current table') converts far better than pitching inclusion. And pitching the actual author by name beats the site's contact form roughly every time.
- 01
Package original data, a useful tool, expert commentary, a tested comparison, or a customer workflow.
- 02
Match the asset to a source that serves the same audience.
- 03
Pitch the source’s reader problem; disclose relationships and avoid control over editorial conclusions.
- Package one asset per quarter: an original benchmark, a tested comparison dataset, or a working template, with a short methodology note.
- Find the actual author of each target listicle (byline, LinkedIn) rather than the site's contact form, and pitch the reader's problem in two short paragraphs.
- For existing listicles you are already in: pitch corrections and fresh data ('your list cites our 2024 pricing; here is the current table'). Update pitches convert far better than inclusion pitches.
Every outreach target is paired with a specific asset its audience would want even if you did not exist, and every pitch names the reader's problem first.
- PRO TIP
The pitch that works reads like help, not marketing: 'your readers ask X; we measured it across 200 accounts; here is the data either way it comes out.'
- WATCH OUT
Paid placement without disclosure poisons the source and, increasingly, models can smell the pattern. If money changes hands, the page must say so.
OPTIONAL / AI CO-PILOTRun this lesson with AI, the prompt, sources and expected output+
Choose the business priority, interpret exceptions, protect confidential data, challenge weak evidence, and approve the final decision.
Clean, classify, compare, calculate, and draft rows from supplied evidence. AI may surface patterns; it does not own strategy.
Review / partner portals, plus source quality overlay from CRM / referral analytics.
| Source | Category | Audience | Pricing | Capabilities | Conflict | Correction owner |
|---|---|---|---|---|---|---|
| Partner directory | Analytics | Agencies | Old | Missing automation | Yes | Partnerships |
CLAUDE / CHATGPT PROMPTAnalyze the evidence without outsourcing the decision+
Remove personal or confidential data. Attach the named exports, explain every column, and tell the model when the dataset was collected.
You are assisting a human B2B SaaS SEO and AEO operator with Module 08: Earn accurate third-party presence. Current lesson: Create an earnable reason to mention Objective: Outreach without value produces weak placements. Required artifact: Third-party source plan BUSINESS CONTEXT I WILL PROVIDE - Product, category, target market, pricing model, sales motion, and geography - The priority customer segment and the commercial outcome for this 90-day cycle - Corrected listings exported from Review / partner portals - Source quality overlay exported from CRM / referral analytics - Definitions for any internal fields, stages, scores, and abbreviations TASK 1. Package original data, a useful tool, expert commentary, a tested comparison, or a customer workflow. 2. Match the asset to a source that serves the same audience. 3. Pitch the source’s reader problem; disclose relationships and avoid control over editorial conclusions. REQUIRED OUTPUT Return a table using these exact columns: Source | Category | Audience | Pricing | Capabilities | Conflict | Correction owner. For every recommendation, cite the source row, URL, call note, or data point that supports it. Add a confidence column in your analysis: High, Medium, or Low. List missing evidence separately instead of guessing. Finish with a section named HUMAN DECISIONS REQUIRED. RULES - Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts. - Do not treat correlation as causation. - Preserve contradictory evidence and explain why it conflicts. - Do not make the final priority or publishing decision. Prepare the evidence for a human owner. - Use this example only as a format reference, not as evidence: Offer anonymized agency reporting benchmarks and a methodology note to an operations newsletter.
Every outreach target has genuine audience value. A named human owner must verify this before the lesson is complete.
Offer anonymized agency reporting benchmarks and a methodology note to an operations newsletter.
Build review and community systems
Authentic customer and practitioner language compounds.
Reviews and community presence compound like savings: slow, boring, and unstoppable if you leave them alone. There is also a way to blow the account overnight. One exposed sockpuppet, one batch of scripted reviews, and a source that models weigh heavily is poisoned against you specifically, with no appeal process.
The honest mechanics are simple. Ask for reviews at moments of demonstrated value, with no script for what to say. Answer community questions completely, under a real name, with your affiliation visible. That is the whole trick, and it is the one part of this course where a shortcut is not slower. It is fatal.
- 01
Request reviews at moments of demonstrated value, without scripting sentiment or gating unhappy users.
- 02
Answer community questions with complete help and disclose affiliation when relevant.
- 03
Track accuracy, freshness, and useful discussion; never use fake accounts or paid undisclosed advocacy.
- Wire the review ask into a value milestone (first report shipped, onboarding completed) with a direct link to the review form. Email or in-app, one sentence, no script for what to say.
- Community: subscribe to the three places your buyers actually ask questions (subreddits, Slack groups, forums). Answer one question per week completely, under a real name, with affiliation in the profile.
- Keep a log of community answers so you can see which threads later show up as citations.
Review requests fire on value milestones with no sentiment steering, community accounts are real names with disclosed affiliation, and everyone touching this work knows the red lines.
- PRO TIP
Ask reviewers to describe their use case in their own words because it helps future buyers judge fit. Do not promise that a specific review format will be quoted.
- WATCH OUT
Never draft the review, never gate the unhappy, never reply to criticism with a fake account. One exposed sockpuppet poisons the source permanently, against you specifically.
OPTIONAL / AI CO-PILOTRun this lesson with AI, the prompt, sources and expected output+
Choose the business priority, interpret exceptions, protect confidential data, challenge weak evidence, and approve the final decision.
Clean, classify, compare, calculate, and draft rows from supplied evidence. AI may surface patterns; it does not own strategy.
CRM / referral analytics, plus source overlap export from Citation tracker.
| Source | Value offered | Proof available | Relationship path | Pitch owner | Status | Outcome |
|---|---|---|---|---|---|---|
| MarTech guide | Benchmark dataset | Method + sample | Editor introduction | PR lead | Drafting | Pending |
CLAUDE / CHATGPT PROMPTAnalyze the evidence without outsourcing the decision+
Remove personal or confidential data. Attach the named exports, explain every column, and tell the model when the dataset was collected.
You are assisting a human B2B SaaS SEO and AEO operator with Module 08: Earn accurate third-party presence. Current lesson: Build review and community systems Objective: Authentic customer and practitioner language compounds. Required artifact: Third-party source plan BUSINESS CONTEXT I WILL PROVIDE - Product, category, target market, pricing model, sales motion, and geography - The priority customer segment and the commercial outcome for this 90-day cycle - Source quality overlay exported from CRM / referral analytics - Source overlap export exported from Citation tracker - Definitions for any internal fields, stages, scores, and abbreviations TASK 1. Request reviews at moments of demonstrated value, without scripting sentiment or gating unhappy users. 2. Answer community questions with complete help and disclose affiliation when relevant. 3. Track accuracy, freshness, and useful discussion; never use fake accounts or paid undisclosed advocacy. REQUIRED OUTPUT Return a table using these exact columns: Source | Value offered | Proof available | Relationship path | Pitch owner | Status | Outcome. For every recommendation, cite the source row, URL, call note, or data point that supports it. Add a confidence column in your analysis: High, Medium, or Low. List missing evidence separately instead of guessing. Finish with a section named HUMAN DECISIONS REQUIRED. RULES - Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts. - Do not treat correlation as causation. - Preserve contradictory evidence and explain why it conflicts. - Do not make the final priority or publishing decision. Prepare the evidence for a human owner. - Use this example only as a format reference, not as evidence: After a successful implementation milestone, invite the customer to describe the original problem, setup, and measurable outcome in their own words.
Review/community work has clear ethical rules. A named human owner must verify this before the lesson is complete.
After a successful implementation milestone, invite the customer to describe the original problem, setup, and measurable outcome in their own words.
Build the battlecard and reframe objections
One reference document that every writer, partner, and outreach pitch pulls from, so the same positioning and the same objection answers appear everywhere AI reads.
When AI repeats something negative about you, the instinct is to publish a denial. Watch what a denial does: 'we do not have a steep learning curve' contains the words 'steep learning curve' with your name attached, and now the model has seen the pairing twice. You just campaigned for the objection.
Reframe instead. Say the true, specific thing that makes the objection obsolete: 'most teams ship their first client report in under an hour', with evidence linked. Then put the reframe everywhere at once, from one shared battlecard, so the FAQ writer, the partner directory, and the founder answering a Reddit thread all say the same sentence. Consistency across surfaces is what a model reads as consensus. Keep the battlecard to one page; at three pages it becomes a document nobody opens.
“[Product] has a steep learning curve and limited integrations.”
“We do not have a steep learning curve, and our integrations are not limited.”
The model now sees your name next to “steep learning curve” twice.“Most teams ship their first client report in under an hour. [Product] connects natively to the 12 ad and analytics sources agencies use most.”
Evidence: onboarding data, Q2 2026; integrations page with field map.- 01
Assemble the battlecard: the identity sentence, the top ten attributes with suggested phrasing in buyer language, the entity facts, and one approved reframe for every objection from Module 06.
- 02
Reframe, do not deny: replace "we do not have a steep learning curve" with the positive, specific version ("most teams ship their first client report in under an hour"), with evidence attached.
- 03
Distribute each reframe across at least three surfaces (a product or FAQ page, a review response or community answer, and a partner or listicle description), then retest the sentiment prompts in 30 days.
- Create one shared doc titled Battlecard: identity sentence, top ten attributes with approved phrasing, entity facts, and a reframe table (objection, what AI says, approved reframe, evidence link).
- Write responses that are true, specific, sourced, and candid about limitations. Test each by asking whether it remains accurate when shared alone.
- Announce it in the channel where content gets written, link it from the brief template, and put a quarterly review on the PMM owner's calendar.
Every objection from Module 06 has one approved reframe with evidence, each reframe is live on at least three surfaces, and nobody on the team is writing positioning from memory.
- PRO TIP
Keep it to one page. A three-page battlecard is a document; a one-page battlecard is a habit.
- WATCH OUT
A reframe without an evidence link is spin, and spin gets paraphrased right back into the objection.
OPTIONAL / AI CO-PILOTRun this lesson with AI, the prompt, sources and expected output+
Choose the business priority, interpret exceptions, protect confidential data, challenge weak evidence, and approve the final decision.
Clean, classify, compare, calculate, and draft rows from supplied evidence. AI may surface patterns; it does not own strategy.
Citation tracker, plus source context from Ahrefs / Semrush.
| Objection or attribute | AI currently says | Approved reframe | Evidence | Surfaces placed | Owner | Sentiment retest |
|---|---|---|---|---|---|---|
| Limited integrations | "Fewer integrations than rivals" | Native to the 12 sources agencies use most | Integrations page + field map | Product page, G2, 2 directories | PMM | 2026-09-30 |
CLAUDE / CHATGPT PROMPTAnalyze the evidence without outsourcing the decision+
Remove personal or confidential data. Attach the named exports, explain every column, and tell the model when the dataset was collected.
You are assisting a human B2B SaaS SEO and AEO operator with Module 08: Earn accurate third-party presence.
Current lesson: Build the battlecard and reframe objections
Objective: One reference document that every writer, partner, and outreach pitch pulls from, so the same positioning and the same objection answers appear everywhere AI reads.
Required artifact: Third-party source plan
BUSINESS CONTEXT I WILL PROVIDE
- Product, category, target market, pricing model, sales motion, and geography
- The priority customer segment and the commercial outcome for this 90-day cycle
- Source overlap export exported from Citation tracker
- Source context exported from Ahrefs / Semrush
- Definitions for any internal fields, stages, scores, and abbreviations
TASK
1. Assemble the battlecard: the identity sentence, the top ten attributes with suggested phrasing in buyer language, the entity facts, and one approved reframe for every objection from Module 06.
2. Reframe, do not deny: replace "we do not have a steep learning curve" with the positive, specific version ("most teams ship their first client report in under an hour"), with evidence attached.
3. Distribute each reframe across at least three surfaces (a product or FAQ page, a review response or community answer, and a partner or listicle description), then retest the sentiment prompts in 30 days.
REQUIRED OUTPUT
Return a table using these exact columns: Objection or attribute | AI currently says | Approved reframe | Evidence | Surfaces placed | Owner | Sentiment retest.
For every recommendation, cite the source row, URL, call note, or data point that supports it.
Add a confidence column in your analysis: High, Medium, or Low.
List missing evidence separately instead of guessing.
Finish with a section named HUMAN DECISIONS REQUIRED.
RULES
- Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts.
- Do not treat correlation as causation.
- Preserve contradictory evidence and explain why it conflicts.
- Do not make the final priority or publishing decision. Prepare the evidence for a human owner.
- Use this example only as a format reference, not as evidence: Objection "limited integrations" becomes "connects natively to the 12 ad and analytics sources agencies use most, with field-level mapping", placed on the integrations page, in the G2 profile, and in two partner directories.Review/community work has clear ethical rules. A named human owner must verify this before the lesson is complete.
Objection "limited integrations" becomes "connects natively to the 12 ad and analytics sources agencies use most, with field-level mapping", placed on the integrations page, in the G2 profile, and in two partner directories.
The workspace shows the source investigation pipeline: observed citations from Module 06, recurrence and relevance scores, the factual consistency audit, and the earning plan. Recurrence prioritizes verification; it does not prove a URL is trusted, authoritative, or causal.
Trusted source network
Prioritize the review sites, communities, partner pages, expert media, datasets, and directories that answer engines actually use.
Citation influence by source class
A source matters when it is repeatedly retrieved for your priority decisions.
Check each item only after the artifact meets the standard. Progress saves on this device; use the academy-home backup to move it elsewhere.