Grok Bot SEO prompts that stop before live titles
Search Console packs, crawls, and SERP briefs on the Bot computer. Distinct from marketing campaigns and from content drafts. The teammate does not push to the CMS or change live titles. You still publish.
In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Search Console and rankings
5 promptsWeekly Search Console query pack
1/21✨ What it does
The Bot pulls queries, pages, and clicks from [GSC PROPERTY] for [DATE RANGE], groups movers, and writes a one-page pack with source screenshots. You still publish any title or page change that pack recommends.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Pull queries, pages, clicks, and impressions from [GSC PROPERTY] for [DATE RANGE]. Group winners, losers, and new queries. Screenshot the source tables. Sources: [GSC PROPERTY], [ANALYTICS IF ANY], last week's pack in [FOLDER] if it exists. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not invent search volume, keyword difficulty, or ranking numbers. If you cannot see a number, say unknown. - Do not request indexing or change GSC settings. Deliverable: One-page pack: movers, suspected cause, recommended next step, screenshot paths. Review point: I decide what to publish.
Pro tip: Name the property and the date range. "This week in SEO" is how you get a vibe memo with no links.
Ranking drop diagnosis for one URL
2/21✨ What it does
The Bot opens Search Console and the live SERP for [URL], lists what moved in [WINDOW], and writes a cause pack with screenshots. You still publish the fix; the Bot does not change the live title.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Diagnose the ranking change for [URL] over [WINDOW]. Compare Search Console, the live SERP for [KEYWORD], and the live page. Separate confirmed, guessed, and unknown. Sources: [GSC PROPERTY], live Google SERP, the live page in the cloud browser. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not invent search volume, keyword difficulty, or ranking numbers. If you cannot see a number, say unknown. Deliverable: What moved, evidence, likely cause, recommended fix, screenshot paths. Review point: I publish the fix.
Pro tip: One URL per job. A sitewide "why did we drop" brief invents a single story.
Query cannibalization map
3/21✨ What it does
The Bot maps which URLs on [PROPERTY] compete for the same [QUERY CLUSTER] in Search Console and names a keep, merge, or redirect plan. You still publish the merge or redirect; the Bot does not change live URLs.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find URLs on [PROPERTY] that rank for the same queries in [QUERY CLUSTER]. Recommend keep, merge, or redirect with the GSC evidence. Sources: [GSC PROPERTY], the live URLs in the cloud browser. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not invent search volume, keyword difficulty, or ranking numbers. If you cannot see a number, say unknown. - Do not create or delete redirects. Deliverable: Query, competing URLs, clicks each, recommendation, evidence links. Review point: I publish the merge or redirect.
Pro tip: Ask for the query and the URLs that share it. Do not invent a cluster from a blog tag.
Position 4 to 20 harvest list
4/21✨ What it does
The Bot lists queries on [GSC PROPERTY] sitting in positions 4 to 20 with enough impressions, plus a one-line brief per URL. You still publish the title or snippet change that list suggests.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List queries on [GSC PROPERTY] in positions 4 to 20 over [DATE RANGE] with at least [MIN IMPRESSIONS]. Add a one-line brief per URL. Do not invent volume. Sources: [GSC PROPERTY] only for the numbers. Live pages if you need to see the current title. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not invent search volume, keyword difficulty, or ranking numbers. If you cannot see a number, say unknown. Deliverable: Query, URL, position, impressions, clicks, one-line brief. Review point: I pick which titles to publish.
Pro tip: Set a minimum impression floor or the list is every query that once saw position 12.
Low CTR titles that still rank
5/21✨ What it does
The Bot finds pages on [PROPERTY] with solid impressions and a weak CTR versus the position, and drafts title and meta candidates. You still publish the live title; the Bot does not write it into the CMS.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find URLs on [PROPERTY] in [DATE RANGE] with impressions above [FLOOR] and CTR below peers at the same position. Draft title and meta candidates. Do not change live titles. Sources: [GSC PROPERTY], live titles in the cloud browser, [BRAND SUFFIX]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not invent search volume, keyword difficulty, or ranking numbers. If you cannot see a number, say unknown. Deliverable: URL, current title, position, CTR, 3 title options, 2 meta options, character counts. Review point: I publish the title I want.
Pro tip: Compare CTR to pages in a similar position, not to a made-up "good CTR".
Technical crawls
4 promptsCrawl 4xx, 5xx, and index blockers
6/21✨ What it does
The Bot crawls [SITE] in the cloud browser from [START URL], staying on [DOMAIN], and lists 4xx, 5xx, noindex, and blocked pages with screenshots. You still publish the fix on the live site.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Crawl [SITE] starting at [START URL]. Stay on [DOMAIN]. Report 4xx, 5xx, noindex, robots blocks, and redirect chains. Screenshot the failure. Sources: The live site in the cloud browser. [SITEMAP URL] if you have it. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not submit the site to an auditor as me. Do not leave [DOMAIN]. Deliverable: URL, status, blocker, screenshot path, suggested fix. Review point: I publish the fix.
Pro tip: Stay on the domain. A wander onto third-party pixels is not a crawl.
Index coverage versus sitemap
7/21✨ What it does
The Bot compares [SITEMAP URL] to Search Console coverage for [PROPERTY] and lists missing, excluded, or unexpected URLs. You still publish sitemap and robots changes; the Bot does not submit the site as you.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare [SITEMAP URL] to coverage in [PROPERTY]. List in sitemap but not indexed, indexed but not in sitemap, and excluded with the GSC reason. Sources: [SITEMAP URL], [GSC PROPERTY] coverage. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not request indexing, remove URLs, or change robots.txt. Deliverable: Three lists with reasons and links. Unknown if a source will not load. Review point: I publish sitemap or robots changes.
Pro tip: Open both sources. A sitemap-only list misses what Google already excluded.
Canonical, robots, and hreflang check
8/21✨ What it does
The Bot opens [URL LIST], reads canonical, robots, and hreflang from view-source, and flags conflicts with screenshots. You still publish the tag fix; the Bot does not edit the live head.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: For each URL in [URL LIST], read canonical, robots, and hreflang. Flag conflicts, self-canonical misses, and hreflang pairs that do not resolve. Sources: Those URLs in the cloud browser. [LOCALE MAP] if you have one. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not edit the live head or CMS. Deliverable: URL, tag, expected, actual, screenshot, suggested fix. Review point: I publish the tag fix.
Pro tip: View-source or the rendered head. A screenshot of the visible page misses the tags.
Core Web Vitals pack for a URL list
9/21✨ What it does
The Bot opens [CWV OR PSI TOOL] for each URL in [LIST], records LCP, INP, and CLS, and writes a short cause note per fail. You still publish the performance fix on the live page.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Run [CWV OR PSI TOOL] on each URL in [LIST]. Record LCP, INP, and CLS. Write a short cause note for each fail. Do not invent scores. Sources: [CWV OR PSI TOOL] in the cloud browser, the live URLs. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not invent search volume, keyword difficulty, or ranking numbers. If you cannot see a number, say unknown. - Do not change hosting, CDN, or production performance settings. Deliverable: URL, LCP, INP, CLS, pass/fail, cause note, tool link. Review point: I publish the performance fix.
Pro tip: Record the tool URL under every number. A "slow page" note with no lab or field cite is useless.
SERP briefs, not live pages
4 promptsSERP capture and ranking brief
10/21✨ What it does
The Bot opens the live Google SERP for [KEYWORD], notes who ranks and why, and writes a brief we could win without inventing volume. You still publish the page; the Bot does not create it in the CMS.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Capture the current SERP for [KEYWORD]. Note who ranks, intent, and gaps versus [EXISTING PAGE IF ANY]. Write a brief. Do not create a CMS draft. Sources: Live Google SERP in the cloud browser, [EXISTING PAGE IF ANY], [POSITIONING]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not invent search volume, keyword difficulty, or ranking numbers. If you cannot see a number, say unknown. Deliverable: Who ranks, intent, gaps, outline, internal links only to URLs you can open. Review point: I decide if we write it, then I publish.
Pro tip: Cite live titles you can see. Do not invent keyword difficulty.
Refresh brief for a decaying URL
11/21✨ What it does
The Bot compares [URL] to today's SERP for [KEYWORD], plus the Search Console trend, and writes a keep, change, or cut brief. You still publish the refresh; the Bot does not edit the live page.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a refresh brief for [URL] versus today's SERP for [KEYWORD], using the Search Console trend in [WINDOW]. Keep, change, or cut. Do not edit live. Sources: The live page, the SERP, [GSC PROPERTY] for that URL. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not invent search volume, keyword difficulty, or ranking numbers. If you cannot see a number, say unknown. Deliverable: Keep / change / cut, GSC trend, draft intro and FAQs that stay off the live page. Review point: I publish the refresh.
Pro tip: Ask for a diff. A full rewrite brief is how you kill links you already earned.
Title and meta candidates, not live
12/21✨ What it does
The Bot drafts title and meta options for [URL] against [KEYWORD] and the current SERP, each with a character count. You still publish the live title; the Bot does not paste it into the CMS.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft 5 title and 5 meta options for [URL] targeting [KEYWORD]. Count characters. Do not change the live title or meta. Sources: The live page, the SERP, [GSC PROPERTY] CTR for that URL if visible, [BRAND SUFFIX]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not invent search volume, keyword difficulty, or ranking numbers. If you cannot see a number, say unknown. Deliverable: Current title, options with character counts, which SERP titles they answer. Review point: I publish the title I want.
Pro tip: Keep the title under 60 characters. The Bot proposes. You save.
Featured snippet and PAA brief
13/21✨ What it does
The Bot captures the featured snippet and People Also Ask box for [QUERY], then writes an answer block and FAQ draft that stay off the live page. You still publish the block if you want it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Capture the featured snippet and PAA for [QUERY]. Write an answer block and FAQ draft that match the format. Leave them off the live page. Sources: Live SERP in the cloud browser, [URL] if we already rank nearby. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not invent search volume, keyword difficulty, or ranking numbers. If you cannot see a number, say unknown. Deliverable: Screenshot paths, current snippet format, draft block, draft FAQs. Review point: I publish the block if I want it.
Pro tip: Screenshot the box. Paraphrase without a picture is how you miss the format Google is rewarding.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
Links, redirects, and index
4 promptsInternal links from GSC queries
14/21✨ What it does
The Bot reads queries that already hit [URL] in [GSC PROPERTY] and suggests anchors only to URLs it can open on [SITE]. You still publish those links; the Bot does not edit the live page.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: From queries that already hit [URL] in [GSC PROPERTY], suggest internal links only to URLs you can open on [SITE]. Mark 200 or 404. Sources: [GSC PROPERTY] for that URL, [SITE] in the cloud browser. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not add links to live pages. Do not invent target URLs. Deliverable: Anchor, target, 200/404, why it helps the query. Review point: I publish the 200s.
Pro tip: If you are not sure the target exists, mark unknown. Dead suggestions are worse than no suggestions.
Redirect map for a URL change
15/21✨ What it does
The Bot builds a from/to redirect map for [OLD URLS] using Search Console clicks and live status codes, and flags chains. You still publish the redirects; the Bot does not change the server.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a from/to redirect map for [OLD URLS] using clicks in [GSC PROPERTY] and live status codes. Flag chains and loops. Do not change the server. Sources: [OLD URLS], [GSC PROPERTY], live status in the cloud browser, [NEW IA DOC]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not edit .htaccess, DNS, or hosting redirects. Deliverable: From, to, clicks, current status, chain warning, unknowns. Review point: I publish the redirects.
Pro tip: Clicks from GSC tell you what is worth mapping. A 1:1 guess from a crawl misses the URLs people still find.
Orphan, thin, and duplicate report
16/21✨ What it does
The Bot crawls [SECTION] on [SITE], lists orphans, near-duplicates, and thin URLs, and names a keep or cut plan with evidence. You still publish the cut or merge; the Bot does not delete pages.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Crawl [SECTION] on [SITE]. List orphans (no inbound internal link you can find), near-duplicates, and thin URLs. Recommend keep, merge, or cut. Sources: [SITE] in the cloud browser, [SITEMAP URL], [GSC PROPERTY] clicks for those URLs. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not delete, noindex, or unpublish pages. Deliverable: URL, issue, evidence, recommendation, GSC clicks if visible. Review point: I publish the cut or merge.
Pro tip: Evidence is a screenshot or a word count you measured. "Looks thin" is not a cut plan.
Schema and rich-result QA
17/21✨ What it does
The Bot opens [URLS] in a rich-result or schema tester, screenshots errors, and drafts a JSON-LD note that stays off the live page. You still publish the markup; the Bot does not inject it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Test [URLS] in [SCHEMA OR RICH RESULT TESTER]. Screenshot errors. Draft JSON-LD notes that stay off the live page. Do not invent properties. Sources: Those URLs, [SCHEMA OR RICH RESULT TESTER] in the cloud browser. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not inject JSON-LD or edit the live head. Deliverable: URL, tester result, error, draft markup path, what still needs a human. Review point: I publish the markup.
Pro tip: Paste the tester URL under every error. A "add FAQ schema" note with no test is a guess.
Standing SEO Bots
4 promptsSEO Bot description
18/21✨ What it does
The Bot writes a description named [NAME] that names [GSC PROPERTY], the crawl domain, never-push-to-CMS, and never-change-live-titles. You still publish that text into the Bot you create.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write an SEO Bot description named [NAME]. Include [GSC PROPERTY], crawl domain [DOMAIN], pack format, never-push-to-CMS, and never-change-live-titles. Sources: [GSC PROPERTY], [DOMAIN], [FOLDER FOR PACKS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not create, rename, or delete Bots. Deliverable: Name, description, pack format, never-do list. Review point: I create the Bot and paste the text.
Pro tip: Write the property and the domain in the description. A generic "SEO Bot" will wander into the CMS.
Monday Search Console routine
19/21✨ What it does
The Bot writes a weekday job that pulls [GSC PROPERTY] since last Monday, posts the mover pack here, and stops if Search Console is missing. You still publish any title change the pack suggests.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a Monday routine that pulls [GSC PROPERTY] since last Monday, posts the mover pack here, and stops if Search Console will not load. Do not change live titles. Sources: [GSC PROPERTY]. Stop if the property is missing. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not invent search volume, keyword difficulty, or ranking numbers. If you cannot see a number, say unknown. - Do not enable the routine. I turn it on after a test week. Deliverable: Routine card: trigger, sources, pack format, stop rule. Review point: I enable it after a test Monday.
Pro tip: If GSC is missing, the routine says so. Do not invent last week's clicks.
What SEO Bots never do
20/21✨ What it does
The Bot writes a never-do list for SEO Bots from your rules, such as [NO LIVE TITLES, NO CMS PUSH, NO FAKE VOLUME, NO DISAVOW], plus the human substitute. You still publish that list into every SEO Bot.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write the never-do list for SEO Bots on this computer from my rules: [EXAMPLE: NO LIVE TITLES, NO CMS PUSH, NO FAKE VOLUME, NO DISAVOW]. Sources: My rules. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not file a disavow, request indexing, or change GSC settings. Deliverable: 12 never-do items with the human substitute for each. Review point: I paste it into every SEO Bot.
Pro tip: Paste this before you teach Search Console. Helpful Bots save a title at 2am.
Ranking crash alert, no live edits
21/21✨ What it does
The Bot writes a watch that fires when [URL OR QUERY] drops more than [N] positions in Search Console and posts a sourced note here. You still publish the recovery change; the Bot does not edit live titles.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a watch for [URL OR QUERY] that fires when position drops more than [N] in [GSC PROPERTY] over [WINDOW]. Post a sourced note here. Do not edit live titles. Sources: [GSC PROPERTY], live SERP for that query. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not push to the CMS, change live titles or meta, or edit published pages. - Do not invent search volume, keyword difficulty, or ranking numbers. If you cannot see a number, say unknown. - Do not enable the watch until I say so. Deliverable: Watch card: trigger, sources, note format, stop if GSC is missing. Review point: I enable it after a test.
Pro tip: Cap how often it fires. A 0.1 position twitch is not a crash.
Free tool
SEO Meta Generator
Generate a title tag, meta description, and slug options.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides