Skip to content

Enhance blog content strategy with AEO/GEO guidelines #5226

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
KristopherLeads wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Enhance blog content strategy with AEO/GEO guidelines #5226

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions nuxt/content/handbook/marketing/content-strategy/blog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -314,6 +314,28 @@ The `<!--more-->` tag is used to define the text shown in the blog index from ea

![Example of how the headers are shown on blogs](/handbook/marketing/images/blog-article.png){.border.border-gray-200.max-w-[600px]}

### AEO/GEO Optimisation

More searches are being handled by agents and AI systems, and as such, content should support this paradigm. Each blog post should have the following.
#### Question-Based Headers
H2 and below should be framed as questions - instead of "The Operational Reality of AI", it should read "What is the Operational Reality of AI in Industry?". AEO/GEO trades heavily on question:answer pairs, so where possible, this pair should be built into the content itself.
Comment on lines +320 to +321

@Yndira-E Yndira-E Jun 17, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@KristopherLeads @sumitshinde-84 does this still stands? considering the comments regarding blog titles? (I know it says H2, but still wanted to check)

@sumitshinde-84 sumitshinde-84 Jun 18, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should add the following line so it does not feel like we are forcing every heading to be question-based:

"The goal is not to force every heading into a question, but to use question-based headings where they reflect genuine user intent and help organize the content more clearly."

#### FAQ Section
Each blog page should have a "faq" section which structures questions and answers for AEO/GEO parsing. This should follow this format:

```
faq:
- question: "Core question about the content?"
answer: "Detailed answer of no more than two sentences."
- question: "Core question about the content?"
answer: "Detailed answer of no more than two sentences."
```
#### tl;dr Section
This section will render as a summary about the page, giving readers and AEO/GEO systems the ability to rapidly summarise and understand the content. It should take this structure:

```
tldr: "This page shows you how to build a blog post and release it for general consumption. It details the steps to take, the rationale for each step, and the practical outcome of each step."
```

@Yndira-E Yndira-E Jun 17, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@KristopherLeads is the how-to structure documented elswhere?

### Rendering Node-RED Flows

The blog uses a flow renderer to make it easier for users to understand what the
Expand Down Expand Up @@ -342,3 +364,5 @@ Feel free to request reviews and merge your blog post when it's ready, even if t
The post, to be published in the future, will be rendered when developing locally and on deployment previews.

By utilizing the scheduling feature, we can maintain a consistent and organized publishing schedule without the need for last-minute adjustments.