Writer Guide to AXO
Writer's Role in AXO
Content writers create the structured, factual, and modular content that LLM agents can easily understand, extract, and reference in their responses to users.
As a content writer, you're on the front lines of Agent Experience Optimization. Your words and structure directly determine whether LLM agents can find, understand, and cite your content. This guide teaches you how to write for both human readers and AI agents.
Writing for LLM Reference
Fact-First Writing Structure
Agents prioritize factual information over narrative buildup. Lead with key facts and data points.:
✅ Good: "React 18 introduced automatic batching, which groups multiple state updates into a single re-render for better performance."
❌ Poor: "In the ever-evolving world of frontend development, React continues to surprise us with amazing features. One such feature that developers are talking about is automatic batching..."
Clear, Declarative Sentences
Write sentences that can stand alone as complete thoughts:
- Complete Context: Each sentence should make sense without surrounding text
- Specific Details: Include relevant numbers, dates, and specifics
- Active Voice: Use active voice for clarity and directness
- Avoid Ambiguity: Eliminate vague terms like "recently," "many," or "often"
Modular Content Structure
Chunking Information
Break content into discrete, referenceable blocks:
Content Chunking Best Practice
Each paragraph should cover one main concept. This allows agents to extract and cite specific information without including irrelevant context.
## Authentication Methods
### API Key Authentication
API keys provide a simple authentication method for server-to-server requests. Include the key in the Authorization header: `Authorization: Bearer your-api-key`.
### OAuth 2.0 Authentication
OAuth 2.0 enables secure user authentication through third-party providers. The flow involves redirecting users to the provider, receiving an authorization code, and exchanging it for an access token.
### JWT Token Authentication
JSON Web Tokens (JWT) contain encoded user information and can be verified without database lookups. Tokens expire after a set time period for security.
Hierarchical Organization
Use heading levels to create clear information hierarchy:
# Main Topic (H1)
## Primary Subtopic (H2)
### Specific Detail (H3)
#### Implementation Note (H4)
Citation-Ready Formatting
Key Takeaways Sections
End articles with clear summary blocks that agents can easily extract:
Key Takeaways Example
- React 18's automatic batching improves performance by reducing re-renders
- Concurrent features allow React to pause and resume work based on priority
- Suspense boundaries enable better loading state management
- The new createRoot API replaces ReactDOM.render for new applications
Fact Blocks for Important Information
Highlight critical facts that deserve special attention:
<FactBlock title="Performance Impact" source="React Team Blog, March 2022" sourceUrl="https://react.dev/blog/2022/03/29/react-v18#new-feature-automatic-batching">
Automatic batching can reduce re-renders by up to 50% in typical React applications, leading to measurable performance improvements.
</FactBlock>
Proper Attribution
Always cite sources for factual claims:
- Primary Sources: Link to original documentation, research, or announcements
- Publication Dates: Include when information was published or last updated
- Author Attribution: Credit original authors and organizations
- Version Specificity: Specify which version of software/tools you're discussing
Content Types That Agents Love
How-To Guides
Structure step-by-step instructions clearly:
## How to Set Up Authentication
### Prerequisites
- Node.js version 16 or higher
- A valid API key from the service provider
### Step 1: Install Dependencies
```bash
npm install express jsonwebtoken
Step 2: Configure Environment Variables
Create a .env
file with your API credentials:
### FAQ Pages
Format questions and answers for easy extraction:
```markdown
## Frequently Asked Questions
### What is the rate limit for API requests?
The API allows 1,000 requests per hour per API key. Rate limits reset at the top of each hour.
### How long do access tokens remain valid?
Access tokens expire after 24 hours. Refresh tokens remain valid for 30 days.
Comparison Tables
Present comparative information in structured formats:
Feature | Basic Plan | Pro Plan | Enterprise |
---|---|---|---|
API Calls/Month | 10,000 | 100,000 | Unlimited |
Rate Limit | 100/hour | 1,000/hour | 10,000/hour |
Support Level | Priority | Dedicated |
Avoiding Agent-Unfriendly Content
Eliminate Fluff and Filler
Remove content that doesn't add informational value:
❌ Poor: "As we dive deep into the fascinating world of web development, it's worth noting that there are many different approaches one might consider..."
✅ Good: "Web development authentication can be implemented using three main approaches: API keys, OAuth 2.0, and JWT tokens."
Reduce Marketing Language
Agents prefer factual descriptions over promotional content:
❌ Poor: "Our revolutionary, game-changing API delivers unparalleled performance that will transform your business!"
✅ Good: "The API processes requests with an average response time of 200ms and supports up to 10,000 concurrent connections."
Avoid Vague References
Be specific about timing, quantities, and sources:
❌ Poor: "Recently, many developers have started using this approach..."
✅ Good: "Since the release of React 18 in March 2022, over 60% of new React projects use the concurrent features according to the State of React 2023 survey."
Content Maintenance for Writers
Regular Content Audits
Review and update content to maintain accuracy:
- Quarterly Reviews: Check facts, links, and relevance every 3 months
- Version Updates: Update content when referenced software/tools release new versions
- Link Maintenance: Ensure all external links remain active and relevant
- Accuracy Verification: Verify that all factual claims remain current
Update Documentation
When updating content, maintain clear change logs:
**Last Updated**: January 15, 2024
**Changes**: Updated API endpoint URLs and added new authentication method
**Next Review**: April 15, 2024
Writing Checklist
Writer's AXO Content Checklist
- Lead with key facts in the first paragraph
- Use clear, declarative sentences that stand alone
- Structure content with proper heading hierarchy
- Include specific details (numbers, dates, versions)
- Add summary blocks for key takeaways
- Cite all factual claims with sources
- Eliminate marketing fluff and vague language
- Format lists and comparisons in structured ways
- Include last updated date and author information
- Test content readability and logical flow
Common Writing Mistakes for AXO
Information Buried in Paragraphs
Problem: Key facts hidden within long paragraphs Solution: Lead with facts, use bullet points for lists
Missing Context
Problem: Sentences that require surrounding text to understand Solution: Make each sentence contextually complete
Outdated Information
Problem: Content with old dates, deprecated methods, or broken links Solution: Regular content audits and update schedules
Poor Source Attribution
Problem: Factual claims without proper citations Solution: Link to primary sources and include publication dates
Measuring Content Success
Track how well your content performs with agents:
- Citation Frequency: How often your content appears in AI responses
- Content Freshness: How current and up-to-date your information remains
- User Engagement: Whether human readers find the structured content helpful
- Search Performance: How well the content performs in traditional and AI search
References
- Writing for the Web - U.S. General Services Administration
- Content Strategy Basics - A List Apart
- Technical Writing Best Practices - Google Developer Documentation
Master these writing techniques to create content that serves both human readers and AI agents effectively. Start with fact-first structure and clear headings, then gradually incorporate advanced formatting techniques.