Choose which sources and channels to improve first

You see citations from publishers, review sites, videos, communities, and your own website. Which source deserves your team's attention first?

Your outcome: a source or asset to work on, a specific reason it matters, and an action your team can realistically take.

Begin with a customer need

Start from a relevant opportunity or question group in Prompt Universe, then inspect Citations and the source ecosystem intelligence available for that scope. You can also begin with citation evidence from a focused investigation.

Choose the business question first: "Which information supports recommendations for our integration use case?" is more actionable than "Which domains are cited most?"

If you only have a broad citation list, narrow it to the need, market, and AI systems relevant to your task before selecting a source.

1. Read the source pattern SpyderBot identifies

Review the ecosystem summary and any relevant source-gap opportunity. Look at ownership, channel, platform, and content type. Use the AI-by-source view where available to see whether a pattern is broad or concentrated in one system.

Pattern	Useful question
Owned information appears but does not address the requirement clearly	Which page should explain the capability better?
Relevant third-party comparisons omit or misdescribe the brand	Is the information inaccurate, incomplete, or simply outside that publisher's coverage?
Videos or communities recur for the selected need	Which creator, thread, or content format answers that need?
Source evidence is sparse	What additional observation is needed before allocating a channel budget?

Citation frequency is an observed pattern, not proof of source authority, user demand, or causal influence over recommendations. Use it to identify where to inspect, not to assign a universal trust score.

If your website is not cited: check whether relevant answers contain citations at all and whether the observed source scope is complete enough to inspect. An uncited answer, a missing citation field, and a cited answer that excludes your site are different situations. None alone proves your website was inaccessible. Use the response and source evidence to decide whether there is a specific gap to investigate.

2. Inspect a specific source item

Open the publisher, creator, community, or page behind the pattern. A large platform domain alone is not a useful outreach target: one relevant video or discussion may matter more to the task than the platform's overall citation count.

Inspect the available content understanding and brand portrayal. Check the content-access status, then verify the actual passage when accessible. Determine what information the source supplies: a capability explanation, comparison criteria, first-hand experience, technical instructions, or a disputed claim.

Keep the distinction clear: the source's portrayal is what the inspected material says; the AI answer's portrayal is what the model produced. They may differ.

3. Choose a feasible action

What you verified	Action	Who can do it
An owned page is incomplete or outdated	Improve that page with approved facts and evidence	Content or product marketing
Correct owned information is difficult to retrieve	Investigate the page with the relevant audit	Website owner or engineering
An external source contains a specific factual error	Prepare a correction request with the exact claim and supporting source	Communications or partner owner
A relevant reviewer lacks product information	Provide current documentation or legitimate evaluation access	Product marketing or partnerships
A community asks a recurring question you can answer accurately	Prepare a useful contribution under that community's rules, with appropriate disclosure	A knowledgeable representative
The source is relevant but no useful intervention is available	Monitor or defer	The person reviewing the opportunity

You control owned content. A publisher controls its editorial choices. A well-prepared request does not guarantee a change, a citation, or a recommendation.

4. Pick the first item without building another score

Use SpyderBot's opportunity and reason as the starting point. Among suitable items, favor one tied to an important customer need, supported by inspectable evidence, and addressable by your team. Keep an external dependency visible when the outcome depends on another organization.

Illustrative example. A software brand sees integration comparisons citing its outdated help page and a third-party review. Inspection confirms that both describe an older export workflow. The team updates the owned page first because it can verify and publish the correct instructions. It then prepares a factual correction request to the reviewer, using that page as support.

It defers a broad video sponsorship idea because the available evidence does not yet identify which audience question or content item the campaign would address.

5. Record the result you expect to verify

Need: the customer question this source supports.
Source item: page, video, review, or discussion reference.
Evidence: what the inspected content and observed answer show.
Action: the specific update, contribution, request, or investigation.
Control: owned change or external dependency.
Owner and checkpoint: who follows through and what to inspect next.

After a change, verify the asset itself. Later, inspect comparable answer and citation evidence. If citations do not change, assess whether the task still achieved its factual or user-information objective before making another investment.

You are done when you can explain why the selected source matters, what your team can change, and how you will check it. "No feasible source action yet" is useful when paired with a specific missing fact or review trigger.