gbp-audit
Skill0 starsChanged 35 days agoMITView on GitHub
Audit Google Business Profile (GMB) accuracy, categories, services, hours and local SEO opportunities for a specific business or branch. Produce an evidence-backed checklist and owner-approved edit drafts.
In this repository8 other files it gives its agents.
- citation-auditSkill
- local-competitor-analysisSkill
- local-keyword-researchSkill
- local-seo-reportSkill
- location-page-seoSkill
- maps-rank-trackingSkill
- review-insightsSkill
- vibelocalSkill
The file
Files
Google Business Profile audit
Read WORKFLOW.md. Reuse the user's branch context; ask for a public Maps URL or identity only if missing. Prefer supplied public details and owner exports before collection. Use places for a small approved public profile sample when needed, and verify the exact branch by place ID/URL and public address. A same-name listing is a candidate until confirmed.
Build a table: field, owner-confirmed fact, observed public value, source/date, status, proposed correction. Check real business name, primary/secondary category fit, public contact details, website landing page, regular/special hours, actual services, service areas and available public attributes. Mark unobserved fields unknown. Public data cannot establish ownership, verification, suspensions, account permissions, bookings or private profile performance.
Prioritize inaccurate customer-facing facts first, then service/category relevance and useful content. Use qualitative priority with a concrete reason; do not fabricate a numerical ranking score or factor weights. Draft a concise business description from supplied facts, service suggestions, useful photo subjects and a posts outline. Unsupported business claims remain questions for the owner.
Respect Google's business representation guidelines: use the real-world name; no keyword-stuffed rebrand, fake office, invented location, duplicate branch profile or fabricated hours. Keep a service-area business's hidden home address private. Do not prescribe review incentives or review gating; follow Google review guidance.
Deliver a short profile finding table and up to five prioritized actions, with owner, approval needed, source and verification step. Offer the smallest relevant next route: Maps baseline, review themes, citation conflicts or branch-page audit. Editing/publishing is a separate approved action; this skill has no Google account write capability.
This route is for a profile audit. A request solely to measure positions goes to maps-rank-tracking; a generic technical website audit should not silently become a Google profile audit.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

