> For the complete documentation index, see [llms.txt](https://marketingiz.gitbook.io/marketingiz-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://marketingiz.gitbook.io/marketingiz-docs/marketingiz.md).

# Marketingiz

Aria Hayes is a dedicated digital marketing professional at [Marketingiz](https://www.marketingiz.com/), specializing in search engine optimization (SEO), content marketing, and backlink development. With a strong understanding of modern digital strategies, she works closely with businesses to improve their online visibility and help them achieve sustainable growth in competitive digital markets. Aria focuses on creating high-quality content and effective link-building strategies that strengthen website authority and improve search engine rankings.At Marketingiz, Aria contributes to developing innovative marketing campaigns designed to attract targeted audiences and increase brand awareness. Her work involves researching industry trends, optimizing website content, and implementing SEO best practices that help businesses reach their full online potential. She believes that successful digital marketing is built on valuable content, ethical SEO practices, and strong audience engagement.


---

# 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://marketingiz.gitbook.io/marketingiz-docs/marketingiz.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.
