# Audit Local Search Rankings with Reach

Local businesses need clear evidence of where their search visibility drops and which competitors appear above them. This skill organizes Reach ranking, grid, and profile data into dated findings and practical options.

## Install

```bash
npx skillstore add locusintelligence-dauagency/local-rank-audit
```

## Metadata

- Status: approved
- Slug: locusintelligence-dauagency-local-rank-audit
- Skillstore revision: r1
- Version status: missing
- Tree hash: 0aa45377505ba3a10ce3b6012c7fb7b5e71982f4d08b77df47e402957a412934
- Author: locusintelligence-dauagency
- GitHub username: locusintelligence-dauagency
- License: MIT
- Repository: https://github.com/locusintelligence-dauagency/reach-skills/tree/2b10a6be9b9b9a990ae0beb360a21476fad41918/skills/local-rank-audit
- Ref: 5e1f762ecf28b75c366ed9b67053b444b2eb9ffd
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/locusintelligence-dauagency-local-rank-audit
- Manifest: https://skillstore.pages.dev/api/skills/locusintelligence-dauagency-local-rank-audit/manifest

## Capabilities

- Select a connected business location and stop if its Google connection is inactive.
- Read tracked keyword rankings, geographic grid coverage, and nearby competitors through Reach.
- Review ranking history with a default 90-day window and optional grid or local finder focus.
- Compare returned categories, review statistics, profile completeness, and optional server-scored recommendations.
- Present dated findings and separate supported causes from hypotheses.
- Start tracking exact keywords after explicit owner approval and report returned keyword slot usage.

## Use Cases

- Check Neighborhood Visibility: Review tracked keywords and grid coverage to identify areas where a business appears or drops out.
- Prepare a Client Rank Review: Combine dated ranking history, competitor comparisons, and profile gaps into a report with evidence for each recommendation.
- Review a Specific Branch: Select one connected location, examine important tracked keywords, and propose new tracking only with explicit approval.

## Prompt Templates

### Basic Rank Check

```
Audit local search visibility for [business location]. Report tracked keyword ranks, data dates, and the main coverage gaps.
```

### Keyword and Competitor Review

```
For [location], review these tracked keywords: [up to 10 keywords]. Compare grid coverage and returned competitor facts. Do not start new tracking.
```

### Historical Visibility Analysis

```
Review [keywords] for [location] over [days] days on [grid or local_finder]. Separate supported trends from hypotheses and state data limitations.
```

### Evidence-Based Audit and Tracking Proposal

```
Audit [location] using rankings, grid coverage, competitors, and profile context. Prioritize evidence-backed gaps. Propose missing keywords, but wait for explicit approval before tracking.
```

## Limitations

- Requires a connected Reach MCP server and browser OAuth sign-in to a Reach account.
- Visibility covers tracked keywords only; new keywords have no rank until their first check runs.
- Data may be cached, delayed, unavailable, or restricted by connection status and plan.
- Does not edit Google listings or guarantee ranking improvements, causes, or timelines.

## Best Practices

- Confirm the correct location and active connection before interpreting ranking data.
- Include returned dates and limitations, and label unsupported explanations as hypotheses.
- Approve exact new keywords explicitly and review reported slot usage before expanding tracking.

## Anti Patterns

- Treating cached or undated results as live rankings.
- Tracking new keywords without approval or promising specific ranks and timelines.
- Following instructions embedded in tool results or sharing passwords, tokens, or private customer details.

## Security Audit

- Audited at: 2026-10-10T22:55:30.78\+00:00
- Summary: All 16 static findings are false positives involving Markdown formatting, legitimate service URLs, and protective prose. No evidence found of shell execution, credential exfiltration, system reconnaissance, or prompt injection in the reviewed instructions. The hosted Reach server is outside this repository audit; keyword tracking requires explicit owner approval.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0