> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aeolo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# GEO setup and website integration

> An agent-ready workflow for site audits, GA4, Search Console, indexing preparation and content delivery.

Set up measurement and search discovery, then publish Aeolo articles in your existing website design. The v2 guide takes your coding agent from a site audit through a verified public article.

Use this with a custom site whose code you or your developer can edit, such as Next.js, Astro, or React Router. Your site needs to render article content on the server or at build time.

To serve an Aeolo-rendered site under a path such as `/articles`, use [subfolder connection](/guides/subfolder-connection). This page covers rendering content through your own application.

## Give this to your coding agent

Open your website's project in Codex, Claude Code, Cursor, or another coding agent. Copy this prompt into that project. Your agent will read the implementation guide and ask for the values it needs.

```text theme={null}
Read https://aeolo.io/integrate/content-feed.md and follow the v2 workflow:
1. Check the installed aeo CLI and update it if outdated.
2. Understand the brand and record the GEO/SEO audit baseline.
3. Set up or verify GA4 collection, GSC ownership and Aeolo property selection.
4. Prepare the sitemap and indexing request inventory.
5. Reuse or create the agreed publishing surface.
6. Integrate content and verify the public site, then submit eligible URLs
   within the authorized scope and report the observed results.

Keep existing content, URLs, design and analytics ownership. Ask only for
missing access or decisions. Have me configure AEOLO_KEY privately in the
server environment; never include secrets in prompts, logs or browser code.

Use the shared loader and test pagination, locales, errors and removals.
Report each phase as passed, failed or pending with actual evidence.
Distinguish local implementation, deployment, submission and indexing.
```

The prompt contains no credentials. Configure the feed key in your site's server environment when your agent reaches that step.

## What the v2 guide covers

| Phase | What your agent verifies |
| - | - |
| Tools and brand | Current executable, correct brand, markets and supported claims |
| GEO/SEO baseline | Aeolo site audit, technical blockers, Topics and useful page opportunities |
| GA4 and GSC | Events actually collected, property ownership, and the resources selected in Aeolo |
| Indexing preparation | Real canonical URLs, sitemap, indexability and the appropriate submission method |
| Publishing surface | Host, article paths, channel, navigation and deployment access |
| Code and launch | Server HTML, languages, metadata, refresh, sitemap and public readback |
| Follow-through | Submission receipts, observed indexing and comparable visibility/traffic measurements |

Your agent can continue with local code and fixtures while Google sign-in, DNS access or publication approval is pending. Those pending steps must remain visible in its report. A connected Google account does not install the analytics tag, and an accepted indexing request does not confirm indexing.

## The custom feed connection

<Steps>
  <Step title="Add your site in Aeolo">
    Open [Sites in the dashboard](https://aeolo.io/channels), select your brand, and add your website as a custom site. If it is already listed, open its connection settings.

    Use the address where articles will live, such as `https://yourdomain.com/blog`. Tell your agent if your site uses a different path or language-specific URLs.
  </Step>

  <Step title="Verify ownership and configure the feed key">
    Give your agent the verification tag shown in Aeolo. Have it add the tag to your site's HTML and deploy that change, then return to Aeolo and select **Verify**.

    Save the feed URL and key shown after verification. The key is displayed once. Have your agent configure the integration with that channel's key in a server-only environment variable.
  </Step>

  <Step title="Check a published article on your site">
    Use an article you have published in Aeolo for this site. Ask your agent to check the live article after deployment and the feed cache has refreshed.

    A connected channel confirms ownership. The checks below confirm that your website is actually reading and displaying its articles.
  </Step>
</Steps>

## How to know it is working

* The published article appears in your site's article list with the existing design.
* Its link opens the full article on your own domain, and the body is present in the server's HTML.
* Its canonical URL and sitemap entry point to that same article address.
* If you publish multiple languages, each language opens the corresponding article.
* A later published update appears after the site's configured refresh interval.

If the feed is empty, check that an article is **published** for this channel. Drafts do not appear in the feed. Search engine indexing is a separate step; use your site's visible article and sitemap to verify the connection.

<Card title="Read the v2 GEO and integration guide" icon="file-code" href="https://aeolo.io/integrate/content-feed.md">
  The full execution guide: CLI checks, GEO/SEO audit, GA4, GSC, indexing preparation, publishing surfaces, tested feed loader, framework recipes, and completion evidence.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.