Productivity
Index coverage versus sitemap
Index coverage versus sitemap turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
The prompt
Index coverage versus sitemap guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning work, making decisions, or organizing complex information and you want a response that is easier to evaluate and act on.
text prompt
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 {{sitemapUrl}} to coverage in {{property}}. List in sitemap but not indexed, indexed but not in sitemap, and excluded with the GSC reason. Sources: {{sitemapUrl}}, {{gscProperty}} 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.
Tune the prompt, not the plumbing.
Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.
Customized prompt962 characters
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 a specific sitemap url to coverage in a specific property. List in sitemap but not indexed, indexed but not in sitemap, and excluded with the GSC reason. Sources: a specific sitemap url, a specific 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.
Useful structure, room to move.
Index coverage versus sitemap guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning work, making decisions, or organizing complex information and you want a response that is easier to evaluate and act on.
The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.
Related prompts
Canonical, robots, and hreflang check
Canonical, robots, and hreflang check turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
ChatGPTGeminiGrok
Closed-lost without a reason
Closed-lost without a reason turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
ChatGPTClaudeGemini
Commit versus what closed
Commit versus what closed turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
ChatGPTClaudeGemini
Coverage versus quota by segment
Coverage versus quota by segment turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
ChatGPTClaudeGemini