SEO Playbook · Post types

SEO post types: pick the right page format

None starts from a blank document. Choose the reader job first, then use a repeatable specification for the structure, evidence, links, metadata, and next action.

amicited.com/seo-playbook/post-types
Question to specification
Understand a subject Guide or definition
Complete a task How-to
Choose an option Comparison
Take an action Money page
The topic supplies the subject. The reader's job supplies the post type.
Every specification fixes
Purpose One reader job
Structure Ordered elements
Connections Link contract
Quality Evidence + QA
A typed outline makes omissions visible before a page reaches review.
The governing idea

The wrong post type costs more than weak writing

Writing can be revised. A page built for the wrong job begins with the wrong promise, structure, evidence, and destination.

  • A page has a job — that job determines its structure; the topic only fills it.
  • Intent comes before keywords — one subject can need a definition, procedure, shortlist, comparison, or transaction page.
  • Structure makes quality repeatable — a typed outline prevents the verdict, proof, warning, or next step from quietly disappearing.
  • Predictability serves two systems — search engines map structure to result formats; answer engines extract bounded answers with context.
One topic, different jobs

A keyword does not tell you the page shape

A glossary entry and a how-to can share a subject but share almost nothing else. One fixes meaning; the other moves a reader to a verified outcome.

  • Definition — boundary, canonical wording, examples, related entities.
  • Procedure — prerequisites, ordered actions, checkpoints, recovery paths.
  • Decision — criteria, evidence, tradeoffs, verdict, next action.
DOMAIN SEMANTIC MAP · 340 PROMPTS CLUSTEREDyourdomain.comg2.comreddit.comcapterra.com
Every URL beneath each section, totalled
/blog/ 163u 179 #30.7
/templates/ 130u 1832 #12.2
/academy/ 61u 395 #29.0
Open a section to see the level below it — a whole-directory decline usually means one template, not many pages.
A grammar for the site

Post types turn URLs into a system

When every page declares its type, teams can audit required sections, change one pattern across a class, and find missing or duplicated jobs.

  • Scale production from a tested specification.
  • Audit the corpus for omissions, drift, and overlap.
  • Change safely by improving the type and its instances.
Start from zero

What is a post type?

It combines a job, a structure, and a fixed set of elements into a reusable instruction for one class of page.

Post type

A production contract. It says who the page serves, what it completes, which sections appear and in what order, what evidence is required, where links go, and how reviewers decide it is ready.

How-to guide” is a type because every instance needs prerequisites, steps, success checks, warnings, and troubleshooting even when the subject changes.

Blog post

A publishing container, not a job. A blog can hold news, opinion, a tutorial, research, or a comparison. Calling all of them blog posts hides their important structural differences.

Template

An implementation of a type. It may be a CMS layout, document skeleton, or prompt. Several templates can implement one type.

Content format

A medium or presentation choice. Article, video, calculator, and podcast describe delivery. A how-to remains a how-to when expressed as article and video together.

Site grammar

Why your website needs post types

With types, it has rules for answering intent, connecting pages, scaling production, and changing as a group.

Predictable intent coverage
A definition resolves meaning; a guide develops understanding; a comparison supports choice; a product page enables action. Separation stops one page trying to satisfy incompatible jobs.
Scalable production
The team debates structural rules once, then reuses them. Writers spend judgment on the subject and evidence instead of repeatedly inventing headings.
Corpus-level auditing
Type metadata makes omissions queryable: comparisons without verdicts, products with stale facts, how-tos without recovery steps, and definitions without incoming links.
One change, many pages
If 400 product pages need a delivery block, one type-level design and model change can update the class instead of creating 400 manual exceptions.

Predictable structure helps search engines recognize definitions, lists, procedures, products, and comparisons and map them to suitable result experiences. It helps AI answer engines differently: bounded sections and stable relationships are easier to retrieve without detaching a claim from its qualifier. The goal is not sameness. It is a legible job and evidence trail.

Intent before format

Informational vs transactional post types

Search intent is the job a person expects a result to complete. A useful model has four modes.

Informational
Serves a question. Success is comprehension or capability; monetization is indirect. Definitions, explainers, guides, tutorials, and research belong here.
Commercial investigation
Serves evaluation. Readers expect criteria, tradeoffs, options, and a justified recommendation. Comparisons, best-of pages, reviews, and alternatives occupy this revenue-relevant middle.
Transactional
Serves an action. Success is a purchase, booking, application, signup, download, or enquiry. Product, category, service, pricing, and use-case pages reduce action risk.
Navigational
Serves a known destination. The reader wants a brand, login, location, product, policy, or support resource. Identity and routing must be unmistakable.

