# Site Structure

Ensuring your site structure makes sense is essential to configuring your pSEO campaign. To give users the best experience and maximise your SEO impact, you should ensure that your pSEO pages fall within a logical hierarchy.

{% hint style="info" %}
You don’t need to design every collection that Findable syncs. Most campaigns will only publish one collection, although all of them are available if you decide to use them.
{% endhint %}

Your site structure will depend on your website, but as a general rule, you should ensure that users can navigate to the pages from your home (even if there are a few steps).

This is the same principle as setting up a blog using your CMS. Your hierarchy will often look something like this:

Home > Blog > Blog articles

Aiming for something like this with your Findable campaign is a good idea. For example, a directory might have:

Home > Directory > Directory pages

For some examples, check out:

* [Free and Paid pSEO Tools on Findable](https://www.findable.au/tools)
* [The Web3 Directory on twodoor marketing](https://www.twodoor.marketing/directory)

To change where your collection sits within your site structure, update the Collection URL. Click on the gear next to the CMS collection to access the settings, then change the URL to anything you’d like.

[You can learn more about Page URLs at Webflow University.](https://university.webflow.com/lesson/page-urls?topics=site-settings)


---

# Agent Instructions: 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:

```
GET https://docs.findable.au/create-pseo-pages/page-design/site-structure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.