Add AI Search Lead use case - #10
Merged
Merged
Conversation
Contributor
|
Merged and live: https://grokbot.dev/use-cases/ai-search-lead/ — verified devtune.ai and the MCP endpoint (properly OAuth-protected), scored the entry (71), and shipped the DevTune integration alongside it (with its integration hub page: https://grokbot.dev/integrations/devtune/). The no-publish-without-approval and no-modeled-guesses rules in your prompt are exactly the discipline we like to see. Thanks for the submission! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Marketing use case for AI Search Lead (
content/use-cases/ai-search-lead.md).Reads engine answers, citations, crawls, 404 demand, Search Console, and GA4 through a connected DevTune project, then drafts the next evidence-ranked page for review. Status is
proposed.The listing tags
integrations: [DevTune]. DevTune is not in the controlled vocabulary yet; maintainer issue: #11