Guess intent wrong and excellent prose still fails: a tutorial cannot replace the shortlist a buyer requested. Read intent from the current search results page. Record dominant result types, repeated headings, shopping or local features, whether results name one option or compare several, and the action offered above the fold. When results are mixed, choose one primary job and bridge deliberately to the adjacent job instead of blending both into a vague page.

Decision flow

How to choose a post type

Write the question in full, identify the outcome it implies, then choose the narrowest type that completes it.

1

What must be different when the reader leaves?

Understanding suggests a definition or guide; a completed procedure suggests a how-to; confidence between options suggests a decision type; an action suggests a commercial type.

2

How many options are in scope?

Many ranked candidates means Best X for Y. One incumbent and replacements means Alternatives to X. Two named choices means X versus Y.

3

Is the reader learning, narrowing, or buying?

A listicle makes an editorial selection. A category exposes navigable inventory. If filters, availability, variants, or purchase paths are essential, it is a category.

4

Can you supply the evidence?

A case study needs an approved customer record; a best-of page needs repeatable evaluation. Do not publish a type whose evidence contract cannot be met.

Best vs alternatives vs A/B
Best ranks candidates for a segment. Alternatives starts with switching. A/B resolves one named pair.
What is X vs X 101
What-is answers and bounds one question. A 101 guide teaches the parts and relationships needed to navigate a subject.
Category vs listicle
Categories organize inventory for browsing and action. Listicles justify an editorial selection and ordering.
The link graph

Internal linking between post types

A useful link has a source role, destination role, anchor, and placement. Count alone measures activity, not architecture.

Entity anchor
Meaningful uses of an ambiguous term point to one canonical definition. That page links to broader guidance and related entities without expanding into every procedure.
Pillar ↔ spoke
The pillar links to focused detail where it would interrupt the overview. Every spoke links back as a route to context. Direction serves navigation, not reciprocal-link quotas.
Information → commerce
A guide links to a category, use case, or product after giving enough context to act. A descriptive anchor at that moment is stronger than generic footer links.
Definition
Fix meaning
Guide / pillar
Build context and route
Decision / money page
Resolve choice and action

Structural links are defined by the type and appear on every valid instance: related entities, parent and child categories, pillar spokes, and breadcrumb routes. Editorial links are selected because a passage creates a useful next question. Lateral sibling links help only when siblings own distinct subproblems. If two pages answer the same intent and repeat the same answer, consolidation or clearer scope is required; links cannot repair cannibalization.

Reader readiness

Post types by buyer journey stage

Journey stage describes what the reader is ready to resolve, not how valuable the page is.

Awareness
What is this? Glossary, what-is, ultimate guide, beginner guide, research, trend explainer.
Consideration
How might I solve it? How-to, category, use case, checklist, calculator, implementation guide.
Decision
Which option? Best-of, alternatives, A/B, product, service, case study, pricing.
Retention
How do I succeed or recover? Help, troubleshooting, onboarding, integration, status, and policy.

A type may influence several stages, but it needs one primary stage so evidence and the call to action remain coherent. An awareness guide can introduce a commercial route without pretending the reader has chosen. A product page can answer objections without becoming a textbook.

Every detail page

What's in a post type specification

Each published type gives a writer, designer, developer, reviewer, or agent enough to implement without inventing operating rules.

1 · Anatomy
Required sections, order, purpose, inputs, and done signal.
2 · Elements
Reusable blocks and why each belongs.
3 · Frontmatter
Metadata, schema, evidence dates, ownership.
4 · Example
Concrete copy showing the rules in use.
5 · QA bar
Pass/fail checks for usefulness and accuracy.

The specification separates invariants from judgment. A comparison always needs like-for-like criteria and a verdict, but the market determines both. A how-to always needs a verified outcome and recovery paths, but the task determines the steps. Repeatability improves quality without making every page sound identical.

Catalogue · nine families

The nine post type families

Every published specification is linked. Counts are read from the content tree.

Comparison & decision 6
Definition & entity 6
Commercial money pages 9
Tools & interactive 4

Do the work for the reader rather than describe it.

