Service Page Template
A structure for service pages with hero copy, benefits, FAQs, CTA fields, and SEO metadata.
Back to Templates
SEO Workflows
SEO Landing Page Template
A page structure for SEO-focused landing pages with slug, title, meta, sections, and CTA fields.
1
When to use this template
Use this structure when you publish SEO-focused landing pages as Pages — each one targeting a keyword theme with a clear slug, metadata, sections, and a single CTA.
A consistent structure keeps every landing page complete on SEO fields and easy to review before it ships.
2
Suggested fields
A starting set of fields for this structure. Adapt the labels, keys, and which fields are required to match your project.
Field labelField keyTypeStatus
SlugslugtextRequired
Hero HeadingheroHeadingtextRequired
SectionssectionslistRequired
CTA LabelctaLabeltextOptional
Featured ImagefeaturedImagemediaOptional
SEO TitleseoTitletextSEO
Meta DescriptionmetaDescriptiontextareaSEO
3
Required fields
The minimum fields every item should have before it can move to review.
Field labelField keyTypeStatus
SlugslugtextRequired
Hero HeadingheroHeadingtextRequired
SectionssectionslistRequired
4
Optional fields
Useful additions you can include per item, or leave out when they don't apply.
Field labelField keyTypeStatus
CTA LabelctaLabeltextOptional
Featured ImagefeaturedImagemediaOptional
5
SEO fields
Search metadata for the item. Keep titles and descriptions unique per item.
Field labelField keyTypeStatus
SEO TitleseoTitletextSEO
Meta DescriptionmetaDescriptiontextareaSEO
6
Example content item
sluggit-backed-cms
heroHeadingThe Git-backed content platform
ctaLabelStart Free Trial
seoTitleGit-backed CMS for agencies
metaDescriptionPublish to GitHub without giving clients access.
7
Markdown / MDX frontmatter example
How the structure looks as frontmatter in a Git-backed content file. Field keys map directly to your content type.
---
title: "The Git-backed content platform"
slug: "git-backed-cms"
seoTitle: "Git-backed CMS for agencies"
---
# Hero
Content body…8
Review & publishing checklist
Confirm these before publishing the item through GitHub. The trigger result is recorded in Publish Logs.
All required fields completedFill every field marked Required before moving to review.
Featured Image reference resolvesConfirm the media path exists in your repo.
SEO Title and Meta Description setWithin recommended length, unique per item.
Sent to Client Reviewers for approvalAdd review context so reviewers know what changed.
Scheduled or ready to publishConfirm date, time, and timezone if scheduling.
Deployment trigger profile configuredTrigger result is recorded in Publish Logs after publishing.
Turn templates into a publishing workflow.
Use Acrosite to create the structure, review content, schedule publishing, and keep output in GitHub.