Page types

There are 4 common page types. Each one is only a path convention.

  • There is no page type field. There is no template.
  • A page type is just the path you choose.
  • Your AI tool gets the same advice when it connects to the MCP server.

See also Writing good pages.

The 4 paths

PathUse it for
/alternatives/[name]People who look for an alternative to a product
/vs/[a]-vs-[b]A comparison of two products
/integrations/[name]How your product works with another one
/use-cases/[name]How a type of customer uses your product

/alternatives/[name]

For people who want to leave a product.

Good structure:

  1. description: the answer first. Name the best options in 2 to 3 sentences.
  2. table: your product and the others, side by side.
  3. heading + text: who should switch, who should stay.
  4. faq: real questions people ask.
  5. related: link to your /vs/ pages.

/vs/[a]-vs-[b]

For a head-to-head comparison.

Good structure:

  1. description: the verdict in 2 to 3 sentences.
  2. table: a fair comparison of features, prices and limits.
  3. heading + text: which one fits which case.
  4. faq.

Be honest about weak points. Use real facts only.

/integrations/[name]

For how your product works with another product.

Good structure:

  1. description: what the integration does.
  2. heading + text + list: the setup steps.
  3. table: what is supported and what is not.
  4. faq.

/use-cases/[name]

For how one type of customer uses your product.

Good structure:

  1. description: the problem of this person and how you solve it.
  2. heading + text: a real example.
  3. list: the features that matter for this person.
  4. faq.
  5. related: link to other use cases.

Good to know

  • Paths use lowercase letters, digits and dashes.
  • Each page still needs its own unique data. Do not reuse one text with a new name.
  • Every block is described in the Blocks reference.

Updated