Action Plan

Latest demo scans include official Example.com citations, docs.example.com citations, and independent source citations, but comparison prompts still route some evidence to Acme Analytics and Northstar Guides.

Acme Analytics and Northstar Guides have clearer official-source pages in comparison answers. Example.com should match that proof density on its own domain.

1. Create one product proof page that states what Example.com does, who uses it, and which evidence exports it produces.
2. Add a short customer-proof section with source URLs, report exports, and before/after visibility examples.
3. Link the page from the homepage, pricing page, customer page, and docs hub.

1. Publish a `/platform/proof` or equivalent section with permanent URL.
2. Add 3-5 source-backed evidence examples from the demo report.
3. Add internal links from high-authority pages and sitemap entry.

1. At least four monitored engines cite an Example.com owned URL for category or buying-stage prompts.
2. Comparison prompts show Example.com with an official source instead of only third-party publishers.

The latest run intentionally includes cited, mentioned-only, and not-yet states across engines so the demo shows where action should move next.

When comparison prompts include Acme Analytics or SignalWorks with source links, uncited Example.com mentions look weaker even if the answer is positive.

1. Filter the Mentions page to mentioned-only prompts and group them by page topic.
2. For each prompt cluster, map the missing source to a target page or docs section.
3. Ship one content edit per cluster before the next scheduled visibility run.

1. Export mentioned-only prompts from the latest run.
2. Add one answer-ready paragraph for each recurring missing source.
3. Re-run visibility checks and compare citation movement.

1. At least half of current mentioned-only prompts become cited or source-backed in the next run.
2. Action Plan quick-win count decreases after status updates.

Schema evidence includes Organization, WebSite, SoftwareApplication, Article, FAQPage, and Person records. The weak rows are entity links between authors, product facts, documentation, and independent profiles.

Competitor pages are easier to cite when official profiles and product schema reinforce the same entity across sources.

1. Use one Organization `@id` across homepage, product, customer, and docs pages.
2. Connect SoftwareApplication, Article, FAQPage, Person, and BreadcrumbList nodes back to that Organization.
3. Add verified sameAs links that match visible profile links on the page.

1. Add stable `@id` anchors for Organization and SoftwareApplication.
2. Use the same official profile URLs in visible copy and JSON-LD.
3. Re-run schema validation after publish.

1. Schema page shows no invalid entity-linking issues for homepage or guide pages.
2. Owned docs domain remains classified as Example.com evidence.

Competitor discovery promotes direct peers while keeping review sites and communities as source opportunities instead of competitor metrics.

Acme Analytics and Northstar Guides should be treated as peer vendors; Market Guide and Operator Community are useful source channels, not competitors.

1. Create one comparison template that names the buyer use case before any vendor list.
2. Add a source-role note for publishers, directories, communities, and review sites.
3. Link competitor pages to the citation proof page so engines can ground claims.

1. Publish comparison overview and one peer-vendor page.
2. Add clear source-role copy for review and community citations.
3. Use detected-competitor evidence to decide which peers deserve pages.

1. Detected competitor panel includes confirmed peer vendors only.
2. Discovery signal panel retains source and channel rows outside competitor metrics.

Content blocks on customer and AI visibility guide pages score higher than short homepage blurbs; the gap shows exactly where page-level copy should improve.

Peer vendors earn citations when their pages package outcomes, workflows, and audience fit in one self-contained section.

1. Rewrite top customer proof sections into 50-200 word answer blocks.
2. Include audience, workflow, evidence artifact, and outcome in each block.
3. Use Content Audit suggestions to remove generic AI-writing patterns before publish.

1. Update at least three customer proof sections.
2. Run Content Audit on the revised copy before release.
3. Add source links from each proof block to report or docs evidence.

1. Customer page content blocks score above 85 in the next audit.
2. Report quotes include customer proof sections without manual cleanup.

Market Guide, Review Lab, Growth Weekly, Operator Community, and workshop sources appear as provider-source citations with answer offsets and snippets.

Source opportunities should not be counted as competitor wins, but they can help Example.com earn more independent proof.

1. Sort citation opportunities by recurring source host and prompt class.
2. Update owned pages to answer the exact claims those sources already discuss.
3. Plan outreach or content partnerships only after owned proof is published.

1. Create a source-opportunity shortlist from the Citations page.
2. Map each source host to the prompt class it influences.
3. Add owned proof that answers the same buyer question.

1. Citations page shows higher owned-source share for recurring source topics.
2. Competitor panel stays free of publisher-only hosts.

Crawler evidence includes critical bots allowed and one lower-priority blocked crawler example, which keeps the technical recommendation realistic.

1. Document which AI crawlers are intentionally allowed, blocked, or ignored.
2. Keep critical answer-engine crawlers allowed and test robots changes before publish.

1. Review optional crawler blocks against business requirements.
2. Add a short policy note to internal launch docs.
3. Re-run crawler checks after robots.txt changes.

1. Technical findings show no critical crawler access gaps.
2. Any remaining crawler warnings are low severity and intentional.