Skip to main content
Not everyone who monitors Scrunch has the permissions — or the bandwidth — to publish content themselves. This workflow closes that gap: pull the visibility data, have Claude draft a fully-contextualized task, and create it in your team’s project management tool so the right person can pick it up.
Tools used in this workflowChoose your project management tool in the tabs below.

Replace the bracketed values, then paste the whole thing into Claude.
What you get: A Linear issue with the full gap context already written — topic, missing prompts, competitor situation, and a clear brief for whoever picks it up.

Tips

After Step 1, ask: “Repeat this for the next 2 lowest-performing tags.” You’ll get 3 gap summaries. Then create a ticket for each using the same tab — one conversation, three tasks created and assigned.
Add this line to the ticket description: “Scrunch tag: [tag name] — filter to this tag in the dashboard for the full data.” Whoever picks up the task can open Scrunch directly to the relevant data without running the analysis again.
If Scrunch shows you’re present sometimes but inconsistently (presence rate 10–40%), you likely need to update an existing page rather than create something new. Add this to Step 1: “Does [brand name] have any presence in this tag at all, or is it zero? If partial, what’s the presence rate?” Zero presence usually means missing content; partial presence usually means weak content.
Once the content is published, add the URL to the ticket and check Scrunch in 30 days. Use the Track Whether It Worked step from the Create Content for AI Citations workflow to close the loop.

Create Content That Gets AI Citations

The workflow for whoever picks up the ticket — pull the brief from Scrunch, generate the content, publish through your CMS.

Find Visibility Gaps Worth Fixing

Run a deeper gap analysis first and save it to Notion or Google Docs before creating tasks.