> For the complete documentation index, see [llms.txt](https://guia.fenicio.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guia.fenicio.help/integraciones-y-herramientas/seo-y-visibilidad-organica/google-search-console.md).

# Google Search Console

Google Search Console es una herramienta gratuita que te permite monitorear y optimizar cómo aparece tu tienda en los resultados de búsqueda.

No sirve para hacer publicidad, sino para mejorar tu posicionamiento orgánico (SEO).

***

## **Credenciales necesarias:**

* Cuenta de Google
* Acceso a Google Search Console
* Permisos de Propietario o Usuario completo
* Dominio o propiedad verificada (DNS, HTML, Tag Manager o Analytics)

***

### ¿Por qué es importante?

Usar Search Console te permite:

* Ver qué búsquedas llevan usuarios a tu tienda
* Detectar errores de indexación
* Enviar y validar tu sitemap
* Analizar el rendimiento (clics, impresiones, posiciones)
* Identificar oportunidades de mejora en SEO

***

### ¿Cómo se configura?

Para ver el paso a paso actualizado, podés seguir la documentación oficial de Google:

* Comenzar con Search Console:\
  <https://support.google.com/webmasters/answer/9128668>
* Verificar tu sitio:\
  <https://support.google.com/webmasters/answer/9008080>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guia.fenicio.help/integraciones-y-herramientas/seo-y-visibilidad-organica/google-search-console.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.