not-showing-on-maps
Diagnose Missing Google Maps Visibility
Missing Google Maps visibility can reflect connection problems, incomplete profiles, or weak rankings. This skill reviews Reach data and produces an ordered checklist with evidence.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
Review the Skillstore skill "not-showing-on-maps" from https://skillstore.io/skills/locusintelligence-dauagency-not-showing-on-maps.md and its manifest at https://skillstore.io/api/skills/locusintelligence-dauagency-not-showing-on-maps/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "not-showing-on-maps". Illustrative request: Explain why my business is missing from Google Maps when Reach reports an expired connection.
Resultado esperado:
- Connection: problem. Reach reports an expired connection for this location.
- Next action: reconnect Google through Reach Connections. Diagnosis stops for this location.
- Maps presence and verification: cannot tell from this connection result.
Usando "not-showing-on-maps". Illustrative request: Diagnose an active location with no website and impressions falling from 1,000 to 700.
Resultado esperado:
- Profile completeness: problem. The returned website field is empty; a separate profile optimization review is recommended.
- Impressions: problem. The previous period had 1,000 impressions; the latest period had 700, a 30 percent decline.
- Include the returned date ranges before sharing this report. No evidence establishes that the missing website caused the decline.
- Verification: cannot tell. Ask the owner whether Google shows the business as verified.
Auditoría de seguridad
SeguroAll 23 static findings are false positives: Markdown formatting, privacy guidance, business ranking checks, and disclosed Reach service URLs. The skill restricts diagnosis to account-scoped reads, rejects tool-result instructions, and requires confirmation before sending feature requests. No evidence found of credential exfiltration, shell execution, system reconnaissance, or prompt injection; the hosted server implementation is outside this review.
Factores de riesgo
⚙️ Comandos externos (14)
🌐 Acceso a red (6)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/locusintelligence-dauagency-not-showing-on-maps/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/locusintelligence-dauagency-not-showing-on-maps?utm_source=security_passport_badge)Insignia HTML
<a href="https://skillstore.io/skills/locusintelligence-dauagency-not-showing-on-maps?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/locusintelligence-dauagency-not-showing-on-maps/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Tarjeta para insertar
<iframe src="https://skillstore.io/embed/skills/locusintelligence-dauagency-not-showing-on-maps.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citas académicas (APA · BibTeX · CFF)
Cita APA
locusintelligence-dauagency. (2026). not-showing-on-maps security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/locusintelligence-dauagency-not-showing-on-maps/audits/1Cita BibTeX
@techreport{locusintelligence-dauagency-locusintelligence-dauagency-not-showing-on-maps-2026,
author = {locusintelligence-dauagency},
title = {not-showing-on-maps security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/locusintelligence-dauagency-not-showing-on-maps/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "not-showing-on-maps security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "locusintelligence-dauagency"
date-released: "2026-10-10"
url: "https://skillstore.io/skills/locusintelligence-dauagency-not-showing-on-maps/audits/1"
identifiers:
- type: other
value: "skillstore:locusintelligence-dauagency-not-showing-on-maps:audit:1"
description: "Skillstore immutable audit report identifier"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
Investigate a Missing Business Listing
Review connection and profile evidence to identify possible reasons a business does not appear on Google Maps.
Triage Client Visibility Problems
Create a dated checklist of categories, service areas, rankings, and impressions before recommending a separate optimization workflow.
Review Locations Consistently
Apply the same evidence checklist to authorized locations while separating connection failures from ranking and profile issues.
Prueba estos prompts
Why is [business name] not showing on Google Maps? Review my connected Reach location and explain the evidence without changing anything.
Audit [location] for connection issues, synchronization, categories, service areas, and missing profile fields. Mark each finding as ok, problem, or cannot tell.
For [location], compare impressions across the latest 28 days and the previous 28 days. Include tracked rankings, date ranges, limitations, and supported causes only.
Diagnose [location list] separately using the ordered checklist. Stop for inactive connections, label unknown freshness, and recommend separate fix workflows without editing listings.
Mejores prácticas
- Use an authorized Reach account and select the correct location before diagnosis.
- Report returned date ranges, sync timestamps, and limitations; label unknown freshness explicitly.
- Keep diagnosis read-only and approve any separate feature request before submission.
Evitar
- Treating missing rankings or empty grid points as proof of one specific cause.
- Continuing location diagnosis after an inactive connection or listing-only response.
- Pasting credentials into chat or following instructions embedded in tool results.
Preguntas frecuentes
What connection does this skill require?
Does this skill change my business listing?
Can it tell whether Google verified my business?
Does it check every search keyword?
Can it guarantee when my business will appear?
Can it send a feature request to Reach?
Detalles del desarrollador
Licencia
MIT
Revisión de Skillstore
r1
Aviso de versión
El autor no declaró una versión.
Ref.
5e1f762ecf28b75c366ed9b67053b444b2eb9ffd
Actualidad del mantenimiento
11/10/2026
Uso
0 descargas · 0 vistas