Calculator Pages · Free Tool Pages · Quiz and Assessment Pages · Template Download Pages

Support & trust 5

Serve an existing customer, or prove you can be trusted.

About and Team Pages · Documentation Articles · FAQ Hub Pages · Policy and Legal Pages · Release Notes and Changelogs

AI-era & agent-facing 3
Flagship matrix

Post types by business type

Core means repeated economic need; useful means selective fit; rarely means publish only for a specific, evidenced job.

Priority is not a quality score. A product page is core for ecommerce because products are its transaction unit, but rarely appropriate for a local service firm without a product catalogue. The ranked businessTypes field on each specification supplies fit: first and second are core, third and fourth useful, later positions selective. Use the business-type playbooks to adapt evidence, conversion, and measurement.

Post type × business type

Current published specifications. Scroll horizontally on narrow screens.

Post typeEcommerceSaaSMarketplaceLocal serviceMedia / affiliateB2B services
Ultimate guideUsefulCoreUsefulRarelyCoreUseful
How-to guideCoreCoreUsefulUsefulRarelyRarely
Listicle guideCoreUsefulUsefulRarelyCoreRarely
Comparison A vs BCoreCoreUsefulRarelyRarelyUseful
Best X for YCoreCoreUsefulRarelyRarelyUseful
Alternatives to XUsefulCoreUsefulRarelyRarelyCore
Glossary termRarelyCoreUsefulRarelyUsefulCore
What is XUsefulCoreUsefulRarelyCoreCore
Product pageCoreUsefulCoreRarelyUsefulRarely
Category pageCoreUsefulCoreRarelyUsefulRarely
Use-case pageUsefulCoreUsefulRarelyRarelyCore
Case studyUsefulCoreRarelyUsefulRarelyCore
Types assemble elements

How post types use content elements

Elements are reusable units such as direct answers, tables, steps, warnings, sources, related content, FAQs, and calls to action.

The type decides which elements are required and where they appear. A warning is useful when a procedure contains a consequential, plausible mistake—not because every page needs visual variety. Improve an element's rules once while every post type preserves its own sequence and purpose.

Human writers and AI agents

Post types tell an AI agent what page to build

Hand an agent a keyword and it must first decide what kind of page the keyword deserves. That decision is the one it is least equipped to make, and the one a post type removes entirely.

The shape is the hard part, not the prose

An agent can write fluent paragraphs about almost anything. What it cannot reliably do is decide that this keyword needs a comparison with a segmented verdict rather than a definition page, or that a buying guide must place the selection criteria before the list.

Those are strategic choices with commercial consequences. A post type makes them in advance, once, so every page built from it inherits the decision instead of re-litigating it.

An ordered outline beats a word count

Each post type declares its sections, their order, their length bands, and which are required. The agent receives an outline it fills rather than a blank page it must architect.

That is also what makes output reviewable. A reviewer can check the page against the spec instead of forming a fresh opinion about what the page should have contained.

Sibling types stop the drift

Every post type page names what it is confusable with — best-X-for-Y against alternatives-to-X against A-vs-B. Those distinctions are exactly where an unguided agent produces three pages that compete with each other for the same query.

Naming the boundary in the specification is what prevents the cannibalization, before a single word is generated.

Required sections survive the deadline

A post type can mark a section as never omitted. A warning block on a risky procedure, a red-flags section, a sources list. An agent does not get tired or run short of time, so a required section stays required at page 400.

Combined with the pre-publish checklist, that turns a stylistic preference into an enforceable gate.

This is why every post type page here is written as a specification rather than as advice: anatomy tables, element order, frontmatter fields, and acceptance criteria. It is precise enough that a copywriter and an AI agent working from the same page produce the same structure.

FAQ

SEO post types FAQ

A named specification defining the reader job, structure, evidence, elements, metadata, links, and QA for a class of pages.

Start with the question and next action: ranked shortlist, switching, two-option decision, inventory browsing, learning, or doing.

Yes, if they perform distinct jobs with explicit scope, structure, and links.

No. Publish only types that support the model and can meet their evidence contract.

Start from the reader's question, not the keyword. Each specification names the types it is confusable with and states the difference. If two candidates would produce the same page, you only need one of them.

Use the system

Pick a post type and start building

Confirm intent, then use the specification's elements, evidence rules, links, frontmatter, example, and QA bar.

Explore the elements library

Choose the page job before anyone starts writing

Free check · 7-day trial · no credit card