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

# Improving content

Once your first campaign is live, there's 2 main courses of action:

1. add new content for another campaign you've identified) - repeat the steps above: [Checklist](/introduction/checklist.md)
2. improve the existing campaign content - the focus of this article

Here's how you can improve your content with Findable:<br>

1. You'll receive ongoing pSEO reports from Findable to track a summary of the campaign
2. Use these with your existing website/SEO performance review process to identify actions to take
3. For the existing campaign, identify:
   1. the best performing pages (impressions, clicks, rank) and spend time to improve the content to make it more useful to your target audience
   2. additional keywords you want to target that align with the campaign, for example using our combo collection in [Creating a Combo Collection](/create-pseo-pages/collections/creating-a-combo-collection.md), if we target a new Location, add a new record to that collection

Of course, any questions you have with any of this, we are here to help.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.findable.au/campaign-scenarios/improving-content.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.