GC.AI Blog Post Template (SEO/GEO Guidelines)

For GC.AI internal team (Caitlin, solutions attorneys, and anyone publishing blog content)

Created by Slam Media Lab | April 2026

Why this exists: Every blog post published on gc.ai affects search performance and AI citation visibility. A well-structured post ranks on Google AND gets cited by ChatGPT, Perplexity, and Gemini. A poorly structured post can cannibalize existing pages, dilute the site, or leave GC AI invisible to LLMs entirely. This template ensures every post helps on both fronts.

1. Before you write

These 3 checks take 5 minutes and prevent the most common SEO mistakes.

[ ] Check with Slam first. Ping Silvia or Kyle before writing. We may already be targeting that keyword, and two pages competing for the same term (keyword cannibalization) hurts both.
[ ] Get a target keyword. Either request one from Slam or identify one yourself:
1. Go to Google and type your topic. Look at "People also ask" and autocomplete suggestions.
2. Pick a specific phrase people actually search (e.g., "AI contract review for in-house counsel" not just "contract review").
3. Search that phrase on gc.ai to make sure no existing page already targets it.
[ ] Confirm index vs. no-index. Not every post should be indexed. Slam will/can advise.

2. Page structure and headings

Element	Rules	Example
H1	One per page. This is the blog post title. Include the target keyword naturally. Sentence case.	"How in-house counsel use AI for contract review"
H2	Major sections. Use 3-5 per post. Each should cover a distinct subtopic. Include keyword variations where natural.	"Why traditional contract review falls short"
H3	Subsections under H2s only. Use when an H2 needs to be broken into parts.	"Time costs" / "Accuracy gaps" / "Scalability limits"
Paragraphs	2-4 sentences max. One idea per paragraph.	--
Lists and tables	Use for steps, features, comparisons. These also improve AI citation rates (see Section 5).	--

Non-negotiable heading rules:

Never skip levels (no H1 → H3, no H2 → H4)
Never use headings for styling. Use bold instead.
Every H2/H3 should make sense as a standalone phrase (imagine it in a table of contents)

Word count:

Minimum: 1,200 words
Sweet spot: 1,500-2,500 words