Preserve content-collection types and static performance.

SEOForge detects Astro version, content collections or legacy content paths, schema-defined frontmatter, layouts, image pipelines, integrations and build output before adding an article.

Choose Growth Review GitHub Integration

Nothing publishes without approvalPaid product accessNo ranking guarantees

src/content/blog/post.md

schema: z.object(...)

getCollection("blog")

astro check && astro build ✓

Detection + content model

Read content.config schemas, collection loaders/frontmatter, route generation, Markdown/MDX settings and the layout component used by real posts.

Metadata, sitemap, images

Follow Astro head/SEO components, canonical site config, @astrojs/sitemap rules and local/remote image service conventions.

Deployment

Prepare a GitHub proposal, run astro check/build plus repository commands, inspect generated routes and wait for the site’s protected deploy flow.

Before → after

From loose Markdown to a schema-valid collection entry.

Before

Missing required frontmatter, raw remote image and no collection-aware internal links.

After

Validated fields, layout-compatible MDX/Markdown, optimized asset path, canonical metadata and generated static route.

Astro checks

Static output must stay predictable.

Validate collection schema and slug behavior
Reuse components permitted in MDX
Respect site/base/trailingSlash configuration
Verify sitemap inclusion and draft filtering
Inspect output without converting rendering mode

01
Detect Astro/content configuration
Evidence, owner and next state remain visible.
02
Draft schema-valid article and assets
Evidence, owner and next state remain visible.
03
Wire layout, links and metadata
Evidence, owner and next state remain visible.
04
Run astro check and build
Evidence, owner and next state remain visible.
05
Inspect generated route and sitemap
Evidence, owner and next state remain visible.
06
Code owner approves and deploys
Evidence, owner and next state remain visible.

Limitations

Custom loaders, SSR adapters, content APIs, private image services and environment-dependent integrations require test credentials/context. SEOForge does not change adapters or rendering mode implicitly.

Paid deployment · human authority

Add Astro content without weakening the static system.

Choose Growth, connect the repository and validate collection/build conventions during onboarding.

Choose Your Plan Book a Demo