# Learnitive SEO Content Plan

This is an editorial backlog, not an instruction to auto-publish generated filler. New articles should be genuinely useful, reviewed, and source-aligned before they are set to `published` and `noindex=0`.

## Positioning

Primary topical authority:

1. Markdown and visual writing
2. LaTeX and academic publishing
3. Research workflows, citations and bibliography
4. Local-first document ownership
5. AI-assisted writing with Local AI and BYOK
6. Learning/tutor workflows
7. Optional Code as a secondary capability, not the primary SEO identity

## Initial article cluster

| Priority | Working title | Search intent | Suggested CTA |
|---|---|---|---|
| P1 | Markdown vs WYSIWYG: Why Learnitive Gives You Both | writing/editor comparison | Start a Markdown project |
| P1 | Local-First Writing: Keep Your Markdown and LaTeX Files Under Your Control | local-first writing | Open Projects |
| P1 | A Practical LaTeX Research Paper Workflow | academic writing | Start a LaTeX project |
| P1 | BibTeX and Biber: A Modern Citation Workflow | bibliography/citations | Open citation tools |
| P1 | How to Organize Research Notes Before You Write | research workflow | Start research notes |
| P1 | Local AI vs BYOK AI for Writers and Researchers | AI privacy/provider choice | Configure AI |
| P2 | Writing a Thesis in LaTeX: Project Structure, Citations and PDF Review | thesis workflow | Use thesis template when validated |
| P2 | Markdown for Long-Form Writing: Notes, Articles and Books | Markdown writing | Start Markdown |
| P2 | Source-Grounded AI Writing: Using Research Context Without Losing Control | research AI | Explore Paper Memory |
| P2 | How Local-First Project Folders Improve Writing Portability | file ownership | Set up Projects Folder |
| P2 | From Research Notes to a Published PDF | end-to-end workflow | Start a project |
| P2 | When Writers Need Code: Keeping Programming Optional Inside a Writing Workspace | secondary Code intent | Expand Code in New Project |

## Existing-domain content strategy

Before launch, inspect old Learnitive blog posts with backlinks/traffic. For each article:

- rewrite and republish at the same slug if it still fits writing/research/local-first/AI;
- otherwise keep the explicit one-to-one redirect in `server/public-legacy-redirects.mjs`;
- use 410 only where the feature/integration is truly retired and no replacement is useful.

Do not bulk publish the inherited developer-first catalogue. Migration 64 and the post-import reconciliation intentionally keep legacy imported posts draft/noindex until editorial review.

## Template SEO gate

Do not target template SEO until there is real validated inventory. Recommended first validated set:

- Markdown Note
- Markdown Article
- Markdown Book / Long-form Draft
- Research Notes
- LaTeX Article
- Research Paper
- Technical Report
- Thesis
- Dissertation
- Literature Review
- Bibliography-enabled Paper
- Academic CV

A template becomes indexable only after trusted runtime validation reports `validationStatus: valid` and the template is not `noIndex`.

## Internal linking

Each published article should link naturally to:

- one relevant feature/use-case page;
- one documentation guide;
- one validated template or tool where applicable;
- `/pricing` only when Pro/BYOK is genuinely relevant.

Avoid repetitive exact-match anchors and avoid forcing Code/developer links into writer/research articles.

## Measurement after launch

Monitor:

- Search Console indexing/coverage after the URL migration;
- 404/410 crawl patterns;
- redirect hits for old URLs;
- branded vs non-branded impressions;
- query clusters for Markdown, LaTeX, citations, local-first and AI writing;
- template pages only after validated inventory is live.